Public bug reported:
Summary:
Neutron LbaaS lags port based monitoring.
Description:
The current HealthMonitory attached to pool that monitors the member port by
default. But some use case may run their service monitoring in a different port
rather than the service port, these type of ECV is incapable in the current
HealthMonitoring Object.
Expected:
We have to have a new field called 'destination': 'ip:port', since most of the
external LBs support this feature and organizations uses it. since pool can
have multiple HealthMonitors attached to it.
'destination': {'allow_post': True, 'allow_put': True,
'validate': {'type:string': None},
'default': '*:*',
'is_visible': True},
Version: Kilo/Liberty
** Affects: neutron
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1541579
Title:
Port based HealthMonitor in neutron_lbaas
Status in neutron:
New
Bug description:
Summary:
Neutron LbaaS lags port based monitoring.
Description:
The current HealthMonitory attached to pool that monitors the member port by
default. But some use case may run their service monitoring in a different port
rather than the service port, these type of ECV is incapable in the current
HealthMonitoring Object.
Expected:
We have to have a new field called 'destination': 'ip:port', since most of
the external LBs support this feature and organizations uses it. since pool can
have multiple HealthMonitors attached to it.
'destination': {'allow_post': True, 'allow_put': True,
'validate': {'type:string': None},
'default': '*:*',
'is_visible': True},
Version: Kilo/Liberty
To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1541579/+subscriptions
--
Mailing list: https://launchpad.net/~yahoo-eng-team
Post to : [email protected]
Unsubscribe : https://launchpad.net/~yahoo-eng-team
More help : https://help.launchpad.net/ListHelp
