14:02:48 #startmeeting Architecture Committee 14:02:48 Meeting started Wed Oct 16 14:02:48 2019 UTC. The chair is farheen. Information about MeetBot at http://wiki.debian.org/MeetBot. 14:02:48 Useful Commands: #action #agreed #help #info #idea #link #topic. 14:02:48 The meeting name has been set to 'architecture_committee' 14:06:02 #topic Agenda portal topics. Onboarding version (Bryan). Release status (Murali) 14:07:51 #info Tausif is sharing a word document 14:08:36 #info Issues reflecting the Search functionality. 14:11:11 #info reviewed Catalog search issues. Viewing the catalog screen. 14:11:32 #info CDS Search requires exact string match. 14:14:17 #info problem: today the front end is flitering the data. From data base we only get 10 records. If you go for all records then you cache everything and then present it. 14:17:53 #info niche search or site search? 14:18:38 #info Manoop - Site search addresses common problem. Does the site search support only catalog searches such as search for 5G 14:19:30 #info to search within the catalog would be a nice feature but in the screen they have shown is the first 5. This doesn't expose the contents of the catalog. 14:20:26 #info Tausif - the search criteria should be applicable for all the columns. 14:20:56 #info Manoop - we are trying to apply this logic throughout the tables. Should we add a custom search field consistently? 14:21:10 #info Tausif - yes this is what we want to achieve. 14:21:28 #info Assuming everyone agrees that this is valuable and needed then what is your proposal? 14:21:42 #info Tausif - modify CDS to do that. 14:23:52 #info Tausif ask the user to put a % after 14:24:18 #info Sayee - CDS calls are causing latency. This should not be database dependencies. 14:25:00 #info Tausif either you get all the data on the front end to slow things down. 14:25:45 #info Sayee- It should be more dynamic. 14:26:20 #info Tausif - Yes either you make multiple calls to CDS or you make a call to the front end. If the community agrees to get all the data at the front end then it is fine. 14:26:55 #info Manoop - Rather than imposing new requirements to CDS per table. Getting the data onto UI and making optimal call to CDS and filtering on the UI would be a better approach. 14:27:47 #info Chris - You have a lot of features in responsive manner. There is a great risk of blowing up the users browser. The user you give 10 rows of data and not 1000s. 14:28:22 #info Manoop - We don't need to add changes to CDS but portal side will handle it. 14:28:49 #info Tausif - There will be a lot of work that is time consuming for the front end developers. 14:30:20 #info Manoop - We have to start adapting chacheing mechanism and using the elastic features unless there are millions of records. 14:30:34 #info We should go on the UI side of filtering. 14:35:37 #info Parag - It depends on the UI filtering when there are getting subset of 1000 records then it will require server side filtering. 14:36:23 #info Change in revision version attribute as set by Onboarding is breaking SV 14:36:30 #topic Change in revision version attribute as set by Onboarding is breaking SV 14:38:19 #info Bryan - Incrementing integer that changes the logic. 14:38:42 #info Phillippe I tested with Muktar today and the test was successful. 14:39:08 #info Bryan - there was nothing I did to change that. 14:39:21 #topic Acumos-3531 14:50:16 #info We are publishing one model in two catalogs and the version changes in the second catalog. 14:50:32 #action Ken work with Nancy from the test team. 14:50:53 #topic Clio release blockers and issues. 14:51:24 #info November 6 will be the ONAP demo 14:52:04 #info Documentation for Acumos C client. We are OK with the user guide. The developer guide is not finished. I didn't anticipate the developer would be out this week. 14:52:32 #info the developer guide will be late. 14:56:14 #info Murali covered all open issues and user stories with the PTLs. 15:02:10 #endmeeting