Hi CloudStack Users and Developers,
we’re currently implementing a new CloudStack environment based on 4.8.0.1
(System VM Template is 4.6) with XenServer 6.5 SP1 and all the latest
updates.
So far everything works as expected we only have an issue regarding the
stability of Site-to-Site VPNs with
GitHub user nvazquez opened a pull request:
https://github.com/apache/cloudstack/pull/1613
CLOUDSTACK-9436: Release network resources on expunge command
JIRA TICKET: https://issues.apache.org/jira/browse/CLOUDSTACK-9436
Improvement for #1594
Due to error on `test/i
Will,
I am inquiring as to the status of 4.9.0 RC2. Are there issues we can help
resolve in order to get it out? If not, do you have an ETA on when it will be
cut?
Thanks,
-John
[email protected]
www.shapeblue.com
53 Chandos Place, Covent Garden, London VA WC2N 4HSUK
@shapeblue
John,
I think we're pending a PR from pdube related to broken VPCs. It sounds very
much like what we found in our QA environment a few weeks ago.
- Si
From: John Burwell
Sent: Thursday, July 21, 2016 10:55 AM
To: [email protected]
Cc: Will Stevens
Subj
I am waiting on pdube's PR to fix some issues with VPCs (not introduced in
4.9, but should be fixed in 4.9).
I am also testing #1613 because I had added #1594 and had to revert it
because I was running into an error consistently ever since. Hopefully
#1613 will run cleanly and I can merge it as w
Hi Raja,
Can we get an answer to this? I have done some XenServer refactoring which
I wish to push upstream but if XenServer 7 integration is being pushed. I'd
like to sit on my changes in favour of getting better support for
XenServer.
-Syed
On Thu, Jul 14, 2016 at 4:21 AM, Erik Weber wrote:
I believe Syed's question is if the XenServer 7 work you guys are doing
will be upstreamed to ACS. Do you guys have an informal timeline?
*Will STEVENS*
Lead Developer
*CloudOps* *| *Cloud Solutions Experts
420 rue Guy *|* Montreal *|* Quebec *|* H3J 1S6
w cloudops.com *|* tw @CloudOps_
On Thu,
I would love to see this as well since XS7 has some nice performance
enhancements.
Regards,
Marty Godsey
-Original Message-
From: [email protected] [mailto:[email protected]] On Behalf Of
Will Stevens
Sent: Thursday, July 21, 2016 1:32 PM
To: [email protected]
Subj
GitHub user rhtyd opened a pull request:
https://github.com/apache/cloudstack/pull/1614
CLOUDSTACK-9437: Fix egress chain and cleanup for allow all traffic
- Fixes use of rules.v4/rules instead of router_rules.v4 file, this makes
sure
that FW_EGRESS_RULE chain gets created on
Hi Will,
The issue is that after upgrading the VR from a pre-4.6 environment, the
outbound traffic for guest VMs stop working (where their egress rule was allow
all for 0.0.0.0/0). Along with this, I found that removing allow all 0.0.0.0/0
egress rule does not remove the rule from VR's filter
Thanks Rohit. @pdube, is this related at all to any of the issues you have
found?
Cheers,
*Will STEVENS*
Lead Developer
*CloudOps* *| *Cloud Solutions Experts
420 rue Guy *|* Montreal *|* Quebec *|* H3J 1S6
w cloudops.com *|* tw @CloudOps_
On Thu, Jul 21, 2016 at 4:13 PM, Rohit Yadav
wrote:
Hi Jonas,
It seems the connection is going down because the dead period detection.
In router run the command 'ipsec auto —status’ to vpn connection status.
When the connection is down initiate traffic from the guest vm to other end of
vpn and go to router check the ipsec vpn status (ipsec auto
12 matches
Mail list logo