Re: Simplifying Fineract CN Demo-server
Happy boxing day fineracters, Hope you all had a marvelous Christmas day. I effected some changes based on the open concerns I earlier expressed here and have just submitted and merged pull requests in fineract-cn-service-starter and fineract-cn-demo-server repositories in this respect. For now, I left out any change to the Notifications service's notificationAdmin role in fineract-cn-demo-server. My observations indicated a 30% drop in demo-server's build time ( about 7 minutes saved ) on each run - whether Option A or Option B. I hope this helps. At Your Service, Isaac Kamga. On Sat, Dec 15, 2018 at 12:41 AM Isaac Kamga wrote: > Hello fineracters, > > Trust that this email finds you well. > > Special congratulations to our Google Summer of Code 2018 interns who > are graduating from University ! > > In an effort to simplify fineract-cn-demo-server and increase the > number of eyeballs looking at the platform's code, I've looked into > demo-server's ServiceRunner and service-starter and have the some > questions which beg for clarification. > > 1. Is it compulsory that the wait time [1] between starting the > microservices be 20 seconds ? Should this be reduced ? To what extent > ? > > 2. After migrating each service [2] when persistence is true, should > there be a 5 seconds sleep ? > > 3. In the tearDown() method [3], should services be killed in any > order or in the reverse order in which they were started in the > before() method [4] ? > > 4. +Ebenezer Graham Any special reason why new notificationsAdmin [5] > role was created ? What if it's possible to use the existing Org Admin > [6] role and user to allow for permissions related to the > notifications service just like the other services do ? > > 5. Should there be a 40 seconds sleep [7] in Microservice's start() > method ? Should this be reduced ? > > 6. +Markus Geiss Can we default CONCURRENCY from 3-10 to 1-1 in > ActiveMQForTest [8] ? I remember your advice to Graham regarding > reduction in the number of received events from 3 to 1. > > 7. +Myrle Krantz , How do we run demo-server jar file with debug > option to start micro-services based on this [9] ? -Dsuspend=y > -Daddress=3020 ? This could help update the How-To-Build wiki page . > > I understand that sometime it's better to apologize than ask for > permission but given that we want demo-server working for everybody, I > thought it would be necessary to ask even the most minute details > concerning changes that affect these integration tests. > > Kindly advise on these issues. > > At Your Service, > Isaac Kamga. > > [1] > https://github.com/apache/fineract-cn-demo-server/blob/8a55eb21ef5588796d9212266901b494cdf006f3/src/main/java/org/apache/fineract/cn/dev/ServiceRunner.java#L338 > > [2] > https://github.com/apache/fineract-cn-demo-server/blob/8a55eb21ef5588796d9212266901b494cdf006f3/src/main/java/org/apache/fineract/cn/dev/ServiceRunner.java#L355 > > [3] > https://github.com/apache/fineract-cn-demo-server/blob/8a55eb21ef5588796d9212266901b494cdf006f3/src/main/java/org/apache/fineract/cn/dev/ServiceRunner.java#L266 > > [4] > https://github.com/apache/fineract-cn-demo-server/blob/8a55eb21ef5588796d9212266901b494cdf006f3/src/main/java/org/apache/fineract/cn/dev/ServiceRunner.java#L187 > > [5] > https://github.com/apache/fineract-cn-demo-server/blob/8a55eb21ef5588796d9212266901b494cdf006f3/src/main/java/org/apache/fineract/cn/dev/ServiceRunner.java#L653 > > [6] > https://github.com/apache/fineract-cn-demo-server/blob/8a55eb21ef5588796d9212266901b494cdf006f3/src/main/java/org/apache/fineract/cn/dev/ServiceRunner.java#L580 > > [7] > https://github.com/apache/fineract-cn-service-starter/blob/020dad06bf9f416d819911401e9b370cd155d936/src/main/java/org/apache/fineract/cn/test/servicestarter/Microservice.java#L178 > > [8] > https://github.com/apache/fineract-cn-service-starter/blob/020dad06bf9f416d819911401e9b370cd155d936/src/main/java/org/apache/fineract/cn/test/servicestarter/ActiveMQForTest.java#L81 > > [9] > https://github.com/apache/fineract-cn-service-starter/blob/020dad06bf9f416d819911401e9b370cd155d936/src/main/java/org/apache/fineract/cn/test/servicestarter/Microservice.java#L171 >
Re: Setup on Containers
Hello Courage, Actually, the script is from https://github.com/openMF/fineract-cn-containers. The problem is that the provisioner is expecting two properties that are not specified in the Dockerfile. provisioner| *** provisioner| APPLICATION FAILED TO START provisioner| *** provisioner| Description: provisioner| provisioner| Binding to target org.apache.fineract.cn.provisioner.config.SystemProperties@72443081 failed: provisioner| provisioner| Property: system.privateKey.modulus provisioner| Value: null provisioner| Reason: may not be null provisioner| provisioner| Property: system.privateKey.exponent provisioner| Value: null provisioner| Reason: may not be null But I kind of figured out the solution. I used a tool online to generate a RSA key. I'm all set now. The platform is running. Thanks Merry Christmas Patrick On Tue, Dec 25, 2018 at 6:43 AM Courage Angeh wrote: > Hi Patrick, > > You wouldn't want to deactivate it 'cause its needed for authentication. > I containerized Fineract CN as a summer of code project, that should help > you out. > https://github.com/openMF/fineract-cn-containers > > Merry Christmas, > Courage. > > On Tue, Dec 25, 2018 at 1:22 AM Patrick Finken > wrote: > > > Hello Everyone, > > > > I'm Patrick. I've recently discovered Fineract CN and I might be > interested > > to use as a backend system for a financial application I'm building. > > I succeed to build and launch the demo-server on my local machine, but > I'm > > stuck when I try to run it inside containers. > > I used the script from the repo "apache/fineract-cn-provisioner", but the > > provisioner service failed to run because of the missing configuration > > "system.privateKey.modulus" and "system.privateKey.exponent". I'm > > guessing it's related to some RSA configuration, but there is a way to > > deactivate it in order to run and test the API? > > > > > > regards > > -- > > Patrick, > > > -- Patrick Finken, Owner
Re: Fineract PMC Chair change: Congratulations Vishwas!
Thank you Myrle, for your leadership in giving Fineract a solid start. All the best , Vishwas. /sijo On Mon, Dec 24, 2018 at 2:19 PM Ruphine Kengne wrote: > Congrats Vishwas. > > Thanks for the wishes and same to you > > Regards. > > On Mon, Dec 24, 2018, 8:19 AM Vishwas Babu < > vish...@confluxtechnologies.com > wrote: > > > Thanks All ! I indeed have big shoes to fill and hope to continue the > > great job that Myrle has been doing for our community. > > > > Wishing you a merry Christmas and a happy new year, > > > > Vishwas > > +1 (202) 716 6675 > > > > > > On Thu, Dec 20, 2018 at 5:25 PM Myrle Krantz wrote: > > > > > Hello all, > > > > > > I am ready to pass on the role of Fineract PMC chair. > > > > > > I believe that a regular change of PMC chair will help to increase > > > community empowerment, and develop skills among the Fineract PMC > > members. I > > > am looking forward to having more time for my other roles. I continue > to > > > be part of Fineract as a committer and PMC member. > > > > > > The Fineract PMC has elected Vishwas Babu as my successor. The ASF > board > > > has approved his appointment. Vishwas is an excellent choice. Vishwas > > has > > > been involved with Fineract for longer than I have, and has a deep > > > knowledge of Fineract community dynamics. > > > > > > Please congratulate Vishwas, and please support him as he serves our > > > community in this new role. > > > > > > Best Regards, > > > Myrle > > > V.P. Emeritus, Apache Fineract > > > > > >
Re: Setup on Containers
Hi Patrick, You wouldn't want to deactivate it 'cause its needed for authentication. I containerized Fineract CN as a summer of code project, that should help you out. https://github.com/openMF/fineract-cn-containers Merry Christmas, Courage. On Tue, Dec 25, 2018 at 1:22 AM Patrick Finken wrote: > Hello Everyone, > > I'm Patrick. I've recently discovered Fineract CN and I might be interested > to use as a backend system for a financial application I'm building. > I succeed to build and launch the demo-server on my local machine, but I'm > stuck when I try to run it inside containers. > I used the script from the repo "apache/fineract-cn-provisioner", but the > provisioner service failed to run because of the missing configuration > "system.privateKey.modulus" and "system.privateKey.exponent". I'm > guessing it's related to some RSA configuration, but there is a way to > deactivate it in order to run and test the API? > > > regards > -- > Patrick, >
