[Starlingx-discuss] Fault Management Containerization (SB 2004008) Follow Up

[Arevalo, Mario Alfredo C]

Hi Cindy,

The first version of the patches will take around 2 weeks, after that, a validation
step will start. In this step I am going to update the patches according to the feedback
received from the community and  Luis Botello will help to validate the functionality of the patches.
As final step, I would like to execute the sanity when all patches are reviewed by the community
an they are ready to be merged. This final step could vary around 2-3 weeks, it will depend on the
response time from the community and the complexity of the required updates, in addition to the
validation tasks.

Best regards.
Mario.
________________________________________
From: Xie, Cindy
Sent: Monday, March 25, 2019 5:44 PM
To: Arevalo, Mario Alfredo C; Arce Moreno, Abraham; starlingx-discuss at lists.starlingx.io
Cc: Tao Liu; Frank.Miller at windriver.com
Subject: RE: [Starlingx-discuss] Fault Management Containerization (SB  2004008) Follow Up

Mario,
Nice to know that you're getting all information and having better understanding for the tasks.

We probably needs to get a little bit more detail granularity of your plan, for each task in the storyboard:

- when the patches will be uploaded for review;
- what tests you're planning to do? Any support required from Ada's team? and when...
- when you expect the patch review comments can be addressed and patch merged to master.

Thanks. - cindy

-----Original Message-----
From: Arevalo, Mario Alfredo C [mailto:mario.alfredo.c.arevalo at intel.com]
Sent: Tuesday, March 26, 2019 8:38 AM
To: Arce Moreno, Abraham <abraham.arce.moreno at intel.com>; starlingx-discuss at lists.starlingx.io
Cc: Tao Liu <tao.liu at windriver.com>; Frank.Miller at windriver.com
Subject: Re: [Starlingx-discuss] Fault Management Containerization (SB 2004008) Follow Up

Hi team,

Thank you for your feedback from our last meeting, and this is my update. I am checking all points described in this thread. Actually I have got progress in the topic related to snmp and the relation with oamcontroller, sysinv and cgts-client.

I plan to send a PR with information about findings/architecture to the stx-fault/doc in a future.

I think, it is not necessary another meeting as it was mentioned, I think I have enough information to continue and I am going to update the current reviews and send news according to the points discussed until today, and contact Tao for specific questions.

Thanks Tao, Abraham and Frank.

Best regards.
Mario.
________________________________________
From: Arce Moreno, Abraham
Sent: Friday, March 22, 2019 10:37 AM
To: starlingx-discuss at lists.starlingx.io
Cc: Arevalo, Mario Alfredo C; Tao Liu
Subject: Fault Management Containerization (SB 2004008) Follow Up

Thanks Frank for setting this up. Thanks everyone for your attendance to this meeting, here you have high level notes and ToDos based in the topics covered.

In Summary

- The presentation Stx-Fault/Containers is located at [0].
- Tao will kindly update the Fault Management architecture diagram, slide 8.
- Mario will send an email no later than Monday afternoon with the latest findings / questions based in his 5 ToDos.
- We will meet again on Tuesday to finalize on tasks and implementation details.

If we are forgetting about any key point in this email, please do not hesitate to reply.

StarlingX Architecture

- 2 instances for each of the following projects:
  - Keystone
  - Horizon
  - Barbican
- Fault Management will have 2 instances as well.

Fault Management Architecture

- [ToDo] [Tao] to modify the Fault Management architecture (Slide 8) Thanks Tao!
- fm-api runs in compute node, snmp provide interfaces
  - [ToDo] [Mario] to check these statements

Fault Management REST API

- [ToDo] [Mario] to write the next level of details for REST API mapping / implementation, consider to include PUT to Event Log.

Fault Management Architecture

- python-fmclient is a wrapper to fm_cli / fm_api
  - [ToDo] [Mario] to understand more about fm_cli as a wrapper and how does it interact and affects fault management containerized strategy.

FM Proposal

- Remove mysql, fm-api, fm-common
  - [ToDo] [Mario] to understand about the removal of fm-api and fm-common from the containerized instance.
- Dependency to cgts-client
  - [ToDo] [Mario] to understand what is cgtc-client and how does it interacts with fault management and the new containerized instance.

OpenStack Applications

The following 2 projects will make use of the Fault Management containerized:
- starlingx-dashboard
- stx-nfv

[0] https://docs.google.com/presentation/d/1_vG83aHTToXlIdJxaJpVL-MHWfRGnxLuyEdFDt-nfwo/edit?usp=sharing

_______________________________________________
Starlingx-discuss mailing list
Starlingx-discuss at lists.starlingx.io
http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss