Skip to content

Update feature_request.md #44

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.

Sign up for GitHub

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

Open
wants to merge 1 commit into
base: master
Choose a base branch
from
Open

Update feature_request.md #44

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
20 changes: 13 additions & 7 deletions .github/ISSUE_TEMPLATE/feature_request.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,18 +1,24 @@
---
name: Feature request
about: Suggest an idea for this project
name: Azure Node automatic resize on Allocation failure due to Azure region data centre capacity limit
about: It should be possible to specify a "failover" VM size to use when deployment of normal VM size allocation or deployment fails due to to Azure region data centre capacity limit and execute the resize of the deallocated VM node, then start the VM node.

---

#### Feature Request Description
- Is your feature request related to a problem? Please describe.
- A clear and concise description of what the problem is. Ex. I'm always frustrated when [...]
- Currently if an auto-scaling Azure node fails to deploy or spin up because of the normal Azure VM size allocation or deployment fails. e.g.
- 5/16/2024 9:29:00 AM The operation on the Azure node MyNode001 finished with status 'Failed', error details:
{"code":"AllocationFailed","message":"Allocation failed. We do not have sufficient capacity for the requested VM size in this region. Read more about improving
likelihood of allocation success at http://aka.ms/allocation-guidance"}

- Unfortunately, this error handling does not help users or applications that depend on the Azure VM node being seamlessly available.


#### Describe Preferred Solution
A clear and concise description of what you want to happen.
A HPC Powershell command (and maybe to GUI) to add an optional parameter to specify a "failover" VM size for a Azure node, and to use the parameter to resize the VM node if you get an error about VM size allocation or deployment failure due to to Azure region data centre capacity limit.

#### Describe Alternatives Considered
A clear and concise description of any alternative solutions or features you've considered.
An other option is to specify a "failover" HPC group to use instead, if VMs won't start in the primary HPC group because of this error.

#### Additional Context
Add any other context or screenshots about the feature request here.
![image](https://github.com/Azure/hpcpack/assets/170510965/d2987031-706d-4365-ae46-30d9a23e3cc9)