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

When increasing a VM count from 1 to 2+, the first original VM should be added into the Availability Set #43

Closed
Badgerati opened this issue Jun 2, 2017 · 2 comments

Comments

@Badgerati
Copy link
Owner

When creating VMs, and the original count is 1, then only 1 VM is created. However, if later it's decided you want 2+ of that VM, and you set the count to say 3, then 2 more VMs are created, with a new Availability Set and Load Balancer; yet only the latter 2 are added to the AS/LB.

This issue is to fix a bug, so that the former first VM is also added into the AS/LB.

@Badgerati Badgerati added the bug label Jun 2, 2017
@Badgerati
Copy link
Owner Author

Badgerati commented Jun 4, 2017

Unfortunately due to a massive design flaw on Microsoft's part, you cannot a an already created VM into an newly created Availability Set...

Therefore, until this issue is resolved on their end, I've set it so that an AS is always created - even for one VM. At least this way you can increase the VM count without worrying too much.

I will at some point look into the removing of VMs for when you lower the count value.

@Badgerati Badgerati added this to the v0.6.0 milestone Jun 4, 2017
@Badgerati
Copy link
Owner Author

This also adds in the ability to change the size of VMs

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant