[jira] [Updated] (FINERACT-1303) Generate Report by Automation
[ https://issues.apache.org/jira/browse/FINERACT-1303?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rahul Pawar updated FINERACT-1303: -- Description: To generate the report, The user should trigger the Automation, and a Credit-Report should be generated to upload which should be satisfied with the format/template which is expected by the Credit Bureau The data filled in the reports will be fetched from the Database by identifying the fields in the schema, which will be mapped to the field of the template provided by the Credit Bureau. This will also reduce the human-error which would cause while putting the data manually in the reports. was: To generate the report, The user should trigger the Automation, and a Credit-Report should be generated, which will be satisfied with the format/template which is expected by the Credit Bureau. The data in the report will be fetched from the Database by identifying the fields in the schema to be mapped to this field of the template provided by the Credit Bureau. This will also reduce the human-error which would cause while putting the data manually in the reports. > Generate Report by Automation > - > > Key: FINERACT-1303 > URL: https://issues.apache.org/jira/browse/FINERACT-1303 > Project: Apache Fineract > Issue Type: Improvement >Reporter: Rahul Pawar >Priority: Major > > To generate the report, The user should trigger the Automation, and a > Credit-Report should be generated to upload which should be satisfied with > the format/template which is expected by the Credit Bureau > The data filled in the reports will be fetched from the Database by > identifying the fields in the schema, which will be mapped to the field of > the template provided by the Credit Bureau. > This will also reduce the human-error which would cause while putting the > data manually in the reports. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (FINERACT-1303) Generate Report by Automation
Rahul Pawar created FINERACT-1303: - Summary: Generate Report by Automation Key: FINERACT-1303 URL: https://issues.apache.org/jira/browse/FINERACT-1303 Project: Apache Fineract Issue Type: Improvement Reporter: Rahul Pawar To generate the report, The user should trigger the Automation, and a Credit-Report should be generated, which will be satisfied with the format/template which is expected by the Credit Bureau. The data in the report will be fetched from the Database by identifying the fields in the schema to be mapped to this field of the template provided by the Credit Bureau. This will also reduce the human-error which would cause while putting the data manually in the reports. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Assigned] (FINERACT-880) Fineract Caches & Kubernetes Deployment
[ https://issues.apache.org/jira/browse/FINERACT-880?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Benura Abeywardena reassigned FINERACT-880: --- Assignee: Benura Abeywardena > Fineract Caches & Kubernetes Deployment > --- > > Key: FINERACT-880 > URL: https://issues.apache.org/jira/browse/FINERACT-880 > Project: Apache Fineract > Issue Type: Improvement > Components: Performance >Reporter: Michael Vorburger >Assignee: Benura Abeywardena >Priority: Major > Labels: kubernetes, scalability, technical > > The Kubernetes deployment contributed in FINERACT-783 by default creates a > Kubernetes Deployment with a single Pod (based on Fineract's Docker Compose > set-up). > The goal of this issue is to investigate what is missing to make it possible > to "scale horizontally" by increasing the number of replicas. > For example, I believe Fineract code caches certain things? I'm not clear if > they are enabled or disabled by default. Such caches typically do not "just > work" if you scale the Kubernetes deployment, because they will cause "cache > inconsistencies", unless the caches collaborate to invalidate entries when > appropriate. This probably need some configuration. Some references: > * Log about some EhCache configuration when Fineract starts > * > [cache.xml|https://github.com/apache/fineract/blob/develop/fineract-provider/src/main/resources/META-INF/spring/cache.xml] > and > [ehcache.xml|https://github.com/apache/fineract/blob/develop/fineract-provider/src/main/resources/META-INF/spring/ehcache.xml] > in Fineract source code > * [package > org.apache.fineract.infrastructure.cache|https://github.com/apache/fineract/tree/develop/fineract-provider/src/main/java/org/apache/fineract/infrastructure/cache] > in Fineract source code > * [~kumaranath_fernando] ([~kumaranathfernando] ?)'s GSOC 2018 > [proposal|https://cwiki.apache.org/confluence/display/FINERACT/Google+Summer+Code+2018+-+Scalability+and+performance+improvements] > and [final > report|https://cwiki.apache.org/confluence/display/FINERACT/GSOC+2018+Final+Report-+Scalability+and+performance+improvements] > * [~apremalal]'s GSOC 2013 work about caching: [YouTube > demo|https://www.youtube.com/watch?v=30X-uHo5MDg], [Mifos.org > blog|https://mifos.org/blog/meet-2013-google-summer-code-class-interns/], > * "Data Layer" on > [https://cwiki.apache.org/confluence/display/FINERACT/Key+Design+Principles] > I personally do not know the details about caching in Fineract. We should > either fine existing create new documentation about this. It would be worth > to reach out to the mailing list to start a discussion and get input on what > is required to make this work. > FYI [~xurror], [~awasum], [~angeh] -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (FINERACT-880) Fineract Caches & Kubernetes Deployment
[ https://issues.apache.org/jira/browse/FINERACT-880?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17269792#comment-17269792 ] Benura Abeywardena commented on FINERACT-880: - [~vorburger] Sir I would like to work on this issue > Fineract Caches & Kubernetes Deployment > --- > > Key: FINERACT-880 > URL: https://issues.apache.org/jira/browse/FINERACT-880 > Project: Apache Fineract > Issue Type: Improvement > Components: Performance >Reporter: Michael Vorburger >Priority: Major > Labels: kubernetes, scalability, technical > > The Kubernetes deployment contributed in FINERACT-783 by default creates a > Kubernetes Deployment with a single Pod (based on Fineract's Docker Compose > set-up). > The goal of this issue is to investigate what is missing to make it possible > to "scale horizontally" by increasing the number of replicas. > For example, I believe Fineract code caches certain things? I'm not clear if > they are enabled or disabled by default. Such caches typically do not "just > work" if you scale the Kubernetes deployment, because they will cause "cache > inconsistencies", unless the caches collaborate to invalidate entries when > appropriate. This probably need some configuration. Some references: > * Log about some EhCache configuration when Fineract starts > * > [cache.xml|https://github.com/apache/fineract/blob/develop/fineract-provider/src/main/resources/META-INF/spring/cache.xml] > and > [ehcache.xml|https://github.com/apache/fineract/blob/develop/fineract-provider/src/main/resources/META-INF/spring/ehcache.xml] > in Fineract source code > * [package > org.apache.fineract.infrastructure.cache|https://github.com/apache/fineract/tree/develop/fineract-provider/src/main/java/org/apache/fineract/infrastructure/cache] > in Fineract source code > * [~kumaranath_fernando] ([~kumaranathfernando] ?)'s GSOC 2018 > [proposal|https://cwiki.apache.org/confluence/display/FINERACT/Google+Summer+Code+2018+-+Scalability+and+performance+improvements] > and [final > report|https://cwiki.apache.org/confluence/display/FINERACT/GSOC+2018+Final+Report-+Scalability+and+performance+improvements] > * [~apremalal]'s GSOC 2013 work about caching: [YouTube > demo|https://www.youtube.com/watch?v=30X-uHo5MDg], [Mifos.org > blog|https://mifos.org/blog/meet-2013-google-summer-code-class-interns/], > * "Data Layer" on > [https://cwiki.apache.org/confluence/display/FINERACT/Key+Design+Principles] > I personally do not know the details about caching in Fineract. We should > either fine existing create new documentation about this. It would be worth > to reach out to the mailing list to start a discussion and get input on what > is required to make this work. > FYI [~xurror], [~awasum], [~angeh] -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (FINERACT-1292) Needs to add ReadinessProbe for MySql pod
[ https://issues.apache.org/jira/browse/FINERACT-1292?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Benura Abeywardena resolved FINERACT-1292. -- Resolution: Implemented > Needs to add ReadinessProbe for MySql pod > - > > Key: FINERACT-1292 > URL: https://issues.apache.org/jira/browse/FINERACT-1292 > Project: Apache Fineract > Issue Type: Task >Affects Versions: 1.4.0 >Reporter: Benura Abeywardena >Assignee: Benura Abeywardena >Priority: Minor > Fix For: 1.5.0 > > > In mysql deployment it's better to add ReadinessProbe which tells when the > container will be available for accepting traffic. This can be achieved by > using a command like `mysqladmin ping -u -p` to check whether > a mysql user has been properly created. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (FINERACT-1302) Add days in year at loan level
[ https://issues.apache.org/jira/browse/FINERACT-1302?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Yahalomi updated FINERACT-1302: - Description: At the moment, days in year configuration is not supported at the loan level so this parameter can only be adjusted at the product level. Adding that parameter will allow greater flexibility to organizations. was: At the moment, daysInYear configuration is not supported on calculateLoanSchedule action and this causes the simulated repayment schedule to be different than the repayment schedule created when you use create loan API. In order to remedy that difference, we only need to add support for this field so that it will be taken into account on the request. > Add days in year at loan level > -- > > Key: FINERACT-1302 > URL: https://issues.apache.org/jira/browse/FINERACT-1302 > Project: Apache Fineract > Issue Type: Improvement > Components: Loan >Affects Versions: 1.4.0 >Reporter: David Yahalomi >Assignee: David Yahalomi >Priority: Minor > > At the moment, days in year configuration is not supported at the loan level > so this parameter can only be adjusted at the product level. > Adding that parameter will allow greater flexibility to organizations. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (FINERACT-1302) Add days in year at loan level
[ https://issues.apache.org/jira/browse/FINERACT-1302?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Yahalomi updated FINERACT-1302: - Summary: Add days in year at loan level (was: Add days in year to calcLoanSchedule) > Add days in year at loan level > -- > > Key: FINERACT-1302 > URL: https://issues.apache.org/jira/browse/FINERACT-1302 > Project: Apache Fineract > Issue Type: Improvement > Components: Loan >Affects Versions: 1.4.0 >Reporter: David Yahalomi >Assignee: David Yahalomi >Priority: Minor > > At the moment, daysInYear configuration is not supported on > calculateLoanSchedule action and this causes the simulated repayment schedule > to be different than the repayment schedule created when you use create loan > API. > In order to remedy that difference, we only need to add support for this > field so that it will be taken into account on the request. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (FINERACT-1302) Add days in year to calcLoanSchedule
David Yahalomi created FINERACT-1302: Summary: Add days in year to calcLoanSchedule Key: FINERACT-1302 URL: https://issues.apache.org/jira/browse/FINERACT-1302 Project: Apache Fineract Issue Type: Improvement Components: Loan Affects Versions: 1.4.0 Reporter: David Yahalomi Assignee: David Yahalomi At the moment, daysInYear configuration is not supported on calculateLoanSchedule action and this causes the simulated repayment schedule to be different than the repayment schedule created when you use create loan API. In order to remedy that difference, we only need to add support for this field so that it will be taken into account on the request. -- This message was sent by Atlassian Jira (v8.3.4#803005)
