gt; I believe you can collect enough information for neutron ovs
> implementation.
>
> 2016-04-25 13:20 GMT-05:00 Rubab Syed <rubab.sye...@gmail.com>:
> > Hi folks,
> >
> > I'm writing a plugin for Monasca to monitor traffic at layer 3. My
> Neutron
> > backend
Hi folks,
I'm writing a plugin for Monasca to monitor traffic at layer 3. My Neutron
backend is OVS and I'm using iptables of network namespaces for getting
traffic counters. Would the following rules in router namespace cover all
the traffic at layer 3 per router per tenant?
- Chain
Hi Umar,
As far as I know, you should follow these steps to make this work:
1- Run stack.sh
2- Add rules to policy.json in /etc/ceilometer
3- Restart ceilometer service. Follow this link [1] to see how can you
restart a particular service.
[1]
On 1 Mar 2016 21:25, "Rubab Syed" <rubab.sye...@gmail.com> wrote:
> Hi all,
>
> I'm planning to write a plugin for Monasca that would enable router's
> traffic monitoring per subnet per tenant. For that purpose, I'm using
> Neutron l3 metering extension [1] that all
Hi all,
I'm planning to write a plugin for Monasca that would enable router's
traffic monitoring per subnet per tenant. For that purpose, I'm using
Neutron l3 metering extension [1] that allows you to filter traffic based
on CIDRs.
My concerns:
- Now given the fact that this extension can be
Hi,
I'm doing a university project in OpenStack. The aim is to monitor virtual
routers per tenant with Monasca(which according to my knowledge hasn't been
implemented yet). The initial features would include monitoring of in/out
traffic per interface. I'm writing a plugin in Monasca for that
Hi,
I'm doing a university project in OpenStack. The aim is to monitor virtual
routers per tenant with Monasca(which according to my knowledge hasn't been
implemented yet). The initial features would include monitoring of in/out
traffic per interface. I'm writing a plugin in Monasca for that
