Open Stack

Thanks for the additional data-points on the granularity that we might need
to address scale (component rather than project level) along with
additional clarification on drivers (scale equivalent to resource being
available versus needing additional resources).  As mentioned earlier,
deployment options (types of infrastructure, services, and their
configuration) also play a vital part in the 'scale' of a service.  This is
a great starting point to the conversation.

On Mon, Sep 28, 2015 at 10:03 AM, Jonathan D. Proulx <jon at csail.mit.edu>
wrote:

> On Sun, Sep 27, 2015 at 06:15:58PM +0000, Kris G. Lindgren wrote:
>
> >For Example, we (Godaddy) use neutron for networking, however
> >we do not use tunneling of any type and we do not create virtual
> >routers or private networks and we do not rely on dhcp (we use
> >config-drive to set instance ip configuration).
>
> This is an important thing to consider.  Even at my <100 node scale I
> don't use neutron L3 so even if a site reports using a project it's
> hard to say what parts tehy are using or how they modefied it to mak
> eit 'scale' as this could include leaving large pieces that don't
> scale on the floor...
>
> -Jon
>
>
>
>


-- 
Thanks,
Shamail Tahir
t: @ShamailXD
tz: Eastern Time
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-operators/attachments/20150929/3150b858/attachment.html>