Closed rhuss closed 6 years ago
In development mode, it will persist, but usually this namespace would be deleted after successful completion.
Actually, I wonder now how to switch on the 'development mode' because I can't find that temporary namespace after provisioning. So I assume that I'm in 'production mode' (btw, using the getting_started guide with an Minishift setup)
Ah, found:
In order to use this feature, the Ansible Service Broker you are running must be configured to run in development mode. In the config file, set devbroker to true
However, the link was broken. Not sure whether I picked up the right one now.
Also it looks like the it's named dev_broker
, not devbroker
:
broker:
dev_broker: true
bootstrap_on_startup: true
refresh_interval: "600s"
launch_apb_on_bind: false
output_request: true
recovery: true
Interestingly, this flag is already set for me, but the temporary namespace didn't survive still.
When adding a DC to the provisioning, then the instruction reads:
Provision using the Web Console UI.
That's a bit brief. Does this mean I have to unprovision the original service first and the perform the same steps ? Or is there an way to upgrade the provisioned service directly.
Ah, found:
In order to use this feature, the Ansible Service Broker you are running must be configured to run in development mode. In the config file, set devbroker to true
However, the link was broken. Not sure whether I picked up the right one now.
Also it looks like the it's named dev_broker, not devbroker:
broker: dev_broker: true bootstrap_on_startup: true refresh_interval: "600s" launch_apb_on_bind: false output_request: true recovery: true
Interestingly, this flag is already set for me, but the temporary namespace didn't survive still.
Thanks for the contribution @rhuss!
To make the temporary namespace survive you can set these options in the broker config:
openshift:
// Always keep the namespace
keep_namespace: false
// Only keep on errors
keep_namespace_on_error: true
When adding a DC to the provisioning, then the instruction reads:
Provision using the Web Console UI.
That's a bit brief. Does this mean I have to unprovision the original service first and the perform the same steps ? Or is there an way to upgrade the provisioned service directly.
To provision the same service again, you'll need to deprovision the existing one and re provision the service with the new resources. You can make services updatable with the
updatable: true
flag in apb.yml.
I'm just making my way through the excellent getting_started guide, and I hope you don't mind if I collect some minor corrections and maybe questions I had in this pull request.