On 19 June 2013 16:01, Adrian Otto <[email protected]> wrote: > It's also useful for situations like rolling updates, for when a complete > redeployment is not practical, affordable, or desirable. Think of this as the > point of intersection between a configuration management system and the > orchestration system. Yes, you can accomplish this with stack-update, but > that could be rather awkward or impractical depending on the size of the > stack/assembly. Imagine something with 2000 nodes in it… perhaps a large > scale triple-o use case. Sometimes groupings are sufficient, and sometimes > they are not.
s/large scale/ medium scale/. With products like http://www8.hp.com/us/en/products/proliant-servers/product-detail.html?oid=5375897 you can get 900 cores, 4TB of memory, in 450 nodes... in a single rack. 5 racks gets you 2000 nodes; a row in a datacentre is substantially more than that :). -Rob -- Robert Collins <[email protected]> Distinguished Technologist HP Cloud Services _______________________________________________ OpenStack-dev mailing list [email protected] http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
