[GitHub] cloudstack issue #872: Strongswan vpn feature

[jayapalu]

Github user jayapalu commented on the issue:

https://github.com/apache/cloudstack/pull/872
  
@swill 
The changes added are some improvements. One example is before running 
ipsec up , calling ipsec down 






---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] cloudstack issue #1692: Fix Smoke Test Failures

[murali-reddy]

Github user murali-reddy commented on the issue:

https://github.com/apache/cloudstack/pull/1692
  
@syed Thanks for testing out. Tests related VPC private gateway, redundant 
VPC are still failing as noted [1]. I am working on fix. We want to proceed 
with this PR with those failing tests are known issues. If the rest of the 
tests are passing can we have LGTM?


[1]http://markmail.org/message/n2p2jziywo7kjzx7#query:+page:1+mid:rvv4kqkim2nme35h+state:results


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] cloudstack issue #1692: Fix Smoke Test Failures

[syed]

Github user syed commented on the issue:

https://github.com/apache/cloudstack/pull/1692
  
@PaulAngus were there any tests that were expected to fail? If so I can 
exclude them and try to debug the ones that were supposed to run correctly.


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] cloudstack issue #1692: Fix Smoke Test Failures

[syed]

Github user syed commented on the issue:

https://github.com/apache/cloudstack/pull/1692
  
My tests have finished. I had run into some issues where one of the tests 
got stuck when cleaning everything. I have yet to determine the root cause. 

I've had 8 test cases. Here is the list of the tests

```
PASS BUT CLEANUP FAILED smoke/test_internal_lb.py

FAIL smoke/test_privategw_acl.py
test_02_vpc_privategw_static_routes 
(integration.smoke.test_privategw_acl.TestPrivateGwACL) ... 
=== TestName: test_02_vpc_privategw_static_routes | Status : FAILED ===
FAIL

test_03_vpc_privategw_restart_vpc_cleanup 
(integration.smoke.test_privategw_acl.TestPrivateGwACL) ... 
=== TestName: test_03_vpc_privategw_restart_vpc_cleanup | Status : FAILED 
===
FAIL
test_04_rvpc_privategw_static_routes 
(integration.smoke.test_privategw_acl.TestPrivateGwACL) ... 
=== TestName: test_04_rvpc_privategw_static_routes | Status : FAILED ===
FAIL


FAIL smoke/test_vpc_redundant.py
Create a redundant VPC with two networks with two VMs in each network ... 
=== TestName: test_01_create_redundant_VPC_2tiers_4VMs_4IPs_4PF_ACL | 
Status : FAILED ===
FAIL
Create a redundant VPC with two networks with two VMs in each network and 
check default routes ... 
=== TestName: test_02_redundant_VPC_default_routes | Status : FAILED ===   
FAIL
Create a redundant VPC with 1 Tier, 1 VM, 1 ACL, 1 PF and test Network GC 
Nics ... 
=== TestName: test_04_rvpc_network_garbage_collector_nics | Status : FAILED 
===
FAIL
Create a redundant VPC with 1 Tier, 1 VM, 1 ACL, 1 PF and test Network GC 
Nics ... 
=== TestName: test_05_rvpc_multi_tiers | Status : FAILED ===
FAIL

PASS smoke/test_network_acl.py
PASS smoke/test_password_server.py
PASS smoke/test_vpc_router_nics.py
PASS smoke/test_vpc_vpn.py
```



---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] cloudstack issue #1572: CLOUDSTACK-9395: Add Virtio RNG device to Instances ...

[wido]

Github user wido commented on the issue:

https://github.com/apache/cloudstack/pull/1572
  
@mlsorensen We can indeed do that, but the good thing for now is that the 
RNG is disabled by default.

You also need a very ancient libvirt for it not to support RNG and that 
will get less and less over time.


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] cloudstack issue #1703: Trillian testrun on PR-1692 fwd-merged on 4.9 branch

[jburwell]

Github user jburwell commented on the issue:

https://github.com/apache/cloudstack/pull/1703
  
@nvazquez @serg38 thank you for your help verifying the is PR.


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] cloudstack issue #1692: Fix Smoke Test Failures

[syed]

Github user syed commented on the issue:

https://github.com/apache/cloudstack/pull/1692
  
I'm running the smoke tests on my setup. I will post the results as soon as 
they have completed.


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] cloudstack issue #1708: Fwd merge 4.8->4.9 marvintestfixes to master

[mlsorensen]

Github user mlsorensen commented on the issue:

https://github.com/apache/cloudstack/pull/1708
  
If we can confirm that these were false positives, we're good to merge, no?


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] cloudstack issue #1692: Fix Smoke Test Failures

[mlsorensen]

Github user mlsorensen commented on the issue:

https://github.com/apache/cloudstack/pull/1692
  
If the three test failures don't represent regressions, we should probably 
get this merged per Rohit's suggestion.


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] cloudstack issue #1572: CLOUDSTACK-9395: Add Virtio RNG device to Instances ...

[mlsorensen]

Github user mlsorensen commented on the issue:

https://github.com/apache/cloudstack/pull/1572
  
I realize I'm late to the party on this, but I'd like to suggest that we 
change from the agent.properties "vm.rng.enable=true" to simply using the 
libvirt version detection like we do for other things, and perhaps allow a 
"vm.rng.disable". It really seems like this is a useful setting and should 
probably be default wherever possible.


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

Re: IPv6 in Basic Networking progress

[Wido den Hollander]

> Op 4 oktober 2016 om 12:38 schreef Wido den Hollander :
> 
> 
> I've submitted the code as a PR for the master branch: 
> https://github.com/apache/cloudstack/pull/1700
> 

While this PR is still open (reviews are welcome!) I'm working on the Security 
Grouping and making progress there.

The code can be found here: 
https://github.com/wido/cloudstack/commits/ipv6-basic-networking-secgroup

I'm currently focusing on Anti Spoofing and basic network security, not so much 
opening individual UDP or TCP ports for Instances. It currently simply allows 
all UDP and TCP traffic.

Wido

> > Op 3 oktober 2016 om 20:43 schreef Wido den Hollander :
> > 
> > 
> > Hi,
> > 
> > One of the things I'm really missing in CloudStack currently is IPv6 
> > support in Basic Networking. Why? Our cloud at PCextreme runs on CloudStack 
> > with Basic Networking and we currently do have IPv6 support, but without 
> > the knowledge of CloudStack.
> > 
> > My goals are currently simple:
> > - The API should return the IPv6 address of the Instance
> > - Security Grouping should prevent IPv6 address spoofing
> > 
> > This is all on the Wiki: 
> > https://cwiki.apache.org/confluence/display/CLOUDSTACK/IPv6+in+Basic+Networking
> > 
> > I didn't get to it due to a lack of time, but I gave it a try again this 
> > weekend and today. With result!: 
> > https://github.com/wido/cloudstack/commits/ipv6-basic-networking
> > 
> > The 'nics' table already has the ip6_address column and the API will return 
> > this value when it is set. So what I did is modify the 
> > DirectPodBasedNetworkGuru that it calculates the EUI-64 IPv6 address a 
> > Instance will obtain using SLAAC.
> > 
> > In the network you have to make sure the routers (not the VR, physical 
> > ones!) are sending our Router Advertisements with the same subnet as you 
> > configured in CloudStack.
> > 
> > The code is actually very simple and it 'works': 
> > https://widodh.o.auroraobjects.eu/cloudstack/ipv6-basic-networking-instance.png
> > 
> > The CloudStack code is very, very IPv4 orientated and has many flaws. It 
> > passes IP-Addresses as Strings and such while native types like InetAddress 
> > might be better, but that would be a major refactor which will consume a 
> > lot of time. And honestly, I don't have the time.
> > 
> > As stated above our goals are currently simple. The API should return a 
> > IPv6 Address so that after deployment anything consuming the API can 
> > instantly connect to the Instance over IPv6.
> > 
> > Wido

Re: Virtualization & IaaS DevRoom, FOSDEM

[Wido den Hollander]

> Op 19 oktober 2016 om 16:57 schreef Rich Bowen :
> 
> 
> A Virtualization & IaaS DevRoom is planned for FOSDEM, and the CFP is 
> available at 
> http://www.ovirt.org/blog/2016/10/call-for-proposal-fosdem-2017/
> 
> It would be awesome to have a CloudStack presence there.
> 

I will be present there anyway. Joining the Distributed Storage (Ceph) room, 
but can always jump in for CloudStack.

Might be time to present some IPv6 stuff for Basic Networking.

Wido

> --Rich

Virtualization & IaaS DevRoom, FOSDEM

[Rich Bowen]

A Virtualization & IaaS DevRoom is planned for FOSDEM, and the CFP is available 
at 
http://www.ovirt.org/blog/2016/10/call-for-proposal-fosdem-2017/

It would be awesome to have a CloudStack presence there.

--Rich

[GitHub] cloudstack issue #1692: Fix Smoke Test Failures

[serg38]

Github user serg38 commented on the issue:

https://github.com/apache/cloudstack/pull/1692
  
We will post results later today for Vmware 5.5/6 tests


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

Re: 4.8, 4.9, and master Testing Status

[Syed Ahmed]

@Paul

I'll test this out on my XS7 setup. I need a little help in getting started
with the details of how you are running them.

-Syed

On Wed, Oct 19, 2016 at 9:03 AM, Paul Angus 
wrote:

> To give a specific example,
>
> Running XenServer7 smoke tests result in a large number of failures due to
> problems with the tests.  If we're going to make any real forward progress,
> we need to be able to get meaningful test results.
>
> Plae review/test these PRs
>
>
>
> pretty please (with sugar on top).
>
>
> Kind regards,
>
> Paul Angus
>
> paul.an...@shapeblue.com
> www.shapeblue.com
> 53 Chandos Place, Covent Garden, London  WC2N 4HSUK
> @shapeblue
>
>
>
>
> -Original Message-
> From: Rohit Yadav [mailto:rohit.ya...@shapeblue.com]
> Sent: 19 October 2016 12:39
> To: dev@cloudstack.apache.org
> Subject: Re: 4.8, 4.9, and master Testing Status
>
> All,
>
>
> At least one more test/review LGTM is required on following PRs, please
> help with your review/tests as they will help us work towards cutting the
> RCs:
>
>
> https://github.com/apache/cloudstack/pull/1692
>
> https://github.com/apache/cloudstack/pull/1703
>
> https://github.com/apache/cloudstack/pull/1708
>
>
> As John has shared in the previous email, we still have outstanding
> failures and we'll be working towards fixing all three of them. If we can
> get them merged before end of the week, we can trigger tests on them again
> to know test status on each of the 4.8, 4.9 and master branches that can
> help us determine the quality on each of the branches and we can work
> towards RCs.
>
>
> Regards.
>
> 
> From: John Burwell 
> Sent: 14 October 2016 12:11:04
> To: dev@cloudstack.apache.org
> Subject: Re: 4.8, 4.9, and master Testing Status
>
> All,
>
> We have made great strides stabilizing the 4.8 [1] and 4.9 [2] smoke
> tests.  While we are not super green, the following remaining
> failures/issues are isolated to the VPC VR and secondary storage.
>
> * CLOUDSTACK-9541: redundant VPC VR: issues when master and backup
> switch happens on failover [3]
> * CLOUDSTACK-9540: createPrivateGateway create private network
> does not create proper VLAN network on XenServer
> * CLOUDSTACK-9528: SSVM Downloads (built-in) template multiple
> times
>
> Therefore, I would like to merge these two PRs so that we can begin the
> process of rebasing and retesting the PRs slotted for 4.8 and 4.9 that are
> not affected by these issues (i.e. PRs unrelated to secondary storage or
> the VR).  Our hope is that we can correct these issues quickly, and by the
> time we have worked through the backlog of pending PRs, these issues will
> be addressed and we can move those impacted forward.
>
> Unfortunately, the master PR [5] has 6 failures and 4 errors on XenServer
> [6] that we are currently analyzing.  We hope to have these resolved
> shortly in order to begin progressing PRs targeting master.
>
> I would like to get 1692 [1] and 1703 [2] merged in the next 24 hours.  We
> need to complete the following actions in order to accomplish this goal:
>
> * Obtain at least one code review LGTM on PR #1692 [1]
> * Obtain at least one code review LGTM on PR #1703 [2]
> * Obtain at least one test review LGTM on PR #1703 [2]
>
> Once these PRs, I will be updating PRs slotted for 4.8 and 4.9 to ping
> authors for a rebase.  Following each rebase, we will trigger blueorangutan
> to retest each one.
>
> Thank again for your patience and assistance, -John
>
> [1]: https://github.com/apache/cloudstack/pull/1692
> [2]: https://github.com/apache/cloudstack/pull/1703
> [3]: https://issues.apache.org/jira/browse/CLOUDSTACK-9541
> [4]: https://issues.apache.org/jira/browse/CLOUDSTACK-9540
> [5]: https://github.com/apache/cloudstack/pull/1708
> [6]: https://github.com/apache/cloudstack/pull/1708#issuecomment-253698099
>
> > On Oct 7, 2016, at 10:12 AM, Will Stevens  wrote:
> >
> > Great work everyone.  Don't worry about the sporadic updates, that is
> > just the nature of the beast when working through stuff like this.
> > Well done so far...
> >
> > *Will STEVENS*
> > Lead Developer
> >
> > *CloudOps* *| *Cloud Solutions Experts
> > 420 rue Guy *|* Montreal *|* Quebec *|* H3J 1S6 w cloudops.com *|* tw
> > @CloudOps_
> >
> > On Fri, Oct 7, 2016 at 9:53 AM, John Burwell
> > 
> > wrote:
> >
> >> All,
> >>
> >> Thank you Ilya and Haijao for your words of encouragement.  In
> >> addition to the efforts of Paul, Rohit, Murali, Abhi, and Bobby,
> >> Sergey Levitskiy has been providing great help testing VMware.
> >>
> >> I apologize for my sporadic status updates.  We have made significant
> >> progress in getting smoke tests to pass on KVM, XenServer, and VMware.
> >> Currently, we have the following number of failures and errors:
> >>
> >>* KVM: 0
> >>* VMware: 4
> >>* 

[GitHub] cloudstack issue #1692: Fix Smoke Test Failures

[syed]

Github user syed commented on the issue:

https://github.com/apache/cloudstack/pull/1692
  
@PaulAngus I will test this out on my XenServer7 setup. I would need some 
help to understand how you are running these. I'll PM you on Slack


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

RE: 4.8, 4.9, and master Testing Status

[Paul Angus]

To give a specific example,

Running XenServer7 smoke tests result in a large number of failures due to 
problems with the tests.  If we're going to make any real forward progress, we 
need to be able to get meaningful test results.

Plae review/test these PRs



pretty please (with sugar on top).


Kind regards,

Paul Angus

paul.an...@shapeblue.com 
www.shapeblue.com
53 Chandos Place, Covent Garden, London  WC2N 4HSUK
@shapeblue
  
 


-Original Message-
From: Rohit Yadav [mailto:rohit.ya...@shapeblue.com] 
Sent: 19 October 2016 12:39
To: dev@cloudstack.apache.org
Subject: Re: 4.8, 4.9, and master Testing Status

All,


At least one more test/review LGTM is required on following PRs, please help 
with your review/tests as they will help us work towards cutting the RCs:


https://github.com/apache/cloudstack/pull/1692

https://github.com/apache/cloudstack/pull/1703

https://github.com/apache/cloudstack/pull/1708


As John has shared in the previous email, we still have outstanding failures 
and we'll be working towards fixing all three of them. If we can get them 
merged before end of the week, we can trigger tests on them again to know test 
status on each of the 4.8, 4.9 and master branches that can help us determine 
the quality on each of the branches and we can work towards RCs.


Regards.


From: John Burwell 
Sent: 14 October 2016 12:11:04
To: dev@cloudstack.apache.org
Subject: Re: 4.8, 4.9, and master Testing Status

All,

We have made great strides stabilizing the 4.8 [1] and 4.9 [2] smoke tests.  
While we are not super green, the following remaining failures/issues are 
isolated to the VPC VR and secondary storage.

* CLOUDSTACK-9541: redundant VPC VR: issues when master and backup 
switch happens on failover [3]
* CLOUDSTACK-9540: createPrivateGateway create private network does not 
create proper VLAN network on XenServer
* CLOUDSTACK-9528: SSVM Downloads (built-in) template multiple times

