14:03:36 <farheen_att> #startmeeting Architecture Committee
14:03:36 <collabot`> Meeting started Wed Mar 11 14:03:36 2020 UTC.  The chair is farheen_att. Information about MeetBot at http://wiki.debian.org/MeetBot.
14:03:36 <collabot`> Useful Commands: #action #agreed #help #info #idea #link #topic.
14:03:36 <collabot`> The meeting name has been set to 'architecture_committee'
14:09:21 <farheen_att> #topic super admin requirements discussion
14:10:11 <farheen_att> #info Phillippe I tried to list functionality that admin and super admin would have.
14:10:29 <farheen_att> #info Rajesh - Never saw the slide.
14:11:01 <farheen_att> #info Phillippe - The admin will have three functions. Manage Add Remove users.  They have to manage the request when a user wants to publish a model.
14:11:18 <farheen_att> #info they have to manage the catalog domain.
14:12:32 <farheen_att> #info Admin's control their domains.  In the user profile you need to add a new field called domain.  The list of domain will be managed by the super admin.  The super admin will have the rite to create the domains
14:13:59 <farheen_att> #info Philippe - In big companies you have specific domains like R&D commercial.  If you are the only admin you will not be able to manage the users of all the domains.
14:14:25 <farheen_att> #info there are two levels.  super admin and admin.
14:26:13 <farheen_att> #info The admin will control the role of the publisher.
14:27:08 <farheen_att> the admin will manage user and roles.
14:27:33 <farheen_att> #action Philippe - create an end to end flow.
14:29:06 <farheen_att> #info Phiippe - Damain A the catalog feature will not be modified.  Will be able to publish to public.
14:30:12 <farheen_att> #info Philippe - Give the publisher role to the admin of the domain.  But if we can give the publisher role to the super admin.
14:32:01 <farheen_att> #action Rajesh in parallel provide the wire-frame.  We can target the UX review in the current sprint.
14:32:54 <farheen_att> #info Amol - there are a lot of screen changes that have to made.
14:33:35 <farheen_att> #action Amol bring a list of all the impacted screens so we can analyze.
14:35:35 <farheen_att> #topic License management admin feature
14:36:31 <farheen_att> #info Michelle - Introduce a formal License Admin role and possibly a license page to control the LUM editor and the RTU editor.
14:39:29 <farheen_att> #info Currently there is no control of who can use the RTU editor.  There is a form field that needs to be controlled.  Access and validation is needed.  We are proposing adding the License Admin role in an Acumos instance to control the access, validation, and creating license profiles.
14:42:14 <farheen_att> #info I got concurrence from the PTL and Community Committee.
14:44:38 <farheen_att> #info Manoop - Starting with the License Admin role.  We should be able to support creating the role and assigning to users.  Beyond that you want to importing of files?
14:46:15 <farheen_att> #info Michelle - The RTU file is sent to LUM and retrieved from LUM.  The License Admin can create license profile can be used to create default licenses for their users.
14:46:33 <farheen_att> #info Manoop will the LUM be coupled with Acumos?
14:46:50 <farheen_att> #info Michelle - we want to bundle it Acumos but keep it stand alone.
14:47:46 <farheen_att> #info Manoop - We can still map artifacts to keep the licensing modules separate.  We can brain storm on that.
14:48:57 <farheen_att> #info Michelle - Our charge was two fold.  Provide and out of box license management and also make it available to be extended with other platforms.
14:49:41 <farheen_att> #Manoop - Mapping of catalogs and models that will eventually become a tightly coupled where license won't be stand alone.
14:50:31 <farheen_att> #info Manoop - we can discuss that in future.  For the license admin role can be designed with Farheen and Reuben.
14:51:31 <farheen_att> #topic Epics SOAJS pipelines
14:51:45 <farheen_att> #topic Composite Solutions
14:52:33 <farheen_att> #info Sayee Vaibhave the ask is to evaluate how SOAJS will impact your composite workflows.  We don't have to develop if the work is too high.
14:53:13 <farheen_att> #info Viabhav - Deployment team has to be evaluated.
14:53:59 <farheen_att> #info We don't have a deployment team.  Dont give the ETE deployment.  How is it being deployed for Acu-Compose and MLWorkbench.
14:54:22 <farheen_att> #info Manoop - Can we re-use HELM charts that Acu-Compose will use?
14:55:15 <farheen_att> #info Vaibhav - We don't deploy HELM charts.  We deploy blueprint orchestrator that takes care of if you have two models 3 images will be deployed.
14:55:49 <farheen_att> #info Manoop - Can we explore to see how we can translate that bp into what SOAJS can provide.
14:57:26 <farheen_att> #info Manoop - action/ Vaibhave create a user story as SOAJS scope and dependent on dev environment.  Me and Murali will get you the environment.
14:57:46 <farheen_att> #topic Training Deploying models
14:58:02 <farheen_att> #info Manoop - we want to see dependencies.
14:59:17 <farheen_att> #info Wenting - You are looking for dependencies we are not ready for that.  We have decision several decision points.  I can put together a deck and defer it to the next release.
14:59:39 <farheen_att> #info If SOAJS is ready you can use it or do you have another choice for Demeter?
15:00:08 <farheen_att> #info Wenting - we will use whatever the platform gives.
15:00:38 <farheen_att> #info Manoop - We will try SOAJS.
15:00:43 <farheen_att> #info Wenting agrees
15:01:31 <farheen_att> #info Manoop - Manoop when the SOAJS is released so Murali keep Wentings epic dependent on the SOAJS epic.
15:01:54 <farheen_att> #info Vaibhav - Looking at the user story I don't see SOAJS.
15:02:27 <farheen_att> #info Manoop - we redefined the scope using Jenkins.  We were unsuccessful so we will update the epics with SOAJS.
15:03:07 <farheen_att> #info Manoop - There are stale repos in Acumos.  Please reply to the list.
15:04:09 <farheen_att> #info Manoop - Mark them as read only so it will be cleaner.
15:04:13 <farheen_att> #endmeeting