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

Update VM AMI #322

Open
1 task done
joshcoburn opened this issue Feb 4, 2025 · 0 comments · May be fixed by #323
Open
1 task done

Update VM AMI #322

joshcoburn opened this issue Feb 4, 2025 · 0 comments · May be fixed by #323
Labels
enhancement New feature or request new Added to an issue when it's new ;)

Comments

@joshcoburn
Copy link

Is your feature request related to a problem? Please describe.

The VMs currently use ubuntu-focal-20.04-amd64-server-* AMI. Ubuntu 20.04 is approaching EOL (April 2025).

Describe the solution you'd like

I have tested changing the VM AMI to ubuntu/images/hvm-ssd-gp3/ubuntu-noble-24.04-amd64-server-* and the deployment succeeded without issue.

Test Scenario:

  • deploy viya4-iac-aws with storage type standard and jump-server enabled
  • viya4-deployment baseline,viya,install with V4_CFG_MANAGE_STORAGE set to true

Results:

  • nfs_server disk successfully RAID 0 and export via NFS as expected
  • jumpserver mounted the filesystem at /viya-share and creates /viya-share/pvs dir as expected
  • proper folder structure is created during DAC viya,install step /viya-share/{namespace}/..
  • SAS Viya deploys and runs without issues

Describe alternatives you've considered

No response

Additional context

No response

Code of Conduct

  • I agree to follow this project's Code of Conduct
@joshcoburn joshcoburn added enhancement New feature or request new Added to an issue when it's new ;) labels Feb 4, 2025
@joshcoburn joshcoburn linked a pull request Feb 4, 2025 that will close this issue
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request new Added to an issue when it's new ;)
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant