Aleks, Apache IDs are only available to committers. The guide to becoming a committer is at https://cwiki.apache.org/confluence/display/FINERACT/Becoming+a+Committer
I know that the major body of your work related to Fineract isn't yet something the customer was willing to contribute back yet so you've been trying to build your public contributions in other ways. I was hoping that this task could be a great way to do that but unfortunately you won't be able to do the actual configuration and setup on the VMs until you have achieved committer status. Nonetheless though a great contribution you could make right now is giving your input on how the VM could be be configured and responded to some of the feedback from Viswa. Your inputs here would be exceptionally valuable to whoever from our group of committers steps up with enough free time to be able to configure the VM. Robert/Aleks - could you please share any questions/feedback you have on the VM setup on this thread? Thanks, Ed On Mon, Mar 19, 2018 at 8:51 AM, Aleksandar Vidakovic < [email protected]> wrote: > Hi Ed, > > ... how do I get one of those Apache IDs? Anything you need from me? > > Cheers, > > Aleks > > On Mon, Mar 19, 2018 at 3:50 PM Ed Cable <[email protected]> wrote: > >> Thanks Viswa. I will let Myrle and others reply to your input. Through >> Apache for this demo infrastructure I think we only have access to one VM. >> >> Myrle, Robert, Aleks, >> >> Did you see Chris' comments on the Infra ticket? https://issues.apache. >> org/jira/browse/INFRA-16203 >> >> Permalink >> <https://issues.apache.org/jira/browse/INFRA-16203?focusedCommentId=16403788&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-16403788> >> [image: cml]Chris Lambertus >> <https://issues.apache.org/jira/secure/ViewProfile.jspa?name=cml> added >> a comment - 2 days ago >> We'll need a list of apache IDs who will need access to the VM. We use >> puppet to maintain configs, so we can set up some boilerplate config for >> httpd with proxy entries and letsencrypt SSL certs if you wish (or you can >> manage that entirely yourself.) We can also install a base set of packages >> if you let us know what you need. >> >> >> On Sun, Mar 18, 2018 at 3:51 AM, Viswa Ramamoorthy < >> [email protected]> wrote: >> >>> Hello, >>> >>> My 2 cents... >>> >>> Assuming >>> a) all of 30+ services (gtihub.com/apache/fineract-cn-*) to be deployed >>> as individual micro services >>> b) in a single VM (this is the quickest as more maturity needed for >>> multi VM deployments) >>> c) usage purpose is for integration environment for functional test & >>> demo >>> >>> I would say 8 core/24 GB/250 GB would be minimum spec. >>> >>> For future service additions, a second VM can be added to make it a >>> cluster. To prepare towards support for deployments in multiple VMs, >>> deployment strategy like Docker needs to be matured. There are other ways >>> to deploy services across multiple VMs. In my opinion, Docker with swarm or >>> Kubernetes would be a very good candidate >>> >>> Regards >>> Viswa Ramamoorthy >>> >>> On Saturday, March 17, 2018 06:45:48 PM EDT, Ed Cable < >>> [email protected]> wrote: >>> >>> I'm not sure the process as it's not well documented nor do I know the >>> virtual machine requirements for Fineract CN but I created the ticket and >>> would appreciate others from PMC to put in comments the specifics >>> required >>> for the instance: https://issues.apache.org/jira/browse/INFRA-16203 >>> >>> Thanks, >>> >>> Ed >>> >>> On Sat, Mar 17, 2018 at 9:01 AM, Myrle Krantz <[email protected]> wrote: >>> >>> > Hey Ed, >>> > >>> > It’s just a matter of putting in an Infra ticket. Anyone on the PMC >>> can do >>> > it. >>> > >>> > Regards, >>> > Myrle >>> >> >>> > >>> > On Sat 17. Mar 2018 at 08:50 Ed Cable <[email protected]> wrote: >>> > >>> > > Myrle, >>> > > >>> > > I know you are still slammed but wanted to see if you had the chance >>> to >>> > > place this request or if it was something I could do as I wanted to >>> get >>> > > Aleks up and going as it's proving problematic for a number of our >>> GSOC >>> > > aspirants to not be able to fully grok the functionality of Fineract >>> CN >>> > > without having access to a web app. For many the high hardware >>> > requirements >>> > > is proving to be an insurmountable barrier. Applications are due by >>> the >>> > > 27th so I was hoping by early next week we might be able to get this >>> > setup. >>> > > >>> > > Cheers, >>> > > >>> > > Ed >>> > > >>> > > On Mon, Mar 12, 2018 at 7:20 AM, Ed Cable <[email protected]> wrote: >>> > > >>> > > > Myrle, >>> > > > >>> > > > Robert Jakech and Aleksander Vidakovic have volunteered to assist. >>> I'll >>> > > > let you move forward with the process and let you provide them the >>> > > > necessary information to allow them to get access to infrstructure >>> and >>> > > get >>> > > > continuous build process going for the community to have access to >>> a >>> > > > publicly available instance of the demo server. >>> > > > >>> > > > Ed >>> > > > >>> > > > On Thu, Mar 8, 2018 at 6:26 AM, Myrle Krantz <[email protected]> >>> wrote: >>> > > > >>> > > >> On Wed, Mar 7, 2018 at 9:25 PM, Ed Cable <[email protected]> >>> wrote: >>> > > >> > Hi all, I wanted to give this thread a new subject line as it's >>> a >>> > > >> valuable >>> > > >> > discussion that had gone beyond the original topic. I'm >>> especially >>> > > >> thinking >>> > > >> > about this in the context of new potential contributors that are >>> > > coming >>> > > >> > along for GSOC that won't have the proper hardware to build and >>> > > deploy. >>> > > >> > >>> > > >> > While you all are continuing the discussion around >>> dockerization of >>> > > >> > services, running from a single process, and running >>> microservices >>> > > >> > selectively, I wanted to raise the request that Myrle and I had >>> > > >> discussed >>> > > >> > around requesting a VM from the Apache infrastructure to use to >>> > > deploy a >>> > > >> > public demo server for the community. This would provide a tool >>> for >>> > > >> users >>> > > >> > and partners to quickly evaluate and keep progress of >>> functionality >>> > > but >>> > > >> > more importantly allow web and mobile devs to test their changes >>> > > without >>> > > >> > having to build the entire project locally. >>> > > >> > >>> > > >> > Myrle can we request such infrastructure? >>> > > >> >>> > > >> I'll request if we have someone who will take on the deployment. >>> Do >>> > we? >>> > > >> >>> > > >> Best Regards, >>> > > >> Myrle >>> > > >> >>> > > > >>> > > > >>> > > > >>> > > > -- >>> >> > > > *Ed Cable* >>> >> >>> > > > President/CEO, Mifos Initiative >>> > > > [email protected] | Skype: edcable | Mobile: +1.484.477.8649 >>> <(484)%20477-8649> >>> >> > > > <(484)%20477-8649> >>> > > > >>> > > > *Collectively Creating a World of 3 Billion Maries | * >>> http://mifos.org >>> > > > <http://facebook.com/mifos> <http://www.twitter.com/mifos> >>> >>> > > > >>> > > > >>> > > >>> > > >>> > > -- >>> > > *Ed Cable* >>> >> >>> > > President/CEO, Mifos Initiative >>> > > [email protected] | Skype: edcable | Mobile: +1.484.477.8649 >>> <(484)%20477-8649> >>> > > >>> >> > > *Collectively Creating a World of 3 Billion Maries | * >>> http://mifos.org >>> > > <http://facebook.com/mifos> <http://www.twitter.com/mifos> >>> > > >>> > >>> >>> >>> >>> -- >>> *Ed Cable* >>> >> >>> President/CEO, Mifos Initiative >>> [email protected] | Skype: edcable | Mobile: +1.484.477.8649 >>> <(484)%20477-8649> >>> >>> *Collectively Creating a World of 3 Billion Maries | *http://mifos.org >>> <http://facebook.com/mifos> <http://www.twitter.com/mifos> >>> >> >> >> >> -- >> *Ed Cable* >> President/CEO, Mifos Initiative >> [email protected] | Skype: edcable | Mobile: +1.484.477.8649 >> <+1%20484-477-8649> >> >> *Collectively Creating a World of 3 Billion Maries | *http://mifos.org >> <http://facebook.com/mifos> <http://www.twitter.com/mifos> >> >> -- *Ed Cable* President/CEO, Mifos Initiative [email protected] | Skype: edcable | Mobile: +1.484.477.8649 *Collectively Creating a World of 3 Billion Maries | *http://mifos.org <http://facebook.com/mifos> <http://www.twitter.com/mifos>