Therefore, I would like to merge these two PRs so that we can begin the process 
of rebasing and retesting the PRs slotted for 4.8 and 4.9 that are not affected 
by these issues (i.e. PRs unrelated to secondary storage or the VR).  Our hope 
is that we can correct these issues quickly, and by the time we have worked 
through the backlog of pending PRs, these issues will be addressed and we can 
move those impacted forward.

Unfortunately, the master PR [5] has 6 failures and 4 errors on XenServer [6] 
that we are currently analyzing.  We hope to have these resolved shortly in 
order to begin progressing PRs targeting master.

I would like to get 1692 [1] and 1703 [2] merged in the next 24 hours.  We need 
to complete the following actions in order to accomplish this goal:

* Obtain at least one code review LGTM on PR #1692 [1]
* Obtain at least one code review LGTM on PR #1703 [2]
* Obtain at least one test review LGTM on PR #1703 [2]

Once these PRs, I will be updating PRs slotted for 4.8 and 4.9 to ping authors 
for a rebase.  Following each rebase, we will trigger blueorangutan to retest 
each one.

Thank again for your patience and assistance, -John

[1]: https://github.com/apache/cloudstack/pull/1692
[2]: https://github.com/apache/cloudstack/pull/1703
[3]: https://issues.apache.org/jira/browse/CLOUDSTACK-9541
[4]: https://issues.apache.org/jira/browse/CLOUDSTACK-9540
[5]: https://github.com/apache/cloudstack/pull/1708
[6]: https://github.com/apache/cloudstack/pull/1708#issuecomment-253698099

> On Oct 7, 2016, at 10:12 AM, Will Stevens  wrote:
>
> Great work everyone.  Don't worry about the sporadic updates, that is 
> just the nature of the beast when working through stuff like this.  
> Well done so far...
>
> *Will STEVENS*
> Lead Developer
>
> *CloudOps* *| *Cloud Solutions Experts
> 420 rue Guy *|* Montreal *|* Quebec *|* H3J 1S6 w cloudops.com *|* tw 
> @CloudOps_
>
> On Fri, Oct 7, 2016 at 9:53 AM, John Burwell 
> 
> wrote:
>
>> All,
>>
>> Thank you Ilya and Haijao for your words of encouragement.  In 
>> addition to the efforts of Paul, Rohit, Murali, Abhi, and Bobby, 
>> Sergey Levitskiy has been providing great help testing VMware.
>>
>> I apologize for my sporadic status updates.  We have made significant 
>> progress in getting smoke tests to pass on KVM, XenServer, and VMware.
>> Currently, we have the following number of failures and errors:
>>
>>* KVM: 0
>>* VMware: 4
>>* XenServer: 8
>>
>> The outstanding failures and errors seem to be the caused by the 
>> following
>> issues:
>>
>>1. On VMware and XenServer, guest VMs in VPCs start but don’t 
>> acquire IP addresses causing tests relying on SSH connectivity tests 
>> to fail.  The issue occurs does not occur on KVM, intermittently on 
>> VMware, and consistently on XenServer.  This issue affects the 
>> 

[GitHub] cloudstack issue #872: Strongswan vpn feature

[swill]

Github user swill commented on the issue:

https://github.com/apache/cloudstack/pull/872
  
@jayapalu the issues are harder to notice if the connection is always 
coming up.  The problem is if you do a configuration which the connection does 
not come up.  Because of the logic I pointed out above, the 
`stopVpnConnection()` function is never called in the java, so the VRs are 
never directed to remove the S2S VPN configuration from the VR.

> Each time we configure the s2s vpn we suppose to overwrite config file 
(ipsec.vpn-.conf).
> Even if the file not got deleted next time the config get overwritten.

This is not actually the case.  If the Connection state is `Disconnected`, 
then the config files are not deleted from the VR.  In that case, for example, 
if you had `dpd=true`, then it will add the following items to the config file.

```
dpddelay=30
dpdtimeout=120
dpdaction=restart
```

Now let's assume that we need to set `dpd=false`, so we remove the 
configuration from ACS ([the files won't get deleted because it is in 
`Disconnected` 
state](https://github.com/apache/cloudstack/blob/master/server/src/com/cloud/network/vpn/Site2SiteVpnManagerImpl.java#L520)).
  Then when the new configuration is applied to the VR, it will see the 
`dpd=false` and will not attempt to modify those lines.  Which means that since 
the config already had those `dpd` lines in the config, they will not be 
removed and every config will include those `dpd` config options even though 
ACS has specified that those config options should not be present.

I have updated the java code to delete the configs from the VR even if the 
connection is disconnected.  I will continue testing and will send a PR to your 
PR soon.

I see you have made changes to this PR.  Are the changes a result of 
testing and these changes fix some bad behavior?


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] cloudstack issue #1692: Fix Smoke Test Failures

[rhtyd]

Github user rhtyd commented on the issue:

https://github.com/apache/cloudstack/pull/1692
  
@NuxRo np, I was pinging most of the active people on the list who may have 
the time/motivation to contribute towards next releases. Thanks.


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] cloudstack issue #1692: Fix Smoke Test Failures

[NuxRo]

Github user NuxRo commented on the issue:

https://github.com/apache/cloudstack/pull/1692
  
Sorry guys, am unable to test currently and cannot LGTM code that I 
obviously don't understand.
Hopefully a coder will step up shortly.


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

Re: 4.8, 4.9, and master Testing Status

[Rohit Yadav]

All,


At least one more test/review LGTM is required on following PRs, please help 
with your review/tests as they will help us work towards cutting the RCs:


https://github.com/apache/cloudstack/pull/1692

https://github.com/apache/cloudstack/pull/1703

https://github.com/apache/cloudstack/pull/1708


As John has shared in the previous email, we still have outstanding failures 
and we'll be working towards fixing all three of them. If we can get them 
merged before end of the week, we can trigger tests on them again to know test 
status on each of the 4.8, 4.9 and master branches that can help us determine 
the quality on each of the branches and we can work towards RCs.


Regards.


From: John Burwell 
Sent: 14 October 2016 12:11:04
To: dev@cloudstack.apache.org
Subject: Re: 4.8, 4.9, and master Testing Status

All,

We have made great strides stabilizing the 4.8 [1] and 4.9 [2] smoke tests.  
While we are not super green, the following remaining failures/issues are 
isolated to the VPC VR and secondary storage.

* CLOUDSTACK-9541: redundant VPC VR: issues when master and backup 
switch happens on failover [3]
* CLOUDSTACK-9540: createPrivateGateway create private network does not 
create proper VLAN network on XenServer
* CLOUDSTACK-9528: SSVM Downloads (built-in) template multiple times

Therefore, I would like to merge these two PRs so that we can begin the process 
of rebasing and retesting the PRs slotted for 4.8 and 4.9 that are not affected 
by these issues (i.e. PRs unrelated to secondary storage or the VR).  Our hope 
is that we can correct these issues quickly, and by the time we have worked 
through the backlog of pending PRs, these issues will be addressed and we can 
move those impacted forward.

Unfortunately, the master PR [5] has 6 failures and 4 errors on XenServer [6] 
that we are currently analyzing.  We hope to have these resolved shortly in 
order to begin progressing PRs targeting master.

I would like to get 1692 [1] and 1703 [2] merged in the next 24 hours.  We need 
to complete the following actions in order to accomplish this goal:

* Obtain at least one code review LGTM on PR #1692 [1]
* Obtain at least one code review LGTM on PR #1703 [2]
* Obtain at least one test review LGTM on PR #1703 [2]

Once these PRs, I will be updating PRs slotted for 4.8 and 4.9 to ping authors 
for a rebase.  Following each rebase, we will trigger blueorangutan to retest 
each one.

Thank again for your patience and assistance,
-John

[1]: https://github.com/apache/cloudstack/pull/1692
[2]: https://github.com/apache/cloudstack/pull/1703
[3]: https://issues.apache.org/jira/browse/CLOUDSTACK-9541
[4]: https://issues.apache.org/jira/browse/CLOUDSTACK-9540
[5]: https://github.com/apache/cloudstack/pull/1708
[6]: https://github.com/apache/cloudstack/pull/1708#issuecomment-253698099

