Hi
On 25 September 2013 04:15, Robert Collins robe...@robertcollins.netwrote:
E.g. for any node I should be able to ask:
- what failure domains is this in? [e.g. power-45, switch-23, ac-15,
az-3, region-1]
- what locality-of-reference features does this have? [e.g. switch-23,
az-3,
On 09/25/2013 05:15 AM, Robert Collins wrote:
One of the major things Tuskar does is model a datacenter - which is
very useful for error correlation, capacity planning and scheduling.
Long term I'd like this to be held somewhere where it is accessible
for schedulers and ceilometer etc. E.g.
@lists.openstack.org,
Date: 09/25/2013 10:37 AM
Subject:Re: [openstack-dev] [TripleO] Generalising racks :-
modelling a datacentre
On 09/25/2013 05:15 AM, Robert Collins wrote:
One of the major things Tuskar does is model a datacenter - which is
very useful for error correlation, capacity planning
On Sep 25, 2013, at 10:36 AM, Tomas Sedovic wrote:
On 09/25/2013 05:15 AM, Robert Collins wrote:
One of the major things Tuskar does is model a datacenter - which is
very useful for error correlation, capacity planning and scheduling.
Tuskar was designed for general infrastructure modeling
We're interested in topology support in order to support placement locality
(to optimize task placement in ensembles). Vish and I started talking about
what would be needed a few months ago, and came up with two approaches that
would work:
- modelling the system as a full graph (ie rich enough
