metadata

Hi Daniel,

 

 

For performance reasons you generally can't modify the configuration from an iRule (including the object metadata).

 

 

What are you trying to do?

 

 

Aaron

Hi Aaron:

 

 

I actually just want to be able to use an iRule to read previously set metadata and make decisions based on that metadata.

 

 

For example, I've found in certain cases that GTM topology based records don't provide enough 'granularity' in selecting the desired pool member of a chosen pool. I've written a faily generic iRule that provides the needed functionality, but my solution requires that I create

 

two pools for each wideip - each contain the same pool members, but the second pool has all pool members administratively disabled except for one pool member that I want to have the topology records to select. The iRule basically just detemines which pool to select depending on the region that LDNS originates from. It's of course not very desireable to have to create 'duplicate' pools, but I haven't found any other 'elegant' way to achieve the behavior I'm looking for. Metadata in this case would provide the needed information that the second pool is providing (the one enabled pool member).

 

 

I know this explanation doesn't convey that well what I'm trying to do (and I can explain it in more detail if you think there is another way of accomplishing the task), but I'm thinking that iRule read-accessible metadata would be highly useful in this case, and probably many other cases as well.

 

 

Daniel

Hi Colleagues,

 

I see that there are no comments last few years, but did you manage to find a way to read a member metadata from an iRule at all?

 

Thanks and regards Biser