Re: Setup on Containers

[Courage Angeh]

Hi Juhan and Patrick,

Juhan,
Thanks for the feedback on the start-up script. I tried your changes and
the new network name fails on my system. So I added a command to create the
network on the start-up script and used the network in the compose files.
Please try it to verify that it works for you and let me know. If it
doesn't work please can you create a start-up script compatible with Mac-OS
and share with the community (via a PR)?
To that please add the improvements you did on the migration script.

If we let Docker assign IP addresses to the Fineract services then we will
have to use Docker to get the IP used by the provisioner script, which is
additional processing time. But you can do the change if you feel
comfortable with that.

Actually, the provision script makes API calls. But to talk to an API we
need the IP address or domain name.

Patrick, I tried using the docker service names in my provisioner shell
script and my shell didn't recognize the service names.

Thanks,
Courage.

On Fri, Jan 4, 2019 at 2:08 PM Patrick Finken 
wrote:

> Be careful, spinning all the containers at the same time required some
> resources.
> First of all check the CPU and the memory you allocated to docker. I think
> by default it is 2GB of ram. it's not enough for all the containers. You
> might want to increase it.
> I suggest you start with just identity and provisioner services to test the
> process.
>
> Patrick
>
> On Fri, Jan 4, 2019 at 1:39 PM Juhan Aasaru  wrote:
>
> > Hi Patrick,
> >
> > thanks for the step-by-step instructions. Here are the results:
> >
> > When I ran "docker-compose up" inside "external-tools" and then "docker
> > network ls" in another terminal I got:
> >
> > 5271e3e6a6ebexternal-tools_app_net   bridge
> >   local
> > 29fa4ca2bf83external-tools_default   bridge
> >   local
> >
> > So the dash ("-") inside the folder name propagates into the network name
> > as well (at least in my mac).
> > To comply with this I changed "externaltools_app_net" to
> > "external-tools_app_net" in start-up.sh and
> > last row of docker-compose.yml in main directory (other option would have
> > been renaming directory "external-tools" to "externaltools").
> >
> > When I ran "docker-compose up" in the main directory I first got an error
> > with a missing jar in ledger-ms, but I discovered that migration-script
> was
> > missing "accounting", I fixed that and created a pull request together
> with
> > adding dash to network name.
> > Courage, would you mind taking a look at the pull request:
> >
> >
> https://github.com/openMF/fineract-cn-containers/pull/7/commits/465dfd21aa516cf2c7a363b7bc30d4346c2316c2
> >
> > After that the "docker-compose up" in the main directory ran until the
> > output was:
> >
> > Attaching to identity-ms, deposit-ms, portfolio-ms, report-ms, ledger-ms,
> > customer-ms, office-ms, rhythm-ms, teller-ms
> >
> > And then it halted.
> >
> > When I run "docker-compose down" and then "docker-compose --verbose up"
> > then I got a bit more info:
> >
> > Attaching to identity-ms, deposit-ms, portfolio-ms, report-ms, ledger-ms,
> > customer-ms, office-ms, rhythm-ms, teller-ms
> > compose.cli.verbose_proxy.proxy_callable: docker events <-
> > (filters={'label': ['com.docker.compose.project=fineract-cn-containers',
> > 'com.docker.compose.oneoff=False']}, decode=True)
> > urllib3.connectionpool._make_request: http://localhost:None "GET
> >
> >
> /v1.25/events?filters=%7B%22label%22%3A+%5B%22com.docker.compose.project%3Dfineract-cn-containers%22%2C+%22com.docker.compose.oneoff%3DFalse%22%5D%7D
> > HTTP/1.1" 200 None
> > compose.cli.verbose_proxy.proxy_callable: docker events ->
> > 
> >
> > I don't quite understand what it means.
> >
> > It seems like it completely freezes Docker as in another terminal even
> > running "docker ps" doesn't repsond anything.
> > Just in case I will now reinstall Docker in my local computer and try
> > again.
> >
> > Juhan
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> > Kontakt Patrick Finken () kirjutas kuupäeval
> R,
> > 4. jaanuar 2019 kell 18:06:
> >
> > > Hey Juan,
> > >
> > > You should first run the external service before running the main
> > services.
> > >
> > > Basically, run the command "docker-compose up" inside the
> external_tools
> > > folder, or specify the docker-compose file: "docker-compose up -f
> > > ./external-toools/docker-compose.yml".
> > > It will spin up cassandra, activemq and maria db. And it will also
> create
> > > the network *"externaltools_app_net". *You can make sure it is the
> > correct
> > > name by running the command "docker network ls". If it's not, for
> > example,
> > > if the folder has a different name,  you should update the main
> > > docker-compose.yml file with the correct network name.
> > >
> > > Then inside the main folder, in a different terminal, run the command
> > > "docker-compose up" to start the main services.
> > >
> > > In the start-up script, since 

