You are viewing a plain text version of this content. The canonical link for it is here.
Posted to fortress@directory.apache.org by Chris Pike <cl...@psu.edu> on 2015/11/19 16:27:50 UTC
Fortress Build Process / Quickstarts
Shawn,
I have been looking at the fortress build process and install scripts. In the past, we have built ansible roles (https://github.com/PennState/fortress-in-a-box), but they still rely on the ant tasks. One of the ideas I had was to build out the ansible roles to install and configure fortress (openldap, tomcat, core, commander, etc...) without relying on ant. Then use these roles to build docker images. This would give users the option of running ansible directly, running ansible with vagrant, or running already built docker images. The downside of this approach is that while docker can be run on windows, ansible can not run on windows as a control machine. Is running on windows a goal of the project? (could still be done, would just be more manual process) Thoughts on this approach?
Thanks,
~Chris Pike
Re: Fortress Build Process / Quickstarts
Posted by Shawn McKinney <sm...@apache.org>.
> On Nov 19, 2015, at 11:41 AM, Chris Pike <cl...@psu.edu> wrote:
>
> I saw your comment about the quickstart in the other email and decided it was a good time to bring this up. If we build docker images, that would be an easy way to support testing on windows. I'll look into building out / updating the existing the ansible roles.
>
> Related to this, I've noticed that fortress-core version 1.0-RC40 is in maven central, but RC41 and the other projects are not, is this on the to do list?
Yes definitely. I would like to get RC41 released by the end of the year and if it proves stable do a 1.0 shortly thereafter.
Shawn
Re: Fortress Build Process / Quickstarts
Posted by Chris Pike <cl...@psu.edu>.
I saw your comment about the quickstart in the other email and decided it was a good time to bring this up. If we build docker images, that would be an easy way to support testing on windows. I'll look into building out / updating the existing the ansible roles.
Related to this, I've noticed that fortress-core version 1.0-RC40 is in maven central, but RC41 and the other projects are not, is this on the to do list?
----- Original Message -----
From: "Shawn McKinney" <sm...@apache.org>
To: fortress@directory.apache.org
Sent: Thursday, November 19, 2015 11:57:22 AM
Subject: Re: Fortress Build Process / Quickstarts
> On Nov 19, 2015, at 9:27 AM, Chris Pike <cl...@psu.edu> wrote:
>
>
> I have been looking at the fortress build process and install scripts. In the past, we have built ansible roles (https://github.com/PennState/fortress-in-a-box), but they still rely on the ant tasks. One of the ideas I had was to build out the ansible roles to install and configure fortress (openldap, tomcat, core, commander, etc...) without relying on ant. Then use these roles to build docker images. This would give users the option of running ansible directly, running ansible with vagrant, or running already built docker images. The downside of this approach is that while docker can be run on windows, ansible can not run on windows as a control machine. Is running on windows a goal of the project? (could still be done, would just be more manual process) Thoughts on this approach?
Hello Chris,
I’m not too concerned about supporting windows for production environments although I think it good to support for developer testing on their local machines. So my quick answer is ‘yes' I think your approach is valid. Your timing is good as well because we need to recreate the fortress quickstart packages and your ideas play into that.
Thanks
Shawn
Re: Fortress Build Process / Quickstarts
Posted by Shawn McKinney <sm...@apache.org>.
> On Nov 19, 2015, at 9:27 AM, Chris Pike <cl...@psu.edu> wrote:
>
>
> I have been looking at the fortress build process and install scripts. In the past, we have built ansible roles (https://github.com/PennState/fortress-in-a-box), but they still rely on the ant tasks. One of the ideas I had was to build out the ansible roles to install and configure fortress (openldap, tomcat, core, commander, etc...) without relying on ant. Then use these roles to build docker images. This would give users the option of running ansible directly, running ansible with vagrant, or running already built docker images. The downside of this approach is that while docker can be run on windows, ansible can not run on windows as a control machine. Is running on windows a goal of the project? (could still be done, would just be more manual process) Thoughts on this approach?
Hello Chris,
I’m not too concerned about supporting windows for production environments although I think it good to support for developer testing on their local machines. So my quick answer is ‘yes' I think your approach is valid. Your timing is good as well because we need to recreate the fortress quickstart packages and your ideas play into that.
Thanks
Shawn