sodafoundation / api

SODA Terra Project API module : is an open source implementation of SODA API connecting storage to platforms like Kubernetes, OpenStack, and VMware
Apache License 2.0
828 stars 316 forks source link

opensds-dock cannot list pools in cinder driver #802

Open AllaeddineEL opened 5 years ago

AllaeddineEL commented 5 years ago

Is this a BUG REPORT or FEATURE REQUEST?:

Uncomment only one, leave it on its own line:

/kind bug /kind feature

What happened: I'm trying to configure dock to use cinder driver to provision block storage from OpenTelekomCloud provider, but the logs of dock show problem listing storage pools

I0531 13:16:09.665570      10 logs.go:75] [Info] LogFlushFrequency: 5s
E0531 13:16:12.666660      10 utils.go:111] Get etcd client:context deadline exceeded, retry 1 time(s)
I0531 13:16:14.692345      10 dock.go:110] Dock server initialized! Start listening on port:[::]:50050
I0531 13:16:14.972323      10 cinder.go:436] Starting list pools in cinder drivers.
E0531 13:16:15.011911      10 cinder.go:441] Cannot list storage pools:Resource not found
E0531 13:16:15.012043      10 discovery.go:168] Call driver to list pools failed:Resource not found
E0531 13:16:15.012140      10 dock.go:94] when calling capabilty report method:There is no pool can be found.

below is the driver config

authOptions:
      noAuth: false
      endpoint: "https://iam.eu-de.otc.t-systems.com/v3"
      domainName: "****"
      username: "****"
      password: "****"
      # Whether to encrypt the password. If enabled, the value of the password must be ciphertext.
      EnableEncrypted: false
      # Encryption and decryption tool. Default value is aes. The decryption tool can only decrypt the corresponding ciphertext.
      PwdEncrypter: "aes"
      tenantName: "****"
    pool:
      eu-de-01:
        storageType: block
        availabilityZone: eu-de-01
        extras:
          dataStorage:
            provisioningPolicy: Thin
            isSpaceEfficient: false
          ioConnectivity:
            accessProtocol: iscsi
            maxIOPS: 20000
            maxBWS: 320
          advanced:
            diskType: SSD
            latency: 3ms
      eu-de-02:
        storageType: block
        availabilityZone: eu-de-02
        extras:
          dataStorage:
            provisioningPolicy: Thin
            isSpaceEfficient: false
          ioConnectivity:
            accessProtocol: iscsi
            maxIOPS: 20000
            maxBWS: 320
          advanced:
            diskType: SSD
            latency: 3ms

What you expected to happen:

How to reproduce it (as minimally and precisely as possible):

Anything else we need to know?:

Environment:

skdwriting commented 5 years ago

@xxwjj @leonwanghui could you please check this issue?

skdwriting commented 5 years ago

@wisererik , could you please check the status of this ?

skdwriting commented 5 years ago

@AllaeddineEL , the pool has been configured already?