-
Notifications
You must be signed in to change notification settings - Fork 42
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
feat(core): add FSx for Lustre integration #461
Conversation
9a653d6
to
82cfda6
Compare
82cfda6
to
1c52c41
Compare
1c52c41
to
814213c
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good for the most part, I just found the bash a little hard to follow at some points. Additional comments would help.
8.2|8.[1-9]*([0-9])) | ||
case $kernel_version in | ||
${rhel_kernel_versions[8.2]}) replace_ver="8.2";; | ||
${rhel_kernel_versions[8.3]} replace_ver="8.3";; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
There is no 8.3 in the array. I also see the RHEL article you linked to has an entry for 8.4, should we add that too? Will we need to manually update this whenever a new version of RHEL is released?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Ah yeah I missed that, added in an entry for 8.3. I went ahead and added an entry for 8.4, but we technically don't need it yet since it's the latest release, so we don't have to download a specific version yet.
Unfortunately, yes. We will need to manually update this whenever a new version of RHEL is released, assuming the FSx Lustre docs also update the instructions with the new kernel versions added.
if [[ -n "${replace_ver+x}" ]]; then | ||
sudo sed -i "s#8#${replace_ver}#" /etc/yum.repos.d/aws-fsx.repo | ||
fi |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Can you add a comment on what is going on here?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Sure, added a brief comment explaining what it does. For more context, the contents of aws-fsx.repo
will look something like this:
[aws-fsx]
name=AWS FSx Packages - $basearch
baseurl=https://fsx-lustre-client-repo.s3.amazonaws.com/el/8/$basearch/
enabled=1
gpgcheck=1
[aws-fsx-src]
name=AWS FSx Source
baseurl=https://fsx-lustre-client-repo.s3.amazonaws.com/el/8/SRPMS/
enabled=1
gpgcheck=1
This changes the baseurl
to point to a URL that has the right versions of the lustre client packages for the kernel we're on
814213c
to
2f470f1
Compare
11f82ca
to
09d74b6
Compare
09d74b6
to
eb9ec56
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
Notes
Repository
construct, as described here: https://docs.aws.amazon.com/fsx/latest/LustreGuide/install-lustre-client.htmlTesting
Repository
construct with an FSxL as the backing filesystem and ensured the repository files were owned by UID:GID=1000:1000 and that the RCS had access to themI deployed & tested:
I was not able to test the following:
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache-2.0 license