Hi Jean-Louis, thanks for the reply. I will try and report back.

Do you any info regarding supporting S3 on Openstack?

Thanks again.

On Wed, Jun 19, 2013 at 8:28 PM, Jean-Louis Martineau
<martin...@zmanda.com> wrote:
> Stratos,
>
> S3 compatibility of OpenStack is not tested, you must use the SWIFT-2.0 api.
> You must specify 3 of USERNAME. PASSWORD, TENANT_NAME or TENANT_ID.
>
> define changer openstack {
>    tpchanger
> "chg-multi:s3:xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx-backups/DailySet/slot-{01,02,03,04,05,06,07,08,09,10}"
>   device_property "S3_SUBDOMAIN"  "no"
>   device_property "S3_SSL" "ON"
>   device_property "S3_STORAGE_CLASS"      "STANDARD"
>
>   device-property "SSL_CA_INFO" "/etc/amanda/xxxxxxxxx.ca-bundle"
>   device-property "S3_HOST" "xxxxxxxxxxxxxxxxxxxxx:443"
>   device-property "VERBOSE" "YES"
>   device-property "S3_SERVICE_PATH" "/v2.0/tokens"
>   device_property "LEOM"  "on"
>   device-property "STORAGE_API" "SWIFT-2.0"
>   device_property "USERNAME"  "???"
>   device_property "PASSWORD"  "????"
>   device_property "TENANT_NAME"  "???"
>   device_property "TENANT_ID" "???"
>
> }
> tpchanger "openstack"
>
>
> Jean-Louis
>
>
> On 06/19/2013 12:56 PM, Stratos Zolotas wrote:
>>
>> Hi, it is my first post and just a few days with amanda.
>>
>> I'm trying to configure backups on Openstack's Swift using S3. I have
>> the following error:
>>
>> $ amlabel DailySet1 DailySet1-1 slot 1
>> Reading label...
>> Error reading volume label: While trying to read tapestart header:
>> Unknown S3 error (None) (HTTP 403)
>> Not writing label.
>>
>>
>> amlabel.log has this:
>>
>> Fri Jun 14 21:57:33 2013: thd-0x13b5400: amlabel: pid 23948 ruid 63998
>> euid 63998 version 3.3.3: start at Fri Jun 14 21:57:33 2013
>> Fri Jun 14 21:57:33 2013: thd-0x13b5400: amlabel: Arguments: DailySet1
>> DailySet1-1 slot 1
>> Fri Jun 14 21:57:33 2013: thd-0x13b5400: amlabel: pid 23948 ruid 63998
>> euid 63998 version 3.3.3: rename at Fri Jun 14 21:57:33 2013
>> Fri Jun 14 21:57:33 2013: thd-0x13b5400: amlabel: Using state file:
>> /etc/amanda/DailySet1/s3-statefile
>> Fri Jun 14 21:57:33 2013: thd-0x13b5400: amlabel: S3 driver using
>> bucket 'xxxxxxxxxxxxxxxxxxxxxxxx-backups', prefix 'DailySet1/slot-01'
>> Fri Jun 14 21:57:33 2013: thd-0x13b5400: amlabel: Create 1 threads
>> Fri Jun 14 21:57:35 2013: thd-0x13b5400: amlabel: GET
>>
>> https://xxxxxxxxxxxxxxx.com:443/xxxxxxxxxxxxxxxxxxxxxxxxxxx-backups/DailySet1%2Fslot-01special-tapestart
>> failed with 403/None
>> Fri Jun 14 21:57:35 2013: thd-0x13b5400: amlabel: Device
>> s3:xxxxxxxxxxxxxxxxxxxxxxxxxx-backups/DailySet1/slot-01 error = 'While
>> trying to read tapestart header: Unknown S3 error (None) (HTTP 403)'
>> Fri Jun 14 21:57:35 2013: thd-0x13b5400: amlabel: Device
>> s3:xxxxxxxxxxxxxxxxxxxxxxxxxxxxx-backups/DailySet1/slot-01 setting
>> status flag(s): DEVICE_STATUS_DEVICE_ERROR, and
>> DEVICE_STATUS_VOLUME_ERROR
>> Fri Jun 14 21:57:35 2013: thd-0x13b5400: amlabel: pid 23948 finish
>> time Fri Jun 14 21:57:35 2013
>>
>> My amanda.conf is:
>>
>> org "DailySet1"
>> infofile "/srv/amanda/state/curinfo"
>> logdir "/srv/amanda/state/log"
>> indexdir "/srv/amanda/state/index"
>> dumpuser "amandabackup"
>> mailto "operati...@xxxxxxxxxx.com"
>>
>> define tapetype S3 {
>>      comment "S3 Bucket"
>>      length 100 gigabytes # Bucket size
>> }
>>
>> device_property "S3_ACCESS_KEY" "xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx"    #
>> Your S3 Access Key
>> device_property "S3_SECRET_KEY" "xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx"    #
>> Your S3 Secret Key
>>
>> device_property "S3_SSL" "ON"                                        #
>> Curl needs to have S3 Certification Authority (Verisign today)
>>
>> # in its CA list. If connection fails, try setting this no NO
>> device-property "SSL_CA_INFO" "/etc/amanda/xxxxxxxxx.ca-bundle"
>> device-property "S3_HOST" "xxxxxxxxxxxxxxxxxxxxx:443"
>>
>> tpchanger
>> "chg-multi:s3:xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx-backups/DailySet1/slot-{01,02,03,04,05,06,07,08,09,10}"
>> # Number of tapes in your "tapecycle"
>> changerfile  "s3-statefile"
>> tapetype S3
>>
>> define dumptype simple-gnutar-remote {
>>      auth "ssh"
>>      ssh_keys "/etc/amanda/MyConfig/ssh-key"
>>      compress none
>>      program "GNUTAR"
>> }
>>
>> Using s3cmd and the same access/secret i have full permissions on the
>> S3 storage, so i cannot figure out why i'm getting a 403 error.
>>
>> Thank you.
>
>

Reply via email to