discovery server not honor TTL min/max per service config

Bug #1469836 reported by Deepinder Setia
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Juniper Openstack
In Progress
Low
Deepinder Setia
Trunk
Won't Fix
Low
Deepinder Setia
OpenContrail
Won't Fix
Low
Deepinder Setia

Bug Description

Discovery server picks up TTL min and max values from configuration file. It also allows service specific configuration items within service sections. So the following configuration should use TTTL values 120-240 for service foobar and 300-1800 for all other services. However discovery uses 300-1800 for discovery also

[DEFAULTS]
# minimim time to allow client to cache service information (seconds)
ttl_min=300

# maximum time to allow client to cache service information (seconds)
ttl_max=1800

######################################################################
# Other service specific knobs ...

# use short TTL for agressive rescheduling if all services are not up
# ttl_short=1

# specify policy to use when assigning services
# policy = [load-balance | round-robin | fixed]
######################################################################

[foobar]
ttl_min=120
ttl_max=240

Tags: discovery
Deepinder Setia (dsetia)
Changed in opencontrail:
importance: Undecided → Low
assignee: nobody → Deepinder Setia (dsetia)
Revision history for this message
OpenContrail Admin (ci-admin-f) wrote : [Review update] master

Review in progress for https://review.opencontrail.org/12053
Submitter: Deepinder Setia (<email address hidden>)

Deepinder Setia (dsetia)
Changed in opencontrail:
status: New → Won't Fix
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.