Hi Stefan,

Thanks for your great inputs. What I will work out is a building approach using 
docker and in the docker file it will get everything downloaded, installed, and 
configured automatically. The resultant docker image won't be pushed to any 
docker hub repository for public download. I thought the way isn't much 
different from the way I do by manually, so I thought the Oracle Java license 
won't be a problem. 

I agree that it would be good to have a Kerby docker image to be public out for 
others to experiment Kerby easily. In the case we do need to be careful and 
ensure only licensed softwares are installed in the box. Sometime later we can 
work on that and provide such a docker image for the purpose, and then let you 
know and please help. Thanks.

Regards,
Kai

-----Original Message-----
From: Stefan Seelmann [mailto:[email protected]] 
Sent: Sunday, December 13, 2015 8:50 PM
To: [email protected]
Subject: Re: FW: [jira] [Created] (DIRKRB-500) Docker building support for 
integration tests

On 12/13/2015 10:31 AM, Zheng, Kai wrote:
> Any thought? I plan to get the initial job done recently because I need a MIT 
> Kerberos setup for some bug shooting but don't want to mess my server. Thanks!

Hi Kai,

We already use Docker for integration testing. For Fortress I created an image 
that contains preconfigured OpenLDAP, plase see [1] for the Dockerfile and 
docs, and [2] for the Jenkins job (which is failing for some days, I'll check). 
For ApacheDS we use existing images to test the installers, see [5] for the 
Jenkins job.

I also created a group at Docker Hub [3], feel free to push your images there. 
I'll can add you to the group, just send me your Docker Hub account name.

Regarding Oracle Java: License wise that may be problematic. The official Java 
Docker images only contain OpenJDK, see [4] for an explaination. There exist 
some personal Oracle Java images on Docker hub though.

Kind Regards,
Stefan

[1] https://github.com/apache/directory-fortress-core/tree/master/docker
[2]
https://builds.apache.org/view/A-D/view/Directory/job/dir-fortress-core-docker-test/
[3] https://hub.docker.com/u/apachedirectory/
[4] https://hub.docker.com/_/java/
[5]
https://builds.apache.org/view/A-D/view/Directory/job/dir-apacheds-docker-installers

> 
> -----Original Message-----
> From: Kai Zheng (JIRA) [mailto:[email protected]]
> Sent: Sunday, December 13, 2015 5:27 PM
> To: [email protected]
> Subject: [jira] [Created] (DIRKRB-500) Docker building support for 
> integration tests
> 
> Kai Zheng created DIRKRB-500:
> --------------------------------
> 
>              Summary: Docker building support for integration tests
>                  Key: DIRKRB-500
>                  URL: https://issues.apache.org/jira/browse/DIRKRB-500
>              Project: Directory Kerberos
>           Issue Type: Sub-task
>             Reporter: Kai Zheng
>             Assignee: Kai Zheng
> 
> 
> This is to propose and support to allow building Kerby in a docker container 
> with all kinds of facilities well prepared for integration tests. Somethings 
> like:
> 1. Oracle Java (1.7 and/or 1.8);
> 2.  MIT Kerberos (client and KDC);
> 3. Well configured PKINIT;
> 4. Necessary development tool chains (JDK, GCC/GDB and etc.) for debugging 
> failed integration test.
> 
> Initially, Linux is considered for the docker container environment.
> 
> Additionally but related, some time consuming tests would be marked as 
> integration tests and targeted to run in the docker setup. For frequently 
> development building, such tests are not to run to speed up. The integration 
> tests could be run in the Jenkins building daily.
> 
> 
> 
> --
> This message was sent by Atlassian JIRA
> (v6.3.4#6332)
> 

Reply via email to