Skip to content
This repository has been archived by the owner on Sep 26, 2021. It is now read-only.

Provisioning stability #1331

Closed
6 of 7 tasks
ehazlett opened this issue Jun 8, 2015 · 1 comment
Closed
6 of 7 tasks

Provisioning stability #1331

ehazlett opened this issue Jun 8, 2015 · 1 comment

Comments

@ehazlett
Copy link
Contributor

ehazlett commented Jun 8, 2015

The creation process varies greatly from provider to provider. Issues like network partitions, provider API hiccups, etc can cause issues. Currently, Machine does not handle those very well. Errors are not always reported well and the user must remove whatever has been created and start over. This affects users using Machine directly as well as indirectly (i.e. Kitematic, Rancher, Machinery). We should improve the provision process to handle various types of failure and better report them when they occur.

Related:

@ehazlett ehazlett added this to the 0.4.0 milestone Jun 8, 2015
@ehazlett ehazlett modified the milestones: 0.3.0, 0.4.0 Jul 13, 2015
@nathanleclaire nathanleclaire modified the milestones: 0.5.0, 0.4.0 Jul 21, 2015
@nathanleclaire nathanleclaire removed this from the 0.5.0 milestone Oct 22, 2015
@dgageot
Copy link
Member

dgageot commented Nov 24, 2015

Closing. Since only #1330 is still opened

@dgageot dgageot closed this as completed Nov 24, 2015
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants