Re: [openstack-dev] [ceilometer] :Regarding wild card configuration in pipeline.yaml

2016-01-29 Thread gordon chung 
  I have a meter subscription m1.* for publisher p1 and I need a subset of m1.* 
 notifications for ex:m1.xyz.* for publisher p2.
If we add p2 to already exisiting sink along with p1,  p2 will get other 
notification's along with m1.xyz.* which are not needed for p2.

To avoid this we had the following entry in pipeline;

sources:
  -name : m1meter
   meters: m1.*,!m1.xyz.*
   sinks:
-m1sink
   .
  -name : m2meter
   meters:m1.xyz.*
   sinks:
-m2sink
sinks:
 -name: m1sink
  publishers:
   -p1

  -name: m2sink
  publishers:
   -p1
   -p2


you will unfortunately need to explicitly list out your required meters 
explicitly (without) wildcard.



>From reply mail it seems there is no strict restriction to support this.Could 
>you please let me know how should we handle such cases in ceilometer.
If we do code modification in pipeline module of ceilometer does it effects any 
other parts of ceilometer frame work.

the code filtering happens here: 
https://github.com/openstack/ceilometer/blob/master/ceilometer/pipeline.py#L275-L287
 and similarly in previous releases.

it will not affect anything other than pipeline filtering so it should be safe 
to change. you are welcome to push your change to community. as i mentioned 
previously, i don't think there is a restriction on having either wildcard or 
negative wildcard support in one pipeline. it was just how it was implemented 
as we did not have a requirement to deal with both (and the added complexity of 
ordering that comes with it)



--
gord
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [ceilometer] :Regarding wild card configuration in pipeline.yaml

2016-01-27 Thread Raghunath D 
Hi Gord,

Could you please kindly suggest how to proceed further on the below issue as 
we are somewhat blocked in our development activity due to the wildcard issue.

With Best Regards
Raghunath Dudyala
Tata Consultancy Services Limited
Mailto: raghunat...@tcs.com
Website: http://www.tcs.com

Experience certainty. IT Services
Business Solutions
Consulting




-Raghunath D/HYD/TCS wrote: - 
To: openstack-dev@lists.openstack.org
From: Raghunath D/HYD/TCS
Date: 01/21/2016 01:06PM
Cc: "Srikanth Vavilapalli" <srikanth.vavilapa...@ericsson.com>
Subject: Re: [openstack-dev] [ceilometer] :Regarding wild card configuration in 
pipeline.yaml


Hi ,
 
 Just to reframe my query:
  I have a meter subscription m1.* for publisher p1 and I need a subset of m1.* 
 notifications for ex:m1.xyz.* for publisher p2.
If we add p2 to already exisiting sink along with p1,  p2 will get other 
notification's along with m1.xyz.* which are not needed for p2.
 
To avoid this we had the following entry in pipeline;

sources:
  -name : m1meter
   meters: m1.*,!m1.xyz.*
   sinks:
-m1sink   
   .
  -name : m2meter
   meters:m1.xyz.*
   sinks:
-m2sink
sinks:
 -name: m1sink
  publishers:
   -p1
   
  -name: m2sink
  publishers:
   -p1
   -p2
 
>From reply mail it seems there is no strict restriction to support this.Could 
>you please let me know how should we handle such cases in ceilometer.
If we do code modification in pipeline module of ceilometer does it effects any 
other parts of ceilometer frame work.
 
 
Thanks and Regards
Raghunath.
 
 
Copied reply mail content from 
http://osdir.com/ml/openstack-dev/2016-01/msg01346.html for reference, due to 
some reason I am not getting reply mail to my mailbox.
-Copied Mail Start 
here-
hi,

i don't completely recall why we don't allow wildcarded exclude and include 
meters. it's probably because there's ambiguity of ordering of wildcard which 
can lead to different filter results.

someone can correct me, but i don't think there's a strict requirement that 
stops us from supporting both at once, just that it's not there.

as it stands now. you'll need to explicitly list out the meters you want (or 
don't want) sent to each pipeline.

cheers,
gord.
-Mail End 
Here-

With Best Regards
Raghunath Dudyala
Tata Consultancy Services Limited
Mailto: raghunat...@tcs.com
Website: http://www.tcs.com

Experience certainty. IT Services
Business Solutions
Consulting




-Raghunath D/HYD/TCS wrote: - 
To: openstack-dev@lists.openstack.org
From: Raghunath D/HYD/TCS
Date: 01/20/2016 07:09PM
Cc: "Srikanth Vavilapalli" <srikanth.vavilapa...@ericsson.com>
Subject: [openstack-dev] [ceilometer] :Regarding wild card configuration in 
pipeline.yaml


Hi ,
 
We have one use-case for which we are using ceilometer for getting 
notifications.
 
We have meter's m1.*,m1.xyz.* and publishers(kafka/udp) as p1 and p2.
i.m1.* notifications/meter data should send to p1 and p2
ii.m1.xyz.* notifications/meter data should send to p1.

