Open Stack

Hey andi and everyone,

Turns out that it's impossible to remove the X-Container-Sync-To:
header.  But it is possible to remove the X-Container-Sync-Key:
header, and that stops container sync.. it's not showing up in my logs
anymore.

Thanks!

On Fri, Jan 6, 2012 at 4:39 PM, andi abes <andi.abes at gmail.com> wrote:
> You could give up on the API, and just go hack the db's directly...
>
>
> On Fri, Jan 6, 2012 at 3:49 PM, Judd Maltin <openstack at newgoliath.com>
> wrote:
>>
>> I'm using swauth.  I authenticated as .super_admin (the tenant:account
>> didn't work last time) and tried this:
>>
>> curl -ik -H 'X-Auth-Token: AUTH_XXX' -XPOST -H 'X-Container-Sync-Key:'
>> -H 'X-Container-Sync-To:'
>> https://voxfiles.net/v1/AUTH_2c96271e-cf06-4eec-80a8-9441e3d1cf40/aaa
>>
>> HTTP/1.1 204 No Content
>> X-Container-Sync-Key: abcde
>> X-Container-Object-Count: 765515
>> X-Container-Sync-To: https://voxfiles.net/aaa
>> X-Container-Read: .r:*
>> X-Container-Bytes-Used: 121156834308
>> Accept-Ranges: bytes
>> Content-Length: 0
>> X-Trans-Id: tx17a2fc45c71941078ffb3b6467cf15f2
>> Date: Fri, 06 Jan 2012 20:43:27 GMT
>>
>> So, I try to remove the values:
>>
>> curl -ik -H 'X-Auth-Token: AUTH_XXX' -XPOST -H 'X-Container-Sync-Key:'
>> -H 'X-Container-Sync-To:'
>> https://voxfiles.net/v1/AUTH_2c96271e-cf06-4eec-80a8-9441e3d1cf40/aaa
>> HTTP/1.1 204 No Content
>> Content-Length: 0
>> Content-Type: text/html; charset=UTF-8
>> X-Trans-Id: tx6327f934a46b433f9883c1132c7bea2f
>> Date: Fri, 06 Jan 2012 20:44:23 GMT
>>
>> But the values are still there:
>>
>> curl -ik -H 'X-Auth-Token: AUTH_XXX' -XHEAD
>>
>> https://voxfiles.net/v1/AUTH_2c96271e-cf06-4eec-80a8-9441e3d1cf40/aaaHTTP/1.1
>> 204 No Content
>> X-Container-Sync-Key: abcde
>> X-Container-Object-Count: 765515
>> X-Container-Sync-To: https://voxfiles.net/aaa
>> X-Container-Read: .r:*
>> X-Container-Bytes-Used: 121156834308
>> Accept-Ranges: bytes
>> Content-Length: 0
>> X-Trans-Id: txe53ef78f72da45e5b0cce88a7991fea8
>> Date: Fri, 06 Jan 2012 20:44:26 GMT
>>
>> I'm going to try a few more permutations..
>>
>> Anyone out there?
>>
>> -judd
>>
>> On Wed, Jan 4, 2012 at 6:00 PM, andi abes <andi.abes at gmail.com> wrote:
>> > keep the sync-to, but kill the sync-key?
>> >
>> > On Wed, Jan 4, 2012 at 5:53 PM, Judd Maltin <openstack at newgoliath.com>
>> > wrote:
>> >>
>> >> Hey everyone!
>> >>
>> >> How can I shut down container sync for just this container?
>> >>
>> >>
>> >> root at proxy02-c01:/etc/swift# curl -i -XPOST -H 'x-auth-token:
>> >> AUTH_tk39cf30deaeb04ff4a83d02544bc8edb5' -H 'X-Container-Sync-To: ""'
>> >> -H 'X-Container-Sync-Key: secret'
>> >>
>> >> https://example.net:8080/v1/AUTH_2c96271e-cf06-4eec-80a8-9441e3d1cf40/aaa
>> >> HTTP/1.1 400 Bad Request
>> >> Content-Type: text/html; charset=UTF-8
>> >> Date: Wed, 04 Jan 2012 22:32:45 GMT
>> >> X-Trans-Id: tx3c142fabff79437ab382dc47eb67e2cb
>> >> Connection: close
>> >> Content-Length: 187
>> >>
>> >> 400 Bad Request
>> >>
>> >> The server could not comply with the request since it is either
>> >> malformed or otherwise incorrect.
>> >>
>> >>  Invalid scheme '' in X-Container-Sync-To, must be "http" or "https".
>> >> root at proxy02-c01:/etc/swift#
>> >>
>> >> Thanks!
>> >> -judd
>> >> _______________________________________________
>> >> Openstack-operators mailing list
>> >> Openstack-operators at lists.openstack.org
>> >> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators
>> >
>> >
>>
>>
>>
>> On Wed, Jan 4, 2012 at 5:53 PM, Judd Maltin <openstack at newgoliath.com>
>> wrote:
>> > Hey everyone!
>> >
>> > How can I shut down container sync for just this container?
>> >
>> >
>> > root at proxy02-c01:/etc/swift# curl -i -XPOST -H 'x-auth-token:
>> > AUTH_tk39cf30deaeb04ff4a83d02544bc8edb5' -H 'X-Container-Sync-To: ""'
>> > -H 'X-Container-Sync-Key: secret'
>> >
>> > https://example.net:8080/v1/AUTH_2c96271e-cf06-4eec-80a8-9441e3d1cf40/aaa
>> > HTTP/1.1 400 Bad Request
>> > Content-Type: text/html; charset=UTF-8
>> > Date: Wed, 04 Jan 2012 22:32:45 GMT
>> > X-Trans-Id: tx3c142fabff79437ab382dc47eb67e2cb
>> > Connection: close
>> > Content-Length: 187
>> >
>> > 400 Bad Request
>> >
>> > The server could not comply with the request since it is either
>> > malformed or otherwise incorrect.
>> >
>> >  Invalid scheme '' in X-Container-Sync-To, must be "http" or "https".
>> > root at proxy02-c01:/etc/swift#
>> >
>> > Thanks!
>> > -judd
>> _______________________________________________
>> Openstack-operators mailing list
>> Openstack-operators at lists.openstack.org
>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators
>
>