Hi Juhan, Awasum and Ebenezer, Concerning the RSA key, the is a walk around that works just fine for now but I just realized it doesn't scale. ( I will really like to get more ideas on this) Using a service to provide the Keys is a little tricky because this service has to provide these keys in a secure way to services that are not up and running. Yes, you have to provide the key before the Fineract services startup. I have an idea on how it could be implemented, it a little rough in my head now, but I open to your own ideas.
Concerning publishing the built Fineract library to an artifactory, It's not really needed for the deployment with Kubernetes or Docker. I am glad that Juhan is working because that's the next EXCITING step after deploying the system. Yannick thanks for the input on code quality checks, I agree with you. I also think that should be added to the Travis build. Ebenezer asked so many questions, cool... ok *:-D* There is no Google cloud image registry, I am not sure why we will need that if we can use the public Docker registry. I haven't spoken of Openshift or seen a scenario where Mifos/Apache will want to deploy there. But maybe you thought of something I am happy to get more ideas. Docker compose works on premise, I didn't say it doesn't work in the cloud. Docker swarm doesn't work 'cause it is not scaling properly (like I said in the first paragraph). Concerning the part about you pulling from DockerHub to GKE and it not working properly: The images are not Mifos' DockerHub account and please can you be specific about what you have done and what precisely doesn't work. P.S: the Kubernetes images build but I haven't implemented a script for them to provision. The CI/CD goes far beyond just building and pushing to an artifactory or an image registry. It's implementing a pipeline between the code repository and the deployment environment where whenever the is a code update in a Fineract library Cassandra or a service like Customer, we have an automation engine that validates the code, all the necessary unit, component and integration test before updating the artifact or image repositories. Then we have the deployment environment automatically pull and deploy this. I hope I answered all the questions. Please feel free to reach if you have any more questions. Regards, Courage. <https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=webmail&utm_term=icon> Virus-free. www.avast.com <https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=webmail&utm_term=link> <#DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2> On Sun, Apr 7, 2019 at 7:23 PM Juhan Aasaru <[email protected]> wrote: > Hi Ebenezer, > > I have a plan to use travis-ci for building fineract-cn projects and > publish the snapshot artifacts to jfrog artifactory. > More info about my plan: > > https://lists.apache.org/thread.html/77d0d9fe87413b3d81a7fb3eca5cd8283da18fa8c5f3d808aec28732@%3Cdev.fineract.apache.org%3E > I already made sure we cannot use jitpack.io for this but I got access to > Fineract-CN's own JFrog account > so I plan to configure Travis to publish there. > > It will take me some time to bet it done but looking at your second > proposal I do agree that the RSA keys seems to > be a problem that needs to be solved before any images can be published to > Docker Hub. > I hope Courage can answer to some of the questions and you can find a way > to generate the keys for the containers. > > Kind regards > Juhan > > > Kontakt Awasum Yannick (<[email protected]>) kirjutas kuupäeval P, 7. > aprill 2019 kell 13:19: > > > There are too many points which you have made here. Is it possible to > > create issues so we get some clarity or even separate threads. > > > > Apache Infra seems to have some services which could help us: > > > > A dedicated CI site: https://ci.apache.org/ > > and another for Jenkins: https://builds.apache.org/ > > > > There is also a tool here for Continuous Code Quality Inspections: > > https://cwiki.apache.org/confluence/display/INFRA/SonarQube+Analysis > > and https://sonarcloud.io/organizations/apache/projects > > > > Everyone should coordinate on list so we dont waste resources. I also > dont > > know what we are doing with the 2 servers Apache Infra gave us. > > > > We should note that Juhan is already working on something similar for > > enabling CI on Fineract CN using Artifactory. I will take time later to > > create distinct issues for all these discussions. > > > > At the end of the day, we should know that the most important bottleneck > > for Fineract CN now is removing Hibernate and replacing it with OpenJPA > or > > EclipseLink and removing the mariadb client dependency or moving to > > postgresql completely as Isaac began doing. Doing the above will enable > us > > release Fineract CN. If someone wants to help at code level, this is > where > > the community is facing difficulties. > > > > Thanks. > > > > > > > > On Sun, Apr 7, 2019 at 8:48 AM Ebenezer Graham <[email protected] > > > > wrote: > > > > > Hello Courage, > > > > > > I have been following this and the other threads for a while now and I > > want > > > to contribute as well as work on it during GSoC. > > > > > > I would like to know the progress with of the CI/CD and begin > > contribution. > > > > > > If I understand the scope of the CI/CD requirements, it has to handle > two > > > things, > > > 1. Build and publish fineract jar artifacts to a public repository such > > as > > > maven artifactory > > > 2. Build and push container images to Mifos' docker hub account. > > > > > > But first of all have you chosen any of the previous suggested > platforms > > ( > > > jitpack.io, jenkins, Gitlab). > > > > > > If yes, how can I access the published artifacts to build images. > > > > > > If not, I would like to suggest a fourth CI platform for consideration > > > -Travis CI. > > > > > > First of all, it's free and has a package for open source projects. > > Unlike > > > Gitlab and Jenkins which will require us to startup our own servers in > > the > > > long run. > > > > > > With Travis, we can simply connect it to GitHub, build -> deploy to > > > dockerhub and maven. In addition, it's well documented. For instance > > check > > > this out. > > > https://docs.travis-ci.com/user/docker/ > > > > > > On of the downside here is the fact that we have to add .travis.yml > files > > > to each repository. > > > > > > Let me know what you think. > > > > > > Secondly, can you expound on the work left with regards to provisioning > > of > > > the services and creating a new service to handle RSA keys for the > > > containers. I believe these two are linked. > > > > > > Also, I have setup GKE and and attempted to pull the images on your > > > personal docker hub accounts however, deployment of the containers has > be > > > unsuccessful and I think I'm doing something wrong. > > > > > > How did you approach the deployment from your end. Did you store your > > > images in Google Container Registry? Did you rebuild the images from > > > GitHub? > > > > > > I would appreciate your guidance on how to deploy new containers from > the > > > existing images. > > > > > > With regards to docker swarm, you said, it work on premise, what do we > > have > > > to do to get it working on the cloud. > > > > > > Lastly, with regards to the deployment script for Openshift, have you > > > started the script for this? > > > > > > Looking forward to hearing from you. > > > > > > *At your service,* > > > > > > *Ebenezer Graham* > > > > > > > > > > > > On Tue, 19 Mar 2019 at 08:38, Courage Angeh <[email protected]> > > > wrote: > > > > > > > Thank for the info Myrle. > > > > > > > > --- > > > > > > > > Hi Isaac, > > > > > > > > Thanks. > > > > Customer has been containerized. You can verify that here: > > > > https://github.com/apache/fineract-cn-customer > > > > > > > > Reporting, Payroll, Notification and Groups are still to be > > containerized > > > > so it has been added as part of the work for the GSoC 2019 session. > > > > > > > > Thanks, > > > > Courage > > > > > > > > On Mon, Mar 18, 2019 at 7:29 PM Isaac Kamga <[email protected]> > > > wrote: > > > > > > > > > Very good work done here Courage, > > > > > > > > > > What about the other services like customer, payroll, etc ? Do they > > > need > > > > to > > > > > be dockerized too OR should that go into further work for this > > session > > > of > > > > > GSoC ? > > > > > > > > > > Cheers, > > > > > Isaac Kamga. > > > > > > > > > > On Thu, Mar 14, 2019 at 5:35 PM Myrle Krantz <[email protected]> > > wrote: > > > > > > > > > > > FYI, > > > > > > > > > > > > I still have access to the mifos org docker hub account from > when I > > > was > > > > > > employed there. James does too apparently. > > > > > > > > > > > > Uploading that stuff to the apache docker hub account is tricky. > > > > > Generally > > > > > > it's not allowed to put non-released software there and Fineract > CN > > > > isn't > > > > > > released yet. > > > > > > > > > > > > Best Regards, > > > > > > Myrle > > > > > > > > > > > > On Wed, Mar 13, 2019 at 10:00 PM Courage Angeh < > > > [email protected] > > > > > > > > > > > wrote: > > > > > > > > > > > > > They are on docker hub. On my account for now, > > > > > > `anh3h/fineract-cn-<service > > > > > > > name>` e.g anh3h/fineract-cn-office > > > > > > > > > > > > > > On Wed, Mar 13, 2019 at 4:18 PM Patrick Finken < > > > > > [email protected] > > > > > > > > > > > > > > wrote: > > > > > > > > > > > > > > > Ok. Once we have the images pushed in the docker hub, I will > > > update > > > > > > your > > > > > > > > scripts and test it locally. > > > > > > > > > > > > > > > > Regards, > > > > > > > > Patrick > > > > > > > > > > > > > > > > On Wed, Mar 13, 2019 at 2:18 PM Courage Angeh < > > > > > [email protected]> > > > > > > > > wrote: > > > > > > > > > > > > > > > > > Hi Patrick, > > > > > > > > > > > > > > > > > > I am aware of the possibility to use minikube. But > > considering > > > > the > > > > > > > number > > > > > > > > > of services I have run simultaneously, > > > > > > > > > K8 using minikube locally will just crash my computer. > > > > > > > > > > > > > > > > > > if have made some progress on the k8 scripts pls feel free > to > > > > > create > > > > > > a > > > > > > > > PR. > > > > > > > > > I will review it > > > > > > > > > > > > > > > > > > On Wed, Mar 13, 2019 at 2:12 PM Patrick Finken < > > > > > > > [email protected] > > > > > > > > > > > > > > > > > > wrote: > > > > > > > > > > > > > > > > > > > I worked on the deployment of fineract-cn on k8s and I > > > produced > > > > > > some > > > > > > > > > > scripts based on what courage started. I can push them to > > the > > > > > > repo. I > > > > > > > > can > > > > > > > > > > start working on it as soon as with have to docker image > > > pushed > > > > > to > > > > > > > the > > > > > > > > > > docker hub. > > > > > > > > > > > > > > > > > > > > @courage, you can install minikube to run k8s locally so > > that > > > > you > > > > > > > don't > > > > > > > > > > need a GKE account. > > > > > > > > > > > > > > > > > > > > Patrick > > > > > > > > > > > > > > > > > > > > On Wed, Mar 13, 2019 at 2:05 PM Courage Angeh < > > > > > > > [email protected]> > > > > > > > > > > wrote: > > > > > > > > > > > > > > > > > > > > > The project is still under Mifos Initiative, > > > > > > > > > > > https://github.com/openMF/fineract-cn-containers > > > > > > > > > > > > > > > > > > > > > > Most of the Dockerfiles have been pushed to the > different > > > > > > Finerect > > > > > > > CN > > > > > > > > > > > repositories. The idea > > > > > > > > > > > is to have the compose file pull directly from Docker > > hub. > > > > > > > > > > > > > > > > > > > > > > On Wed, Mar 13, 2019 at 1:52 PM Awasum Yannick < > > > > > > [email protected]> > > > > > > > > > > wrote: > > > > > > > > > > > > > > > > > > > > > > > Thanks Courage. Please, Which Github repos ? Are they > > on > > > > > > Fineract > > > > > > > > > > Repos? > > > > > > > > > > > Do > > > > > > > > > > > > you want to put them there? > > > > > > > > > > > > > > > > > > > > > > > > On Wed, Mar 13, 2019 at 6:48 PM Courage Angeh < > > > > > > > > > [email protected]> > > > > > > > > > > > > wrote: > > > > > > > > > > > > > > > > > > > > > > > > > They are all on the GitHub repo. > > > > > > > > > > > > > Still working on the swarm thing though. > > > > > > > > > > > > > > > > > > > > > > > > > > Previously was updating the deployment for docker > and > > > k8 > > > > > > > > > > > simultaneously, > > > > > > > > > > > > > but my credits for my GKE account is finished so > the > > K8 > > > > > > scripts > > > > > > > > > are a > > > > > > > > > > > > > little behind. > > > > > > > > > > > > > > > > > > > > > > > > > > On Wed, Mar 13, 2019 at 1:42 PM Awasum Yannick < > > > > > > > > [email protected]> > > > > > > > > > > > > wrote: > > > > > > > > > > > > > > > > > > > > > > > > > > > Hi Courage, > > > > > > > > > > > > > > > > > > > > > > > > > > > > Are the Docker Compose, Swarm scripts and K8 > > scripts > > > > all > > > > > > > > > available > > > > > > > > > > on > > > > > > > > > > > > our > > > > > > > > > > > > > > Apache Github repos? I think that will be great. > > > > > > > > > > > > > > > > > > > > > > > > > > > > On Wed, Mar 13, 2019 at 6:38 PM Courage Angeh < > > > > > > > > > > > [email protected]> > > > > > > > > > > > > > > wrote: > > > > > > > > > > > > > > > > > > > > > > > > > > > > > Hi Patrick and Myrle, > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > Actually, we started some work on Kubernetes. > > > > > > > > > > > > > > > If you have the physical resource to set-up > > > > Kubernetes > > > > > > and > > > > > > > > > > > implement > > > > > > > > > > > > > the > > > > > > > > > > > > > > > scripts to deploy with > > > > > > > > > > > > > > > Fineract CN using k8 please go ahead to send > > your > > > > > > > > > contributions. > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > But for the summer of code, Mifos or Apache > > hasn't > > > > > > provided > > > > > > > > us > > > > > > > > > > with > > > > > > > > > > > > the > > > > > > > > > > > > > > > resource yet. > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > So we are going with swarm since we can use > that > > > for > > > > > now. > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > Thanks, > > > > > > > > > > > > > > > Courage > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > On Wed, Mar 13, 2019 at 1:32 PM Myrle Krantz < > > > > > > > > [email protected] > > > > > > > > > > > > > > > > > > > > > > wrote: > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > Hey Patrick, > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > I would love to see that. There's no reason > > not > > > to > > > > > do > > > > > > > > both! > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > Best, > > > > > > > > > > > > > > > > Myrle > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > On Wed, Mar 13, 2019 at 6:29 PM Patrick > Finken > > < > > > > > > > > > > > > > > [email protected] > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > wrote: > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > Hello guys, > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > I was wondering since the industry tends > > toward > > > > > > > > kubernetes > > > > > > > > > > for > > > > > > > > > > > > > > > containers > > > > > > > > > > > > > > > > > orchestration, wouldn't be better to > > configure > > > > > > > > fineract-cn > > > > > > > > > > > > > deployment > > > > > > > > > > > > > > > > with > > > > > > > > > > > > > > > > > K8s instead of docker swarm? Or maybe > keeping > > > the > > > > > two > > > > > > > > > > > versions? I > > > > > > > > > > > > > > could > > > > > > > > > > > > > > > > > help to contribute to the K8s version. > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > regards, > > > > > > > > > > > > > > > > > Patrick > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > On Wed, Mar 13, 2019 at 12:24 PM Juhan > > Aasaru < > > > > > > > > > > > [email protected]> > > > > > > > > > > > > > > > wrote: > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > Hey! > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > Great work, Courage! > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > Regarding what you wrote in your first > > mail: > > > > > > > > > > > > > > > > > > Lastly, we could publish the built > Fineract > > > CN > > > > > > > services > > > > > > > > > > > > libraries > > > > > > > > > > > > > > to > > > > > > > > > > > > > > > a > > > > > > > > > > > > > > > > > > Maven Artifactory so developers will not > > have > > > > to > > > > > > > > manually > > > > > > > > > > > clone > > > > > > > > > > > > > and > > > > > > > > > > > > > > > > > publish > > > > > > > > > > > > > > > > > > these services by themselves. > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > You didn't put that into the Jira ticket > > but > > > I > > > > > got > > > > > > an > > > > > > > > > idea > > > > > > > > > > > how > > > > > > > > > > > > we > > > > > > > > > > > > > > > could > > > > > > > > > > > > > > > > > > smoothly solve this step using > jitpack.io > > > > > > > > > > > > > > > > > > I thought it would be good to share this > > idea > > > > in > > > > > > the > > > > > > > > > > current > > > > > > > > > > > > > > > > discussion. > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > Publishing a new version of a library to > > > Maven > > > > > > > Central > > > > > > > > is > > > > > > > > > > > > quite a > > > > > > > > > > > > > > > work. > > > > > > > > > > > > > > > > > > With jitpack.io one can just use a git > > > commit > > > > > hash > > > > > > > as > > > > > > > > a > > > > > > > > > > > > version > > > > > > > > > > > > > > > number > > > > > > > > > > > > > > > > > (or > > > > > > > > > > > > > > > > > > branchname-SNAPSHOT to get the build of > the > > > > > latest > > > > > > > > > commit). > > > > > > > > > > > > > > > > > > Basically, you one needs to configure > > jitpack > > > > > > > > repository > > > > > > > > > > as a > > > > > > > > > > > > > > > > dependency > > > > > > > > > > > > > > > > > (I > > > > > > > > > > > > > > > > > > use maven style as example): > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > <repository> > > > > > > > > > > > > > > > > > > <id>jitpack.io</id> > > > > > > > > > > > > > > > > > > <url>https://jitpack.io > </url> > > > > > > > > > > > > > > > > > > </repository> > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > and then there is need to specify the > > > > dependency > > > > > > > using > > > > > > > > > > Github > > > > > > > > > > > > > url: > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > For example > > > > > > > > > > > > > > > > > > > > > https://github.com/apache/fineract-cn-identity > > > > > > > > > > > > > > > > > > with Latest commit 6f8498d 4 days ago > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > turns into the following dependency: > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > <dependency> > > > > > > > > > > > > > > > > > > > > > > <groupId>com.github.aasaru</groupId> > > > > > > > > > > > > > > > > > > > > > > > > > > <artifactId>fineract-cn-identity</artifactId> > > > > > > > > > > > > > > > > > > <version>6f8498d</version> > > > > > > > > > > > > > > > > > > </dependency> > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > Jitpack checks out and builds the jar > > during > > > > the > > > > > > > first > > > > > > > > > > > request. > > > > > > > > > > > > > > > > > > And it can be also downloaded from the > > public > > > > > Maven > > > > > > > > repo > > > > > > > > > > that > > > > > > > > > > > > > > jitpack > > > > > > > > > > > > > > > > > > serves. Url would be something like: > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > https://jitpack.io/com/github/apache/fineract-cn-identity/6f8498d/ > > > > > > > > > > > > > > . > > > > > > > > > > > > > > > .. > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > For now this doesn't work yet (I suspect > > the > > > > > gradle > > > > > > > > > command > > > > > > > > > > > > that > > > > > > > > > > > > > > > > > > jitpack uses doesn't result with a build > > > > > > > > > > > > > > > > > > due to the current configuration of > > > > > > > > fineract-cn-identity > > > > > > > > > > > > > > > build.gradle. > > > > > > > > > > > > > > > > > This > > > > > > > > > > > > > > > > > > needs yet to be investigated. > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > Kind regards > > > > > > > > > > > > > > > > > > Juhan > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > Kontakt Courage Angeh (< > > > [email protected] > > > > >) > > > > > > > > > kirjutas > > > > > > > > > > > > > > kuupäeval > > > > > > > > > > > > > > > P, > > > > > > > > > > > > > > > > > 10. > > > > > > > > > > > > > > > > > > märts 2019 kell 23:03: > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > Hi Guys, > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > I have created this task on Jira: > > > > > > > > > > > > > > > > > > > > > > > > https://issues.apache.org/jira/browse/FINCN-139 > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > I think the project to should be added > to > > > the > > > > > > GSoC > > > > > > > > 2019 > > > > > > > > > > > > > idealist. > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > Thanks, > > > > > > > > > > > > > > > > > > > Courage > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > On Sat, Mar 9, 2019 at 2:04 PM Courage > > > Angeh > > > > < > > > > > > > > > > > > > > > [email protected] > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > wrote: > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > Thanks and you're welcome. > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > On Sat, Mar 9, 2019, 8:01 AM Myrle > > > Krantz < > > > > > > > > > > > > [email protected]> > > > > > > > > > > > > > > > > wrote: > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > >> Wonderful! > > > > > > > > > > > > > > > > > > > >> > > > > > > > > > > > > > > > > > > > >> I've merged. > > > > > > > > > > > > > > > > > > > >> > > > > > > > > > > > > > > > > > > > >> Thank you Courage, > > > > > > > > > > > > > > > > > > > >> Myrle > > > > > > > > > > > > > > > > > > > >> > > > > > > > > > > > > > > > > > > > >> On Sat, Mar 9, 2019 at 1:14 AM > Courage > > > > > Angeh < > > > > > > > > > > > > > > > > > [email protected]> > > > > > > > > > > > > > > > > > > > >> wrote: > > > > > > > > > > > > > > > > > > > >> > > > > > > > > > > > > > > > > > > > >> > Hello guys, > > > > > > > > > > > > > > > > > > > >> > > > > > > > > > > > > > > > > > > > > >> > Hope this email finds you well. > For > > > the > > > > > past > > > > > > > > > weeks, > > > > > > > > > > I > > > > > > > > > > > > have > > > > > > > > > > > > > > > been > > > > > > > > > > > > > > > > > > > working > > > > > > > > > > > > > > > > > > > >> on > > > > > > > > > > > > > > > > > > > >> > moving the different Fineract CN > > > service > > > > > > > > > Dockerfiles > > > > > > > > > > > to > > > > > > > > > > > > > > their > > > > > > > > > > > > > > > > > > > respective > > > > > > > > > > > > > > > > > > > >> > repositories. Here are the PRs, > can > > > some > > > > > > > please > > > > > > > > > view > > > > > > > > > > > and > > > > > > > > > > > > > > merge > > > > > > > > > > > > > > > > > them: > > > > > > > > > > > > > > > > > > > >> > > > > > > > > > > > > > > > > > > > > >> > > > > > > > > > > https://github.com/apache/fineract-cn-rhythm/pull/7 > > > > > > > > > > > > > > > > > > > >> > > > > > > > > > > > https://github.com/apache/fineract-cn-identity/pull/8 > > > > > > > > > > > > > > > > > > > >> > > > > > > > > > > https://github.com/apache/fineract-cn-office/pull/8 > > > > > > > > > > > > > > > > > > > >> > > > > > > > > > > > > > https://github.com/apache/fineract-cn-accounting/pull/9 > > > > > > > > > > > > > > > > > > > >> > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > https://github.com/apache/fineract-cn-deposit-account-management > > > > > > > > > > > > > > > > > > > >> > > > > > > > > https://github.com/apache/fineract-cn-portfolio > > > > > > > > > > > > > > > > > > > >> > > > > > > > > > > > https://github.com/apache/fineract-cn-teller/pull/10 > > > > > > > > > > > > > > > > > > > >> > > > > > > > > > > > > > > > > > > > > >> > What work is left for successful > > > > > deployment? > > > > > > > > > > > > > > > > > > > >> > > > > > > > > > > > > > > > > > > > > >> > First, we need to configure Docker > > > > scripts > > > > > > to > > > > > > > > > deploy > > > > > > > > > > > and > > > > > > > > > > > > > > > manage > > > > > > > > > > > > > > > > > the > > > > > > > > > > > > > > > > > > > >> system > > > > > > > > > > > > > > > > > > > >> > on swarm mode. Then update > provision > > > and > > > > > > > > migration > > > > > > > > > > > > script > > > > > > > > > > > > > to > > > > > > > > > > > > > > > > work > > > > > > > > > > > > > > > > > > with > > > > > > > > > > > > > > > > > > > >> > cluster environments and create > the > > > > chart > > > > > > > > > accounts. > > > > > > > > > > > > > > > > > > > >> > We also have to add Jenkins to the > > > > > different > > > > > > > > > > Fineract > > > > > > > > > > > CN > > > > > > > > > > > > > > > > services, > > > > > > > > > > > > > > > > > > > then > > > > > > > > > > > > > > > > > > > >> > each service to its image on > > > DockerHub. > > > > > > > > > > > > > > > > > > > >> > Lastly, we could publish the built > > > > > Fineract > > > > > > CN > > > > > > > > > > > services > > > > > > > > > > > > > > > > libraries > > > > > > > > > > > > > > > > > > to a > > > > > > > > > > > > > > > > > > > >> > Maven Artifactory so developers > will > > > not > > > > > > have > > > > > > > to > > > > > > > > > > > > manually > > > > > > > > > > > > > > > clone > > > > > > > > > > > > > > > > > and > > > > > > > > > > > > > > > > > > > >> publish > > > > > > > > > > > > > > > > > > > >> > these services by themselves. > > > > > > > > > > > > > > > > > > > >> > > > > > > > > > > > > > > > > > > > > >> > But all this needs resources like > a > > > > > > DockerHub > > > > > > > > and > > > > > > > > > > > > Jenkins > > > > > > > > > > > > > > > > account. > > > > > > > > > > > > > > > > > > > >> > I would like to propose this > project > > > > for a > > > > > > > GSoC > > > > > > > > > > > project. > > > > > > > > > > > > > > > > > > > >> > > > > > > > > > > > > > > > > > > > > >> > Thanks, > > > > > > > > > > > > > > > > > > > >> > Courage. > > > > > > > > > > > > > > > > > > > >> > > > > > > > > > > > > > > > > > > > > >> > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > -- > > > > > > > > > > > > > > > > > Patrick Finken, > > > > > > > > > > > > > > > > > Owner > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > -- > > > > > > > > > > Patrick Finken, > > > > > > > > > > Owner > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > -- > > > > > > > > Patrick Finken, > > > > > > > > Owner > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > <https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=webmail&utm_term=icon> Virus-free. www.avast.com <https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=webmail&utm_term=link> <#DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2>
