amanda 3.4.3 and Swift keystone

[kladiv]

Hello,
does S3 Device support Swift using Keystone authentication? (like OVH Object Storage) ?
I did some tests but authentication seems not work.

Thank you

Best,
Claudio

[paddy]

What version of Swift are you using? We have tested with Icehouse and Juno (not with recent releases) with keystone auth.

[kladiv]

Hi, i'm trying with OVH Object Storage.
Can you help me? Maybe i miss some S3 Device configurations?

Here some OVH useful links:
https://www.ovh.com/us/public-cloud/storage/object-storage/
https://www.ovh.com/us/g1921.creating_object_container
https://www.ovh.com/us/g1868.object_storage_cyberduck

PS. if useful i can create a user so you can check

Thank you

[martineau]

You posted no information about the failure, how do you believe someone can help you!!!!

What error do you get?
Post your configuration.
Add 'device-property "VERBOSE" "YES"' in the changer section.
retry an amcheck.
Post the resulting amcheck debug files.

[kladiv]

Hi,
some of my configs:

define changer "storageobject" {
  tpchanger "chg-multi:s3:user1"
  device_property "S3_HOST" "storage.bhs3.cloud.ovh.net:443"
  device_property "S3_BUCKET_LOCATION" "GRA3"
  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" "/v1/auth_6f................................................"
#  device_property "SWIFT_ACCOUNT_ID" "16......................................."
#  device_property "SWIFT_ACCESS_KEY" "vx........................................"
  device_property "USERNAME" "n7............................"
  device_property "PASSWORD" "vx..........................................."
  device_property "TENANT_ID" "6f................................................"
  device_property "TENANT_NAME" "16......................."
}
define storage "default" {
  autolabel "$c_$3s" empty volume-error
  autoflush all
  runtapes 1
  tapedev "storageobject"
  tapetype "container"
}
define tapetype container {
    comment "Container Size"
    length 1024 gigabytes
}

Log: amlabel.20170328015028.debug

