Page 2 of 3 FirstFirst 123 LastLast
Results 11 to 20 of 21

Thread: amanda 3.4.3 and Swift keystone

  1. #11
    Join Date
    Aug 2015
    Posts
    14

    Default

    Quote Originally Posted by martineau View Post
    We already support it!!!

    I already told you to correctly set S3_SERVICE_PATH and S3_HOST.
    Didn't see any answer before.
    What values do i need to fill? Why S3_HOST is not correct?

  2. #12

    Default

    hmmm s3 service path, very nice support anyway

  3. #13
    Join Date
    Aug 2015
    Posts
    14

    Default

    Did more tests, still got errors.
    Which values are required for S3_SERVICE_PATH and S3_HOST parameters?

  4. #14
    Join Date
    Nov 2005
    Location
    Canada
    Posts
    1,045

    Default

    Why do you believe someone know the answer? You are the one using OVH, you are the one that should know the answer!

    Did you search the OVH web site for the information? Or you are asking someone else to do it?
    Find the authentication server name, find how to get a token.

  5. #15
    Join Date
    Aug 2015
    Posts
    14

    Default

    Ok,
    keystone URL should be: https://auth.cloud.ovh.net/v2.0
    I can get a token, but it's 24h valid only.

    Which S3 parameters need to use?

  6. #16
    Join Date
    Nov 2005
    Location
    Canada
    Posts
    1,045

    Default

    The URL to get a token is probably https://auth.cloud.ovh.net/v2.0/tokens
    S3_HOST "auth.cloud.ovh.net"
    S3_SERVICE_PATH "/v2.0/tokens"

  7. #17
    Join Date
    Aug 2015
    Posts
    14

    Default

    Hello, thank you!
    Did test again. These actual parameters:

    tpchanger "chg-multi:s3:user1"
    device_property "S3_HOST" "auth.cloud.ovh.net"
    device-property "VERBOSE" "yes"
    device-property "REFRESH_TOKEN" "yes"
    device-property "S3_SSL" "yes"
    device_property "STORAGE_API" "SWIFT-2.0"
    device-property "S3_SERVICE_PATH" "/v2.0/tokens"
    device_property "USERNAME" "n7.............."
    device_property "PASSWORD" "vx........................."
    device_property "TENANT_ID" "6f........................................."
    device_property "TENANT_NAME" "16......................"
    amlabel debug log:

    mar apr 11 14:00:54.204222435 2017: pid 7727: thd-0x18b8a00: amlabel: pid 7727 ruid 63998 euid 63998 version 3.4.3: start at Tue Apr 11 14:00:54 2017
    mar apr 11 14:00:54.204328805 2017: pid 7727: thd-0x18b8a00: amlabel: Arguments: user1 User1 slot 1
    mar apr 11 14:00:54.204897418 2017: pid 7727: thd-0x18b8a00: amlabel: reading config file /etc/amanda/amanda.conf
    mar apr 11 14:00:54.205203872 2017: pid 7727: thd-0x18b8a00: amlabel: reading config file /etc/amanda/user1/amanda.conf
    mar apr 11 14:00:54.236879426 2017: pid 7727: thd-0x18b8a00: amlabel: pid 7727 ruid 63998 euid 63998 version 3.4.3: rename at Tue Apr 11 14:00:54 2017
    mar apr 11 14:00:54.254410600 2017: pid 7727: thd-0x18b8a00: amlabel: Using state file: /etc/amanda/user1/changer
    mar apr 11 14:00:54.254991428 2017: pid 7727: thd-0x18b8a00: amlabel: /usr/local/share/perl/5.18.2/Amanda/Label.pm:564:info:1000008 Reading label...
    mar apr 11 14:00:54.256646987 2017: pid 7727: thd-0x18b8a00: amlabel: S3 driver using bucket 'user1', prefix ''
    mar apr 11 14:00:54.256738259 2017: pid 7727: thd-0x18b8a00: amlabel: curl version: libcurl/7.35.0 OpenSSL/1.0.1f zlib/1.2.8 libidn/1.28 librtmp/2.3
    mar apr 11 14:00:54.256750407 2017: pid 7727: thd-0x18b8a00: amlabel: curl compiled for OPENSSL
    mar apr 11 14:00:54.257573710 2017: pid 7727: thd-0x18b8a00: amlabel: Create 1 threads
    mar apr 11 14:00:54.257928494 2017: pid 7727: thd-0x18b8a00: amlabel: Hostname was NOT found in DNS cache
    mar apr 11 14:00:54.262217341 2017: pid 7727: thd-0x18b8a00: amlabel: Trying 5.39.17.176...
    mar apr 11 14:00:54.264529446 2017: pid 7727: thd-0x18b8a00: amlabel: Connected to auth.cloud.ovh.net (5.39.17.176) port 443 (#0)
    mar apr 11 14:00:54.265032366 2017: pid 7727: thd-0x18b8a00: amlabel: successfully set certificate verify locations:
    mar apr 11 14:00:54.265046734 2017: pid 7727: thd-0x18b8a00: amlabel: CAfile: none
    mar apr 11 14:00:54.265055571 2017: pid 7727: thd-0x18b8a00: amlabel: CApath: /etc/ssl/certs
    mar apr 11 14:00:54.265226223 2017: pid 7727: thd-0x18b8a00: amlabel: SSLv3, TLS handshake, Client hello (1):
    mar apr 11 14:00:54.282687323 2017: pid 7727: thd-0x18b8a00: amlabel: SSLv3, TLS handshake, Server hello (2):
    mar apr 11 14:00:54.282765034 2017: pid 7727: thd-0x18b8a00: amlabel: SSLv3, TLS handshake, CERT (11):
    mar apr 11 14:00:54.283563928 2017: pid 7727: thd-0x18b8a00: amlabel: SSLv3, TLS handshake, Server key exchange (12):
    mar apr 11 14:00:54.285153131 2017: pid 7727: thd-0x18b8a00: amlabel: SSLv3, TLS handshake, Server finished (14):
    mar apr 11 14:00:54.285923599 2017: pid 7727: thd-0x18b8a00: amlabel: SSLv3, TLS handshake, Client key exchange (16):
    mar apr 11 14:00:54.285943540 2017: pid 7727: thd-0x18b8a00: amlabel: SSLv3, TLS change cipher, Client hello (1):
    mar apr 11 14:00:54.286057305 2017: pid 7727: thd-0x18b8a00: amlabel: SSLv3, TLS handshake, Finished (20):
    mar apr 11 14:00:54.288353893 2017: pid 7727: thd-0x18b8a00: amlabel: SSLv3, TLS change cipher, Client hello (1):
    mar apr 11 14:00:54.288462923 2017: pid 7727: thd-0x18b8a00: amlabel: SSLv3, TLS handshake, Finished (20):
    mar apr 11 14:00:54.288499990 2017: pid 7727: thd-0x18b8a00: amlabel: SSL connection using ECDHE-RSA-AES128-GCM-SHA256
    mar apr 11 14:00:54.288520767 2017: pid 7727: thd-0x18b8a00: amlabel: Server certificate:
    mar apr 11 14:00:54.288547105 2017: pid 7727: thd-0x18b8a00: amlabel: subject: OU=Domain Control Validated; CN=auth.cloud.ovh.net
    mar apr 11 14:00:54.288565836 2017: pid 7727: thd-0x18b8a00: amlabel: start date: 2015-04-20 09:14:39 GMT
    mar apr 11 14:00:54.288580315 2017: pid 7727: thd-0x18b8a00: amlabel: expire date: 2018-04-20 09:14:39 GMT
    mar apr 11 14:00:54.288641854 2017: pid 7727: thd-0x18b8a00: amlabel: subjectAltName: auth.cloud.ovh.net matched
    mar apr 11 14:00:54.288665647 2017: pid 7727: thd-0x18b8a00: amlabel: issuer: C=BE; O=GlobalSign nv-sa; CN=AlphaSSL CA - SHA256 - G2
    mar apr 11 14:00:54.288680561 2017: pid 7727: thd-0x18b8a00: amlabel: SSL certificate verify ok.
    mar apr 11 14:00:54.288763223 2017: pid 7727: thd-0x18b8a00: amlabel: Hdr Out: POST /v2.0/tokens HTTP/1.1
    mar apr 11 14:00:54.288809804 2017: pid 7727: thd-0x18b8a00: amlabel: Hdr Out: Host: auth.cloud.ovh.net
    mar apr 11 14:00:54.288820394 2017: pid 7727: thd-0x18b8a00: amlabel: Hdr Out: Accept: application/xml
    mar apr 11 14:00:54.288829927 2017: pid 7727: thd-0x18b8a00: amlabel: Hdr Out: Content-MD5: viEm+0EzygmFLwkcfBXB0Q==
    mar apr 11 14:00:54.288839324 2017: pid 7727: thd-0x18b8a00: amlabel: Hdr Out: Content-Length: 321
    mar apr 11 14:00:54.288848315 2017: pid 7727: thd-0x18b8a00: amlabel: Hdr Out: Content-Type: application/xml
    mar apr 11 14:00:54.288857354 2017: pid 7727: thd-0x18b8a00: amlabel: Hdr Out: Date: Tue, 11 Apr 2017 12:00:54 GMT
    mar apr 11 14:00:54.288866643 2017: pid 7727: thd-0x18b8a00: amlabel: Hdr Out:
    mar apr 11 14:00:54.288912939 2017: pid 7727: thd-0x18b8a00: amlabel: Data Out: <?xml version="1.0" encoding="UTF-8"?><auth xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns="http://docs.openstack.org/identity/api/v2.0" tenantId="6f................................." tenantName="16............................."><pass wordCredentials username="n7..............." password="vx........................."/></auth>
    mar apr 11 14:00:54.288927124 2017: pid 7727: thd-0x18b8a00: amlabel: We are completely uploaded and fine
    mar apr 11 14:00:54.301906427 2017: pid 7727: thd-0x18b8a00: amlabel: Hdr In: HTTP/1.1 400 Bad Request
    mar apr 11 14:00:54.302021256 2017: pid 7727: thd-0x18b8a00: amlabel: Hdr In: Vary: X-Auth-Token
    mar apr 11 14:00:54.302056473 2017: pid 7727: thd-0x18b8a00: amlabel: Hdr In: Content-Type: application/json
    mar apr 11 14:00:54.302189509 2017: pid 7727: thd-0x18b8a00: amlabel: Hdr In: Content-Length: 258
    mar apr 11 14:00:54.302214888 2017: pid 7727: thd-0x18b8a00: amlabel: Hdr In: Date: Tue, 11 Apr 2017 12:00:54 GMT
    mar apr 11 14:00:54.302369314 2017: pid 7727: thd-0x18b8a00: amlabel: Time Offset (remote - local) :0
    mar apr 11 14:00:54.302392053 2017: pid 7727: thd-0x18b8a00: amlabel: Hdr In:
    mar apr 11 14:00:54.302405205 2017: pid 7727: thd-0x18b8a00: amlabel: Data In: {"error": {"message": "Expecting to find application/json in Content-Type header - the server could not comply with the request since it is either malformed or otherwise incorrect. The client is assumed to be in error.", "code": 400, "title": "Bad Request"}}
    mar apr 11 14:00:54.302445233 2017: pid 7727: thd-0x18b8a00: amlabel: Connection #0 to host auth.cloud.ovh.net left intact
    mar apr 11 14:00:54.302466336 2017: pid 7727: thd-0x18b8a00: amlabel: data in 258: {"error": {"message": "Expecting to find application/json in Content-Type header - the server could not comply with the request since it is either malformed or otherwise incorrect. The client is assumed to be in error.", "code": 400, "title": "Bad Request"}}
    mar apr 11 14:00:54.302491678 2017: pid 7727: thd-0x18b8a00: amlabel: POST https://auth.cloud.ovh.net/v2.0/tokens failed with 400/None
    mar apr 11 14:00:54.302519950 2017: pid 7727: thd-0x18b8a00: amlabel: Device s3:user1 error = 's3_open2 failed: Unknown S3 error (None) (HTTP 400)'
    mar apr 11 14:00:54.302558571 2017: pid 7727: thd-0x18b8a00: amlabel: Device s3:user1 setting status flag(s): DEVICE_STATUS_DEVICE_ERROR
    mar apr 11 14:00:54.305000650 2017: pid 7727: thd-0x18b8a00: amlabel: /usr/local/share/perl/5.18.2/Amanda/Label.pm:654:error:1000012 Error reading volume label: s3_open2 failed: Unknown S3 error (None) (HTTP 400).
    mar apr 11 14:00:54.305411719 2017: pid 7727: thd-0x18b8a00: amlabel: /usr/local/share/perl/5.18.2/Amanda/Label.pm:853:error:1000034 Not writing label.
    Reading Doc https://www.ovh.com/us/g1872.managing_tokens this should be cURL method:
    $ curl -X POST $OS_AUTH_URL/tokens -H "Content-Type: application/json" -d '{"auth": {"tenantName": "'$OS_TENANT_NAME'", "passwordCredentials": {"username": "'$OS_USERNAME'", "password": "'$OS_PASSWORD'"}}}' | python -mjson.tool

    Maybe Content-Type: application/json required?

  8. #18
    Join Date
    Nov 2005
    Location
    Canada
    Posts
    1,045

    Default

    older keystone supported both xml and json.
    Amanda is using xml.
    xml support was removed in Juno !!!

    amanda must be enhanced to use json !!!

  9. #19
    Join Date
    Aug 2015
    Posts
    14

    Default

    Quote Originally Posted by martineau View Post
    older keystone supported both xml and json.
    Amanda is using xml.
    xml support was removed in Juno !!!

    amanda must be enhanced to use json !!!
    Ok
    I hope to see json content-type support in the next release

  10. #20
    Join Date
    Nov 2005
    Location
    Canada
    Posts
    1,045

    Default

    It's in 3.4.4

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •