Open Stack

On Fri, Oct 9, 2015 at 3:00 AM, Christian Berendt <christian at berendt.io>
wrote:

> On 10/08/2015 10:26 PM, Bernd Bausch wrote:
> > Isn't font awesome distinct from bootstrap?
> > In other words, I think we need both. Plus Jquery.
>
> We need all of them, yes. I want to know if we want to provide those
> files on our own (static CSS/JS files) or if we want to use CDNs where
> possible.
>
> E.g. at the moment we provide the Bootstrap and jQuery files on our own.
> Should we use a CDN here?
>

Looking at the Network performance tab in Google Chrome Web Dev tools, I
don't see that font-awesome css files are coming across the network. For
sure there are js and css files coming from /static. This view is on both
the landing page and a page using our theme.

Using CDN will always give you better performance. But I'm not sure how
much gain we need. To figure out if we want CDN we'd have to do performance
tests from different locations. Not sure it's worth the effort. And should
that effort instead be spent on the Object Storage solution for serving
static content that the infra team has in test now? I think at this point
I'm asking more questions than I'm answering, ha.

So the cleanup to remove files we're not using is certainly valuable. But
the CDN vs static is part of a larger question of moving to Object Storage
with the Infra team instead of Cloud Sites infrastructure from Rackspace.

Anne



>
> Christian.
>
> --
> Christian Berendt
> Cloud Solution Architect
> Mail: berendt at b1-systems.de
>
> B1 Systems GmbH
> Osterfeldstraße 7 / 85088 Vohburg / http://www.b1-systems.de
> GF: Ralph Dehner / Unternehmenssitz: Vohburg / AG: Ingolstadt,HRB 3537
>
> _______________________________________________
> OpenStack-docs mailing list
> OpenStack-docs at lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-docs
>



-- 
Anne Gentle
Rackspace
Principal Engineer
www.justwriteclick.com
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-docs/attachments/20151009/9de28c80/attachment.html>