We can have multiple VMs on a blade, for instance MANY guests on an esxi blade, or multiple LPARs on a p-blade. Each of these VMs don't consume a lot of CPU/Networking.
We have tested 100 VMs on a single blade successfully. Not that they were doing a lot, but were available. Reality is more like 5-20, depending on what they are doing. If I run a yum update all on all of those at the same time, it will flatline my blade. I would take ""only target one of these set of machines at a time" inside some sort of micro groups." if that was easy enough to do, but I'd even prefer "only target N of these set..." since the blades CAN take more than one yum update at a time. For instance, I have 16 cores on some of my blades, so I'd take 8 at a time and see how that goes. I really thought --randomize-hosts would have been easier. >>>Ericw On Monday, October 6, 2014 8:34:29 AM UTC-4, Michael DeHaan wrote: > > "Changing the setting to random and the fork value to 40 gives me a > reasonable chance that all 40 forks will be more or less equally > distributed. With more than 40 blades, it's a good bet only one fork per > blade" > > So this seems to imply you have more than one VM running on a given blade > (and not that you are talking about a blade chassis). > > -- You received this message because you are subscribed to the Google Groups "Ansible Project" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/ansible-project/ded64f71-ad07-4046-87f3-53af296c009b%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
