The problem over upload from local and the problem with the console proxy
were not a problem with cloudstack, was a problem of our network
configuration.
As I told before, we have public IPs and private IPs routed into the
backbone network, so used as "public" IPs also, both mixed.
The systemvm si
Finally found how to fix-it persistent-ly:
*1. Upgrade tomcat version*
Following the clue from that thread:
https://issues.apache.org/jira/browse/CLOUDSTACK-7907
- wget https://archive.apache.org/dist/tomcat/tomcat-6/v6.0.53/bin/
apache-tomcat-6.0.53.tar.gz
- tar --directory /opt -xzf
Hello all!
(I work with Marc)
Thanks Ilya:
About the Template upload from local-->
- I installed the lastest tomcat 6 stable release, but the problem was not
solved.
- I fixed the problem creating the /var/www/html/public dir at the SSVM and
it worked.
But this change will be lost when the SSV
Please see comments in-line
On 5/25/17 2:14 AM, Marc Poll Garcia wrote:
> Hi all,
>
> we have just upgraded our cloud environment based on Cloudstack 4.5.2 to
> 4.9.2 and we're expriencing some issues after this.
>
> Our setup is the following one:
>
> - 1 x cloudstack managment server
> - 1 x
Hello again,
About the Cloudstack version upgrade, we've build it from sources, to
create new self-compiled package 4.9.2 version with "noredit", in order to
achieve VMware hypervisor compatibility.
During that process, we changed some files, trying to get Vmxnet3 as
virtual NIC by default instea
Hi all,
we have just upgraded our cloud environment based on Cloudstack 4.5.2 to
4.9.2 and we're expriencing some issues after this.
Our setup is the following one:
- 1 x cloudstack managment server
- 1 x bbdd server cloudstack database on it
- 2 x Vmware Hipervisors (hosts)
I'm performing a li
