Skip to content
This repository was archived by the owner on Jan 21, 2020. It is now read-only.

Mitigate the risk of creating a LOT of instances or deleting instances that we don't manage? #409

Open
dgageot opened this issue Feb 22, 2017 · 1 comment
Labels

Comments

@dgageot
Copy link
Contributor

dgageot commented Feb 22, 2017

If there is a bug in an Infrakit plugin or a misconfiguration in the templates, Infrakit could create too many instances or it could delete instances it doesn't manage or from another group.

How could be mitigate this kind of behaviour with some kind of cross cutting checks/quotas/protection/...?

@dgageot dgageot added the idea label Feb 22, 2017
@thebsdbox
Copy link
Contributor

It's certainly a concern, i've had occasions where the instances I'm provisioning haven't reported complete in time. This results in the group plugin attempting to deploy more instances, then having to delete the excess when they've all finished deploying.

To mitigate this, i've added in logic into the instance plugin so that it will keep track of what is "being" provisioned and allows the plugin to have more control over the actual state. Allowing the plugin to report back to the group plugin that whilst the instances aren't ready, they're being provisioned.

@chungers chungers added this to the v0.5 milestone Mar 3, 2017
@chungers chungers removed this from the v0.5 milestone Apr 9, 2017
chungers pushed a commit to chungers/infrakit that referenced this issue Sep 30, 2017
Fix ssh container, generate ssh host key
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Projects
None yet
Development

No branches or pull requests

3 participants