Identity Controller Boilerplate #50
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
At present, when provisioning in a cluster, it blocks a long time waiting for OpenStack to do what it needs to do. This has a knock on effect for UX in that said delay is visible in the UI and CLI tools. This lays down the groundwork to make this asychronous so we don't hold up uer interaction, but we do cluster provisioning. This is a template also for phyiscal network provisioning that takes even longer, and causes request timeouts that need to be avoided.
This makes identity provisioning asynchronous and idempotent, which is far more fault tolerant and can hide long provisioning times better at the front end - the cost just disappears into cluster provisioning. Two very important things to note, first the openstack configuration should live in a separate CR, second we've now got a problem in that the kubernetes service needs to poll for provisioning, which cannot be done without a token...
spjmurray
force-pushed
the
identity_controller
branch
6 times, most recently
from
314fec8
to
f86b65e
Compare
As previously commented, having openstack state in a controlled resource is a bad idea. This separates stuff out so that a shadow record is created to hold state, so the managed resource is not required to be updated.
spjmurray
force-pushed
the
identity_controller
branch
from
f86b65e
to
6362e1e
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
At present, when provisioning in a cluster, it blocks a long time waiting for OpenStack to do what it needs to do. This has a knock on effect for UX in that said delay is visible in the UI and CLI tools. This lays down the groundwork to make this asychronous so we don't hold up uer interaction, but we do cluster provisioning. This is a template also for phyiscal network provisioning that takes even longer, and causes request timeouts that need to be avoided.