+ mailing list as I think the technical info in this thread is beneficial to the community audience as well.

 

From: Liu, Tao [mailto:Tao.Liu@windriver.com]
Sent: Monday, April 22, 2019 11:56 PM
To: An, Ran1 <ran1.an@intel.com>; Xie, Cindy <cindy.xie@intel.com>; Arevalo, Mario Alfredo C <mario.alfredo.c.arevalo@intel.com>; Sun, Austin <austin.sun@intel.com>; Arce Moreno, Abraham <abraham.arce.moreno@intel.com>; Lara, Cesar <cesar.lara@intel.com>; Botello Ortega, Luis <luis.botello.ortega@intel.com>; Miller, Frank <Frank.Miller@windriver.com>
Subject: RE: FM containerization collaboration

 

Hi Ran,

 

See comments inline:

 

Tao

 

From: An, Ran1 [mailto:ran1.an@intel.com]
Sent: Friday, April 19, 2019 12:25 PM
To: Liu, Tao; Xie, Cindy; Arevalo, Mario Alfredo C; Sun, Austin; Arce Moreno, Abraham; Lara, Cesar; Botello Ortega, Luis; Miller, Frank
Subject: RE: FM containerization collaboration

 

Hi Tao

   Thanks for your comments.

a)      Just a verify: Is it right that VIM alarm interfaces use fm_api to raise/clear alarms and fm_rest_api to audit alarms currently? So it is required to change VIM alarm interfaces using POST/PUT/DELETE fm_rest_api?

TL> Currently, the VIM alarm handlers use fm_api to raise/clear/audit alarms, and nfv orchestration uses fm_rest_api.   Yes, the alarm handlers will  interface with  the containerized  fm_rest_api (via fmclient)  to raise/clear/audit the instance alarms, and generate instances event logs. 

 

b)      There is no task to trace “modify glance/neutron alarm interfaces to the containerized FM restful api”. Are they not required in story 2004008? Or they are included in current task?

TL> I don’t think there is a requirement for glance/neutron to raise alarms.

 

Thanks

Ran

 

From: Liu, Tao [mailto:Tao.Liu@windriver.com]
Sent: Wednesday, April 17, 2019 10:42 PM
To: Xie, Cindy <cindy.xie@intel.com>; An, Ran1 <ran1.an@intel.com>; Arevalo, Mario Alfredo C <mario.alfredo.c.arevalo@intel.com>; Sun, Austin <austin.sun@intel.com>; Arce Moreno, Abraham <abraham.arce.moreno@intel.com>; Lara, Cesar <cesar.lara@intel.com>; Botello Ortega, Luis <luis.botello.ortega@intel.com>; Miller, Frank <Frank.Miller@windriver.com>
Subject: RE: FM containerization collaboration

 

Hi Ran,

 

I added inline comments below.

 

 

Tao

From: Xie, Cindy [mailto:cindy.xie@intel.com]
Sent: Tuesday, April 16, 2019 8:53 PM
To: An, Ran1; Arevalo, Mario Alfredo C; Sun, Austin; Arce Moreno, Abraham; Lara, Cesar; Botello Ortega, Luis; Miller, Frank; Liu, Tao
Subject: RE: FM containerization collaboration

 

+ Liu Tao from WR into the loop for the tech discussions.

 

From: An, Ran1
Sent: Wednesday, April 17, 2019 8:13 AM
To: Arevalo, Mario Alfredo C <mario.alfredo.c.arevalo@intel.com>; Xie, Cindy <cindy.xie@intel.com>; Sun, Austin <austin.sun@intel.com>; Arce Moreno, Abraham <abraham.arce.moreno@intel.com>; Lara, Cesar <cesar.lara@intel.com>; Botello Ortega, Luis <luis.botello.ortega@intel.com>; Frank.Miller@windriver.com
Subject: RE: FM containerization collaboration

 

Hi Mario:

    I investigated SB 2004008 and have following questions:

    1) clarify what the final goal for containerized fm service:

a)      Is the goal to apply a containerized fm service with POST/PUT/GET/DELETE restful apis exported, which can serve glance, neutron and horizon and stx-nfvi to set/clear/query alarms? Is my understanding right?

TL>  The goal is to add the FM panel into the containerized horizon instance along with alarm banner. The VIM alarm interfaces will be modified to use  the containerized  FM REST API to raise/clear/audit the openstack alarms/events. 

b)      If a) is right, what's the rest apis required? Should we map all fm_api to fm_rest_api?

TL> No, VIM alarm interfaces will use the POST/PUT/GET/DELETE restful apis to raise/clear/audit alarms.

c)      could you let me know more about the new database plan?

TL> The backend database will be configured to use mysql via helm charts.

d)      what does " Task 0000 Add calls from python-fmclient to fm-manager " mean in your doc?

TL> I don’t think this task is required. I will leave it to Mario to clarify.

 

    2) could you share the current status of tests about helm charts and armada manifest? 

         a) Could we apply a containerized fm service by "system application-apply" now?

         b) Could we launch a fm service by helm charts with tiller? 

         Is anything I can help here?

TL> Questions for Mario.

 

Thanks

Ran

 

From: Arevalo, Mario Alfredo C
Sent: Tuesday, April 16, 2019 2:15 AM
To: Xie, Cindy <cindy.xie@intel.com>; An, Ran1 <ran1.an@intel.com>; Sun, Austin <austin.sun@intel.com>; Arce Moreno, Abraham <abraham.arce.moreno@intel.com>; Lara, Cesar <cesar.lara@intel.com>; Botello Ortega, Luis <luis.botello.ortega@intel.com>; Frank.Miller@windriver.com
Subject: RE: FM containerization collaboration

 

Hi Cindy,

Good day, unfortunately, It is not possible for me to attend the meeting,
however I wonder it is possible to move it to Wednesday.

Best regards.
Mario.


From: Xie, Cindy
Sent: Sunday, April 14, 2019 4:26 PM
To: An, Ran1; Sun, Austin; Arevalo, Mario Alfredo C; Arce Moreno, Abraham; Lara, Cesar; Botello Ortega, Luis; Frank.Miller@windriver.com
Subject: FM containerization collaboration
When: Tuesday, April 16, 2019 6:00 AM-7:00 AM.
Where: Skype Meeting

Cesar/Mario,

Ran wants to see if it’s helpful to join SB#2004008 to accelerate the remaining several tasks. Want to sync-up w/ you to avoid the overlap. Please let me know if the slot works OK.

 

Thx. - cindy

 

 

.........................................................................................................................................

à Join Skype Meeting    

Trouble Joining? Try Skype Web App

Join by phone

+1(916)356-2663 (or your local bridge access #) Choose bridge 5. (Global)                English (United States)

Find a local number

 

Conference ID: 6636013518

Forgot your dial-in PIN? |Help    

 

[!OC([1033])!]

.........................................................................................................................................

 

Skype users: Recordings are subject to the Audio/Video Recording Policy.