Re: Clean up old and obsolete branches

[Daan Hoogland]

thanks for that list Khosrow,  Also very usefull for cleaning people to
clean their own fork.
I think you can start with the lowest pom versions but I changed one
because the referred ticket isn't closed. It's my own and I'll have a look
later today. For a lot of the branches the ticket aren't clear because only
 or CS- is in the titel. Only when CLOUDSTACK- is in the titel you can see immediately that it is closed by the
automatic strikethrough that happens. just a heads-up.

+1


On Fri, Dec 1, 2017 at 2:13 AM, Gabriel Beims Bräscher  wrote:

> Thanks for the initiative, Khosrow.
>
> +1 on removing obsolete branches.
>
> 2017-11-30 18:05 GMT-02:00 Khosrow Moossavi :
>
> > Hi Community
> >
> > I would like to start the discussion around deleting old and obsolete
> > branches on github repository. This will help newcomers (including
> myself)
> > to keep track of which branches are important and which are not. And
> since
> > almost everyone's working on their own forks there is no need to keep
> > feature/bugfix/hotfix branches around in the main official repository.
> >
> > I've created an issue which contains full list of branches in
> > GH/apache/cloudstack repo as of time of writing this email and the
> > proposition of which one of them can be deleted.
> >
> > https://issues.apache.org/jira/browse/CLOUDSTACK-10169
> >
> > I would appreciate your questions, comments, suggestions.
> >
> > Thanks
> >
> > Khosrow Moossavi
> >
> > Cloud Infrastructure Developer
> >
> > CloudOps
> >
>



-- 
Daan

Re: S2S VPN to AWS problems

[Srinivas Gandikota]

Nux,


You can get one tunnel working, but requires two manual changes in the VR 
strongswan vpn options.


  1.  Enforce ikev1
  2.  add compress=no

If all other pieces are in sync, tunnel should be up.

Thanks,
Srinivas




From: Nux! 
Sent: Thursday, November 30, 2017 11:04 PM
To: dev
Cc: users
Subject: S2S VPN to AWS problems

Hello,

Has anyone managed to get a s2s VPN up with an AWS VPC?
I see AWS require the setup of two tunnels which does not seem possible in ACS. 
Connecting to either tunnels alone results in the VPN getting disconnected.

Any pointers much appreciated!

--
Sent from the Delta quadrant using Borg technology!

Nux!
www.nux.ro
DISCLAIMER
==
This e-mail may contain privileged and confidential information which is the 
property of Accelerite, a Persistent Systems business. It is intended only for 
the use of the individual or entity to which it is addressed. If you are not 
the intended recipient, you are not authorized to read, retain, copy, print, 
distribute or use this message. If you have received this communication in 
error, please notify the sender and delete all copies of this message. 
Accelerite, a Persistent Systems business does not accept any liability for 
virus infected mails.

Re: Clean up old and obsolete branches

[Gabriel Beims Bräscher]

Thanks for the initiative, Khosrow.

+1 on removing obsolete branches.

2017-11-30 18:05 GMT-02:00 Khosrow Moossavi :

> Hi Community
>
> I would like to start the discussion around deleting old and obsolete
> branches on github repository. This will help newcomers (including myself)
> to keep track of which branches are important and which are not. And since
> almost everyone's working on their own forks there is no need to keep
> feature/bugfix/hotfix branches around in the main official repository.
>
> I've created an issue which contains full list of branches in
> GH/apache/cloudstack repo as of time of writing this email and the
> proposition of which one of them can be deleted.
>
> https://issues.apache.org/jira/browse/CLOUDSTACK-10169
>
> I would appreciate your questions, comments, suggestions.
>
> Thanks
>
> Khosrow Moossavi
>
> Cloud Infrastructure Developer
>
> CloudOps
>

Clean up old and obsolete branches

[Khosrow Moossavi]

Hi Community

I would like to start the discussion around deleting old and obsolete
branches on github repository. This will help newcomers (including myself)
to keep track of which branches are important and which are not. And since
almost everyone's working on their own forks there is no need to keep
feature/bugfix/hotfix branches around in the main official repository.

I've created an issue which contains full list of branches in
GH/apache/cloudstack repo as of time of writing this email and the
proposition of which one of them can be deleted.

https://issues.apache.org/jira/browse/CLOUDSTACK-10169

I would appreciate your questions, comments, suggestions.

Thanks

Khosrow Moossavi

Cloud Infrastructure Developer

CloudOps

Re: [PROPOSE] RM for 4.11

[Simon Weller]

Great Rohit! We'll provide as much support to you guys as we can.


From: Rohit Yadav 
Sent: Wednesday, November 29, 2017 4:14 AM
To: dev@cloudstack.apache.org
Subject: [PROPOSE] RM for 4.11

Hi All,

I’d like to put myself forward as release manager for 4.11. The 4.11
releases will be the next major version LTS release since 4.9 and will be
supported for 20 months per the LTS manifesto [2] until 1 July 2019.

Daan Hoogland and Paul Angus will assist during the process and all of us
will be the gatekeepers for reviewing/testing/merging the PRs, others will
be welcome to support as well.

As a community member, I will try to help get PRs reviewed, tested and
merged (as would everyone else I hope) but with an RM hat on I would like
to see if we can make that role less inherently life-consuming and put the
onus back on the community to get stuff done.

Here the plan:
1. As RM I put forward the freeze date of the 8th of January 2018, hoping
for community approval.
2. After the freeze date (8th Jan) until GA release, features will not be
allowed and fixes only as long as there are blocker issues outstanding.
Fixes for other issues will be individually judged on their merit and risk.
3. RM will triage/report critical and blocker bugs for 4.11 [4] and
encourage people to get them fixed.
4. RM will create RCs and start voting once blocker bugs are cleared and
baseline smoke test results are on par with previous 4.9.3.0/4.10.0.0 smoke
test results.
5. RM will allocate at least a week for branch stabilization and testing.
At the earliest, on 15th January, RM will put 4.11.0.0-rc1 for voting from
the 4.11 branch, and master will be open to accepting new features.
6. RM will repeat 3-5 as required. Voting/testing of -rc2, -rc3 and so on
will be created as required.
7. Once vote passes - RM will continue with the release procedures [1].

In conjunction with that, I also propose and put forward the date of 4.12
cut-off as 4 months [3] after GA release of 4.11 (so everyone knows when
the next one is coming hopefully giving peace of mind to those who have
features which would not make the proposed 4.11 cut off).

I’d like the community (including myself and colleagues) to:
- Up to 8th January, community members try to review, test and merge as
many fixes as possible, while super-diligent to not de-stabilize the master
branch.
- Engage with gatekeepers to get your PRs reviewed, tested and merged
(currently myself, Daan and Paul, others are welcome to engage as well). Do
not merge the PRs
- A pull request may be reverted where the author(s) are not responding and
authors may be asked to re-submit their changes after taking suitable
remedies.
- Find automated method to show (at a glance) statuses of PRs with respect
to:
  · Number of LGTMs
  · Smoke tests
  · Functional tests
  · Travis tests passing
  · Mergeability
- Perform a weekly run of a component-test matrix against the master branch
before Jan 8th cut off (based on current hypervisors including basic (KVM)
and advanced networking).
- Continue to fix broken tests.

Thoughts, feedback, comments?

[1] https://cwiki.apache.org/confluence/display/CLOUDSTACK/Release+Procedure
Release Procedure - Apache Cloudstack - Apache Software 
...
cwiki.apache.org
This page describes the steps that a release manager needs to take to perform a 
release of Apache CloudStack. (Thanks to the couchdb project for a great 
template to ...



[2] https://cwiki.apache.org/confluence/display/CLOUDSTACK/LTS
LTS - Apache Cloudstack - Apache Software 
Foundation
cwiki.apache.org
The project plans to produce the following types of releases: Regular: 
Introduce new features and enhancements. These releases are targeted for users 
who require the ...



[3] https://cwiki.apache.org/confluence/display/CLOUDSTACK/Releases
Releases - Apache Cloudstack - Apache Software 
Foundation
cwiki.apache.org
Overview. All available releases can be found on the Apache CloudStack 
project's website, on the Downloads page. The release-specific child pages in 
this wiki are not ...



[4] The current list of blocker and critical bugs currently stands as per
the following list:
https://issues.apache.org/jira/issues/?jql=project%20%3D%20CLOUDSTACK%20AND%20issuetype%20%3D%20Bug%20AND%20status%20in%20(Open%2C%20%22In%20Progress%22%2C%20Reopened)%20AND%20priority%20in%20(Blocker%2C%20Critical)%20AND%20affectedVersion%20in%20(4.10.0.0%2C%204.10.1.0%2C%204.11.0.0%2C%20Future)%20ORDER%20BY%20priority%20DESC%2C%20updated%20DESC

Regards,
Rohit Yadav

Re: Hello

[Daan Hoogland]

nice to virtually meet you again, Ernie. have fun

On Thu, Nov 30, 2017 at 11:26 AM, Nux!  wrote:

> Welcome Ernie :>
>
> --
> Sent from the Delta quadrant using Borg technology!
>
> Nux!
> www.nux.ro
>
> - Original Message -
> > From: "Rohit Yadav" 
> > To: "dev" 
> > Sent: Thursday, 30 November, 2017 09:47:17
> > Subject: Re: Hello
>
> > Welcome Ernie!
> >
> >
> > - Rohit
> >
> > 
> > From: Ernie Janse van Rensburg 
> > Sent: Thursday, November 30, 2017 2:08:57 PM
> > To: dev@cloudstack.apache.org
> > Subject: Hello
> >
> > Hi All
> >
> > I have recently joined Shape Blue as a software engineer and looking
> forward to
> > be part of the community.
> >
> > Regards
> >
> > Ernie Janse van Rensburg
> >
> > (Cape Town - South Africa)
> >
> > ernie.jvrensb...@shapeblue.com
> > www.shapeblue.com
> > ,
> > @shapeblue
> >
> >
> >
> >
> > rohit.ya...@shapeblue.com
> > www.shapeblue.com
> > 53 Chandos Place, Covent Garden, London  WC2N 4HSUK
> > @shapeblue
>



-- 
Daan

S2S VPN to AWS problems

[Nux!]

Hello,

Has anyone managed to get a s2s VPN up with an AWS VPC?
I see AWS require the setup of two tunnels which does not seem possible in ACS. 
Connecting to either tunnels alone results in the VPN getting disconnected.

Any pointers much appreciated!

--
Sent from the Delta quadrant using Borg technology!

Nux!
www.nux.ro

Re: [PROPOSE] RM for 4.11

[Milamber]

Looks good to me Rohit. Thank you and good luck

On 29/11/2017 10:14, Rohit Yadav wrote:

Hi All,

I’d like to put myself forward as release manager for 4.11. The 4.11
releases will be the next major version LTS release since 4.9 and will be
supported for 20 months per the LTS manifesto [2] until 1 July 2019.

Daan Hoogland and Paul Angus will assist during the process and all of us
will be the gatekeepers for reviewing/testing/merging the PRs, others will
be welcome to support as well.

As a community member, I will try to help get PRs reviewed, tested and
merged (as would everyone else I hope) but with an RM hat on I would like
to see if we can make that role less inherently life-consuming and put the
onus back on the community to get stuff done.

Here the plan:
1. As RM I put forward the freeze date of the 8th of January 2018, hoping
for community approval.
2. After the freeze date (8th Jan) until GA release, features will not be
allowed and fixes only as long as there are blocker issues outstanding.
Fixes for other issues will be individually judged on their merit and risk.
3. RM will triage/report critical and blocker bugs for 4.11 [4] and
encourage people to get them fixed.
4. RM will create RCs and start voting once blocker bugs are cleared and
baseline smoke test results are on par with previous 4.9.3.0/4.10.0.0 smoke
test results.
5. RM will allocate at least a week for branch stabilization and testing.
At the earliest, on 15th January, RM will put 4.11.0.0-rc1 for voting from
the 4.11 branch, and master will be open to accepting new features.
6. RM will repeat 3-5 as required. Voting/testing of -rc2, -rc3 and so on
will be created as required.
7. Once vote passes - RM will continue with the release procedures [1].

In conjunction with that, I also propose and put forward the date of 4.12
cut-off as 4 months [3] after GA release of 4.11 (so everyone knows when
the next one is coming hopefully giving peace of mind to those who have
features which would not make the proposed 4.11 cut off).

I’d like the community (including myself and colleagues) to:
- Up to 8th January, community members try to review, test and merge as
many fixes as possible, while super-diligent to not de-stabilize the master
branch.
- Engage with gatekeepers to get your PRs reviewed, tested and merged
(currently myself, Daan and Paul, others are welcome to engage as well). Do
not merge the PRs
- A pull request may be reverted where the author(s) are not responding and
authors may be asked to re-submit their changes after taking suitable
remedies.
- Find automated method to show (at a glance) statuses of PRs with respect
to:
   · Number of LGTMs
   · Smoke tests
   · Functional tests
   · Travis tests passing
   · Mergeability
- Perform a weekly run of a component-test matrix against the master branch
before Jan 8th cut off (based on current hypervisors including basic (KVM)
and advanced networking).
- Continue to fix broken tests.

Thoughts, feedback, comments?

[1] https://cwiki.apache.org/confluence/display/CLOUDSTACK/Release+Procedure
[2] https://cwiki.apache.org/confluence/display/CLOUDSTACK/LTS
[3] https://cwiki.apache.org/confluence/display/CLOUDSTACK/Releases
[4] The current list of blocker and critical bugs currently stands as per
the following list:
https://issues.apache.org/jira/issues/?jql=project%20%3D%20CLOUDSTACK%20AND%20issuetype%20%3D%20Bug%20AND%20status%20in%20(Open%2C%20%22In%20Progress%22%2C%20Reopened)%20AND%20priority%20in%20(Blocker%2C%20Critical)%20AND%20affectedVersion%20in%20(4.10.0.0%2C%204.10.1.0%2C%204.11.0.0%2C%20Future)%20ORDER%20BY%20priority%20DESC%2C%20updated%20DESC

Regards,
Rohit Yadav

Re: Leipzig 2017 slides

[Nux!]

Excellent, thanks Dag

--
Sent from the Delta quadrant using Borg technology!

Nux!
www.nux.ro

- Original Message -
> From: "Dag Sonstebo" 
> To: "dev" 
> Sent: Thursday, 30 November, 2017 12:50:30
> Subject: Re: Leipzig 2017 slides

> Sorry – I should have quantified that Lucian – check
> http://www.shapeblue.com/cloudstack-eu-user-group-roundup-leipzig-november-2017/
> - it has links to the slide decks available so far.
> 
> Regards,
> Dag Sonstebo
> Cloud Architect
> ShapeBlue
> 
> On 30/11/2017, 12:44, "Dag Sonstebo"  wrote:
> 
>Hi Lucian,
>
>I’ve contacted Thomas H – and I’ll upload his slides when he gets back to 
> me.
>Check Sebastian’s slides as well – very interesting.
>
>Regards,
>Dag Sonstebo
>Cloud Architect
>ShapeBlue
>
>On 30/11/2017, 12:34, "Nux!"  wrote:
>
>Hello,
>
>I saw Shapeblue made their slides available, what about the others?
>I was particularly interested in the Terraform related presentation as 
> I've just
>started playing with it.
>
>Regards,
>Lucian
>
>--
>Sent from the Delta quadrant using Borg technology!
>
>Nux!
>www.nux.ro
>
>
>
>dag.sonst...@shapeblue.com
>www.shapeblue.com
>53 Chandos Place, Covent Garden, London  WC2N 4HSUK
>@shapeblue
>  
> 
>
>
> 
> 
> dag.sonst...@shapeblue.com
> www.shapeblue.com
> 53 Chandos Place, Covent Garden, London  WC2N 4HSUK
> @shapeblue

Re: Leipzig 2017 slides

[Dag Sonstebo]

Sorry – I should have quantified that Lucian – check 
http://www.shapeblue.com/cloudstack-eu-user-group-roundup-leipzig-november-2017/
 - it has links to the slide decks available so far.

Regards,
Dag Sonstebo
Cloud Architect
ShapeBlue

On 30/11/2017, 12:44, "Dag Sonstebo"  wrote:

Hi Lucian,

I’ve contacted Thomas H – and I’ll upload his slides when he gets back to 
me. Check Sebastian’s slides as well – very interesting.

Regards,
Dag Sonstebo
Cloud Architect
ShapeBlue

On 30/11/2017, 12:34, "Nux!"  wrote:

Hello,

I saw Shapeblue made their slides available, what about the others?
I was particularly interested in the Terraform related presentation as 
I've just started playing with it.

Regards,
Lucian

--
Sent from the Delta quadrant using Borg technology!

Nux!
www.nux.ro



dag.sonst...@shapeblue.com 
www.shapeblue.com
53 Chandos Place, Covent Garden, London  WC2N 4HSUK
@shapeblue
  
 




dag.sonst...@shapeblue.com 
www.shapeblue.com
53 Chandos Place, Covent Garden, London  WC2N 4HSUK
@shapeblue
  
 

Re: Leipzig 2017 slides

[Dag Sonstebo]

Hi Lucian,

I’ve contacted Thomas H – and I’ll upload his slides when he gets back to me. 
Check Sebastian’s slides as well – very interesting.

Regards,
Dag Sonstebo
Cloud Architect
ShapeBlue

On 30/11/2017, 12:34, "Nux!"  wrote:

Hello,

I saw Shapeblue made their slides available, what about the others?
I was particularly interested in the Terraform related presentation as I've 
just started playing with it.

Regards,
Lucian

--
Sent from the Delta quadrant using Borg technology!

Nux!
www.nux.ro



dag.sonst...@shapeblue.com 
www.shapeblue.com
53 Chandos Place, Covent Garden, London  WC2N 4HSUK
@shapeblue
  
 

Leipzig 2017 slides

[Nux!]

Hello,

I saw Shapeblue made their slides available, what about the others?
I was particularly interested in the Terraform related presentation as I've 
just started playing with it.

Regards,
Lucian

--
Sent from the Delta quadrant using Borg technology!

Nux!
www.nux.ro

Re: [PROPOSE] RM for 4.11

[Nux!]

Hehe, good job.

--
Sent from the Delta quadrant using Borg technology!

Nux!
www.nux.ro

- Original Message -
> From: "Giles Sirett" 
> To: "dev" 
> Sent: Thursday, 30 November, 2017 11:29:18
> Subject: RE: [PROPOSE] RM for 4.11

> We built said statue at collab in Miami this year..
> https://twitter.com/shapeblue/status/936194768589254656
> 
> 
> Kind regards
> Giles
> 
> giles.sir...@shapeblue.com
> www.shapeblue.com
> 53 Chandos Place, Covent Garden, London  WC2N 4HSUK
> @shapeblue
>  
> 
> 
> 
> -Original Message-
> From: Nux! [mailto:n...@li.nux.ro]
> Sent: 29 November 2017 16:25
> To: dev 
> Subject: Re: [PROPOSE] RM for 4.11
> 
> That's great, Rohit!
> 
> I'm in talks with some folks to build you a statue. ;-) (Hope it'll turn out
> better than Ronaldo's..)
> 
> --
> Sent from the Delta quadrant using Borg technology!
> 
> Nux!
> www.nux.ro
> 
> - Original Message -
>> From: "Rohit Yadav" 
>> To: "dev" 
>> Sent: Wednesday, 29 November, 2017 10:14:54
>> Subject: [PROPOSE] RM for 4.11
> 
>> Hi All,
>> 
>> I’d like to put myself forward as release manager for 4.11. The 4.11
>> releases will be the next major version LTS release since 4.9 and will
>> be supported for 20 months per the LTS manifesto [2] until 1 July 2019.
>> 
>> Daan Hoogland and Paul Angus will assist during the process and all of
>> us will be the gatekeepers for reviewing/testing/merging the PRs,
>> others will be welcome to support as well.
>> 
>> As a community member, I will try to help get PRs reviewed, tested and
>> merged (as would everyone else I hope) but with an RM hat on I would
>> like to see if we can make that role less inherently life-consuming
>> and put the onus back on the community to get stuff done.
>> 
>> Here the plan:
>> 1. As RM I put forward the freeze date of the 8th of January 2018,
>> hoping for community approval.
>> 2. After the freeze date (8th Jan) until GA release, features will not
>> be allowed and fixes only as long as there are blocker issues outstanding.
>> Fixes for other issues will be individually judged on their merit and risk.
>> 3. RM will triage/report critical and blocker bugs for 4.11 [4] and
>> encourage people to get them fixed.
>> 4. RM will create RCs and start voting once blocker bugs are cleared
>> and baseline smoke test results are on par with previous
>> 4.9.3.0/4.10.0.0 smoke test results.
>> 5. RM will allocate at least a week for branch stabilization and testing.
>> At the earliest, on 15th January, RM will put 4.11.0.0-rc1 for voting
>> from the 4.11 branch, and master will be open to accepting new features.
>> 6. RM will repeat 3-5 as required. Voting/testing of -rc2, -rc3 and so
>> on will be created as required.
>> 7. Once vote passes - RM will continue with the release procedures [1].
>> 
>> In conjunction with that, I also propose and put forward the date of
>> 4.12 cut-off as 4 months [3] after GA release of 4.11 (so everyone
>> knows when the next one is coming hopefully giving peace of mind to
>> those who have features which would not make the proposed 4.11 cut off).
>> 
>> I’d like the community (including myself and colleagues) to:
>> - Up to 8th January, community members try to review, test and merge
>> as many fixes as possible, while super-diligent to not de-stabilize
>> the master branch.
>> - Engage with gatekeepers to get your PRs reviewed, tested and merged
>> (currently myself, Daan and Paul, others are welcome to engage as
>> well). Do not merge the PRs
>> - A pull request may be reverted where the author(s) are not
>> responding and authors may be asked to re-submit their changes after
>> taking suitable remedies.
>> - Find automated method to show (at a glance) statuses of PRs with
>> respect
>> to:
>>  · Number of LGTMs
>>  · Smoke tests
>>  · Functional tests
>>  · Travis tests passing
>>  · Mergeability
>> - Perform a weekly run of a component-test matrix against the master
>> branch before Jan 8th cut off (based on current hypervisors including
>> basic (KVM) and advanced networking).
>> - Continue to fix broken tests.
>> 
>> Thoughts, feedback, comments?
>> 
>> [1]
>> https://cwiki.apache.org/confluence/display/CLOUDSTACK/Release+Procedu
>> re [2] https://cwiki.apache.org/confluence/display/CLOUDSTACK/LTS
>> [3] https://cwiki.apache.org/confluence/display/CLOUDSTACK/Releases
>> [4] The current list of blocker and critical bugs currently stands as
>> per the following list:
>> https://issues.apache.org/jira/issues/?jql=project%20%3D%20CLOUDSTACK%
>> 20AND%20issuetype%20%3D%20Bug%20AND%20status%20in%20(Open%2C%20%22In%2
>> 0Progress%22%2C%20Reopened)%20AND%20priority%20in%20(Blocker%2C%20Crit
>> ical)%20AND%20affectedVersion%20in%20(4.10.0.0%2C%204.10.1.0%2C%204.11
>> .0.0%2C%20Future)%20ORDER%20BY%20priority%20DESC%2C%20updated%20DESC
>> 
>> Regards,
> > Rohit Yadav

RE: [PROPOSE] RM for 4.11

[Giles Sirett]

We built said statue at collab in Miami this year..
https://twitter.com/shapeblue/status/936194768589254656


Kind regards
Giles

giles.sir...@shapeblue.com 
www.shapeblue.com
53 Chandos Place, Covent Garden, London  WC2N 4HSUK
@shapeblue
  
 


-Original Message-
From: Nux! [mailto:n...@li.nux.ro] 
Sent: 29 November 2017 16:25
To: dev 
Subject: Re: [PROPOSE] RM for 4.11

That's great, Rohit!

I'm in talks with some folks to build you a statue. ;-) (Hope it'll turn out 
better than Ronaldo's..)

--
Sent from the Delta quadrant using Borg technology!

Nux!
www.nux.ro

- Original Message -
> From: "Rohit Yadav" 
> To: "dev" 
> Sent: Wednesday, 29 November, 2017 10:14:54
> Subject: [PROPOSE] RM for 4.11

> Hi All,
> 
> I’d like to put myself forward as release manager for 4.11. The 4.11 
> releases will be the next major version LTS release since 4.9 and will 
> be supported for 20 months per the LTS manifesto [2] until 1 July 2019.
> 
> Daan Hoogland and Paul Angus will assist during the process and all of 
> us will be the gatekeepers for reviewing/testing/merging the PRs, 
> others will be welcome to support as well.
> 
> As a community member, I will try to help get PRs reviewed, tested and 
> merged (as would everyone else I hope) but with an RM hat on I would 
> like to see if we can make that role less inherently life-consuming 
> and put the onus back on the community to get stuff done.
> 
> Here the plan:
> 1. As RM I put forward the freeze date of the 8th of January 2018, 
> hoping for community approval.
> 2. After the freeze date (8th Jan) until GA release, features will not 
> be allowed and fixes only as long as there are blocker issues outstanding.
> Fixes for other issues will be individually judged on their merit and risk.
> 3. RM will triage/report critical and blocker bugs for 4.11 [4] and 
> encourage people to get them fixed.
> 4. RM will create RCs and start voting once blocker bugs are cleared 
> and baseline smoke test results are on par with previous 
> 4.9.3.0/4.10.0.0 smoke test results.
> 5. RM will allocate at least a week for branch stabilization and testing.
> At the earliest, on 15th January, RM will put 4.11.0.0-rc1 for voting 
> from the 4.11 branch, and master will be open to accepting new features.
> 6. RM will repeat 3-5 as required. Voting/testing of -rc2, -rc3 and so 
> on will be created as required.
> 7. Once vote passes - RM will continue with the release procedures [1].
> 
> In conjunction with that, I also propose and put forward the date of 
> 4.12 cut-off as 4 months [3] after GA release of 4.11 (so everyone 
> knows when the next one is coming hopefully giving peace of mind to 
> those who have features which would not make the proposed 4.11 cut off).
> 
> I’d like the community (including myself and colleagues) to:
> - Up to 8th January, community members try to review, test and merge 
> as many fixes as possible, while super-diligent to not de-stabilize 
> the master branch.
> - Engage with gatekeepers to get your PRs reviewed, tested and merged 
> (currently myself, Daan and Paul, others are welcome to engage as 
> well). Do not merge the PRs
> - A pull request may be reverted where the author(s) are not 
> responding and authors may be asked to re-submit their changes after 
> taking suitable remedies.
> - Find automated method to show (at a glance) statuses of PRs with 
> respect
> to:
>  · Number of LGTMs
>  · Smoke tests
>  · Functional tests
>  · Travis tests passing
>  · Mergeability
> - Perform a weekly run of a component-test matrix against the master 
> branch before Jan 8th cut off (based on current hypervisors including 
> basic (KVM) and advanced networking).
> - Continue to fix broken tests.
> 
> Thoughts, feedback, comments?
> 
> [1] 
> https://cwiki.apache.org/confluence/display/CLOUDSTACK/Release+Procedu
> re [2] https://cwiki.apache.org/confluence/display/CLOUDSTACK/LTS
> [3] https://cwiki.apache.org/confluence/display/CLOUDSTACK/Releases
> [4] The current list of blocker and critical bugs currently stands as 
> per the following list:
> https://issues.apache.org/jira/issues/?jql=project%20%3D%20CLOUDSTACK%
> 20AND%20issuetype%20%3D%20Bug%20AND%20status%20in%20(Open%2C%20%22In%2
> 0Progress%22%2C%20Reopened)%20AND%20priority%20in%20(Blocker%2C%20Crit
> ical)%20AND%20affectedVersion%20in%20(4.10.0.0%2C%204.10.1.0%2C%204.11
> .0.0%2C%20Future)%20ORDER%20BY%20priority%20DESC%2C%20updated%20DESC
> 
> Regards,
> Rohit Yadav

Re: Hello

[Nux!]

Welcome Ernie :>

--
Sent from the Delta quadrant using Borg technology!

Nux!
www.nux.ro

- Original Message -
> From: "Rohit Yadav" 
> To: "dev" 
> Sent: Thursday, 30 November, 2017 09:47:17
> Subject: Re: Hello

> Welcome Ernie!
> 
> 
> - Rohit
> 
> 
> From: Ernie Janse van Rensburg 
> Sent: Thursday, November 30, 2017 2:08:57 PM
> To: dev@cloudstack.apache.org
> Subject: Hello
> 
> Hi All
> 
> I have recently joined Shape Blue as a software engineer and looking forward 
> to
> be part of the community.
> 
> Regards
> 
> Ernie Janse van Rensburg
> 
> (Cape Town - South Africa)
> 
> ernie.jvrensb...@shapeblue.com
> www.shapeblue.com
> ,
> @shapeblue
> 
> 
> 
> 
> rohit.ya...@shapeblue.com
> www.shapeblue.com
> 53 Chandos Place, Covent Garden, London  WC2N 4HSUK
> @shapeblue

Re: Issue with Opensaml and Self-Signed Certificates

[Rohit Yadav]

Harika,


I'm planning to run some tests by end of next week, I'll keep you posted.

Meanwhile, try to debug the issue, attach a debugger and see what is causing 
the failure and use one of the publicly available SAML idp providers, the issue 
could also be related to your SAML sp/idp configuration.


Regards.


From: Harika Punna 
Sent: Thursday, November 30, 2017 11:03:05 AM
To: Rohit Yadav; dev@cloudstack.apache.org
Subject: Re: Issue with Opensaml and Self-Signed Certificates


Rohit,



I have tried the same thing on latest master, even on that I could the same 
dependencies.



Are you using opensaml of version 2.6.4? Have you faced this issue when working 
with self-signed certificates.



I would appreciate any help on this.







Thanks,

Harika.



From: Rohit Yadav 
Date: Wednesday, 29 November 2017 at 1:09 PM
To: "dev@cloudstack.apache.org" , Harika Punna 

Subject: Re: Issue with Opensaml and Self-Signed Certificates



Harika, Can you test the latest master and see if you can reproduce the error?

Get Outlook for Android



rohit.ya...@shapeblue.com
www.shapeblue.com
@shapeblue






From: Harika Punna 
Sent: Wednesday, November 29, 2017 10:57:53 AM
To: Rohit Yadav; dev@cloudstack.apache.org
Subject: Re: Issue with Opensaml and Self-Signed Certificates



Rohit,



I was trying to configure ACS with ADFS using saml plugin.



I find the not-yet-commons-ssl.jar in the opensaml-2.6.4 dependency of 
plugins/user-authentication/saml2/pom.xml



The dependency tree of not-yet-commons-ssl is as follows-

opensaml-2.6.4 > openws-1.5.4 > xmltooling-1.4.4 > not-yet-commons-ssl-0.3.9



May I know which version of opensaml are you using?





Thanks,

Harika.





From: Rohit Yadav 
Date: Tuesday, 28 November 2017 at 6:56 PM
To: Harika Punna , "dev@cloudstack.apache.org" 

Subject: Re: Issue with Opensaml and Self-Signed Certificates



Harika,



Can you share what exactly are you doing, perhaps you can submit a PR and ask 
for review?

I did not find any usage of a KeyStoreBuilder class in current master, nor 
we've a not-yet-commons-ssl dependency in current codebase.



Regard.

rohit.ya...@shapeblue.com
www.shapeblue.com
@shapeblue






From: Harika Punna 
Sent: Tuesday, November 28, 2017 2:13:33 PM
To: dev@cloudstack.apache.org; Rohit Yadav
Subject: Re: Issue with Opensaml and Self-Signed Certificates



Hi Rohit,

Could you please help me on this?

-Harika.



On 27/11/17, 4:26 PM, "Harika Punna"  wrote:

Hi,


When I use Opensaml on 4.10 with the self-signed certificates I get the 
following error, though the configuration for the opensaml and ssl is proper. 
It works fine if I debug and supply the password of the keystore in 
KeyStoreBuilder class, which is in not-yet-commons-ssl.jar.


Has anyone faced this issue, I tried with different versions of opensaml 
but nothing worked. Found similar issue on SO at [1], but none of them helped.



java.io.IOException: DerInputStream.getLength(): lengthTag=109, too big.

at sun.security.util.DerInputStream.getLength(DerInputStream.java:561)

at sun.security.util.DerValue.init(DerValue.java:365)

at sun.security.util.DerValue.(DerValue.java:320)

at sun.security.pkcs12.PKCS12KeyStore.engineLoad(PKCS12KeyStore.java:1914)

at java.security.KeyStore.load(KeyStore.java:1445)

at org.apache.commons.ssl.KeyStoreBuilder.tryJKS(KeyStoreBuilder.java:450)

at org.apache.commons.ssl.KeyStoreBuilder.parse(KeyStoreBuilder.java:416)

at org.apache.commons.ssl.TrustMaterial.(TrustMaterial.java:207)

at org.apache.commons.ssl.TrustMaterial.(TrustMaterial.java:160)

at org.apache.commons.ssl.TrustMaterial.(TrustMaterial.java:165)

at org.apache.commons.ssl.TrustMaterial.(TrustMaterial.java:170)

at org.apache.commons.ssl.TrustMaterial.(TrustMaterial.java:83)

at 
org.opensaml.xml.security.x509.X509Util.decodeCertificate(X509Util.java:359)

at 
org.opensaml.xml.security.keyinfo.KeyInfoHelper.getCertificate(KeyInfoHelper.java:201)

at 
org.opensaml.xml.security.keyinfo.KeyInfoHelper.getCertificates(KeyInfoHelper.java:176)

at 
org.opensaml.xml.security.keyinfo.KeyInfoHelper.getCertificates(KeyInfoHelper.java:150)

at 
org.apache.cloudstack.saml.SAML2AuthManagerImpl.addIdpToMap(SAML2AuthManagerImpl.java:293)

at 
org.apache.cloudstack.saml.SAML2AuthManagerImpl.discoverAndAddIdp(SAML2AuthManagerImpl.java:323)

at 
org.apache.cloudstack.saml.SAML2AuthManagerImpl.access$200(SAML2AuthManagerImpl.java:92)

at 

Re: Hello

[Rohit Yadav]

Welcome Ernie!


- Rohit


From: Ernie Janse van Rensburg 
Sent: Thursday, November 30, 2017 2:08:57 PM
To: dev@cloudstack.apache.org
Subject: Hello

Hi All

I have recently joined Shape Blue as a software engineer and looking forward to 
be part of the community.

Regards

Ernie Janse van Rensburg

(Cape Town - South Africa)

ernie.jvrensb...@shapeblue.com
www.shapeblue.com
,
@shapeblue




rohit.ya...@shapeblue.com 
www.shapeblue.com
53 Chandos Place, Covent Garden, London  WC2N 4HSUK
@shapeblue
  
 

Re: Hello

[Erik Weber]

Welcome on board :-)

On Thu, Nov 30, 2017 at 9:38 AM, Ernie Janse van Rensburg
 wrote:
> Hi All
>
> I have recently joined Shape Blue as a software engineer and looking forward 
> to be part of the community.
>
> Regards
>
> Ernie Janse van Rensburg
>
> (Cape Town - South Africa)
>
> ernie.jvrensb...@shapeblue.com
> www.shapeblue.com
> ,
> @shapeblue
>
>
>

Hello

[Ernie Janse van Rensburg]

Hi All

I have recently joined Shape Blue as a software engineer and looking forward to 
be part of the community.

Regards

Ernie Janse van Rensburg

(Cape Town - South Africa)

ernie.jvrensb...@shapeblue.com 
www.shapeblue.com
,   
@shapeblue