We can correlate m1.* as network.* and m1.xyz.* as network.incoming.*
The pipeline.yaml is updated as:
--
sources:
  -name : m1meter
   meters: m1.*,m1.xyz.*
   sinks:
-m1sink   

sinks:
 -name: m1sink
  publishers:
   -p1
   -p2


With the above configuration p1 also receives other than m1.xyz.* notifications
which are not subscribed by p1.To avoid this duplication's,pipeline.yaml is 
updates as:
-
sources:
  -name : m1meter
   meters: m1.*,!m1.xyz.*
   sinks:
-m1sink   
   .
  -name : m2meter
   meters:m1.xyz.*
   sinks:
-m2sink
sinks:
 -name: m1sink
  publishers:
   -p1
   -p2
 
 -name: m2sink
  publishers:
   -p1

  
This configuration is failing under source rule checking with reason "both 
included and
excluded meters specified.

Info/Help needed:
  Do we have any way in ceilometer frame work to achieve this or

Re: [openstack-dev] [ceilometer] :Regarding wild card configuration in pipeline.yaml

2016-01-20 Thread Raghunath D 
Hi ,

 Just to reframe my query:
  I have a meter subscription m1.* for publisher p1 and I need a subset of m1.* 
 notifications for ex:m1.xyz.* for publisher p2.
If we add p2 to already exisiting sink along with p1,  p2 will get other 
notification's along with m1.xyz.* which are not needed for p2.

To avoid this we had the following entry in pipeline;

sources:
  -name : m1meter
   meters: m1.*,!m1.xyz.*
   sinks:
-m1sink   
   .
  -name : m2meter
   meters:m1.xyz.*
   sinks:
-m2sink
sinks:
 -name: m1sink
  publishers:
   -p1
   
  -name: m2sink
  publishers:
   -p1
   -p2
 
>From reply mail it seems there is no strict restriction to support this.Could 
>you please let me know how should we handle such cases in ceilometer.
If we do code modification in pipeline module of ceilometer does it effects any 
other parts of ceilometer frame work.


Thanks and Regards
Raghunath.


Copied reply mail content from 
http://osdir.com/ml/openstack-dev/2016-01/msg01346.html for reference, due to 
some reason I am not getting reply mail to my mailbox.
-Copied Mail Start 
here-
hi,

i don't completely recall why we don't allow wildcarded exclude and include 
meters. it's probably because there's ambiguity of ordering of wildcard which 
can lead to different filter results.

someone can correct me, but i don't think there's a strict requirement that 
stops us from supporting both at once, just that it's not there.

as it stands now. you'll need to explicitly list out the meters you want (or 
don't want) sent to each pipeline.

cheers,
gord.
-Mail End 
Here-

With Best Regards
Raghunath Dudyala
Tata Consultancy Services Limited
Mailto: raghunat...@tcs.com
Website: http://www.tcs.com

Experience certainty. IT Services
Business Solutions
Consulting




-Raghunath D/HYD/TCS wrote: - 
To: openstack-dev@lists.openstack.org
From: Raghunath D/HYD/TCS
Date: 01/20/2016 07:09PM
Cc: "Srikanth Vavilapalli" <srikanth.vavilapa...@ericsson.com>
Subject: [openstack-dev] [ceilometer] :Regarding wild card configuration in 
pipeline.yaml


Hi ,
 
We have one use-case for which we are using ceilometer for getting 
notifications.
 
We have meter's m1.*,m1.xyz.* and publishers(kafka/udp) as p1 and p2.
i.m1.* notifications/meter data should send to p1 and p2
ii.m1.xyz.* notifications/meter data should send to p1.

We can correlate m1.* as network.* and m1.xyz.* as network.incoming.*
The pipeline.yaml is updated as:
--
sources:
  -name : m1meter
   meters: m1.*,m1.xyz.*
   sinks:
-m1sink   

sinks:
 -name: m1sink
  publishers:
   -p1
   -p2


With the above configuration p1 also receives other than m1.xyz.* notifications
which are not subscribed by p1.To avoid this duplication's,pipeline.yaml is 
updates as:
-
sources:
  -name : m1meter
   meters: m1.*,!m1.xyz.*
   sinks:
-m1sink   
   .
  -name : m2meter
   meters:m1.xyz.*
   sinks:
-m2sink
sinks:
 -name: m1sink
  publishers:
   -p1
   -p2
 
 -name: m2sink
  publishers:
   -p1

  
This configuration is failing under source rule checking with reason "both 
included and
excluded meters specified.

Info/Help needed:
  Do we have any way in ceilometer frame work to achieve this or could you 
provide 
us some suggestions how to achieve this in ceilometer.
 
With Best Regards
Raghunath Dudyala
Tata Consultancy Services Limited
Mailto: raghunat...@tcs.com
Website: http://www.tcs.com

Experience certainty. IT Services
Business Solutions
Consulting

