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

[Scaling] #6428

Draft
wants to merge 4 commits into
base: develop
Choose a base branch
from
Draft

[Scaling] #6428

wants to merge 4 commits into from

Conversation

himani2411
Copy link
Contributor

Description of changes

  • Describe what you're changing and why you're doing these changes.

Tests

  • Describe the automated and/or manual tests executed to validate the patch.
  • Describe the added/modified tests.

References

  • Link to impacted open issues.
  • Link to related PRs in other packages (i.e. cookbook, node).
  • Link to documentation useful to understand the changes.

Checklist

  • Make sure you are pointing to the right branch.
  • If you're creating a patch for a branch other than develop add the branch name as prefix in the PR title (e.g. [release-3.6]).
  • Check all commits' messages are clear, describing what and why vs how.
  • Make sure to have added unit tests or integration tests to cover the new/modified code.
  • Check if documentation is impacted by this change.

Please review the guidelines for contributing and Pull Request Instructions.

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

@himani2411 himani2411 requested review from a team as code owners September 10, 2024 13:04
@himani2411 himani2411 marked this pull request as draft September 10, 2024 13:04
Himani Deshpande added 4 commits January 7, 2025 10:02
…gle file

* Refactoring ComputeFleet to download common_dna.json and compute resource specific dna

* giving PutObject access to headnode for s3-do-not-delete bucket

* rename common,headnode and compute dna json

* Adding compute-dna.json and downloading it from S3

* Adding stack arn in a write file

* Using config Version to download and upload json files specific to a cluster-config version so that we can rollback using the previous config version when needed

* Reduce cfn-init for compute fleet to just mention files.This file is never created but a change in config version in AWS::CloudFormation::Init signifies an update

* give listversionObject and ListBucketVersions access to compute node
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant