Hi Sudhakar, The allocation manager from last year contributions is here - https://github.com/apache/airavata-sandbox/tree/master/allocation-manager <https://github.com/apache/airavata-sandbox/tree/master/allocation-manager> the one Dimuthu is suggesting to clean up is a stale one.
I think we should turn the allocation manager into a larger goal of enforcing quotas mainly for user storage and probably take on as soon as possible. Cheers, Suresh > On Nov 30, 2018, at 8:37 AM, Pamidighantam, Sudhakar V > <spami...@illinois.edu> wrote: > > What is the estimated timeline for enforceable allocation management to be > available in Airavata, 2019, 2020? > > Thanks, > Sudhakar. > > From: DImuthu Upeksha <dimuthu.upeks...@gmail.com> > Reply-To: "dev@airavata.apache.org" <dev@airavata.apache.org> > Date: Friday, November 30, 2018 at 8:30 AM > To: "dev@airavata.apache.org" <dev@airavata.apache.org> > Subject: Re: Unused modules > > Hi Suresh, > > +1 for removing gfac modules as well > > Dimuthu > > On Fri, Nov 30, 2018 at 6:32 PM Apache Airavata <smarru.apa...@gmail.com > <mailto:smarru.apa...@gmail.com>> wrote: > +1 to remove all of them. While you are at it, should we also remove gfac > modules from develop and staging branches? > > Suresh > > > On Nov 30, 2018, at 6:44 AM, DImuthu Upeksha <dimuthu.upeks...@gmail.com > <mailto:dimuthu.upeks...@gmail.com>> wrote: > > Hi Folks, > > I can see that some modules [1] are no longer being used or actively > developed. > > allocation-manager > cloud > compute-account-provisioning > configuration > db-event-manager > integration-tests > monitoring > security > workflow > workflow-model > xbaya > xbaya-gui > > I'm suggesting to remove these unused modules as they affect the build time > and the clarity of the code. Any objections / suggestions? > > [1] https://github.com/apache/airavata/tree/staging/modules > <https://github.com/apache/airavata/tree/staging/modules> > > Thanks > Dimuthu
