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

minor updates to proposal to clarify a few points #842

Merged
merged 2 commits into from Mar 21, 2018

Conversation

maleck13
Copy link
Contributor

Minor changes to ensure the proposal lines up with what will be done.

@openshift-ci-robot openshift-ci-robot added the size/S Denotes a PR that changes 10-29 lines, ignoring generated files. label Mar 20, 2018
Copy link
Contributor

@shawn-hurley shawn-hurley left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

NIT on the wording.


```

Under the hood, this APB module would take the key-value pair, and store it in a
ConfigMap named ```$POD_NAME```. This ConfigMap would live within the
temporary namespace ```$POD_NAMESPACE``` and be created by the broker before the APB pod was created.
temporary namespace ```$POD_NAMESPACE``` and be created by the Service Bundle when with the first call to ```asb_set_state```.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Service Bundle when with the first call to...

Service Bundle on the first call to... ?

After an action was successfully completed (ie the Service Bundle exited with a 0 exit code) and before the sandbox namespace was removed, the broker would copy the ConfigMap back to the broker's namespace and name it ```<ServiceInstanceID>-state```. If a ConfigMap with
that name was already present, the broker would update and append the values.
There should only ever be one ConfigMap per ServiceInstance. The ConfigMap would be removed from the broker's namespace
once the the deprovision action completed successfully.
once the the deprovision action was invoked for that ServiceInstance.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This is fine for now. I think that soon we will need to worry about subsequent deprovsion calls after a failed deprovsion. I think this is something that the service catalog is working on.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

ok good to know.

@maleck13
Copy link
Contributor Author

@shawn-hurley updated wording

Copy link
Contributor

@jmrodri jmrodri left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

ACK

@shawn-hurley shawn-hurley merged commit 8088db9 into openshift:master Mar 21, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
size/S Denotes a PR that changes 10-29 lines, ignoring generated files.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

5 participants