No problem, glad you got it sorted.
Regards,
Dag Sonstebo
Cloud Architect
ShapeBlue
On 24/07/2017, 10:30, "[email protected]"
wrote:
Hi Dag,
thanks again. We modified the DB last Friday and so far, this seems to
work. We could move VMs to the new Hosts and new VMs
Hi Dag,
thanks again. We modified the DB last Friday and so far, this seems to work. We
could move VMs to the new Hosts and new VMs are provisioned there as well.
Thank you again for your help.
Regards
Daniel
Am 21.07.17, 11:26 schrieb "Dag Sonstebo" :
Hi Daniel,
Resource calcul
Hi Daniel,
Resource calculation will not be greatly affected by 4Mhz – you should be safe
here. Keep in mind you are running with something like a 75% alert and 85%
disable threshold on your clusters (see cluster settings / global settings) –
and unless you increase the disable threshold to 100
Hi, Daniel.
You are completely right. Change your CPU Freq in DB is safe, an CPU
overprovisioning will help you.
2017-07-21 14:57 GMT+07:00 :
> Hi Dag, Hi Ivan,
>
> thanks to both of you for your reply. I would like to build on the
> question of my colleague Christian.
>
> Can you elaborate what
Hi Dag, Hi Ivan,
thanks to both of you for your reply. I would like to build on the question of
my colleague Christian.
Can you elaborate what would happen if we’d just change the service offering in
the database? From my understanding the main problem is, that during VM
creation the old and s
Hi Christian – my twopence worth – for the sake of 4Mhz the DB change should be
OK, it seems a bit overkill to create and replace all your service offerings
just to accommodate your new 1995MHz hardware.
Regards,
Dag Sonstebo
Cloud Architect
ShapeBlue
On 21/07/2017, 08:07, "Ivan Kudryavtsev" w
Hi. You just have to restart all affected VMs after offering change,
because running VMs only get new resources after restart.
It might be better to configure CPU overprovisioning in case you met system
limits.
21 июл. 2017 г. 13:59 пользователь
написал:
> Hi Ivan,
>
> thanks für die quick repl
Hi Ivan,
thanks für die quick reply.
Would you mind elaborating somewhat further on the potential implications. Can
I avoid unfaire resource provisioning by modifiying all existing service
offerings equally, e.g. changing the CPU Speed of all offering from 1999 to
1995 MHz?
Cheers,
Christian
Hi, you can actually do it thru DB, but it can lead to several
implications, like unfare resource provisioning. The better way is just
delete the offering, create the new with the same name and switch all VMs
either automatically or asking users.
Have a good day.
21 июл. 2017 г. 2:55 ДП пользоват
Dear all,
as there is no means to modify an existing Cloudstack Service Offering neither
via Cloudstack API nor with the GUI, I’m wondering what would happen if the CPU
speed of the service offerings is changed directly in the cloud DB (table
service_offering). Does this have any impact on exi
10 matches
Mail list logo
