Hello Mike,
It works pretty well if we use separate network for Management and VMware
hosts. If you can have a look on the logs you will get to know the reason of
not getting deployed. Make sure that you have proper routing between you
Management network and POD network (VMware hosts) .
Vive
Hi,
I'm running into trouble with deploying the SystemVMs. I think it's because
the "Management Network" is different IP/VLAN than what my ESXi vmkernel port
group is.
I have re-read the installation doc and if this is in fact a requirement than
it stinks...
In the vSwitch properties dialog
Had a similar issue. Try to disable firewalld.
-Original Message-
From: Quốc Bảo Võ
Sent: Wednesday, July 1, 2020 12:56 PM
To: users@cloudstack.apache.org
Subject: Can someone help me with this
Hi, I'm just getting started with Apache Cloudstack. I have installed it step
by step at th
Andrija,
I appreciate you sharing your thoughts on this. I'm getting my ducks in a row
on the XenServer side (for the upgrade) & I'll give the plan a go.
I'll report in afterwards, wish me luck!
Thanks,
David
David Merrill
Senior Systems Engineer,
Managed and Private/Hybrid Cloud Services
OTEL
Hi, I'm just getting started with Apache Cloudstack. I have installed it step
by step at this site:
http://docs.cloudstack.apache.org/en/4.14.0.0/quickinstallationguide/qig.html.
But when I run it on the browser, it can't connect to UI interface and I don't
know how to fix it
+1 with adding documentation.
And maybe we should also refactor the port check logic and error message.
Currently, code just tries to connect the socket for the port and if it fails
that with the message,
Detected that another management node with the same IP XX.XX.XX.XX is already
running, ple
+1, agree with Rohit
On 2020-07-01 08:34, Rohit Yadav wrote:
I think we can document in our CloudStack qig/release/install notes to
say users must disable cockpit on CentOS8. Here are my 2paisas;
* Most users using CentOS (7/8) won't use a single-host specific
management tool/UI such as coc
Besides updating the documentation, I'm tempted to even explicitly add a
command that would disable the cockpit service on boot and stop it (and
echo the message that we've disabled it...)- as part of the
cloudstack-setup-management or similar.
Otherwise, novice users will certainly stumble soone
I think we can document in our CloudStack qig/release/install notes to say
users must disable cockpit on CentOS8. Here are my 2paisas;
* Most users using CentOS (7/8) won't use a single-host specific management
tool/UI such as cockpit; they would probably use some fleet management software
Hi Vincent,
We'll need to investigate deeper as it could be a regression/backend issue, can
you log your issue here:
https://github.com/apache/cloudstack/issues
Thanks.
Regards.
From: Vincent Hermes
Sent: Monday, June 29, 2020 15:50
To: users@cloudstack.apach
10 matches
Mail list logo
