s; (2) Support encrypting data incoming
from unchanged clients"
See: https://wiki.openstack.org/wiki/Swift/server-side-enc
We would like to invite feedback.
DH
Regards,
David Hadas,
Openstack Swift ATC, Architect, Master Inventor
IBM Research Labs, Haifa
Tel:Int+972-4-829-6104
Fax:
welcomed.
DH
Regards,
David Hadas,
Openstack Swift ATC, Architect, Master Inventor
IBM Research Labs, Haifa
Tel:Int+972-4-829-6104
Fax: Int+972-4-829-6112
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org
ay, but if we document it as a supported
> interface we'll have to be more careful about how we maintain it.What's
> motivating you to change what's there? Do you think keystone or swauth
> incur a measurable overhead from the callback based auth in the full
>
Hi,
Starting from 1.9, Swift has get_info() support allowing middleware to get
container and/or account information maintained by Swift.
Middleware can use get_info() on a container to retrieve the container
metadata.
In a similar way, middleware can use get_inf() on an account to retrieve
the acc
Hi,
In Portland, we discussed a somewhat related issue of having multiple
replication levels in one Swift cluster.
It may be that a provider would not wish to expose the use of EC or the
level of replication used. For example a provider may offer a predefined
set of services such as "Gold", "Silve
