The latest ova readme files for CUC do have a one-liner about 1 cpu restrictions for Unified Messaging under the 1000 users template information, but yeah, it's pretty easy to overlook.
-E On Wed, Jul 27, 2016 at 6:41 PM, Erick Wellnitz <ewellnitzv...@gmail.com> wrote: > Based on that caveat, I'd think that's the best bet. Same with running > out of storage space in anything other than the common partition. Too bad > PCD doesn't do CUC migrations. > > If I remember correctly this caveat is due to an application limitation > and not the OS. > > On Jul 27, 2016 11:17 AM, "Anthony Holloway" < > avholloway+cisco-v...@gmail.com> wrote: > > > > > > Hi Everyone, > > > > I have been telling people on this list > <http://cisco-voip.markmail.org/thread/rrege2ktkvjha2oa> for a while now, > and for that matter, in person too, that you can just shutdown the VM and > modify the vCPU count per VM and then power it back on. > > > > In fact, I know I've done this a half a dozen times in the past. > However, for CUC, a colleague of mine just uncovered the following bullet > point: > > > *> "Adding vCPU is supported for all apps except Unity and Unity > Connection, but requires VM to be shutdown first."* > > > > Source: > http://docwiki.cisco.com/wiki/Unified_Communications_VMware_Requirements#Resize_Virtual_Machine > > > > So, with CUC being the exception, it would stand to reason that CUC > requires a DRS backup, new OVA deployment, then DRS restore to change the > vCPU count, correct? > > > > To add to the confusion, PDI is even stating > <https://supportforums.cisco.com/discussion/12111866/changing-cpu-core-count-esxi-unity-connection-86> > in certain cases online that changing the vCPU count without a DRS > backup.restore is support. > > > > So, what do you know about this? Is CUC really different from the other > apps, or is this a case of bad documentation? > > > > Thanks. > > > > _______________________________________________ > > cisco-voip mailing list > > cisco-voip@puck.nether.net <cisco-voip@puck.nether.net> > > https://puck.nether.net/mailman/listinfo/cisco-voip > <https://puck.nether.net/mailman/listinfo/cisco-voip> > > > > > _______________________________________________ > cisco-voip mailing list > cisco-voip@puck.nether.net > https://puck.nether.net/mailman/listinfo/cisco-voip > >
_______________________________________________ cisco-voip mailing list cisco-voip@puck.nether.net https://puck.nether.net/mailman/listinfo/cisco-voip