=-=-=
Notice: The information contained in this e-mail
message and/or attachments to it may contain 
confidential or privileged information. If you are 
not the intended recipient, any dissemination, use, 
review, distribution, printing or copying of the 
information contained in this e-mail message 
and/or attachments to it are strictly prohibited. If 
you have received this comm

Re: [openstack-dev] [ceilometer] :Regarding wild card configuration in pipeline.yaml

2016-01-20 Thread gord chung 

hi,

i don't completely recall why we don't allow wildcarded exclude and 
include meters. it's probably because there's ambiguity of ordering of 
wildcard which can lead to different filter results.


someone can correct me, but i don't think there's a strict requirement 
that stops us from supporting both at once, just that it's not there.


as it stands now. you'll need to explicitly list out the meters you want 
(or don't want) sent to each pipeline.


cheers,


On 20/01/2016 8:39 AM, Raghunath D wrote:

Hi ,
We have one use-case for which we are using ceilometer for getting 
notifications.

We have meter's m1.*,m1.xyz.* and publishers(kafka/udp) as p1 and p2.
i.m1.* notifications/meter data should send to p1 and p2
ii.m1.xyz.* notifications/meter data should send to p1.

We can correlate m1.* as network.* and m1.xyz.* as network.incoming.*
The pipeline.yaml is updated as:
--
sources:
  -name : m1meter
   meters: m1.*,m1.xyz.*
   sinks:
-m1sink

sinks:
 -name: m1sink
  publishers:
   -p1
   -p2


With the above configuration p1 also receives other than m1.xyz.* 
notifications
which are not subscribed by p1.To avoid this 
duplication's,pipeline.yaml is updates as:

-
sources:
  -name : m1meter
   meters: m1.*,!m1.xyz.*
   sinks:
-m1sink
   .
  -name : m2meter
   meters:m1.xyz.*
   sinks:
-m2sink
sinks:
 -name: m1sink
  publishers:
   -p1
   -p2

 -name: m2sink
  publishers:
   -p1
 

This configuration is failing under source rule checking with reason 
"both included and

excluded meters specified.

*Info/Help needed:*
  Do we have any way in ceilometer frame work to achieve this or could 
you provide

us some suggestions how to achieve this in ceilometer.

With Best Regards
RaghunathDudyala
TataConsultancy Services Limited
Mailto: raghunat...@tcs.com
Website: http://www.tcs.com 

Experience certainty. IT Services
Business Solutions
Consulting


=-=-=
Notice: The information contained in this e-mail
message and/or attachments to it may contain
confidential or privileged information. If you are
not the intended recipient, any dissemination, use,
review, distribution, printing or copying of the
information contained in this e-mail message
and/or attachments to it are strictly prohibited. If
you have received this communication in error,
please notify us by reply e-mail or telephone and
immediately and permanently delete the message
and any attachments. Thank you



__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev


--
gord

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

[openstack-dev] [ceilometer] :Regarding wild card configuration in pipeline.yaml

2016-01-20 Thread Raghunath D 
Hi ,

We have one use-case for which we are using ceilometer for getting 
notifications.

We have meter's m1.*,m1.xyz.* and publishers(kafka/udp) as p1 and p2.
i.m1.* notifications/meter data should send to p1 and p2
ii.m1.xyz.* notifications/meter data should send to p1.

We can correlate m1.* as network.* and m1.xyz.* as network.incoming.*
The pipeline.yaml is updated as:
--
sources:
  -name : m1meter
   meters: m1.*,m1.xyz.*
   sinks:
-m1sink   

sinks:
 -name: m1sink
  publishers:
   -p1
   -p2


With the above configuration p1 also receives other than m1.xyz.* notifications
which are not subscribed by p1.To avoid this duplication's,pipeline.yaml is 
updates as:
-
sources:
  -name : m1meter
   meters: m1.*,!m1.xyz.*
   sinks:
-m1sink   
   .
  -name : m2meter
   meters:m1.xyz.*
   sinks:
-m2sink
sinks:
 -name: m1sink
  publishers:
   -p1
   -p2
 
 -name: m2sink
  publishers:
   -p1

  
This configuration is failing under source rule checking with reason "both 
included and
excluded meters specified.

Info/Help needed:
  Do we have any way in ceilometer frame work to achieve this or could you 
provide 
us some suggestions how to achieve this in ceilometer.
 
With Best Regards
Raghunath Dudyala
Tata Consultancy Services Limited
Mailto: raghunat...@tcs.com
Website: http://www.tcs.com

Experience certainty. IT Services
Business Solutions
Consulting

=-=-=
Notice: The information contained in this e-mail
message and/or attachments to it may contain 
confidential or privileged information. If you are 
not the intended recipient, any dissemination, use, 
review, distribution, printing or copying of the 
information contained in this e-mail message 
and/or attachments to it are strictly prohibited. If 
you have received this communication in error, 
please notify us by reply e-mail or telephone and 
immediately and permanently delete the message 
and any attachments. Thank you


__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev