Hi Andrija,
Thanks for the reply, basically what is happening is that on normal operation
the console vms is listening on ports 80 and 8080, however when I configure a
domain on consoleproxy.url.domain or consoleproxy.sslEnabled , for example:
console.kuasar.net, and I recreate the systemvm, I
Having the same IP for both old/new mgmt server will cause you issues -
don't do that.
Simply, introduce a 2nd mgmt server (don't touch the DB), make sure it
works, then stop/kill old mgmt.
Later, migrate DB to a new Mysql server (could be on that new mgmt2 server)
- and update the db.properties
Hi Vivek,
Storage QoS is applicable only to specific storage plugins that supports it
(e.g. ACS will pass min/max_IOPS to SolidFire plugin, so a LUN with those
min/max IOPS will be created on the SolidFire backend) - not sure if ANY
other storage vendor has this supported/implemented in ACS.
As f
All,
Thanks to Ivet, we have an advisory published here now:
https://blogs.apache.org/cloudstack/entry/cloudstack-advisory-on-spring4shell-cve
Regards.
From: Rohit Yadav
Sent: Wednesday, April 13, 2022 22:06
To: [email protected] ;
[email protected]
How do you try to " expose to Internet the ConsoleProxy VM using
LoadBalancer"? What is your Public IP vs SSVM vs LoadBalancer vs DNS setup?
When you initiate a Console access to a VM, your browser will connect to
the Public IP of the SSVM (if no SSL used) or to the DNS name based on the
Public IP
