Yes Andrei, if you are using Advanced Networking you can leave the default
Xenserver install without running the Optional commands.
-Sanjeev
-Original Message-
From: Andrei Mikhailovsky [mailto:and...@arhont.com]
Sent: Wednesday, May 21, 2014 3:48 AM
To: users@cloudstack.apache.org
Subj
Hi Andrei,
As you said egress rules are not applicable for system vms. Since you are using
advanced networking you don’t have to add any iptable rules on the hypervisor.
Also make sure that on the hypervisor network is set to "openvswitch".
If you are trying to download the template from any of
So I got the console proxy working via HTTPS (by managing my own "
realhostip.com" DNS) last week and everything was working fine. Today, all
of a sudden, the console proxy stopped working again. The browser says,
"Connecting to 192-168-100-159.realhostip.com..." and eventually times out.
I trie
Okay, so what if I am using Advanced Networking?
I guess I can leave the default xenserver install without running the Optional
commands.
Andrei
- Original Message -
From: "Carlos Reátegui"
To: users@cloudstack.apache.org
Sent: Tuesday, 20 May, 2014 11:15:09 PM
Subject: Re: Xe
I believe OVS is only required for security groups in a basic network.
I am using a shared network without security groups in a basic zone with OVS.
No issues over the last 9 months. With a bridge backend you are limited to 2
NICs in a bond on the XenCenter UI, but with OVS you can use 4 NICs.
Andrei,
Those commands are still required for use in a CloudStack basic zone. If
you are using an advanced zone, then the default XenServer backend of ovs
is correct.
-tim
On Tue, May 20, 2014 at 5:29 PM, Andrei Mikhailovsky wrote:
> Hi guys,
>
> I am looking at the installation guide for Xen
Hi guys,
I am looking at the installation guide for XenServer hypervisor and got a
question about this section:
http://docs.cloudstack.apache.org/projects/cloudstack-installation/en/latest/hypervisor/xenserver.html#install-cloudstack-xenserver-support-package-csp
It states that the CSP func
Jayapal,
I would imagine this is the case for guest vms. However, I would think that the
default policy for system vms would allow dns resolution so that ssvm would be
able to download templates and isos from the internet. Is this not the case?
Where would I control the default egress rules
For user vms outgoing traffic to allow you need to add egress rules on network.
Thanks,
Jayapal
On 20-May-2014, at 8:38 PM, Andrei Mikhailovsky wrote:
> Hello guys,
>
> Having a bit of an issue with clean installs of ACS 4.2.1. The same issue is
> present on ACS 4.3. Both of the system vms
Hello guys,
Having a bit of an issue with clean installs of ACS 4.2.1. The same issue is
present on ACS 4.3. Both of the system vms are created and shown as Running.
When I login either to ssvm or cpvm I am able to ping internal and external dns
servers, as well as I can ping public hosts like
10 matches
Mail list logo