Fix AWS deployment issues, add Object support for AWS #18
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Fix issue #14 by adding the work-around as described in the vagrant-aws project to the Vagrantfiles.
Fix issue #15 which is in fact a vagrant-aws one by documenting a work-around.
Fix issue #16 by exempting the management network key configuration for the AWS deployment. On AWS there exists no management network.
Object deployment is supported by adding a VIP address to the single NIC on an AWS deployment and using that for the CES services as well as for the Spectrum Scale cluster network. As a pre-req the AWS deployment is now also based on CentOS 8 and Spectrum Scale Developer Edition 5.1.1.