git.net

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Setup on Containers


Hi Juhan,

The Kubernetes scripts should not work correctly 'cause I am still to work
on them,  I am moving to a different cloud platform, for some reason, it's
delaying.
Also, you should run the applications locally and they should run
successfully, NOTE THAT I UPDATED THE CODE ON PROVISIONER ONLY, so you
would only need my code for provisioner. I won't say the IP addresses are
hard coded, I just decided to use those IP addresses, you could configure
different IP addresses. Another good idea will be to configure the IP
addresses at a much higher so that it will be easier to manage changes
whenever we need to use a different IP address.

Also, rhythm is not commented out, just payroll is commented out and that
was done on purpose. I plan to use it to help me optimize the scripts so
that adding a new service would not need a lot of configuration as it does
now.

That should be a typo, I would check out your PR thanks. It's different on
my PC so sorry about that.

I hope I answered your questions. If you have any other questions
please feel free.

Thanks,
Courage.

On Sun, Dec 30, 2018 at 11:14 AM Juhan Aasaru <aasaru@xxxxxxxxx> wrote:

> Hi Courage,
>
> I also checked out the work you have done on containers as I also plan to
> deploy the Fineract CN services to the cloud. Would you mind explaining a
> few things for me:
>
> 1. I tried running the scripts (taken from your GitHub fork) locally (I
> always find I need to be able to run anything locally first before
> deploying to anywhere else).
> I tried out both the Kubernetes scripts (with Minikube) and the
> docker-compose scripts. I didn't manage to get them running because of the
> hardcoded IP addresses (there is no easy method in mac to have several
> static IP addresses at the same time). I don't have much experience with
> deploying container-based
> systems so if you could elaborate on the topic a bit and if it would make
> sense to
> to replace IP addresses with service names or aliases.
>
> 2. The docker-compose.yml in root directory has all of the services besides
> rythm-ms commented out. Can one just comment other services back in or is
> there some work that needs to be done first?
>
> 3. I think I found a typo in external-scripts/docker-compose.yml
> You have mapped Cassandra port 9042 to port 9142 for the outside world but
> I think it should be still 9042. I created a pull request for you repo to
> fix this.
>
> I hope you have a chance to help me with my questions.
>
> Thanks
> Juhan Aasaru
>
>
>
>
>
>
>
>
>
> Kontakt Courage Angeh (<courageangeh@xxxxxxxxx>) kirjutas kuupäeval K, 26.
> detsember 2018 kell 17:29:
>
> > Hi Patrick,
> >
> > Could you check this out instead?
> > https://github.com/Anh3h/fineract-cn-docker-scripts
> > I am still to merge that into the Mifos codebase
> > That should work.
> >
> > Thanks,
> > Courage.
> >
> > On Tue, Dec 25, 2018 at 6:04 PM Patrick Finken <patrick@xxxxxxxxxxxxxxxx
> >
> > wrote:
> >
> > > 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 <courageangeh@xxxxxxxxx>
> > > 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 <
> > patrick@xxxxxxxxxxxxxxxx
> > > >
> > > > 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
> > >
> >
>