Open Stack

On 12 Sep 2013, at 11:51, Thierry Carrez <thierry at openstack.org> wrote:
> 
> That said I agree that reinventing HTTP POST storage sounds overkill and
> storing directly to swift would be a lot simpler.

+2

> Does Swift include
> complex access rules that we could leverage to implement the same kind
> of security that James described in his original post ?

There is HTTP referrer ACL support if this is what you are talking about.

> If not, would it make sense to actually add what we need to Swift itself ? (after all,
> it's, you know, an OpenStack project)

feel free to ask ;)

Chmouel.


>> [...]
>> *For example, depending on the size of the logs (and therefore the
>> job/worker) we could actually use javascript to serve up the swift
>> object with CORS further reducing the infrastructure requirement and
>> utilising the powerful CPU's and javascript engines we all have. I
>> already started doing that as a crude way to serve and add formatting to
>> my logs[1]. Basically javascript grabs a file and runs some regex for
>> highlighting. So my worker only reports
>> http://laughing-spice/logviewer/?q=http://worker/job/index.html where
>> the index.html contains links to logs like
>> http://laughing-spice/logviewer/?q=http://worker/job/mysqllog.txt etc.
>> [...]
> 
> Sidenote: I like that idea too, but I'm not sure how well that would
> work with our huge logs.
> 
> -- 
> Thierry Carrez (ttx)
> 
> _______________________________________________
> OpenStack-Infra mailing list
> OpenStack-Infra at lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-infra