> On Oct 7, 2016, at 10:12 AM, Will Stevens  wrote:
>
> Great work everyone.  Don't worry about the sporadic updates, that is just
> the nature of the beast when working through stuff like this.  Well done so
> far...
>
> *Will STEVENS*
> Lead Developer
>
> *CloudOps* *| *Cloud Solutions Experts
> 420 rue Guy *|* Montreal *|* Quebec *|* H3J 1S6
> w cloudops.com *|* tw @CloudOps_
>
> On Fri, Oct 7, 2016 at 9:53 AM, John Burwell 
> wrote:
>
>> All,
>>
>> Thank you Ilya and Haijao for your words of encouragement.  In addition to
>> the efforts of Paul, Rohit, Murali, Abhi, and Bobby, Sergey Levitskiy has
>> been providing great help testing VMware.
>>
>> I apologize for my sporadic status updates.  We have made significant
>> progress in getting smoke tests to pass on KVM, XenServer, and VMware.
>> Currently, we have the following number of failures and errors:
>>
>>* KVM: 0
>>* VMware: 4
>>* XenServer: 8
>>
>> The outstanding failures and errors seem to be the caused by the following
>> issues:
>>
>>1. On VMware and XenServer, guest VMs in VPCs start but don’t
>> acquire IP addresses causing tests relying on SSH connectivity tests to
>> fail.  The issue occurs does not occur on KVM, intermittently on VMware,
>> and consistently on XenServer.  This issue affects the test_vpc_redundant,
>> test_privategw_acl, and test_vpc_vpn test suites.   We believe that this
>> issue may be caused by either the guest VMs startup/DHCP wait period
>> winning the race with the VPC VR configuration or there is a problem on the
>> VPC VR assigning IP addresses.  We are currently investigating and expect
>> to identify the root cause shortly.
>>2. SSVM downloads str being restarted due to ping timeouts on
>> XenServer and VMware.  We are seeing the following messages such as the
>> following in the Management Server logs:
>>
>>com.cloud.utils.exception.CloudRuntimeException: Failed
>> to send command, due to 
>> 

[GitHub] cloudstack issue #1692: Fix Smoke Test Failures

[rhtyd]

Github user rhtyd commented on the issue:

https://github.com/apache/cloudstack/pull/1692
  
All, we need a LGTM on this one to get the ball moving on release work. 
Pinging several -- @karuturi @swill @wido @NuxRo @nvazquez @serg38 
@GaborApatiNagy @harikrishna-patnala @JayapalUradi @K0zka @rafaelweingartner 
@terbolous @pyr @syed
Thanks.


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] cloudstack issue #1712: CLOUDSTACK-9550: Use context to filter items in a me...

[borisstoyanov]

Github user borisstoyanov commented on the issue:

https://github.com/apache/cloudstack/pull/1712
  
I've navigated through Zone -> Compute and Storage -> to clusters, hosts 
and pr storages -> Metrics View. All the resources are there and they seem to 
be showing the same as from infrastructure. LGTM 👍 

![screen shot 2016-10-19 at 12 09 33 
pm](https://cloud.githubusercontent.com/assets/13551960/19512588/53bc16de-95f5-11e6-8c7b-2021df29b8f2.png)

![screen shot 2016-10-19 at 12 09 47 
pm](https://cloud.githubusercontent.com/assets/13551960/19512589/53bd57c4-95f5-11e6-8aaa-a356c040ff67.png)

![screen shot 2016-10-19 at 12 10 52 
pm](https://cloud.githubusercontent.com/assets/13551960/19512587/53bb1efa-95f5-11e6-9f48-456f711274df.png)

![screen shot 2016-10-19 at 12 11 56 
pm](https://cloud.githubusercontent.com/assets/13551960/19512590/53bf8666-95f5-11e6-9c83-528cd007a75b.png)



---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] cloudstack issue #872: Strongswan vpn feature

[jayapalu]

Github user jayapalu commented on the issue:

https://github.com/apache/cloudstack/pull/872
  
I have created two VPCs and configured the s2s vpn from UI. My tunnels are 
coming up without manually restarting the ipsec in this branch.

s2s_customer_gateway:

++--+--+---+-++---++--+--+-+-+---++-+
| id | uuid | name | gateway_ip| 
guest_cidr_list | ipsec_psk  | ike_policy| esp_policy | ike_lifetime | 
esp_lifetime | dpd | force_encap | domain_id | account_id | removed |

++--+--+---+-++---++--+--+-+-+---++-+
|  7 | 9cff8e2a-2848-46fc-80ef-7dcc47bfd4e4 | cg1  | 10.147.46.102 | 
10.1.0.0/16 | 1234567890 | 3des-md5;modp1024 | 3des-md5   |86400 |  
   3600 |   0 |   0 | 1 |  2 | NULL|
|  8 | 60bd9e15-0a18-4334-ab98-ff56b0f839a5 | cg2  | 10.147.46.103 | 
10.2.0.0/16 | 1234567890 | 3des-md5;modp1024 | 3des-md5   |86400 |  
   3600 |   1 |   0 | 1 |  2 | NULL|

++--+--+---+-++---++--+--+-+-+---++-+
2 rows in set (0.00 sec)

ipsec status
Security Associations (1 up, 0 connecting):
vpn-10.147.46.102[17]: ESTABLISHED 10 minutes ago, 
10.147.46.103[10.147.46.103]...10.147.46.102[10.147.46.102]
vpn-10.147.46.102{21}:  INSTALLED, TUNNEL, ESP SPIs: c562e87d_i c6a45be4_o
vpn-10.147.46.102{21}:   10.2.0.0/16 === 10.1.0.0/16 


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] cloudstack issue #1712: CLOUDSTACK-9550: Use context to filter items in a me...

[blueorangutan]

Github user blueorangutan commented on the issue:

https://github.com/apache/cloudstack/pull/1712
  
Packaging result: ✔centos6 ✔centos7 ✔debian. JID-64


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] cloudstack issue #1712: CLOUDSTACK-9550: Use context to filter items in a me...

[borisstoyanov]

Github user borisstoyanov commented on the issue:

https://github.com/apache/cloudstack/pull/1712
  
@blueorangutan package


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] cloudstack issue #1712: CLOUDSTACK-9550: Use context to filter items in a me...

[blueorangutan]

Github user blueorangutan commented on the issue:

https://github.com/apache/cloudstack/pull/1712
  
@borisstoyanov a Jenkins job has been kicked to build packages. I'll keep 
you posted as I make progress.


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] cloudstack issue #1712: CLOUDSTACK-9550: Use context to filter items in a me...

[rhtyd]

Github user rhtyd commented on the issue:

https://github.com/apache/cloudstack/pull/1712
  
@borisstoyanov can you help with manual testing of the fix with some 
screenshots, thanks.


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] cloudstack pull request #1712: CLOUDSTACK-9550: Use context to filter items ...

[rhtyd]

GitHub user rhtyd opened a pull request:

https://github.com/apache/cloudstack/pull/1712

CLOUDSTACK-9550: Use context to filter items in a metrics view

Use available context to filter a metrics view based on zone, cluster, host
in the context object. This fixes metrics view filtering when metrics view 
is
viewed via Zone->Compute and Storage-> for a resource.

/cc @jburwell @karuturi -- this is a pure UI fix, one manual test LGTM 
would be required.

You can merge this pull request into a Git repository by running:

$ git pull https://github.com/shapeblue/cloudstack 
metrics-view-context-filtering

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/cloudstack/pull/1712.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #1712


commit 2767e1ade6cd9918ea952be4898d02ae30479feb
Author: Rohit Yadav 
Date:   2016-10-19T06:11:08Z

CLOUDSTACK-9550: Use context to filter items in a metrics view

Use available context to filter a metrics view based on zone, cluster, host
in the context object. This fixes metrics view filtering when metrics view 
is
viewed via Zone->Compute and Storage-> for a resource.

Signed-off-by: Rohit Yadav 




---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] cloudstack issue #872: Strongswan vpn feature

[jayapalu]

Github user jayapalu commented on the issue:

https://github.com/apache/cloudstack/pull/872
  
@swill I did not test the case of delete vpn on error state, so I did not 
come across the vpn config file mess.
Each time we configure the s2s vpn we suppose to overwrite  config fie 
(ipsec.vpn-.conf).
Even if the file not got deleted next time the config get overwritten. 

Please add your commits in this PR so that we will have track.
I am also testing today, I will add few changes.



---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---