Invitation to edit Apache Fineract's board report for Jan 2019

[Vishwas Babu]

Hello Fineractors,

Hope all of you are having a great beginning to the new year.

The initial draft of the board report for the previous quarter is shared at
https://cwiki.apache.org/confluence/display/FINERACT/2019-1+January+Report ,
please edit as you see fit. I plan to do a once over on the coming Monday
and submit the report by Tuesday the 8th of Jan (PST).

Wishing you a wonderful weekend,
Vishwas

Re: Setup on Containers

[Patrick Finken]

Be careful, spinning all the containers at the same time required some
resources.
First of all check the CPU and the memory you allocated to docker. I think
by default it is 2GB of ram. it's not enough for all the containers. You
might want to increase it.
I suggest you start with just identity and provisioner services to test the
process.

Patrick

On Fri, Jan 4, 2019 at 1:39 PM Juhan Aasaru  wrote:

> Hi Patrick,
>
> thanks for the step-by-step instructions. Here are the results:
>
> When I ran "docker-compose up" inside "external-tools" and then "docker
> network ls" in another terminal I got:
>
> 5271e3e6a6ebexternal-tools_app_net   bridge
>   local
> 29fa4ca2bf83external-tools_default   bridge
>   local
>
> So the dash ("-") inside the folder name propagates into the network name
> as well (at least in my mac).
> To comply with this I changed "externaltools_app_net" to
> "external-tools_app_net" in start-up.sh and
> last row of docker-compose.yml in main directory (other option would have
> been renaming directory "external-tools" to "externaltools").
>
> When I ran "docker-compose up" in the main directory I first got an error
> with a missing jar in ledger-ms, but I discovered that migration-script was
> missing "accounting", I fixed that and created a pull request together with
> adding dash to network name.
> Courage, would you mind taking a look at the pull request:
>
> https://github.com/openMF/fineract-cn-containers/pull/7/commits/465dfd21aa516cf2c7a363b7bc30d4346c2316c2
>
> After that the "docker-compose up" in the main directory ran until the
> output was:
>
> Attaching to identity-ms, deposit-ms, portfolio-ms, report-ms, ledger-ms,
> customer-ms, office-ms, rhythm-ms, teller-ms
>
> And then it halted.
>
> When I run "docker-compose down" and then "docker-compose --verbose up"
> then I got a bit more info:
>
> Attaching to identity-ms, deposit-ms, portfolio-ms, report-ms, ledger-ms,
> customer-ms, office-ms, rhythm-ms, teller-ms
> compose.cli.verbose_proxy.proxy_callable: docker events <-
> (filters={'label': ['com.docker.compose.project=fineract-cn-containers',
> 'com.docker.compose.oneoff=False']}, decode=True)
> urllib3.connectionpool._make_request: http://localhost:None "GET
>
> /v1.25/events?filters=%7B%22label%22%3A+%5B%22com.docker.compose.project%3Dfineract-cn-containers%22%2C+%22com.docker.compose.oneoff%3DFalse%22%5D%7D
> HTTP/1.1" 200 None
> compose.cli.verbose_proxy.proxy_callable: docker events ->
> 
>
> I don't quite understand what it means.
>
> It seems like it completely freezes Docker as in another terminal even
> running "docker ps" doesn't repsond anything.
> Just in case I will now reinstall Docker in my local computer and try
> again.
>
> Juhan
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
> Kontakt Patrick Finken () kirjutas kuupäeval R,
> 4. jaanuar 2019 kell 18:06:
>
> > Hey Juan,
> >
> > You should first run the external service before running the main
> services.
> >
> > Basically, run the command "docker-compose up" inside the external_tools
> > folder, or specify the docker-compose file: "docker-compose up -f
> > ./external-toools/docker-compose.yml".
> > It will spin up cassandra, activemq and maria db. And it will also create
> > the network *"externaltools_app_net". *You can make sure it is the
> correct
> > name by running the command "docker network ls". If it's not, for
> example,
> > if the folder has a different name,  you should update the main
> > docker-compose.yml file with the correct network name.
> >
> > Then inside the main folder, in a different terminal, run the command
> > "docker-compose up" to start the main services.
> >
> > In the start-up script, since the IPs are not hardcoded anymore, you
> should
> > also replace the IP with the service name. Also, make sure the network
> name
> > is correct. It should be the same as the previous step.
> >
> > Let me know if it works.
> >
> > Patrick
> >
> > On Thu, Jan 3, 2019 at 6:03 PM Juhan Aasaru  wrote:
> >
> > > Hi!
> > >
> > > Courage and Patrick, thanks for explaining to me about the IP addresses
> > > pointing me at the correct repo. Courage, thanks for the recent work on
> > the
> > > repo and for replacing the static IP-s with the service names inside
> > > docker-compose files, I think this increases the readability a lot.
> > >
> > > I tried to run it locally (I didn't yet replace static IP-s with the
> > > service names) and these are my observations.
> > >
> > > When previously I had a problem with static IP-s being not found when
> > > running in Mac then
> > > now I only had to change one thing :
> > > in start-up.sh script I changed this line:
> > >
> > > while ! nc -z 172.16.238.5 9042; do
> > >
> > > to refer to localhost like this:
> > >
> > > while ! nc -z 127.0.0.1 9042; do
> > >
> > > Because in Mac host system doesn't know anything about Docker IP-s.
> > >
> > > But I got stuck with this line of start-up.sh script:
> > >
> > > docker run -d --name 

Re: Setup on Containers

[Juhan Aasaru]

Hi Patrick,

thanks for the step-by-step instructions. Here are the results:

When I ran "docker-compose up" inside "external-tools" and then "docker
network ls" in another terminal I got:

5271e3e6a6ebexternal-tools_app_net   bridge
  local
29fa4ca2bf83external-tools_default   bridge
  local

So the dash ("-") inside the folder name propagates into the network name
as well (at least in my mac).
To comply with this I changed "externaltools_app_net" to
"external-tools_app_net" in start-up.sh and
last row of docker-compose.yml in main directory (other option would have
been renaming directory "external-tools" to "externaltools").

When I ran "docker-compose up" in the main directory I first got an error
with a missing jar in ledger-ms, but I discovered that migration-script was
missing "accounting", I fixed that and created a pull request together with
adding dash to network name.
Courage, would you mind taking a look at the pull request:
https://github.com/openMF/fineract-cn-containers/pull/7/commits/465dfd21aa516cf2c7a363b7bc30d4346c2316c2

After that the "docker-compose up" in the main directory ran until the
output was:

Attaching to identity-ms, deposit-ms, portfolio-ms, report-ms, ledger-ms,
customer-ms, office-ms, rhythm-ms, teller-ms

And then it halted.

When I run "docker-compose down" and then "docker-compose --verbose up"
then I got a bit more info:

Attaching to identity-ms, deposit-ms, portfolio-ms, report-ms, ledger-ms,
customer-ms, office-ms, rhythm-ms, teller-ms
compose.cli.verbose_proxy.proxy_callable: docker events <-
(filters={'label': ['com.docker.compose.project=fineract-cn-containers',
'com.docker.compose.oneoff=False']}, decode=True)
urllib3.connectionpool._make_request: http://localhost:None "GET
/v1.25/events?filters=%7B%22label%22%3A+%5B%22com.docker.compose.project%3Dfineract-cn-containers%22%2C+%22com.docker.compose.oneoff%3DFalse%22%5D%7D
HTTP/1.1" 200 None
compose.cli.verbose_proxy.proxy_callable: docker events ->


I don't quite understand what it means.

It seems like it completely freezes Docker as in another terminal even
running "docker ps" doesn't repsond anything.
Just in case I will now reinstall Docker in my local computer and try again.

Juhan















Kontakt Patrick Finken () kirjutas kuupäeval R,
4. jaanuar 2019 kell 18:06:

