016 2:50 PM
To: [email protected]
Subject: SITE TO SITE VPN ERROR IN OUR ENVIRONMENT with CLOUDSTACK-4.3.1 AND
XENSERVER 6.2
Hi Team,
In our environment we are using cloudstack-4.3.1 and xenserver 6.2
We have created VPC router with SUPER-CIDR value as X.X.X.X/16.
After creating VPC r
: Venkat Boggarapu [mailto:[email protected]]
Sent: Wednesday, 01 June 2016 2:50 PM
To: [email protected]
Subject: SITE TO SITE VPN ERROR IN OUR ENVIRONMENT with CLOUDSTACK-4.3.1 AND
XENSERVER 6.2
Hi Team,
In our environment we are using cloudstack-4.3.1 and xenserver 6.2
We have
Hi Team,
In our environment we are using cloudstack-4.3.1 and xenserver 6.2
We have created VPC router with SUPER-CIDR value as X.X.X.X/16.
After creating VPC router, created a new TIER with X.X.X.X/24 with the same
network, gateway.
Finally we are unable to configure the IPSEC with the
Not sure what you mean by "not properly deployed." Could you give me a bit
more detail on that? Thanks!
On Thu, Nov 6, 2014 at 11:23 AM, Min Chen wrote:
> This is for VMs that are not properly deployed.
>
> Thanks
> -min
>
> On 11/6/14 10:12 AM, "Mike Tutkowski"
> wrote:
>
> >Hey everyone,
> >
This is for VMs that are not properly deployed.
Thanks
-min
On 11/6/14 10:12 AM, "Mike Tutkowski" wrote:
>Hey everyone,
>
>If a VM has been running on a host at some point, how can any of the
>volumes it's associated with have a null for pool_id?
>
>Thanks,
>Mike
>
>On Thu, Nov 6, 2014 at 11:08
Hey everyone,
If a VM has been running on a host at some point, how can any of the
volumes it's associated with have a null for pool_id?
Thanks,
Mike
On Thu, Nov 6, 2014 at 11:08 AM, Min Chen wrote:
> Yes, that is the workaround, just set pool_id to some dummy pool.
>
>
> On 11/6/14 10:01 AM,
Yes, that is the workaround, just set pool_id to some dummy pool.
On 11/6/14 10:01 AM, "Rafael Weingartner"
wrote:
>Thanks, After I looked at the CS source code. I worked around it by
>setting
>a pool_id in the database in the volume table.
>
>On Thu, Nov 6, 2014 at 3:58 PM, Min Chen wrote:
>
Thanks, After I looked at the CS source code. I worked around it by setting
a pool_id in the database in the volume table.
On Thu, Nov 6, 2014 at 3:58 PM, Min Chen wrote:
> This is a bug https://issues.apache.org/jira/browse/CLOUDSTACK-6934, which
> has been fixed in 4.5.0. The VM to be expunged
This is a bug https://issues.apache.org/jira/browse/CLOUDSTACK-6934, which
has been fixed in 4.5.0. The VM to be expunged did not allocate volume on
primary storage.
Thanks
-min
On 11/6/14 4:57 AM, "Rafael Weingartner"
wrote:
>HI,
>
>Have already someone seen a null pointer when deleting a VM?
HI,
Have already someone seen a null pointer when deleting a VM?
I have and environment running for a while with CS 4.3.1, and today I tried
to delete a VM that was in expunging state but it keeps getting an error:
2014-11-06 10:54:23,473 DEBUG [c.c.v.VirtualMachineManagerImpl]
(Job-Executor-37:
;>
>>
>
>Numbers don't really mean anything. CloudStack and CloudPlatform are
>different.
>
>CloudPlatform is based on CloudStack but the fact that CloudPlatform is
>at 4.3.1 does not mean that it is the same than what CloudStack 4.3.1
>will be.
>
>If you now the cl
apache.org
> Subject: Re: Cloudstack 4.3.1
>
>
> On Jul 22, 2014, at 9:41 AM, Len Bellemore
> wrote:
>
> > Hi Guys,
> >
> > Anyone know when the 4.3.1 release is due to come out? I'm really
> interested in the bugfix for listUsageRecords throwing a null point
Cheers Sebastien.
-Original Message-
From: Sebastien Goasguen [mailto:[email protected]]
Sent: 22 July 2014 19:55
To: [email protected]
Subject: Re: Cloudstack 4.3.1
On Jul 22, 2014, at 9:41 AM, Len Bellemore
wrote:
> Hi Guys,
>
> Anyone know when the 4.3.1 release
On Jul 22, 2014, at 9:41 AM, Len Bellemore
wrote:
> Hi Guys,
>
> Anyone know when the 4.3.1 release is due to come out? I'm really interested
> in the bugfix for listUsageRecords throwing a null pointer exception:
> https://issues.apache.org/jira/browse/CLOUDSTACK-6472
>
Len, I am going to
hing. CloudStack and CloudPlatform are different.
CloudPlatform is based on CloudStack but the fact that CloudPlatform is at
4.3.1 does not mean that it is the same than what CloudStack 4.3.1 will be.
If you now the cloudstack commit that fixes that Nexus1000v please tell me and
I will make sur
One comment on 4.3.1, if you are planning to deploy Nexus1000v in a zone
it currently fails on CloudPlatform 4.3.1 which from my understanding is
what Cloudstack will release soon.
On 7/22/14, 8:41 AM, "Len Bellemore"
wrote:
>Hi Guys,
>
>Anyone know when the 4.3.1 release is due to come out?
Hi Guys,
Anyone know when the 4.3.1 release is due to come out? I'm really interested
in the bugfix for listUsageRecords throwing a null pointer exception:
https://issues.apache.org/jira/browse/CLOUDSTACK-6472
Thanks
Len
IMPORTANT NOTICE. This electronic messag
Ilya,
You are addressing non developpers, so I am crossposting.
On Fri, Jun 6, 2014 at 4:25 AM, ilya musayev
wrote:
> Creating a separate thread to see what community thinks on next minor
> release of CloudStack 4.3.1
>
> There are more patches that need to be cherry-picked/backpo
18 matches
Mail list logo
