You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@bigtop.apache.org by Konstantin Boudnik <co...@apache.org> on 2016/02/09 19:07:20 UTC
Re: https://ci.bigtop.org
Thanks for starting on this, Olaf.
Andres Purtell is VP right now, but I don't think we need to deal with any of
the commercial CAs, nor get INFRA, Ross or ASF budget into this. I'd recommend
to use EFF "Let’s Encrypt" initiative [1] to get the SSL certificate for free and
be done with it. Check [2] for more info
[1] https://letsencrypt.org/
[2] https://www.eff.org/deeplinks/2015/12/lets-encrypt-project-comes-fruition-2015-review
I will comment on the INFRA ticket
Cos
On Tue, Feb 09, 2016 at 06:43PM, Olaf Flebbe wrote:
> Hi
>
> I asked INFRA wether it is possible to get a SSL Certificate for our CI.
>
> This is in my opinion necessary to protect the credentials of the CI against
> random hackers. (I accidentially used the CI on a open Wifi at FOSDEM,
> oops).
>
> Please see INFRA-11187 .Point is that bigtop VP (cos?, rvs?) has to talk
> with Apache President (currently Ross Gardler) about getting the cost of
> this cert budgeted.
>
> Unsure how to proceed:
>
> Other possibilities could be that we find a sponsor for that.
>
> Other possibilities which comes in my mind now is using the free Let's
> Encrypt! https://letsencrypt.org certificates . I do not know if we can use
> it.
>
> Least possibility to use a private (snakeoil) certificate, at least the
> traffic is crypted, but on the other side users get an ugly warning page.
>
> What do you think?
>
> Cheers,
> Olaf
Re: https://ci.bigtop.org
Posted by Olaf Flebbe <of...@oflebbe.de>.
Hi
Let's encrypt is a little bit weird to use. Have to stop jenkins in order to get port 80 ... and it does not support amazon linux welll.
Olaf
> Am 09.02.2016 um 19:07 schrieb Konstantin Boudnik <co...@apache.org>:
>
> Thanks for starting on this, Olaf.
>
> Andres Purtell is VP right now, but I don't think we need to deal with any of
> the commercial CAs, nor get INFRA, Ross or ASF budget into this. I'd recommend
> to use EFF "Let’s Encrypt" initiative [1] to get the SSL certificate for free and
> be done with it. Check [2] for more info
>
> [1] https://letsencrypt.org/
> [2] https://www.eff.org/deeplinks/2015/12/lets-encrypt-project-comes-fruition-2015-review
>
> I will comment on the INFRA ticket
> Cos
>
> On Tue, Feb 09, 2016 at 06:43PM, Olaf Flebbe wrote:
>> Hi
>>
>> I asked INFRA wether it is possible to get a SSL Certificate for our CI.
>>
>> This is in my opinion necessary to protect the credentials of the CI against
>> random hackers. (I accidentially used the CI on a open Wifi at FOSDEM,
>> oops).
>>
>> Please see INFRA-11187 .Point is that bigtop VP (cos?, rvs?) has to talk
>> with Apache President (currently Ross Gardler) about getting the cost of
>> this cert budgeted.
>>
>> Unsure how to proceed:
>>
>> Other possibilities could be that we find a sponsor for that.
>>
>> Other possibilities which comes in my mind now is using the free Let's
>> Encrypt! https://letsencrypt.org certificates . I do not know if we can use
>> it.
>>
>> Least possibility to use a private (snakeoil) certificate, at least the
>> traffic is crypted, but on the other side users get an ugly warning page.
>>
>> What do you think?
>>
>> Cheers,
>> Olaf
>
>
Re: https://ci.bigtop.org
Posted by Konstantin Boudnik <co...@apache.org>.
Good stuff!
On Tue, Feb 09, 2016 at 11:15PM, Olaf Flebbe wrote:
> Pfff this was tough
>
> https://ci.bigtop.apache.org is running now !!!
>
> I have to go to bed now. Short intro:
>
> Apache reverse proxy config for jenkins in /etc/httpd/conf.d/ssl.conf
> Certificates configured in the same file. This file should be stable now.
> A reload page /var/www/html/index.html
>
> Apache has now way to much modules
>
> ec2-user@master:
>
> Jenkins is run as docker instance but now with port 8080 redirected to 8080
> (start with sudo startjenkins.sh
>
>
> Recreating certs (needed every month!)
>
> sudo docker run --rm -i -t -p 80 -p 443:443 -v "/home/ec2-user/etc:/etc/letsencrypt" letsencrypt certonly --standalone --email dev@bigtop.apache.org -d ci.bigtop.apache.org
>
> New certs in ~/etc (as Root! yes! Root! we need root here!)
>
> ...
>
> Over and out
> Olaf
>
>
>
>
Re: https://ci.bigtop.org
Posted by Faraaz Sareshwala <fs...@quantcast.com>.
Yes, thanks! I’ve closed out the ticket (BIGTOP-2304) regarding this.
On 2/9/16, 3:11 PM, "Jay Vyas" <ja...@gmail.com> wrote:
>Thanks Olaf !
>
>> On Feb 9, 2016, at 5:15 PM, Olaf Flebbe <of...@oflebbe.de> wrote:
>>
>> Pfff this was tough
>>
>> https://ci.bigtop.apache.org is running now !!!
>>
>> I have to go to bed now. Short intro:
>>
>> Apache reverse proxy config for jenkins in /etc/httpd/conf.d/ssl.conf
>> Certificates configured in the same file. This file should be stable now.
>> A reload page /var/www/html/index.html
>>
>> Apache has now way to much modules
>>
>> ec2-user@master:
>>
>> Jenkins is run as docker instance but now with port 8080 redirected to 8080
>> (start with sudo startjenkins.sh
>>
>>
>> Recreating certs (needed every month!)
>>
>> sudo docker run --rm -i -t -p 80 -p 443:443 -v "/home/ec2-user/etc:/etc/letsencrypt" letsencrypt certonly --standalone --email dev@bigtop.apache.org -d ci.bigtop.apache.org
>>
>> New certs in ~/etc (as Root! yes! Root! we need root here!)
>>
>> ...
>>
>> Over and out
>> Olaf
>>
>>
>>
>>
Re: https://ci.bigtop.org
Posted by Jay Vyas <ja...@gmail.com>.
Thanks Olaf !
> On Feb 9, 2016, at 5:15 PM, Olaf Flebbe <of...@oflebbe.de> wrote:
>
> Pfff this was tough
>
> https://ci.bigtop.apache.org is running now !!!
>
> I have to go to bed now. Short intro:
>
> Apache reverse proxy config for jenkins in /etc/httpd/conf.d/ssl.conf
> Certificates configured in the same file. This file should be stable now.
> A reload page /var/www/html/index.html
>
> Apache has now way to much modules
>
> ec2-user@master:
>
> Jenkins is run as docker instance but now with port 8080 redirected to 8080
> (start with sudo startjenkins.sh
>
>
> Recreating certs (needed every month!)
>
> sudo docker run --rm -i -t -p 80 -p 443:443 -v "/home/ec2-user/etc:/etc/letsencrypt" letsencrypt certonly --standalone --email dev@bigtop.apache.org -d ci.bigtop.apache.org
>
> New certs in ~/etc (as Root! yes! Root! we need root here!)
>
> ...
>
> Over and out
> Olaf
>
>
>
>
Re: https://ci.bigtop.org
Posted by "김영우 (YoungWoo Kim)" <yw...@apache.org>.
Awesome! thanks Olaf !!
2016년 2월 10일 수요일, Olaf Flebbe<of...@oflebbe.de>님이 작성한 메시지:
> Pfff this was tough
>
> https://ci.bigtop.apache.org is running now !!!
>
> I have to go to bed now. Short intro:
>
> Apache reverse proxy config for jenkins in /etc/httpd/conf.d/ssl.conf
> Certificates configured in the same file. This file should be stable now.
> A reload page /var/www/html/index.html
>
> Apache has now way to much modules
>
> ec2-user@master:
>
> Jenkins is run as docker instance but now with port 8080 redirected to 8080
> (start with sudo startjenkins.sh
>
>
> Recreating certs (needed every month!)
>
> sudo docker run --rm -i -t -p 80 -p 443:443 -v
> "/home/ec2-user/etc:/etc/letsencrypt" letsencrypt certonly --standalone
> --email dev@bigtop.apache.org <javascript:;> -d ci.bigtop.apache.org
>
> New certs in ~/etc (as Root! yes! Root! we need root here!)
>
> ...
>
> Over and out
> Olaf
>
>
>
>
>
Re: https://ci.bigtop.org
Posted by Olaf Flebbe <of...@oflebbe.de>.
Hi Evans,
you are right. port 50000 is for windows slave processes.
Olaf
> Am 11.02.2016 um 01:23 schrieb Evans Ye <ev...@apache.org>:
>
> Did you run into any issuse w/o 50000 port? I think slave just need to be
> sshed.
> 2016年2月11日 上午3:11於 "Olaf Flebbe" <of...@oflebbe.de>寫道:
>
>> Thanks all !
>>> Am 10.02.2016 um 01:51 schrieb Roman Shaposhnik <ro...@shaposhnik.org>:
>>>
>>> This is really awesome! Thank you Olaf! Btw, any chance any of this
>>> can be documented for less advanced among us? ;-)
>>
>> I added an advanced chapter to the excellent guide by evans in our
>> https://cwiki.apache.org/confluence/display/BIGTOP/Bigtop+CI+Setup+Guide
>>
>> This way I can look it up myself ;-)
>>
>> (Evans: I added -p 50000:50000 to the docker command line in you doc.
>> AFAIK this is needed for external slaves?)
>>
>> This is not exactly the same config documented we have on our CI, will
>> align it later.
>>
>> Olaf
>>
>>
Re: https://ci.bigtop.org
Posted by Evans Ye <ev...@apache.org>.
Did you run into any issuse w/o 50000 port? I think slave just need to be
sshed.
2016年2月11日 上午3:11於 "Olaf Flebbe" <of...@oflebbe.de>寫道:
> Thanks all !
> > Am 10.02.2016 um 01:51 schrieb Roman Shaposhnik <ro...@shaposhnik.org>:
> >
> > This is really awesome! Thank you Olaf! Btw, any chance any of this
> > can be documented for less advanced among us? ;-)
>
> I added an advanced chapter to the excellent guide by evans in our
> https://cwiki.apache.org/confluence/display/BIGTOP/Bigtop+CI+Setup+Guide
>
> This way I can look it up myself ;-)
>
> (Evans: I added -p 50000:50000 to the docker command line in you doc.
> AFAIK this is needed for external slaves?)
>
> This is not exactly the same config documented we have on our CI, will
> align it later.
>
> Olaf
>
>
Re: https://ci.bigtop.org
Posted by Olaf Flebbe <of...@oflebbe.de>.
Thanks all !
> Am 10.02.2016 um 01:51 schrieb Roman Shaposhnik <ro...@shaposhnik.org>:
>
> This is really awesome! Thank you Olaf! Btw, any chance any of this
> can be documented for less advanced among us? ;-)
I added an advanced chapter to the excellent guide by evans in our https://cwiki.apache.org/confluence/display/BIGTOP/Bigtop+CI+Setup+Guide
This way I can look it up myself ;-)
(Evans: I added -p 50000:50000 to the docker command line in you doc. AFAIK this is needed for external slaves?)
This is not exactly the same config documented we have on our CI, will align it later.
Olaf
Re: https://ci.bigtop.org
Posted by Evans Ye <ev...@apache.org>.
Thanks Olaf!
You just finished the last mile of our CI infra. Appreciate that!
2016年2月10日 上午8:51於 "Roman Shaposhnik" <ro...@shaposhnik.org>寫道:
> This is really awesome! Thank you Olaf! Btw, any chance any of this
> can be documented for less advanced among us? ;-)
>
> Thanks,
> Roman.
>
> On Tue, Feb 9, 2016 at 2:15 PM, Olaf Flebbe <of...@oflebbe.de> wrote:
> > Pfff this was tough
> >
> > https://ci.bigtop.apache.org is running now !!!
> >
> > I have to go to bed now. Short intro:
> >
> > Apache reverse proxy config for jenkins in /etc/httpd/conf.d/ssl.conf
> > Certificates configured in the same file. This file should be stable now.
> > A reload page /var/www/html/index.html
> >
> > Apache has now way to much modules
> >
> > ec2-user@master:
> >
> > Jenkins is run as docker instance but now with port 8080 redirected to
> 8080
> > (start with sudo startjenkins.sh
> >
> >
> > Recreating certs (needed every month!)
> >
> > sudo docker run --rm -i -t -p 80 -p 443:443 -v
> "/home/ec2-user/etc:/etc/letsencrypt" letsencrypt certonly --standalone
> --email dev@bigtop.apache.org -d ci.bigtop.apache.org
> >
> > New certs in ~/etc (as Root! yes! Root! we need root here!)
> >
> > ...
> >
> > Over and out
> > Olaf
> >
> >
> >
> >
>
Re: https://ci.bigtop.org
Posted by Roman Shaposhnik <ro...@shaposhnik.org>.
This is really awesome! Thank you Olaf! Btw, any chance any of this
can be documented for less advanced among us? ;-)
Thanks,
Roman.
On Tue, Feb 9, 2016 at 2:15 PM, Olaf Flebbe <of...@oflebbe.de> wrote:
> Pfff this was tough
>
> https://ci.bigtop.apache.org is running now !!!
>
> I have to go to bed now. Short intro:
>
> Apache reverse proxy config for jenkins in /etc/httpd/conf.d/ssl.conf
> Certificates configured in the same file. This file should be stable now.
> A reload page /var/www/html/index.html
>
> Apache has now way to much modules
>
> ec2-user@master:
>
> Jenkins is run as docker instance but now with port 8080 redirected to 8080
> (start with sudo startjenkins.sh
>
>
> Recreating certs (needed every month!)
>
> sudo docker run --rm -i -t -p 80 -p 443:443 -v "/home/ec2-user/etc:/etc/letsencrypt" letsencrypt certonly --standalone --email dev@bigtop.apache.org -d ci.bigtop.apache.org
>
> New certs in ~/etc (as Root! yes! Root! we need root here!)
>
> ...
>
> Over and out
> Olaf
>
>
>
>
Re: https://ci.bigtop.org
Posted by Olaf Flebbe <of...@oflebbe.de>.
Pfff this was tough
https://ci.bigtop.apache.org is running now !!!
I have to go to bed now. Short intro:
Apache reverse proxy config for jenkins in /etc/httpd/conf.d/ssl.conf
Certificates configured in the same file. This file should be stable now.
A reload page /var/www/html/index.html
Apache has now way to much modules
ec2-user@master:
Jenkins is run as docker instance but now with port 8080 redirected to 8080
(start with sudo startjenkins.sh
Recreating certs (needed every month!)
sudo docker run --rm -i -t -p 80 -p 443:443 -v "/home/ec2-user/etc:/etc/letsencrypt" letsencrypt certonly --standalone --email dev@bigtop.apache.org -d ci.bigtop.apache.org
New certs in ~/etc (as Root! yes! Root! we need root here!)
...
Over and out
Olaf