creiht's profile - activity

2014-01-22 12:00:24 -0500 received badge  Nice Answer (source)
2014-01-02 01:12:26 -0500 received badge  Good Answer (source)
2013-11-01 20:56:40 -0500 received badge  Nice Answer (source)
2013-10-26 00:12:35 -0500 received badge  Nice Answer (source)
2013-08-26 18:11:05 -0500 received badge  Nice Answer (source)
2013-07-08 10:50:15 -0500 received badge  Good Answer (source)
2013-07-04 02:52:33 -0500 received badge  Nice Answer (source)
2013-06-27 23:03:43 -0500 answered a question Do we really need these many swift auths S3, TempAuth, SwiftAuth, cacheAuth.....?

Swift has been around for quite a while, and has a legacy of supporting several auth systems. The beauty of a plugable system, is that you only have to use the one that suits your needs.

TempAuth: This is an overly simple auth system used primarily for development and trying out swift for the first time. It is not at all meant to be used for a production deployment. It only supports the V1 auth contract and only works for swift.

Swauth: This is an auth system that runs on top of swift. It was built to be a more scalable auth system that could be used for certain production workloads. It was built before an official Openstack auth system (Keystone) existed. It only supports the V1 auth contract and only works for swift.

Swift3: The swift3 middleware and associated auth pieces are made availabe to povide an S3 compatible interface on top of Swift. Amazon's auth protocol is very different from Openstack's and thus requires a different set of auth middleware.

Keystone: Keystone is the official Openstack auth solution that works across products. It has many backends and auth schemes, but I wouldn't be the person that could adequately describe them all. This is the recommended solution to use if you are using swift along with the rest of the Openstack suite.

Custom: Last but not least, it is very easy to write custom auth middleware. While swift is an integral part of Openstack, it is also deployed in many places outside of Openstack, and those deployments have their own custom auth middleware that integrates swift into their current systems.

I hope this helps.

2013-06-27 22:50:41 -0500 answered a question couldn't connect to host after setup swift

That error usually means that either the services are not running, or you are using the wrong port. Swift services are usually started with something like:

swift-init main start

You can also check /etc/swift/proxy-server.conf to see what ip and port it is set to listen to.

TempAuth also only works with the v1.0 auth contract, so if you should use the following URL:


2013-06-19 11:12:16 -0500 answered a question what minimum configuration of the system is required for installing swift on a single node for testing purpose

There are very minimal requirements for setting up a test installation. We actually have instructions just for this here:

I do this regularly for dev and testing on VMs in the Rackspace Cloud.

2013-06-19 11:10:51 -0500 received badge  Critic (source)
2013-06-08 22:29:14 -0500 received badge  Good Answer (source)
2013-06-06 12:28:46 -0500 answered a question why is object storage used

Object Storage can be used for many things. Within Openstack, it can be used to store OS Images, and backups of Volumes. It is also used as a general service for end users. Both Amazon's S3 and Rackspace's Cloud Files (which is Openstack Swift) have proven useful for many use cases, including backups, media, streaming, documents, etc.

In short, it is most useful for when you need durable, long term storage of objects (usually files).

2013-05-28 14:24:21 -0500 answered a question Swift Proxy Account GET with 503 error

I'm not familiar with the Hastexo instructions, but the logs should reveal the issue. I would start taking a look at the proxy server logs to see why a 503 was returned (and possibly which account servers are having issues), and then look at the account server logs to figure out what specific error is causing the issue. Each request returns a transaction id, which is logged with each request to make it easier to search for log lines that deal with that specific request.

2013-05-01 18:11:51 -0500 received badge  Nice Answer (source)
2013-05-01 16:52:07 -0500 answered a question Wrong date and time on files (swift)

Since you are using the S3 compatibility layer for swift, there are some areas that can't report completely accurate information. For example container listings in swift don't store last-modified times for the objects, so bucket listings in the S3 requests don't have valid last-modified times.

2013-04-29 14:28:44 -0500 answered a question How to integrate Swift functionalities in Horizon Dashboard

There currently isn't a an api available for the ring data within swift. You could use the ring library directly, but would require that the horizon servers have access to the ring files, which would not be likely.

2013-04-29 14:20:30 -0500 answered a question Why do I see "Unable to find authentication token in headers" using swift with staticweb?

This appears to be a bug in the keystone authtoken middleware. There is no need to print that warning, since the container is public accessible.

2013-04-29 14:19:06 -0500 answered a question Do you recommend to have raid1 for the operating system on the nodes of a Swift cluster?

Yes, it is a good idea to provide redundancy to the root file system for the host OS as that will help reduce the number of host outages.

2013-04-12 08:54:43 -0500 answered a question How can I search for objects through metadata in Swift?

Swift currently doesn't support filtering container listings based on object metadata.

2013-04-02 20:02:24 -0500 received badge  Guru (source)
2013-04-02 20:02:24 -0500 received badge  Enlightened (source)
2013-04-01 17:28:18 -0500 received badge  Great Answer (source)
2013-04-01 09:21:32 -0500 received badge  Good Answer (source)
2013-04-01 05:03:57 -0500 received badge  Nice Answer (source)
2013-03-30 04:00:04 -0500 received badge  Teacher (source)
2013-03-30 01:04:23 -0500 answered a question Does openstack swift provide object locking?

When multiple writes occur to the same object in swift, the last write wins as determined by timestamp (very similarly as you describe for Eucalyptus).