Skip to content
This repository has been archived by the owner on Jul 22, 2024. It is now read-only.

Load SCBE backend on startup and implement the Activate Interface #21

Closed
shay-berman opened this issue May 11, 2017 · 1 comment
Closed
Assignees
Milestone

Comments

@shay-berman
Copy link
Contributor

shay-berman commented May 11, 2017

  • Load the SCBE backend during the Ubiquity server start up
  • Add the relevant SCBE config parameters
  • Implement SCBE backend Activate interface. The Activate should login to SCBE and to validate that the default service is actually available.
  • Enable default values to few parameters : Port=8440, VerifySSL=true

How to test good path :

  1. 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.

  2. Run ubiquity server and make sure you see "scbe init start" and "scbe init end" in the log file (by default /tmp/ubiquity.log)

  3. 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

  4. Run the ubiquity DVP

  5. 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"

@shay-berman shay-berman self-assigned this May 11, 2017
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)
shay-berman added a commit that referenced this issue May 21, 2017
@midoblgsm
Copy link
Contributor

midoblgsm commented May 23, 2017

@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
@midoblgsm midoblgsm added this to the POC milestone Jun 7, 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
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
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

2 participants