On Thu, Sep 08, 2016 at 03:52:42PM +0000, Kris G. Lindgren wrote: > I completely agree about the general rule of thumb. I am only looking at the > team that specifically supports openstack. For us frontend support for > public clouds is handled by another team/org all together.
in my previous job the ratio was 1 openstack guy / 300 prod hv and ~ 50 non prod hypervisors (non prod clouds). we had 5 different clouds, 2 biggest clouds shared keystone and glance (same dc, different buildings, almost lan latency). the biggest cloud had 2 regions (different connectivity on same dc building) a different team took care of the underlying hw, live migrations (when necessary but usually escalated to the openstack team) and install the computes running a single salt stack command. another team developed a in-house horizon replacement that job definitively burned me, i'd say that the sweet spot is about 1 person every 200 hv, but if your regions are very similar and you have control of the whole stack (i didn't) i think 1 person every 300 hv is doable we only used nova, neutron (provider networks), glance and keystone. -- 1AE0 322E B8F7 4717 BDEA BF1D 44BB 1BA7 9F6C 6333 keybase: https://keybase.io/gfa _______________________________________________ OpenStack-operators mailing list OpenStack-operators@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators