This repository has been archived by the owner on Jul 22, 2024. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 26
Load SCBE backend on startup and implement the Activate Interface #21
Comments
shay-berman
added a commit
that referenced
this issue
May 11, 2017
- Load SCBE backend during Ubiquity initialization - Implemented Activate interface for the SCBE backend. - The activate triggers SCBE login and verify that the default service exist. - Adding SCBE config structure and load it during the initialization of the backend TODOs : - Add UT for the scbe.go - Add backend DB table during activation
shay-berman
added a commit
that referenced
this issue
May 18, 2017
…if one of them failed (instead of failing immediately)
Closed
@shay-berman , please take a look at this and let me know what do you think commit. The idea is, if a backend is specified in the activate call, we will activate just the specified backend. If the backend is not specified, we will activate all backend. |
shay-berman
added a commit
that referenced
this issue
Jun 3, 2017
…(so it will finish activation successfully).
shay-berman
added a commit
that referenced
this issue
Jun 3, 2017
shay-berman
added a commit
that referenced
this issue
Jun 3, 2017
shay-berman
added a commit
that referenced
this issue
Jun 22, 2017
- Load SCBE backend during Ubiquity initialization - Implemented Activate interface for the SCBE backend. - The activate triggers SCBE login and verify that the default service exist. - Adding SCBE config structure and load it during the initialization of the backend TODOs : - Add UT for the scbe.go - Add backend DB table during activation
shay-berman
added a commit
that referenced
this issue
Jun 22, 2017
…if one of them failed (instead of failing immediately)
shay-berman
added a commit
that referenced
this issue
Jun 22, 2017
…(so it will finish activation successfully).
shay-berman
added a commit
that referenced
this issue
Jun 22, 2017
shay-berman
added a commit
that referenced
this issue
Jun 22, 2017
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
How to test good path :
configure ubiquity server.conf as here with ScbeConfig tags. (make sure you have the directory mentioned in SpectrumScaleConfig.configPath, yes for now we took the config from this param)
Make sure u have SCBE up and running with one service delegated to the interface, and also configure this service as the default one.
Run ubiquity server and make sure you see "scbe init start" and "scbe init end" in the log file (by default /tmp/ubiquity.log)
Configure the ubiquity DVP(docker volume plugin) conf file (make sure you have the directory /etc/docker/plugins).
make sure to remove the [SpectrumNfsRemoteConfig] tag so it will use the SCBE backend and not SScNFS
Run the ubiquity DVP
Now simulate DVP activation by just trigger this command:
#> curl -X POST http://127.0.0.1:9000/Plugin.Activate
Verify : you should see in the log file that scbe activation line : "scbe remoteClient: Activate success"
The text was updated successfully, but these errors were encountered: