yahoo-eng-team team mailing list archive

[Miguel Angel Ajo <majopela@xxxxxxxxxx>]

Public bug reported:

Use case
=======
Monitoring of the "segmentation resources".

Logging the status of such resources as we go, (or the pass over a certain threshold) would allow monitoring solutions to identify tripping over
certain levels, and warn the administrator to take action: cleaning up
unused tenant networks, changing configuration, changing segmentation
technologies. etc.

Description
=========
Depending on configuration, and underlaying technologies, the segmentation
ids can be exhausted (vlan/vni/tunnel keys, etc..), making it a consumable
resource.

External monitoring solutions have no easy way to determine the amount of
"segmentation resources" available on the underlaying resource technology.

Alternatives
==========
One alternative could be providing a generic API to retrieve the usage of
resources. That would require the monitoring solution to make API calls
and therefore use credentials, making it harder to leverage standard
deployments and monitoring tools. This could also be considered as a second
step of this RFE.

** Affects: neutron
     Importance: Undecided
         Status: New


** Tags: rfe

** Description changed:

  Use case
  =======
  Monitoring of the "segmentation resources".
  
- Logging the status of such resources as we go, (or the pass over a certain threshold)
- would allow monitoring solutions to identify tripping over certain levels,
- and warn the administrator to take action: cleaning up unused tenant networks,
- changing configuration, changing segmentation technologies. etc.
- 
+ Logging the status of such resources as we go, (or the pass over a certain threshold) would allow monitoring solutions to identify tripping over
+ certain levels, and warn the administrator to take action: cleaning up
+ unused tenant networks, changing configuration, changing segmentation
+ technologies. etc.
  
  Description
  =========
- Depending on configuration, and underlaying technologies, the segmentation ids
- can be exhausted (vlan/vni/tunnel keys, etc..), making it a consumable resource.
+ Depending on configuration, and underlaying technologies, the segmentation
+ ids can be exhausted (vlan/vni/tunnel keys, etc..), making it a consumable
+ resource.
  
- External monitoring solutions have no easy way to determine the amount of 
+ External monitoring solutions have no easy way to determine the amount of
  "segmentation resources" available on the underlaying resource technology.
- 
  
  Alternatives
  ==========
- One alternative could be providing a generic API to retrieve the usage of 
+ One alternative could be providing a generic API to retrieve the usage of
  resources. That would require the monitoring solution to make API calls
  and therefore use credentials, making it harder to leverage standard
  deployments and monitoring tools. This could also be considered as a second
  step of this RFE.

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1559978

Title:
  [RFE] log segmentation_id over threshold for monitoring

Status in neutron:
  New

Bug description:
  Use case
  =======
  Monitoring of the "segmentation resources".

  Logging the status of such resources as we go, (or the pass over a certain threshold) would allow monitoring solutions to identify tripping over
  certain levels, and warn the administrator to take action: cleaning up
  unused tenant networks, changing configuration, changing segmentation
  technologies. etc.

  Description
  =========
  Depending on configuration, and underlaying technologies, the segmentation
  ids can be exhausted (vlan/vni/tunnel keys, etc..), making it a consumable
  resource.

  External monitoring solutions have no easy way to determine the amount of
  "segmentation resources" available on the underlaying resource technology.

  Alternatives
  ==========
  One alternative could be providing a generic API to retrieve the usage of
  resources. That would require the monitoring solution to make API calls
  and therefore use credentials, making it harder to leverage standard
  deployments and monitoring tools. This could also be considered as a second
  step of this RFE.

To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1559978/+subscriptions