Hi Bhakti, I have few questions here. Correct me if I am wrong please.
1) Why are we developing a separate application for the admin features. I think we could append these admin features also to the same code base [1]. As per my understanding, it'll be just about adding some javascript code to enable these features. More than that, it's a way to reuse all the other common components (Login, sign up, home etc.) 2) Is there a reason for using the Django service layer between the client and the custom apis? Just curious to know. 3) Should the tenant creation be allowed for both admin and normal users? I can see there's a tenant approval process allowed only for admin users. I wonder if there is a reason for having an approval process? Regards, Dinuka [1] https://github.com/apache/airavata-custos-portal On Sat, Oct 17, 2020 at 9:07 PM Isuru Ranawaka <[email protected]> wrote: > > > ---------- Forwarded message --------- > From: Narvekar, Bhakti Sunil <[email protected]> > Date: Fri, Oct 16, 2020 at 9:29 PM > Subject: Overall architecture and deployment of Custos Admin Portal > To: [email protected] <[email protected]> > Cc: Ranawaka, Isuru Janith <[email protected]>, Isuru Ranawaka < > [email protected]> > > > Hello Everyone, > > > > We are planning to integrate Custos Portal with Custos Admin portal. I > would like to share the overall architecture for Custos Admin Portal and > the architecture for Custos Portal will be explained by Isuru. > > > > *Overall Archirecture: *The Custos Admin portal is implemented using > Django and Vue.js. > > Below is the working for Custos Admin Portal: > > > > 1. A user/admin can register/login into the system. > 2. If a user logs in, he can perform the below specified actions: > 1. Request new tenant – The user enters details like client name, > email, redirect URL, etc to create a new tenant. Once a tenant is > created > successfully, Custos ID and Custos Secret are displayed for the client. > 2. List all tenants – The user can view all the tenants that he has > created so far. If he clicks on the clickable link, he can view all the > details for a tenant. > 3. If an admin logs in, he can perform the below specified actions: > 1. Request new tenant – The admin enters details like client name, > email, redirect URL, etc to create a new tenant. Once a tenant is > created > successfully, Custos ID and Custos Secret are displayed for the client. > 2. List all tenants – The admin can view all the tenants that he > has created so far. On clicking the clickable link, admin can perform > the > three functions – edit, approve or decline. > > > > > > > > > > > > *Deployment:* > > The portal is deployed on centos using Apache and mod_wsgi. The link to > view the admin portal is -> https://dev.portal.custos.scigap.org/ > > > > > > > > Sincerely, > > Bhakti Narvekar > > > > > > > > > -- > Research Software Engineer > Indiana University, IN > >
