Re: [VOTE] Apache CloudStack 4.12.0.0 [RC2]

2019-02-21 Thread Gabriel Beims Bräscher
Hello all,

To keep the expected RM workflow I have Pushed the branch
4.12.0.0-RC20190212T2301 for the RC2.
It would be great to have a few more votes; thus, VOTE will be extended
until Tuesday (26th of February).

Git Branch and Commit SH:
https://github.com/apache/cloudstack/tree/4.12.0.0-RC20190212T2301

https://github.com/apache/cloudstack/commit/e5b3aa4b5a5d1a25c79313cecd3ae1c9f074baca

Commit: e5b3aa4b5a5d1a25c79313cecd3ae1c9f074baca

Thanks for all the help so far.

Additional information:
I am building packages from commit e5b3aa4, I will ping it again when have
they available on http://cloudstack.apt-get.eu/.

Updating the votes:
+1 (PMC / binding)
* Wido
* Rafael

+1 (non-binding)
* Gabriel (me)

0
none

-1
none

Em qui, 21 de fev de 2019 às 04:12, Rohit Yadav 
escreveu:

> Hi Gabriel,
>
>
> Master is still on 4.12.0.0-SNAPSHOT, so it cannot be considered 4.12.0.0
> RC2. Master does not have the release script commit that changes the
> version when you perform the release. What if there is a bug in the script
> that patches the codebase and changes the version?
>
>
> Ideally, I would expect either a new RC to be cut if there was a new
> change and the script re-run and the new RC branch/tag to be shared for
> testing and voting. The way you're using is not the official release
> process we've agreed, you're basically asking people to test and vote on
> the master branch/tag that is NOT going to be the release/tag.
>
>
> Kindly rectify and push the RC branch.
>
>
> - Rohit
>
> 
> From: Gabriel Beims Bräscher 
> Sent: Wednesday, February 20, 2019 11:53:08 PM
> To: users
> Cc: dev@cloudstack.apache.org
> Subject: Re: [VOTE] Apache CloudStack 4.12.0.0 [RC2]
>
> Rohit, I have created PR #3187 "master smoketest health check" and it has
> passed on all checks.
>
> Simon, I have not pushed upstream a branch for the RC; The RC2 is
> considering the master latest commit (709845f).
> If we need an RC3 I will then create a branch for it and unfreeze the
> master.
>
> Git Branch and Commit SH:
> https://github.com/apache/cloudstack/tree/master
>
> https://github.com/apache/cloudstack/commit/709845f4a333ad2ace0183706433a0653ba159c6
> Commit: 709845f4a333ad2ace0183706433a0653ba159c6
>
> Regards,
> Gabriel.
>
> PR #3187: https://github.com/apache/cloudstack/pull/3187
>
> Em qua, 20 de fev de 2019 às 11:54, Simon Weller 
> escreveu:
>
> > I'm also going to find some time to build and test 4.12 this week. So
> > reading the thread here, there's no  RC branch and we're using master?
> >
> > -Si
> >
> >
> >
> > 
> > From: Rohit Yadav 
> > Sent: Wednesday, February 20, 2019 1:50 AM
> > To: dev@cloudstack.apache.org; users
> > Subject: Re: [VOTE] Apache CloudStack 4.12.0.0 [RC2]
> >
> > Hi Gabriel,
> >
> >
> > I'll try to find some time this weekend to test the RC2.
> >
> >
> > However, on top of things, the commit/sha does not seem super stable
> > (intermittently failing travis smoketests on master, but not on 4.11 for
> > example) and I could not find the 4.12.0.0-RC20190212T2301 branch on
> > asf/github remotes. Have you confirmed near ~100% smoketests pass for
> > atleast kvm/vmware/xenserver on the RC?
> >
> >
> > - Rohit
> >
> > 
> >
> >
> >
> > 
> > From: Gabriel Beims Bräscher 
> > Sent: Tuesday, February 19, 2019 9:12:28 PM
> > To: dev@cloudstack.apache.org; users
> > Subject: Re: [VOTE] Apache CloudStack 4.12.0.0 [RC2]
> >
> > Hello all,
> >
> > I would like to update that we still have 48 hours (extended another 72
> > hours) for testing and voting 4.12 RC2.
> >
> > So far we have 2 votes:
> > +1 (PMC / binding)
> > * wido
> >
> > +1 (non binding)
> > * me
> >
> > 0
> > none
> >
> > -1
> > none
> >
> >
> > Em seg, 18 de fev de 2019 às 09:37, Paul Angus  >
> > escreveu:
> >
> > > Ah,
> > >
> > > Previously I followed the documentation here:
> > >
> > >
> https://cwiki.apache.org/confluence/display/CLOUDSTACK/Release+Procedure
> > >
> > >
> > >
> > > Master can be unfrozen once we reach a point that the code is healthy
> > > enough to cut the first RC as the release is then on its own branch.
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > > *From:* Gabriel Beims Bräscher 
> > > *Sent:* 18 February 2019 12:16
> > > *To:* Paul Angus 
> > > *Cc:* dev@cloudstack.apache.org; users 
> > > *Subject:* Re: [VOTE] Apache CloudStack 4.12.0.0 [RC2]
> > >
> > >
> > >
> > > Paul, I did not create a branch. As the master branch is on freeze, I
> > > considered the master to be used on building and tests.
> > >
> > >
> > >
> > > Git Branch and Commit SH:
> > > https://github.com/apache/cloudstack/tree/master
> > >
> > >
> >
> https://github.com/apache/cloudstack/commit/709845f4a333ad2ace0183706433a0653ba159c6
> > > Commit: 709845f4a333ad2ace01

RE: [VOTE] Apache CloudStack 4.12.0.0 [RC2]

2019-02-21 Thread Paul Angus
I'm afraid that I think this has to be a new vote, which needs everyone to vote 
again as the commit SHA has changed.
I'm fairly sure that it is legitimate for people to look at the git logs and 
satisfy themselves that nothing has changed since they last voted and vote 
without repeating testing, but I believe that you do have to reset the vote 
tally to 0s all round.

paul.an...@shapeblue.com 
www.shapeblue.com
Amadeus House, Floral Street, London  WC2E 9DPUK
@shapeblue
  
 


-Original Message-
From: Gabriel Beims Bräscher  
Sent: 21 February 2019 11:29
To: users 
Cc: dev@cloudstack.apache.org
Subject: Re: [VOTE] Apache CloudStack 4.12.0.0 [RC2]

Hello all,

To keep the expected RM workflow I have Pushed the branch
4.12.0.0-RC20190212T2301 for the RC2.
It would be great to have a few more votes; thus, VOTE will be extended until 
Tuesday (26th of February).

Git Branch and Commit SH:
https://github.com/apache/cloudstack/tree/4.12.0.0-RC20190212T2301

https://github.com/apache/cloudstack/commit/e5b3aa4b5a5d1a25c79313cecd3ae1c9f074baca

Commit: e5b3aa4b5a5d1a25c79313cecd3ae1c9f074baca

Thanks for all the help so far.

Additional information:
I am building packages from commit e5b3aa4, I will ping it again when have they 
available on http://cloudstack.apt-get.eu/.

Updating the votes:
+1 (PMC / binding)
* Wido
* Rafael

+1 (non-binding)
* Gabriel (me)

0
none

-1
none

Em qui, 21 de fev de 2019 às 04:12, Rohit Yadav 
escreveu:

> Hi Gabriel,
>
>
> Master is still on 4.12.0.0-SNAPSHOT, so it cannot be considered 
> 4.12.0.0 RC2. Master does not have the release script commit that 
> changes the version when you perform the release. What if there is a 
> bug in the script that patches the codebase and changes the version?
>
>
> Ideally, I would expect either a new RC to be cut if there was a new 
> change and the script re-run and the new RC branch/tag to be shared 
> for testing and voting. The way you're using is not the official 
> release process we've agreed, you're basically asking people to test 
> and vote on the master branch/tag that is NOT going to be the release/tag.
>
>
> Kindly rectify and push the RC branch.
>
>
> - Rohit
>
> 
> From: Gabriel Beims Bräscher 
> Sent: Wednesday, February 20, 2019 11:53:08 PM
> To: users
> Cc: dev@cloudstack.apache.org
> Subject: Re: [VOTE] Apache CloudStack 4.12.0.0 [RC2]
>
> Rohit, I have created PR #3187 "master smoketest health check" and it 
> has passed on all checks.
>
> Simon, I have not pushed upstream a branch for the RC; The RC2 is 
> considering the master latest commit (709845f).
> If we need an RC3 I will then create a branch for it and unfreeze the 
> master.
>
> Git Branch and Commit SH:
> https://github.com/apache/cloudstack/tree/master
>
> https://github.com/apache/cloudstack/commit/709845f4a333ad2ace01837064
> 33a0653ba159c6
> Commit: 709845f4a333ad2ace0183706433a0653ba159c6
>
> Regards,
> Gabriel.
>
> PR #3187: https://github.com/apache/cloudstack/pull/3187
>
> Em qua, 20 de fev de 2019 às 11:54, Simon Weller 
> 
> escreveu:
>
> > I'm also going to find some time to build and test 4.12 this week. 
> > So reading the thread here, there's no  RC branch and we're using master?
> >
> > -Si
> >
> >
> >
> > 
> > From: Rohit Yadav 
> > Sent: Wednesday, February 20, 2019 1:50 AM
> > To: dev@cloudstack.apache.org; users
> > Subject: Re: [VOTE] Apache CloudStack 4.12.0.0 [RC2]
> >
> > Hi Gabriel,
> >
> >
> > I'll try to find some time this weekend to test the RC2.
> >
> >
> > However, on top of things, the commit/sha does not seem super stable 
> > (intermittently failing travis smoketests on master, but not on 4.11 
> > for
> > example) and I could not find the 4.12.0.0-RC20190212T2301 branch on 
> > asf/github remotes. Have you confirmed near ~100% smoketests pass 
> > for atleast kvm/vmware/xenserver on the RC?
> >
> >
> > - Rohit
> >
> > 
> >
> >
> >
> > 
> > From: Gabriel Beims Bräscher 
> > Sent: Tuesday, February 19, 2019 9:12:28 PM
> > To: dev@cloudstack.apache.org; users
> > Subject: Re: [VOTE] Apache CloudStack 4.12.0.0 [RC2]
> >
> > Hello all,
> >
> > I would like to update that we still have 48 hours (extended another 
> > 72
> > hours) for testing and voting 4.12 RC2.
> >
> > So far we have 2 votes:
> > +1 (PMC / binding)
> > * wido
> >
> > +1 (non binding)
> > * me
> >
> > 0
> > none
> >
> > -1
> > none
> >
> >
> > Em seg, 18 de fev de 2019 às 09:37, Paul Angus 
> >  >
> > escreveu:
> >
> > > Ah,
> > >
> > > Previously I followed the documentation here:
> > >
> > >
> https://cwiki.apache.org/confluence/display/CLOUDSTACK/Release+Procedu
> re
> > >
> > >
> > >
> > > Master can be unfrozen once we reach a point that the code is 
> > > healthy enough to cut the first RC as th

Re: [VOTE] Apache CloudStack 4.12.0.0 [RC2]

2019-02-21 Thread Rafael Weingärtner
In case the vote resets.
+1 from me (binding vote)

On Thu, Feb 21, 2019 at 9:49 AM Paul Angus  wrote:

> I'm afraid that I think this has to be a new vote, which needs everyone to
> vote again as the commit SHA has changed.
> I'm fairly sure that it is legitimate for people to look at the git logs
> and satisfy themselves that nothing has changed since they last voted and
> vote without repeating testing, but I believe that you do have to reset the
> vote tally to 0s all round.
>
> paul.an...@shapeblue.com
> www.shapeblue.com
> Amadeus House, Floral Street, London  WC2E 9DPUK
> @shapeblue
>
>
>
>
> -Original Message-
> From: Gabriel Beims Bräscher 
> Sent: 21 February 2019 11:29
> To: users 
> Cc: dev@cloudstack.apache.org
> Subject: Re: [VOTE] Apache CloudStack 4.12.0.0 [RC2]
>
> Hello all,
>
> To keep the expected RM workflow I have Pushed the branch
> 4.12.0.0-RC20190212T2301 for the RC2.
> It would be great to have a few more votes; thus, VOTE will be extended
> until Tuesday (26th of February).
>
> Git Branch and Commit SH:
> https://github.com/apache/cloudstack/tree/4.12.0.0-RC20190212T2301
> 
>
> https://github.com/apache/cloudstack/commit/e5b3aa4b5a5d1a25c79313cecd3ae1c9f074baca
> <
> https://github.com/apache/cloudstack/commit/709845f4a333ad2ace0183706433a0653ba159c6
> >
> Commit: e5b3aa4b5a5d1a25c79313cecd3ae1c9f074baca
>
> Thanks for all the help so far.
>
> Additional information:
> I am building packages from commit e5b3aa4, I will ping it again when have
> they available on http://cloudstack.apt-get.eu/.
>
> Updating the votes:
> +1 (PMC / binding)
> * Wido
> * Rafael
>
> +1 (non-binding)
> * Gabriel (me)
>
> 0
> none
>
> -1
> none
>
> Em qui, 21 de fev de 2019 às 04:12, Rohit Yadav  >
> escreveu:
>
> > Hi Gabriel,
> >
> >
> > Master is still on 4.12.0.0-SNAPSHOT, so it cannot be considered
> > 4.12.0.0 RC2. Master does not have the release script commit that
> > changes the version when you perform the release. What if there is a
> > bug in the script that patches the codebase and changes the version?
> >
> >
> > Ideally, I would expect either a new RC to be cut if there was a new
> > change and the script re-run and the new RC branch/tag to be shared
> > for testing and voting. The way you're using is not the official
> > release process we've agreed, you're basically asking people to test
> > and vote on the master branch/tag that is NOT going to be the
> release/tag.
> >
> >
> > Kindly rectify and push the RC branch.
> >
> >
> > - Rohit
> >
> > 
> > From: Gabriel Beims Bräscher 
> > Sent: Wednesday, February 20, 2019 11:53:08 PM
> > To: users
> > Cc: dev@cloudstack.apache.org
> > Subject: Re: [VOTE] Apache CloudStack 4.12.0.0 [RC2]
> >
> > Rohit, I have created PR #3187 "master smoketest health check" and it
> > has passed on all checks.
> >
> > Simon, I have not pushed upstream a branch for the RC; The RC2 is
> > considering the master latest commit (709845f).
> > If we need an RC3 I will then create a branch for it and unfreeze the
> > master.
> >
> > Git Branch and Commit SH:
> > https://github.com/apache/cloudstack/tree/master
> >
> > https://github.com/apache/cloudstack/commit/709845f4a333ad2ace01837064
> > 33a0653ba159c6
> > Commit: 709845f4a333ad2ace0183706433a0653ba159c6
> >
> > Regards,
> > Gabriel.
> >
> > PR #3187: https://github.com/apache/cloudstack/pull/3187
> >
> > Em qua, 20 de fev de 2019 às 11:54, Simon Weller
> > 
> > escreveu:
> >
> > > I'm also going to find some time to build and test 4.12 this week.
> > > So reading the thread here, there's no  RC branch and we're using
> master?
> > >
> > > -Si
> > >
> > >
> > >
> > > 
> > > From: Rohit Yadav 
> > > Sent: Wednesday, February 20, 2019 1:50 AM
> > > To: dev@cloudstack.apache.org; users
> > > Subject: Re: [VOTE] Apache CloudStack 4.12.0.0 [RC2]
> > >
> > > Hi Gabriel,
> > >
> > >
> > > I'll try to find some time this weekend to test the RC2.
> > >
> > >
> > > However, on top of things, the commit/sha does not seem super stable
> > > (intermittently failing travis smoketests on master, but not on 4.11
> > > for
> > > example) and I could not find the 4.12.0.0-RC20190212T2301 branch on
> > > asf/github remotes. Have you confirmed near ~100% smoketests pass
> > > for atleast kvm/vmware/xenserver on the RC?
> > >
> > >
> > > - Rohit
> > >
> > > 
> > >
> > >
> > >
> > > 
> > > From: Gabriel Beims Bräscher 
> > > Sent: Tuesday, February 19, 2019 9:12:28 PM
> > > To: dev@cloudstack.apache.org; users
> > > Subject: Re: [VOTE] Apache CloudStack 4.12.0.0 [RC2]
> > >
> > > Hello all,
> > >
> > > I would like to update that we still have 48 hours (extended another
> > > 72
> > > hours) for testing and voting 4.12 RC2.
> > >
> > > So far we have 2 votes:
> > > +1 (PMC / binding)
> > > * wido
> > >
> > > +1 (non binding)
> > > * me
> > >
> > > 0

Re: [VOTE] Apache CloudStack 4.12.0.0 [RC2]

2019-02-21 Thread Gabriel Beims Bräscher
Hi All,

I am closing the VOTE for RC2. Please, review and test RC3 on the e-mail
thread "[VOTE] Apache CloudStack 4.12.0.0 [RC3]".

Em qui, 21 de fev de 2019 às 09:53, Rafael Weingärtner <
rafaelweingart...@gmail.com> escreveu:

> In case the vote resets.
> +1 from me (binding vote)
>
> On Thu, Feb 21, 2019 at 9:49 AM Paul Angus 
> wrote:
>
> > I'm afraid that I think this has to be a new vote, which needs everyone
> to
> > vote again as the commit SHA has changed.
> > I'm fairly sure that it is legitimate for people to look at the git logs
> > and satisfy themselves that nothing has changed since they last voted and
> > vote without repeating testing, but I believe that you do have to reset
> the
> > vote tally to 0s all round.
> >
> > paul.an...@shapeblue.com
> > www.shapeblue.com
> > Amadeus House, Floral Street, London  WC2E 9DPUK
> > @shapeblue
> >
> >
> >
> >
> > -Original Message-
> > From: Gabriel Beims Bräscher 
> > Sent: 21 February 2019 11:29
> > To: users 
> > Cc: dev@cloudstack.apache.org
> > Subject: Re: [VOTE] Apache CloudStack 4.12.0.0 [RC2]
> >
> > Hello all,
> >
> > To keep the expected RM workflow I have Pushed the branch
> > 4.12.0.0-RC20190212T2301 for the RC2.
> > It would be great to have a few more votes; thus, VOTE will be extended
> > until Tuesday (26th of February).
> >
> > Git Branch and Commit SH:
> > https://github.com/apache/cloudstack/tree/4.12.0.0-RC20190212T2301
> > 
> >
> >
> https://github.com/apache/cloudstack/commit/e5b3aa4b5a5d1a25c79313cecd3ae1c9f074baca
> > <
> >
> https://github.com/apache/cloudstack/commit/709845f4a333ad2ace0183706433a0653ba159c6
> > >
> > Commit: e5b3aa4b5a5d1a25c79313cecd3ae1c9f074baca
> >
> > Thanks for all the help so far.
> >
> > Additional information:
> > I am building packages from commit e5b3aa4, I will ping it again when
> have
> > they available on http://cloudstack.apt-get.eu/.
> >
> > Updating the votes:
> > +1 (PMC / binding)
> > * Wido
> > * Rafael
> >
> > +1 (non-binding)
> > * Gabriel (me)
> >
> > 0
> > none
> >
> > -1
> > none
> >
> > Em qui, 21 de fev de 2019 às 04:12, Rohit Yadav <
> rohit.ya...@shapeblue.com
> > >
> > escreveu:
> >
> > > Hi Gabriel,
> > >
> > >
> > > Master is still on 4.12.0.0-SNAPSHOT, so it cannot be considered
> > > 4.12.0.0 RC2. Master does not have the release script commit that
> > > changes the version when you perform the release. What if there is a
> > > bug in the script that patches the codebase and changes the version?
> > >
> > >
> > > Ideally, I would expect either a new RC to be cut if there was a new
> > > change and the script re-run and the new RC branch/tag to be shared
> > > for testing and voting. The way you're using is not the official
> > > release process we've agreed, you're basically asking people to test
> > > and vote on the master branch/tag that is NOT going to be the
> > release/tag.
> > >
> > >
> > > Kindly rectify and push the RC branch.
> > >
> > >
> > > - Rohit
> > >
> > > 
> > > From: Gabriel Beims Bräscher 
> > > Sent: Wednesday, February 20, 2019 11:53:08 PM
> > > To: users
> > > Cc: dev@cloudstack.apache.org
> > > Subject: Re: [VOTE] Apache CloudStack 4.12.0.0 [RC2]
> > >
> > > Rohit, I have created PR #3187 "master smoketest health check" and it
> > > has passed on all checks.
> > >
> > > Simon, I have not pushed upstream a branch for the RC; The RC2 is
> > > considering the master latest commit (709845f).
> > > If we need an RC3 I will then create a branch for it and unfreeze the
> > > master.
> > >
> > > Git Branch and Commit SH:
> > > https://github.com/apache/cloudstack/tree/master
> > >
> > > https://github.com/apache/cloudstack/commit/709845f4a333ad2ace01837064
> > > 33a0653ba159c6
> > > Commit: 709845f4a333ad2ace0183706433a0653ba159c6
> > >
> > > Regards,
> > > Gabriel.
> > >
> > > PR #3187: https://github.com/apache/cloudstack/pull/3187
> > >
> > > Em qua, 20 de fev de 2019 às 11:54, Simon Weller
> > > 
> > > escreveu:
> > >
> > > > I'm also going to find some time to build and test 4.12 this week.
> > > > So reading the thread here, there's no  RC branch and we're using
> > master?
> > > >
> > > > -Si
> > > >
> > > >
> > > >
> > > > 
> > > > From: Rohit Yadav 
> > > > Sent: Wednesday, February 20, 2019 1:50 AM
> > > > To: dev@cloudstack.apache.org; users
> > > > Subject: Re: [VOTE] Apache CloudStack 4.12.0.0 [RC2]
> > > >
> > > > Hi Gabriel,
> > > >
> > > >
> > > > I'll try to find some time this weekend to test the RC2.
> > > >
> > > >
> > > > However, on top of things, the commit/sha does not seem super stable
> > > > (intermittently failing travis smoketests on master, but not on 4.11
> > > > for
> > > > example) and I could not find the 4.12.0.0-RC20190212T2301 branch on
> > > > asf/github remotes. Have you confirmed near ~100% smoketests pass
> > > > for atleast kvm/vmware/xenserver on the RC?
> > > >
> > > >
> > > > - Rohit
> > 

[VOTE] Apache CloudStack 4.12.0.0 [RC3]

2019-02-21 Thread Gabriel Beims Bräscher
Hi All,

I've created a 4.12.0.0 release (RC3), with the following artifacts up for
a vote:

Git Branch and Commit SH:
https://github.com/apache/cloudstack/tree/4.12.0.0-RC20190212T2301
https://github.com/apache/cloudstack/commit/e5b3aa4b5a5d1a25c79313cecd3ae1c9f074baca
Commit: e5b3aa4b5a5d1a25c79313cecd3ae1c9f074baca

Source release for 4.12.0.0-RC20190212T2301:
https://dist.apache.org/repos/dist/dev/cloudstack/4.12.0.0/

PGP release keys (signed using 25908455):
https://dist.apache.org/repos/dist/release/cloudstack/KEYS

The vote will be open for 3 business days (until 26th February).

For sanity in tallying the vote, can PMC members please be sure to indicate
"(binding)" with their vote?

[ ] +1  approve
[ ] +0  no opinion
[ ] -1  disapprove (and reason why)

Additional information:

*Note:* the RC2 VOTE ("[VOTE] Apache CloudStack 4.12.0.0 [RC2]") had no
blocker bug to be fixed; however, the VOTE process led to the need of an
RC3. For more details, please follow the discussions at the respective
email thread.

