Thanks Suneel,
Its working after applying the changes.
Thanks and regards,
Tejas
From: Venkata Suneel Babu Mallela
To: cloudusersusers
Date: 10/07/2014 11:23 AM
Subject:Re: Zenoss Monitoring with Cloudstack 4.3
Try with ”http://xx.xx.xx.xx:8080”.
Thank you,
Suneel Mall
It looks like not enough CPU?
// Hosts's actual total CPU: 38384 and CPU after applying
overprovisioning: 307072
What is the Old and New Service Offering?
On Tue, Oct 7, 2014 at 10:31 AM, Amir Abbasi wrote:
> Hi,
>
> After changing the Service Offering I can't start the VM:
>
>
> 2014-10-07
Hosts are OK!
I've downgraded the comoute offering from "4*2.4GHZ and 8G RAM" to "2*2.4GHZ
and 4G RAM".
- Original Message -
From: "James Scott"
To:
Sent: Tuesday, October 07, 2014 12:10 PM
Subject: Re: Unable to create a deployment for VM
It looks like not enough CPU?
// Host
Hello,
Get VPN to work.
1. Network Offering should be with enabled "Conserve mode".
2. VPN can be enabled only in source-nat IP.
I suggest to update documentation and include "Conserve mode"
requirement in Network Offering for VPN service.
On 10/06/2014 07:38 PM, Mārtiņš Jakubovičs wrote:
H
I run 4.3.1 and my environments are very large. I plan to stay on it for
a while.
Depending on the size if you go into 100 hypervisors, you may want to
tweak java heap.
On 10/6/14, 1:11 AM, AnilKumar Lakineni wrote:
Hi All,
Good Morning,
I want to deploy ACS for production. So can anybody
I have a new CloudStack install and am facing the situation where guests
can't access the public network. It assigns the public IP and gateway
correctly, but when I ssh into the VM, it can only reach the private side.
Specifically, I'm testing the secondary storage VM. Sorry for the config
dump b
One other oddity - output from "route -n" on the secondary storage VM.
It's creating routes for the public mgmt service that route back through
the private VLAN gateway.
route -n
Kernel IP routing table
Destination Gateway Genmask Flags Metric RefUse
Iface
0.0.0.0 X
If I understand network configuration correctly - you are not using VLANs in
reality, because you don't add tag to your traffic. The same for Cisco switch -
it just listens on different ports. Traffic for public/private is untagged. I
am not 100% sure, because my set-up is based on single NIC, b