> Hey Juan,
>
> You should first run the external service before running the main services.
>
> Basically, run the command "docker-compose up" inside the external_tools
> folder, or specify the docker-compose file: "docker-compose up -f
> ./external-toools/docker-compose.yml".
> It will spin up cassandra, activemq and maria db. And it will also create
> the network *"externaltools_app_net". *You can make sure it is the correct
> name by running the command "docker network ls". If it's not, for example,
> if the folder has a different name,  you should update the main
> docker-compose.yml file with the correct network name.
>
> Then inside the main folder, in a different terminal, run the command
> "docker-compose up" to start the main services.
>
> In the start-up script, since the IPs are not hardcoded anymore, you should
> also replace the IP with the service name. Also, make sure the network name
> is correct. It should be the same as the previous step.
>
> Let me know if it works.
>
> Patrick
>
> On Thu, Jan 3, 2019 at 6:03 PM Juhan Aasaru  wrote:
>
> > Hi!
> >
> > Courage and Patrick, thanks for explaining to me about the IP addresses
> > pointing me at the correct repo. Courage, thanks for the recent work on
> the
> > repo and for replacing the static IP-s with the service names inside
> > docker-compose files, I think this increases the readability a lot.
> >
> > I tried to run it locally (I didn't yet replace static IP-s with the
> > service names) and these are my observations.
> >
> > When previously I had a problem with static IP-s being not found when
> > running in Mac then
> > now I only had to change one thing :
> > in start-up.sh script I changed this line:
> >
> > while ! nc -z 172.16.238.5 9042; do
> >
> > to refer to localhost like this:
> >
> > while ! nc -z 127.0.0.1 9042; do
> >
> > Because in Mac host system doesn't know anything about Docker IP-s.
> >
> > But I got stuck with this line of start-up.sh script:
> >
> > docker run -d --name provisioner-ms --env
> > eureka.instance.hostname=172.16.238.2 --env ribbon.listOfServers=
> > 172.16.238.2:9090 \
> >   --env eureka.client.serviceUrl.defaultZone=
> > http://172.16.238.2:8761/eureka
> > --env  activemq.brokerUrl=tcp://
> > 172.16.238.3:61616 \
> >   --env cassandra.contactPoints=172.16.238.5:9042 --env
> > mariadb.host=172.16.238.4 --network externaltools_app_net \
> >   --ip 172.16.238.6 provisioner:latest
> >
> > It gets an error:
> >
> > docker: Error response from daemon: network externaltools_app_net not
> > found.
> >
> > Which kind of makes sense because it is declared in the 

Re: Setup on Containers

[Patrick Finken]

Hey Juan,

You should first run the external service before running the main services.

Basically, run the command "docker-compose up" inside the external_tools
folder, or specify the docker-compose file: "docker-compose up -f
./external-toools/docker-compose.yml".
It will spin up cassandra, activemq and maria db. And it will also create
the network *"externaltools_app_net". *You can make sure it is the correct
name by running the command "docker network ls". If it's not, for example,
if the folder has a different name,  you should update the main
docker-compose.yml file with the correct network name.

Then inside the main folder, in a different terminal, run the command
"docker-compose up" to start the main services.

In the start-up script, since the IPs are not hardcoded anymore, you should
also replace the IP with the service name. Also, make sure the network name
is correct. It should be the same as the previous step.

Let me know if it works.

Patrick

On Thu, Jan 3, 2019 at 6:03 PM Juhan Aasaru  wrote:

> Hi!
>
> Courage and Patrick, thanks for explaining to me about the IP addresses
> pointing me at the correct repo. Courage, thanks for the recent work on the
> repo and for replacing the static IP-s with the service names inside
> docker-compose files, I think this increases the readability a lot.
>
> I tried to run it locally (I didn't yet replace static IP-s with the
> service names) and these are my observations.
>
> When previously I had a problem with static IP-s being not found when
> running in Mac then
> now I only had to change one thing :
> in start-up.sh script I changed this line:
>
> while ! nc -z 172.16.238.5 9042; do
>
> to refer to localhost like this:
>
> while ! nc -z 127.0.0.1 9042; do
>
> Because in Mac host system doesn't know anything about Docker IP-s.
>
> But I got stuck with this line of start-up.sh script:
>
> docker run -d --name provisioner-ms --env
> eureka.instance.hostname=172.16.238.2 --env ribbon.listOfServers=
> 172.16.238.2:9090 \
>   --env eureka.client.serviceUrl.defaultZone=
> http://172.16.238.2:8761/eureka
> --env  activemq.brokerUrl=tcp://
> 172.16.238.3:61616 \
>   --env cassandra.contactPoints=172.16.238.5:9042 --env
> mariadb.host=172.16.238.4 --network externaltools_app_net \
>   --ip 172.16.238.6 provisioner:latest
>
> It gets an error:
>
> docker: Error response from daemon: network externaltools_app_net not
> found.
>
> Which kind of makes sense because it is declared in the root docker-compose
> file that is started only later by the same script.
> I tried copying this network declaration from root docker-compose.yml to
> external-tools/docker-compose.yml but no luck.
> When I completely removed ip and network flags from docker-run command then
> the provisioner couldn't find cassandra
> This error, however, can be something to do with my own environment.
>
> Courage, could you please explain the idea with the different networks
> ("externaltools_app_net" declared and "default" referred in root
> docker-compose.yml and app_net declared and used in
> external-tools/docker-compose.yml). If all the services are in the same
> network then could we maybe just use one network?
>
> While I was writing this the new emails arrived about maybe not needing the
> static ip-s at all.
> If the provisioner script needs to know the IP-s then one way would be to
> let docker assign the ip-s itself
> but then to look them up:
>
> https://stackoverflow.com/questions/17157721/how-to-get-a-docker-containers-ip-address-from-the-host
> This wouldn't still work in mac, however.
> Or if provisioning can be done via API maybe the provisioner script could
> be solved using similar approach?
>
> Kind regards
> Juhan
>
>
>
> Kontakt Ed Cable () kirjutas kuupäeval N, 3. jaanuar
> 2019 kell 18:46:
>
> > I want to thank everyone for their valuable and transparent discussion on
> > helping improve the deployability of Fineract CN in the cloud.
> >
> > The mailing list is the perfect place for an open, back-and-forth
> > discussion and debate and of course some aspects might get lost in
> > translation but I don't want anybody to hesitate from sharing their
> inputs
> > and rationale. I encourage others in the community have experience in
> this
> > domain to participate in the discussion as well.
> >
> > Hopefully at the end of this discuss we can document and summarize our
> > findings in the wiki as the conclusive documentation that we've landed
> > upon.
> >
> > Cheers,
> >
> > Ed
> >
> > On Thu, Jan 3, 2019 at 9:28 AM Courage Angeh 
> > wrote:
> >
> > > Hi Patrick,
> > >
> > > Thanks for the explanation. The hardcoded IP addresses are necessary.
> The
> > > is a provisioner script that uses these addresses to provision the
> system
> > > after startup. Starting the Fineract CN services is just one part of
> the
> > > set-up process.
> > > If you read the README you will realize that.
> > >
> > > I think it would have been better for you to 

