[prev in list] [next in list] [prev in thread] [next in thread]
List: cisco-voip
Subject: Re: [cisco-voip] Changing vCPU Quantities
From: Evgeny Izetov <eizetov () gmail ! com>
Date: 2016-07-27 23:31:00
Message-ID: CAKLHLoV=ZhxGu=z3vtyL__MzMw=0EhibWU5DEAMGHCqZHgJb-g () mail ! gmail ! com
[Download RAW message or body]
[Attachment #2 (multipart/alternative)]
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 <ewellnitzvoip@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-voip@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
>
>
[Attachment #5 (text/html)]
<div dir="ltr">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.<div><br></div><div>-E</div></div><div \
class="gmail_extra"><br><div class="gmail_quote">On Wed, Jul 27, 2016 at 6:41 PM, \
Erick Wellnitz <span dir="ltr"><<a href="mailto:ewellnitzvoip@gmail.com" \
target="_blank">ewellnitzvoip@gmail.com</a>></span> wrote:<br><blockquote \
class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc \
solid;padding-left:1ex"><p dir="ltr">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.</p> <p dir="ltr">If I \
remember correctly this caveat is due to an application limitation and not the OS. \
<br></p><div><div class="h5"> <p dir="ltr">On Jul 27, 2016 11:17 AM, "Anthony \
Holloway" <<a href="mailto:avholloway%2Bcisco-voip@gmail.com" \
target="_blank">avholloway+cisco-voip@gmail.com</a>> wrote:<br> </p>
<blockquote><p dir="ltr">><br>
</p>
</blockquote>
</div></div><p dir="ltr"></p><div><div class="h5">> Hi Everyone,<br>
><br>
> I have been<a href="http://cisco-voip.markmail.org/thread/rrege2ktkvjha2oa" \
target="_blank"> telling people on this list</a> 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.<br> ><br>
> 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:<br> ><br>
<i>> "Adding vCPU is supported for all apps except Unity and Unity \
Connection, but requires VM to be shutdown first."</i><br> ><br>
> Source: <a href="http://docwiki.cisco.com/wiki/Unified_Communications_VMware_Requirements#Resize_Virtual_Machine" \
target="_blank">http://docwiki.cisco.com/wiki/Unified_Communications_VMware_Requirements#Resize_Virtual_Machine</a><br>
><br>
> 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?<br> ><br>
> To add to the confusion,<a \
href="https://supportforums.cisco.com/discussion/12111866/changing-cpu-core-count-esxi-unity-connection-86" \
target="_blank"> PDI is even stating</a> in certain cases online that changing the \
vCPU count without a DRS backup.restore is support.<br> ><br>
> So, what do you know about this? Is CUC really different from the other apps, \
or is this a case of bad documentation?<br> ><br>
> Thanks.<br>
><br></div></div>
> _______________________________________________<br>
> cisco-voip mailing list<br>
<a href="mailto:cisco-voip@puck.nether.net" target="_blank">> \
cisco-voip@puck.nether.net</a><br> <a \
href="https://puck.nether.net/mailman/listinfo/cisco-voip" target="_blank">> \
https://puck.nether.net/mailman/listinfo/cisco-voip</a><br> ><p></p>
<br>_______________________________________________<br>
cisco-voip mailing list<br>
<a href="mailto:cisco-voip@puck.nether.net">cisco-voip@puck.nether.net</a><br>
<a href="https://puck.nether.net/mailman/listinfo/cisco-voip" rel="noreferrer" \
target="_blank">https://puck.nether.net/mailman/listinfo/cisco-voip</a><br> \
<br></blockquote></div><br></div>
_______________________________________________
cisco-voip mailing list
cisco-voip@puck.nether.net
https://puck.nether.net/mailman/listinfo/cisco-voip
[prev in list] [next in list] [prev in thread] [next in thread]
Configure |
About |
News |
Add a list |
Sponsored by KoreLogic