Hi,
In Basic Networking the preferred deployment method is exactly how you
describe, and is actually enforced by global settings.
Each POD should have a unique Guest IP Range and Reserved IP Range. I also
consider it best practice to have your Hosts on a completely different IP range.
The Ide
Hello,
I think it should be possible what you suggest. Have not tried it though.
Lucian
--
Sent from the Delta quadrant using Borg technology!
Nux!
www.nux.ro
- Original Message -
> From: "cs user"
> To: users@cloudstack.apache.org
> Sent: Tuesday, 10 March, 2015 21:25:58
> Subject: B
Hi All,
Apologies, second question in one evening :-)
If you have 1 zone in cloudstack configured for basic networking, and 2
pods. Are you able to configure these pods to have completely different
subnets on different vlans?
This is certainly possible to do in the webinterface, but will it
Hi,
It's impossible to know without looking at the changes in 4.3.1,
4.3.2. Your routers will be running old code, and will probably work,
but might not, e.g. if a router script is called with parameters that
don't exist in the version of the script that the router runs. If you
don't plan on mak
Hi,
I think more logs are needed, in DEBUG mode if you can.
Also agent logs and perhaps libvirt logs, just in case.
Lucian
--
Sent from the Delta quadrant using Borg technology!
Nux!
www.nux.ro
- Original Message -
> From: "Andrija Panic"
> To: d...@cloudstack.apache.org, users@clouds
Hi,
we are having issues from time to time with starting VR - while creating
VPC.
Here is the few lines from MGMT log:
2015-03-10 16:11:50,018 WARN [c.c.n.v.VpcManagerImpl]
(Job-Executor-27:ctx-84f4fba4 ctx-970acb35) Failed to start vpc [VPC
[621-VPC-delete] due to
com.cloud.exception.AgentUnav
Hi,
I was wondering is it possibe to update/replace the VR template somehow
without actually updating the ACS.
I'm running ACS 4.3.0, and having some issues with remote IP not being
really shown during Port Forwarding and Static NAT (VR also does SNAT
beside the DNAT)
I know question is a little
It could be a bug in that case. I guess you could file it on the tracker for
further investigation.
Regards,
Somesh
-Original Message-
From: Sonali Jadhav [mailto:son...@servercentralen.se]
Sent: Tuesday, March 10, 2015 8:21 AM
To: users@cloudstack.apache.org
Subject: RE: unable to remo
nice to hear
On Tue, Mar 10, 2015 at 6:41 PM, Daniel Kollmer
wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> On 03/10/2015 12:54 PM, Partha Goswami wrote:
> > Also try disabling VLAN tagging, just normally.
> >
>
> Actually I just found out what it was. I had created the cloudbr0 an
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 03/10/2015 12:54 PM, Partha Goswami wrote:
> Also try disabling VLAN tagging, just normally.
>
Actually I just found out what it was. I had created the cloudbr0 and
cloudbr1 interfaces by hand as I had read in the documentation here:
http://clouds
Hi somesh,
I just cross checked that, service_offering where id=14, is nothing but
"Custom" compute offering I created. That’s why ram_size value is set to NULL.
So basically I cant/don’t want to change value of ram_size service offering, Is
this bug?
/Sonali
-Original Message-
From
Hi Somesh,
I have very weird values in Service offering table,
mysql> select * from service_offering;
++--+---+--+-+-++---+--+-++--+-++
| id | cpu | spe
Also try disabling VLAN tagging, just normally.
On Tue, Mar 10, 2015 at 5:23 PM, Partha Goswami
wrote:
> see, exact problem I have faced with HyperV what i did, I created external
> switch which contains public Ip address and one internal switch which
> contain private, and need to make sure you
see, exact problem I have faced with HyperV what i did, I created external
switch which contains public Ip address and one internal switch which
contain private, and need to make sure you can access internet from both
switch/bridge. Now in ZONES > Physcal Network I have defind the switch name
and f
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hello all
I am wondering how to properly do the network setup for the system VM
because at this point it does not work.
A short description of my setup:
I have a network in which my hypervisor host primary nic exists
192.168.182.224/28
I also have a
We were not able to change the ip. CS blocked it. Some address was still in use.
We removed all the system VMs and changed it in the database. Not a nice way.
Ingo
-Ursprüngliche Nachricht-
Von: Sanjeev Neelarapu [mailto:sanjeev.neelar...@citrix.com]
Gesendet: Dienstag, 10. März 2015 06:
16 matches
Mail list logo