#acumos-meeting: Architecture Committee

Meeting summary

1. New agenda items (farheen, 14:06:31)
   1. Rajesh: add the SSL certificates as a topic. (farheen, 14:07:01)
   
   
2. Plan for architecture calls forward. (farheen, 14:07:32)
   1. Manoop: I have been leading the architecture design, review for the last four releases. It is time to open this role to another community member to take over. If you have an interest in reviewing the architecture PTL. It is not a huge burden rather a great opportunity LFAI goals aligned with Acumos which have visibility across Ai projects. (farheen, 14:10:55)
   2. Manoop proposed reducing the number of architecture calls since we are not doing active architecture design. Because we are at the end of the release cycle I propose we move this call merged with the PTL call. (farheen, 14:12:44)
   3. Reuben: We had a similar discussion on the community committee yesterday. We were talking about reducing TSC calls so we don't really discuss so much about plans but only raise cross team issues. If we did that then this meeting might be the one where we discuss things and bring them to the TSC. We can play it by ear and schedule meetings (farheen, 14:14:09)
   4. Manoop: I have seen other open source projects where they have many resources to run the calls. I have seen other open source projects with less resources who call out the meetings when needed. We can not force people to things. I totally agree if we are covering these discussions in the PTL calls then we can have those discussions on the (farheen, 14:15:59)
   5. Nat: I remember having the conversation about an ONAP TSC meeting where they had a call once a month where they discuss the votes and blockers and dependency issues. (farheen, 14:16:51)
   6. Manoop: Agree (farheen, 14:16:55)
   7. Manoop: TSC calls are twice weekly. By the time you bring your topics the votes are ready. The design decisions happen on the PTL calls. If there is a developer level meeting needed then it is done on an adhoc basis. (farheen, 14:18:09)
   8. Nat: Too many meetings is wearing out the people. It is repetitive. We proposed the frequency of the TSC call to every other week. Focus on other key meetings on the PTL meetings that can be discussed for specific intent. (farheen, 14:18:56)
   9. The PTL call we discuss granular and the architecture calls. We discussed about it otherwise more frequency will have raw resource constraints. (farheen, 14:19:47)
   10. Manoop: If we hear of anyone stepping up to lead the design discussions for the architecture calls that will be good. (farheen, 14:21:37)
   11. Nat: Everything will be open soon for fresh minds to take over. (farheen, 14:22:14)
   12. Manoop: I am not abandoning the call. I will be there to support whoever is taking over the role. (farheen, 14:22:47)
   
   
3. SSL encryption (farheen, 14:23:31)
   1. Rajesh: sharing his screen. (farheen, 14:23:44)
   2. https://docs.acumos.org/en/clio/submodules/federation/docs/config.html?highlight=troubleshooting (farheen, 14:26:20)
   3. There is no documentation of how this works on dev and IST. (farheen, 14:26:49)
   4. Manoop: there is an assumption that you bring your cert. (farheen, 14:27:07)
   5. Rajesh: No it's not related to the certificate. (farheen, 14:27:23)
   6. Manoop: I am not an expert in this area in Acumos. We only have one resource Andrew Gauld. Ask Andrew what your questions are. Explore All in One documentation. (farheen, 14:28:41)
   7. Manoop: That is the process that Ken and others have used. I would recommend you talk to Andrew and Ken because that is more vetted. But One Click Deploy scripts worked in Clio. (farheen, 14:29:23)
   8. Nat: Vineet can give you the details. This is under Demeter. (farheen, 14:29:55)
   9. https://gerrit.acumos.org/r/gitweb?p=system-integration.git;a=tree;f=AIO;h=3add23586e35d224b4828c448e6be44e9acb44af;hb=refs/heads/master (farheen, 14:30:36)
   10. the process may be similar but configuration will be a little different than what Ken is doing in IST. (farheen, 14:31:04)
   
   
4. Blockers and Defects in Demeter (farheen, 14:32:10)
   1. Murali 6 open and 14 in progress. Let me go through the components. These are from deployment. SOAJS issue I sent you an issue yesterday. Vaibhav is unable to access. (farheen, 14:32:56)
   2. Manoop: Yes, we id that K8 cluster where SOAJS is installed was restarted. Some of the pods in SOAJS are in a crashed loop stage. The back end modules are failing. It is not an access issue. Bobbie and Sanjay are looking into getting these pods running. It did not work yet. Sanjay reached out to Antoine and he gave some commands for (farheen, 14:34:24)
   3. Manoop: If you ask me the days we are left with along with the composition blueprints I have very low confidence that we can finish it in time for Demeter. We can target for the point release. (farheen, 14:35:15)
   4. Manoop: I recommend you take these issues to the testing team. (farheen, 14:38:07)
   5. Phillippe: on 4186 I thought it was portal's issue but it is onboarding so I will work on it. 4087 requires expertise in enginex. It will take time. (farheen, 14:43:36)
   6. Rajesh 4077 we are putting the license into nexus. (farheen, 14:44:09)
   7. Manoop: We are waiting for a build from the Licensing and deployment for SOAJS. I will try to get it by Friday. (farheen, 14:44:36)
   8. Phillippe: We will not have a build this week for onboarding. We will have a build to the java client. Keep track on daily basis and keep track of the testing testing team. (farheen, 14:45:25)
   9. It our courtesy to inform the test teams that they will be receiving a new build. (farheen, 14:46:06)

Action items

1. (none)

People present (lines said)

1. farheen (42)
2. collab-meetbot (3)