mar mar 28 01:50:28.782008267 2017: pid 31712: thd-0xf13a00: amlabel: pid 31712 ruid 63998 euid 63998 version 3.4.3: start at Tue Mar 28 01:50:28 2017
mar mar 28 01:50:28.782167323 2017: pid 31712: thd-0xf13a00: amlabel: Arguments: user1 User1 slot 1
mar mar 28 01:50:28.782789427 2017: pid 31712: thd-0xf13a00: amlabel: reading config file /etc/amanda/amanda.conf
mar mar 28 01:50:28.784846092 2017: pid 31712: thd-0xf13a00: amlabel: reading config file /etc/amanda/user1/amanda.conf
mar mar 28 01:50:28.877412328 2017: pid 31712: thd-0xf13a00: amlabel: pid 31712 ruid 63998 euid 63998 version 3.4.3: rename at Tue Mar 28 01:50:28 2017
mar mar 28 01:50:28.910084745 2017: pid 31712: thd-0xf13a00: amlabel: Using state file: /etc/amanda/user1/changer
mar mar 28 01:50:28.910691097 2017: pid 31712: thd-0xf13a00: amlabel: /usr/local/share/perl/5.18.2/Amanda/Label.pm:564:info:1000008 Reading label...
mar mar 28 01:50:28.919057862 2017: pid 31712: thd-0xf13a00: amlabel: S3 driver using bucket 'user1', prefix ''
mar mar 28 01:50:28.919166447 2017: pid 31712: thd-0xf13a00: amlabel: curl version: libcurl/7.35.0 OpenSSL/1.0.1f zlib/1.2.8 libidn/1.28 librtmp/2.3
mar mar 28 01:50:28.919176040 2017: pid 31712: thd-0xf13a00: amlabel: curl compiled for OPENSSL
mar mar 28 01:50:28.920094703 2017: pid 31712: thd-0xf13a00: amlabel: Create 1 threads
mar mar 28 01:50:28.920389611 2017: pid 31712: thd-0xf13a00: amlabel: Hostname was NOT found in DNS cache
mar mar 28 01:50:28.980989256 2017: pid 31712: thd-0xf13a00: amlabel:   Trying 158.69.169.81...
mar mar 28 01:50:29.061817525 2017: pid 31712: thd-0xf13a00: amlabel: Connected to storage.bhs3.cloud.ovh.net (158.69.169.81) port 443 (#0)
mar mar 28 01:50:29.062627014 2017: pid 31712: thd-0xf13a00: amlabel: successfully set certificate verify locations:
mar mar 28 01:50:29.062652534 2017: pid 31712: thd-0xf13a00: amlabel:   CAfile: none
mar mar 28 01:50:29.062666020 2017: pid 31712: thd-0xf13a00: amlabel:   CApath: /etc/ssl/certs
mar mar 28 01:50:29.062968357 2017: pid 31712: thd-0xf13a00: amlabel: SSLv3, TLS handshake, Client hello (1):
mar mar 28 01:50:29.155004212 2017: pid 31712: thd-0xf13a00: amlabel: SSLv3, TLS handshake, Server hello (2):
mar mar 28 01:50:29.155108225 2017: pid 31712: thd-0xf13a00: amlabel: SSLv3, TLS handshake, CERT (11):
mar mar 28 01:50:29.160722815 2017: pid 31712: thd-0xf13a00: amlabel: SSLv3, TLS handshake, Server key exchange (12):
mar mar 28 01:50:29.161195884 2017: pid 31712: thd-0xf13a00: amlabel: SSLv3, TLS handshake, Server finished (14):
mar mar 28 01:50:29.161937278 2017: pid 31712: thd-0xf13a00: amlabel: SSLv3, TLS handshake, Client key exchange (16):
mar mar 28 01:50:29.161955942 2017: pid 31712: thd-0xf13a00: amlabel: SSLv3, TLS change cipher, Client hello (1):
mar mar 28 01:50:29.162099696 2017: pid 31712: thd-0xf13a00: amlabel: SSLv3, TLS handshake, Finished (20):
mar mar 28 01:50:29.242967314 2017: pid 31712: thd-0xf13a00: amlabel: SSLv3, TLS change cipher, Client hello (1):
mar mar 28 01:50:29.243150236 2017: pid 31712: thd-0xf13a00: amlabel: SSLv3, TLS handshake, Finished (20):
mar mar 28 01:50:29.243218153 2017: pid 31712: thd-0xf13a00: amlabel: SSL connection using ECDHE-RSA-AES128-GCM-SHA256
mar mar 28 01:50:29.243243653 2017: pid 31712: thd-0xf13a00: amlabel: Server certificate:
mar mar 28 01:50:29.243283676 2017: pid 31712: thd-0xf13a00: amlabel:    subject: OU=Domain Control Validated; OU=PositiveSSL Multi-Domain; CN=storage.bhs1.cloud.ovh.net
mar mar 28 01:50:29.243307112 2017: pid 31712: thd-0xf13a00: amlabel:    start date: 2017-02-14 00:00:00 GMT
mar mar 28 01:50:29.243326569 2017: pid 31712: thd-0xf13a00: amlabel:    expire date: 2018-02-14 23:59:59 GMT
mar mar 28 01:50:29.243414080 2017: pid 31712: thd-0xf13a00: amlabel:    subjectAltName: storage.bhs3.cloud.ovh.net matched
mar mar 28 01:50:29.243450875 2017: pid 31712: thd-0xf13a00: amlabel:    issuer: C=GB; ST=Greater Manchester; L=Salford; O=COMODO CA Limited; CN=COMODO RSA Domain Validation Secure Server CA
mar mar 28 01:50:29.243469897 2017: pid 31712: thd-0xf13a00: amlabel:    SSL certificate verify ok.
mar mar 28 01:50:29.243614038 2017: pid 31712: thd-0xf13a00: amlabel: Hdr Out: POST /v1/auth_6f949adcbcf4461696ec48fe65b647d1 HTTP/1.1
mar mar 28 01:50:29.243628814 2017: pid 31712: thd-0xf13a00: amlabel: Hdr Out: Host: storage.bhs3.cloud.ovh.net
mar mar 28 01:50:29.243640364 2017: pid 31712: thd-0xf13a00: amlabel: Hdr Out: Accept: application/xml
mar mar 28 01:50:29.243652059 2017: pid 31712: thd-0xf13a00: amlabel: Hdr Out: Content-MD5: viEm+0EzygmFLwkcfBXB0Q==
mar mar 28 01:50:29.243663273 2017: pid 31712: thd-0xf13a00: amlabel: Hdr Out: Content-Length: 321
mar mar 28 01:50:29.243675902 2017: pid 31712: thd-0xf13a00: amlabel: Hdr Out: Content-Type: application/xml
mar mar 28 01:50:29.243686487 2017: pid 31712: thd-0xf13a00: amlabel: Hdr Out: Date: Mon, 27 Mar 2017 23:50:28 GMT
mar mar 28 01:50:29.243698894 2017: pid 31712: thd-0xf13a00: amlabel: Hdr Out:
mar mar 28 01:50:29.243767245 2017: pid 31712: thd-0xf13a00: 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................"><passwordCredentials username="n7................" password="vx....................................................."/></auth>
mar mar 28 01:50:29.243806296 2017: pid 31712: thd-0xf13a00: amlabel: We are completely uploaded and fine
mar mar 28 01:50:29.373209875 2017: pid 31712: thd-0xf13a00: amlabel: Hdr In: HTTP/1.1 401 Unauthorized
mar mar 28 01:50:29.373324908 2017: pid 31712: thd-0xf13a00: amlabel: Hdr In: Content-Length: 131
mar mar 28 01:50:29.373365589 2017: pid 31712: thd-0xf13a00: amlabel: Hdr In: Content-Type: text/html; charset=UTF-8
mar mar 28 01:50:29.373498121 2017: pid 31712: thd-0xf13a00: amlabel: Hdr In: Www-Authenticate: Swift realm="auth_6f.........................................."
mar mar 28 01:50:29.373523636 2017: pid 31712: thd-0xf13a00: amlabel: Hdr In: WWW-Authenticate: Keystone uri='http://127.0.0.1:5008'
mar mar 28 01:50:29.373542112 2017: pid 31712: thd-0xf13a00: amlabel: Hdr In: X-Trans-Id: tx23ac386bbd8e4584b6a47-0058d9a545
mar mar 28 01:50:29.373608605 2017: pid 31712: thd-0xf13a00: amlabel: Hdr In: X-Openstack-Request-Id: tx23ac386bbd8e4584b6a47-0058d9a545
mar mar 28 01:50:29.373629930 2017: pid 31712: thd-0xf13a00: amlabel: Hdr In: Date: Mon, 27 Mar 2017 23:50:29 GMT
mar mar 28 01:50:29.373715810 2017: pid 31712: thd-0xf13a00: amlabel: Time Offset (remote - local) :0
mar mar 28 01:50:29.373732310 2017: pid 31712: thd-0xf13a00: amlabel: Hdr In:
mar mar 28 01:50:29.373743618 2017: pid 31712: thd-0xf13a00: amlabel: Data In: <html><h1>Unauthorized</h1><p>This server could not verify that you are authorized to access the document you requested.</p></html>
mar mar 28 01:50:29.373815261 2017: pid 31712: thd-0xf13a00: amlabel: Connection #0 to host storage.bhs3.cloud.ovh.net left intact
mar mar 28 01:50:29.373835286 2017: pid 31712: thd-0xf13a00: amlabel: data in 131: <html><h1>Unauthorized</h1><p>This server could not verify that you are authorized to access the document you requested.</p></html>
mar mar 28 01:50:29.373861871 2017: pid 31712: thd-0xf13a00: amlabel: POST https://storage.bhs3.cloud.ovh.net:443/v1/auth_6f.................................... failed with 401/None
mar mar 28 01:50:29.373893028 2017: pid 31712: thd-0xf13a00: amlabel: Device s3:user1 error = 's3_open2 failed: Unknown S3 error (None) (HTTP 401)'
mar mar 28 01:50:29.373930656 2017: pid 31712: thd-0xf13a00: amlabel: Device s3:user1 setting status flag(s): DEVICE_STATUS_DEVICE_ERROR
mar mar 28 01:50:29.376719397 2017: pid 31712: thd-0xf13a00: 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 401).
mar mar 28 01:50:29.377122024 2017: pid 31712: thd-0xf13a00: amlabel: /usr/local/share/perl/5.18.2/Amanda/Label.pm:853:error:1000034 Not writing label.

[lillyjacob]

I think that S3 device support swift . GET service, DELETE bucket, PUT bucket, DELETE object etc are the service provide by it. I f you have any doubt you will get detailed theory about it from dissertation writing services

[martineau]

The S3_SERVICE_PATH should probably be "/v2.0/tokens"

[martineau]

And S3_HOST must be the hostname of the authentication server.

[kladiv]

Hi, any news? Can you support me?

[martineau]

We already support it!!!

I already told you to correctly set S3_SERVICE_PATH and S3_HOST.