Hi guys, I have updated the script used to provision the services after start-up. I have broken the code into functions. each function performs a specific task. As of now, all the services provision successfully. I am still to implement the function to create the chart of accounts after provisioning the services. What's left: - Migrate services - Passing multiple tenants to script - Port functionality to Google Container Engine - Upgrade script to perform better
Thanks, Courage On Fri, Oct 5, 2018 at 8:09 AM Isaac Kamga <[email protected]> wrote: > Hello Courage, > > Thanks for updating the community on your progress with containerization of > Fineract CN. > > James, I guess Courage used Ubuntu because she it's her default system for > development and there were limited Cloud resources for her to experiment > with other distros. > > Graham, when you're done integrating the notifications service into > demo-server and it works for everybody who clones the code, then you can > require Courage to containerize that service. Don't push her when you've > not done your homework...I have waited for the said PR for a month now. > > Cheers, > Isaac Kamga. > > On Fri, Oct 5, 2018 at 4:29 AM Ebenezer Graham <[email protected]> > wrote: > > > Yes, I have integrated it into the demo-server. However, I am refactoring > > the authentication process at the moment. Is that a problem? > > > > It is currently using a notifications user to authenticate, however, in > the > > next PR to the Demo server it will be using an auth style similar to > > rhythm. > > > > > > *At your service,* > > > > *Ebenezer Graham* > > > > *BSc (Hons) Computing* > > > > > > [image: EmailSignature.png] > > > > African Leadership University, > > > > Power Mill Road, Pamplemousses, > > > > Mauritius. > > > > > > *skype*: > > ebenezer.graham > > GitHub <https://github.com/ebenezergraham> | LinkedIn > > <https://www.linkedin.com/in/ebenezer-graham/> | Twitter > > <https://twitter.com/pactmart> | Facebook > > <https://www.facebook.com/pactmart> > > www.pactmart.com | Freelancing made easy. > > > > > > *“Talk is cheap, show me the code.” *- *Linus Torvalds* > > > > > > > > > > On Thu, 4 Oct 2018 at 17:19, Courage Angeh <[email protected]> > wrote: > > > > > Okay, yea. I can do that if you have successfully intergrated the > > > notification microservice on demo-server. > > > Nevetheless if you haven't, we can always add that anytime, with just a > > few > > > lines of code. > > > > > > On Thu, Oct 4, 2018, 6:37 AM Ebenezer Graham <[email protected] > > > > > wrote: > > > > > > > Hi Courage, > > > > > > > > Can you make provision for the notification service as well. > > > > > > > > On Thu, 4 Oct 2018, 07:50 Courage Angeh, <[email protected]> > > wrote: > > > > > > > > > Hello Guys, > > > > > > > > > > I am starting this new thread so that it can be used to monitor the > > > > > progress in containerizing Fineract CN. > > > > > > > > > > I have written the documentation > > > > > < > > > > > > > > > > > > > > > https://cwiki.apache.org/confluence/display/FINERACT/Containerizing+Fineract+CN > > > > > > > > > > > needed to set up the desired environment. I will update the > > > documentation > > > > > based on the feedback from the community. > > > > > I have also moved the code based to > > > > > https://github.com/openMF/fineract-cn-containers.git > > > > > It's quite messy as of now since I was concentrating on making some > > > > > functionalities work but I will clean it up ASAP. > > > > > > > > > > So what works: > > > > > > > > > > - I have implemented the necessary scripts to containerize and > > > deploy > > > > > the Finerct service and external service i.e Cassandra, MariaDB, > > > > Eureka, > > > > > and ActiveMQ, using Docker, docker-compose, and Kubernetes. > > > > > - I have implemented scripts to start up and shut down the > system > > > when > > > > > deploying using docker compose > > > > > - I am currently implementing a provisioning script that > supposed > > to > > > > > provision the system after deployment. I am following the > > deployment > > > > > strategy defined in Demo Server's ServiceRunner.java file. So > far > > > the > > > > > provisioner script, > > > > > > > > > > > > > > > 1. Registers the up and running microservices via the > provisioner > > > > > microservice > > > > > 2. Then starts provisioning a tenant. As of now, it registers > the > > > > tenant > > > > > via provisioner, -> authenticates as an administrator, -> > assigns > > > > > identity > > > > > manager for the tenant, -> creates the scheduler user, -> > enables > > > the > > > > > scheduler user's account, then logins in ready to provision the > > > other > > > > > microservices > > > > > > > > > > I will clean up the code base before continue working on the other > > > > > microservices. > > > > > > > > > > Work to be done: > > > > > > > > > > - Implement script to provision Rythm, organization, customer, > > > ledger, > > > > > portfolio, deposit-account-manager, teller, report, cheque > payroll > > > and > > > > > group > > > > > - Implement migration script > > > > > - Upgrade bash script so it could be more user-friendly like > > > > > Linux commands and their man pages > > > > > - We could also use a Configuration management like ansible or > > > puppet > > > > to > > > > > manage the configurations required to deploy the system. > > > > > > > > > > So that's the progress of the project as of now, I will continue > > > updating > > > > > this thread as I make progress on the project. I will be happy to > > have > > > > the > > > > > community join this train :-) > > > > > > > > > > Thanks, > > > > > Courage > > > > > > > > > > > > > > >
