portscan driver for VNF application Monitoring

Registered by hyunsik Yang

This driver is Port monitoring driver for checking application Status.

Until now, Tacker monitoring drivers can check network(ping) and application(using HTTP URL).

Moreover, When VNF is rebooted by Ping monitoring result, tacker re-make same whole VNF.

Therefore, I think port monitoring driver is needed for auto healing of VNFC level and it is a useful when we check the VNF inside status too.

Actually, VNF is logical entity and it consists of several VNFCs. So, When failover occurs in a VNFC level, we don't need make a new VNF. we just re-make a single VNFC.

For that, we need a port monitoring to check running single VNFC function well or not.

One of the use-case is EPC(Evolved Packet Core). It consists of several function such as S-GW, P-GW and MME.

https://review.openstack.org/#/c/329409/ --> implementation
https://review.openstack.org/#/c/389993/ --> specification

Blueprint information

Status:
Started
Approver:
Sridhar Ramaswamy
Priority:
Undefined
Drafter:
hyunsik Yang
Direction:
Needs approval
Assignee:
hyunsik Yang
Definition:
New
Series goal:
Accepted for pike
Implementation:
Needs Code Review
Milestone target:
None
Started by
hyunsik Yang

Related branches

Sprints

Whiteboard

Gerrit topic: https://review.openstack.org/#q,topic:(detached,n,z

Addressed by: https://review.openstack.org/329409
    portscan driver for VNF application Monitoring

Gerrit topic: https://review.openstack.org/#q,topic:portscan-monitoring,n,z

Gerrit topic: https://review.openstack.org/#q,topic:bp/portscan-monitoring,n,z

Gerrit topic: https://review.openstack.org/#q,topic:bp/Implements,n,z

Addressed by: https://review.openstack.org/389993
    Specification for portscan driver for VNF application Monitoring blueprint Implements: blueprint portscan-monitoring

Moving to Pike - sridhar_ram, Feb 3, 2017

(?)

Work Items

This blueprint contains Public information 
Everyone can see this information.