Ceilometer currently has no support for metering VPN as a Service. Cloud providers/Operators have the need to monitor and meter various aspects of the Network Services. This spec deals with metering VPN as a service(VPNaaS).
The measurements needed for metering VPNaas are categorized into two, provider and service level. Following are the measurements targeted to be included in Ceilometer:
Provider level metrics:
- Type of VPN (Openswan, Cisco etc..) - depends on flavor framework in neutron(See Dependencies)
Service level metrics:
- VPN service Status
- Number of Connections
- Bandwidth - Needs changes to neutron VPNaaS(See Dependencies)
g = gauge, c = cumulative, p = pollster
The resources associated with these metrics are captured as part of resource discovery. Neutron exposes apis to capture this data which are invoke via pollsters from the ceilometer side. The notifications on neutron services side are a bit slim. As we add these notification messages to the neutron side, we will enhance the ceilometer side to capture these events through notification handlers.
For reference implemenation on neutron side, there will be an api call to retrieve stats such as connections and bandwidth.
New sources need to be included in pipeline.yaml for each group of pollsters that share a discovery extension. An example below:
sources: - name: fw_source interval: 600 meters: - "network.services.vpn" discovery: - "vpn" sinks: - network_services_sink
Similarly, we will have sources for connections and bandwidth.
The end user should be able to interact via the existing API and CLI.
This change should not have any major impact on performance/Scalability.
This feature should have minimal impact on developers for ongoing maintenance
New measurements around VPNaaS and other network services will be part of the network pollsters and notifications. So ongoing maintenance will be handled by the Ceilometer team, myself included.
Unit and integration Tests will be added to cover the necessary neutron_client calls, pollsters and notifications.
The Measurement docs need to be updated to reflect the new meters captured from VPNaaS API and notifications.