All Travis and Jenkins checks have passed [1] for the branch
4.12.0.0-RC20190212T2301.

For users' convenience, packages are available in
http://cloudstack.apt-get.eu/
4.12.0.0 RC3 is available for the following distros:
- Ubuntu 14.04, 16.04, and 18.04;
- CentOS6 and CentOS7.

Please, use the template 4.11.2 (located in [2]) when testing the RC3.
The release notes [3] still need to be updated.

[1] https://github.com/apache/cloudstack/pull/3189
[2] http://download.cloudstack.org/systemvm/4.11/
[3]
http://docs.cloudstack.apache.org/projects/cloudstack-release-notes/en/latest/index.html


VMs Connection break under two isolate network

2019-02-21 Thread gu haven
hi ,all
  I try iperf wget scp connection will break after 200 seconds ,Do  need 
any optimization in vr ?

environment infomation below:

cloudstack 4.11.2

xenserver 7.1 CU2 Enterprise

NIC :MLNX 25GbE 2P ConnectX4LX

bond mode in xenserver : acitce-active



[cid:7d9efc71-ebb3-49ef-9ced-a887dbf1e3a1]




Re:VMs Connection break under two isolate network

2019-02-21 Thread Haijiao
Hi, Devs and Community Users


To be more specific,  our environment is built with 
* 2 Dell R740XD Servers + Dell Compellent Storage w/ iSCSI
* Each server equiped with two Mellanox Connect-4 LX 25GbE network adapters, 
and configured with bond mode(active+active) in XenServer
* CloudStack 4.11.2 LTS + XenServer 7.1CU2(LTS) Enterprise


Everything goes fine with shared network, but the weird thing is if we setup 2 
isolated networks,  try to use 'iperf',  'wget' or 'SCP' to test the network 
performance betwen two VMs located in these 2 isolated networks,  the traffic 
will drop to zero in about 200-300 seconds,  even though we were still able to 
ping or SSH VM B1 from A1 or verse. 


VM A1 ---> VR A(Isloated Network A) > VR B(Isolated Network B)  > VM B1

We have checked the configuration on switches, upgraded Mellanox driver for 
XenServer,  but no luck. 
Meanwhile, we can not re-produce this issue in another environment (XenServer 
7.1CU2+ACS 4.11.2+ Intel Gb network). 


 It seems it might be related to Mellanox adapter, but we have no idea what 
part we could possibly miss in this case. 


Any advice would be highly appreciated !   Thank you !


在2019年02月22 13时09分, "gu haven"写道:


hi ,all 
  I try iperf wget scp connection will break after 200 seconds ,Do  need 
any optimization in vr ?
  
environment infomation below:

cloudstack 4.11.2

xenserver 7.1 CU2 Enterprise

NIC :MLNX 25GbE 2P ConnectX4LX 

bond mode in xenserver : acitce-active
















RE: Welcome Paul Bencko!

2019-02-21 Thread Paul Bencko
Thank you everyone for the warm welcome 😊! Glad to be part of this community!



Bencko Paul
Java Software Developer, ENA
Ness Digital Engineering  

-Original Message-
From: Nathan Johnson  
Sent: Tuesday, February 19, 2019 10:04 PM
To: dev@cloudstack.apache.org
Subject: Welcome Paul Bencko!

I would like to introduce a new team member Paul Bencko who will be helping us 
out with some ACS development related tasks.

Welcome Paul!

Nathan Johnson
Senior R&D Engineer
Education Networks of America