Re: Share Product Create Issue

[Santosh Math]

Hi Zayyad,

In the first step 'Details', Provide Description. It's mandatory, but
Asterisk is missing, which  is fixed for next release.

https://staging.openmf.org/#/createshareproduct

On Fri, Jan 4, 2019 at 5:05 PM Zayyad A. Said <
zay...@intrasofttechnologies.com> wrote:

> Devs,
>
>
>
> I am trying to create a share product with the following parameters, am
> getting data integrity issue on terms:
>
>
>
> Product Name: Share Premium (SP)
>
> Decimal Place: 0
>
> Multiples of: 1
>
> Total No of shares: 1,000,000
>
> Shares to be issued: 1,000,000
>
> Nominal Price: 1
>
> Shares per client: 1,000 (Min.)/1,000 (Default)/ 50,000 (Max)
>
> Min. Active Period 365 Days
>
> Lock-in Period: 3 Months
>
> Allow dividends for inactive: true
>
> Market Price Period from: 1/01/2018 @ 100/=
>
> No charges and use cash accounting.
>
>
>
> Try replicating this terms on your instance and advise if you can create a
> share product.
>
>
>
> Regards;
>
>
>
> *
>
> *Zayyad A. Said | Chairman & C.E.O*
>
>
>
> Cell No.: +254 716 615274 | Skype: *zsaid2011*
>
> Email: zay...@intrasofttechnologies.com
>
> Schedule Meetings: https://calendly.com/zayyadsaid
>
> [image: Description: Email banner]
>
>
>


-- 
Thanks & Regards

Santosh Math

*QA Engineer*

*Conflux Technologies Pvt Ltd *
| *Office*: +91-080-41208662 |

*Address*: #304, 2nd Floor, 7th Main Road, HRBR Layout 1st Block,
Bengaluru, Karnataka, 560043 INDIA

Share Product Create Issue

[Zayyad A. Said]

Devs,

 

I am trying to create a share product with the following parameters, am
getting data integrity issue on terms:

 

Product Name: Share Premium (SP)

Decimal Place: 0

Multiples of: 1

Total No of shares: 1,000,000

Shares to be issued: 1,000,000

Nominal Price: 1

Shares per client: 1,000 (Min.)/1,000 (Default)/ 50,000 (Max)

Min. Active Period 365 Days

Lock-in Period: 3 Months

Allow dividends for inactive: true

Market Price Period from: 1/01/2018 @ 100/=

No charges and use cash accounting.

 

Try replicating this terms on your instance and advise if you can create a
share product.

 

Regards;

 

***

Zayyad A. Said | Chairman & C.E.O

 

Cell No.: +254 716 615274 | Skype: zsaid2011

Email:  
zay...@intrasofttechnologies.com 

Schedule Meetings:  
https://calendly.com/zayyadsaid 

Description: Email banner