#147 Hot Reload of configuration parameters
We have been using Open Diameter in a prototype for
quite a while now. Before we start and re-invent the
wheel, I was wondering if there is any support so far
for dynamic configuration reloading (HUP). I'm trying
to estimate if OD was designed with that in mind, (and
thus this options would require minor changes), or if
this would require mammoth changes. If it is supported,
to what extend is it usable ?
If it is not supported, I'd like to address the
Open Diameter group in order to lay down what would be
required to give Open Diameter HUP capabilities, so
that we may agreed on what should be done.
Here are some ideas on what I would see as initial
requirements:
- When HUP signal is issued, new configuration is
reloaded, but old configuration is kept alive for
already existing connection until they complete (i.e, a
peer waiting for a CEA would switch from old
configuration to new config when CEA is received and
processed).
- Reliability: Upon HUP failure, (i.e,
re-configuration fails due to bad config), Open
Diameter transparently rolls back to old config without
any service interruption. Upon HUP success,
configuration is switched without service interruption.
- What to do in stateful transaction ? Is there any
state changes that would be required. (I have always
used stateless sessions so far, so I would not know.
Can anyone comment on this ?)
I usually search thoroughly the OD mailing-list, docs
and code before I blindly post a message here, but I
was curious to have inputs before I get too far.
