Monitor set_template_destination

Once the monitor template is created and associated with node addresses and pool members, monitor instances will have been created. Changing the template destination IP and port when there are active instances using the old IP:port would not be a good thing to do, so the GUI went ahead to make the destination IP:port read-only once the template has been created.

 

 

In iControl, the set_template_destination is meant to allow the users to change the destination IP:Port for any monitor template, but this should only be done while the created template has not been associated to anything yet, so that there are no previous instances using the old destination IPs/ports. BTW, I just found that the internal validation code is a little overzealous, so it doesn't even allow set_template_destination to work, thus essentially it has the same read-only effect as the GUI. :-)

 

 

I'll create a CR to make set_template_destination work in the next release, but as I said, it's meant to allow changing the template destination before any association is made.

 

 

Hope this answers your question.

 

Thanks,

 

Loc