Request for improvement of functionality with tags to allow balancing by region about scalelite HOT 8 OPEN

I'm thinking about support for passing a regex as meta_server-tag in a future iteration of the feature. Would that be sufficient for your purposes?

from scalelite.

I'm thinking about support for passing a regex as meta_server-tag in a future iteration of the feature. Would that be sufficient for your purposes?

If I understand you correctly, then yes. Well, that is, I’ll finally be able to convey this design
(region1|region2|region3)
or
region[123]
This is quite suitable for me and completes my tasks.

But there is still a question that is generally not so critical and may not be closed for me personally.
It would be cool to be able to assign 2 tags to 1 server. For example, one tag is regional, and the second, for example, means that the BBB can host a conference with a large number of people

Well, and accordingly, when balancing, if the server has a match for two tags at once, increased balancing coefficients would be given and the choice would fall on servers that match a larger number of tags

from scalelite.

I'm thinking about support for passing a regex as meta_server-tag in a future iteration of the feature. Would that be sufficient for your purposes?

Is this implemented in version 1.6.1?

from scalelite.

I'm thinking about support for passing a regex as meta_server-tag in a future iteration of the feature. Would that be sufficient for your purposes?

Is this implemented in version 1.6.1?

No. Since this improvement of the feature is not useful to our organization, it's nothing that I can contribute super short term. It would rather be a candidate for the next developer summit.
Note that I'm not associated with Blindside Networks, but just on open-source contributor. You might be able to find a way to accelerate the development by reaching out to Blindside Networks.

from scalelite.

I'm thinking about support for passing a regex as meta_server-tag in a future iteration of the feature. Would that be sufficient for your purposes?

Is this implemented in version 1.6.1?

No. Since this improvement of the feature is not useful to our organization, it's nothing that I can contribute super short term. It would rather be a candidate for the next developer summit. Note that I'm not associated with Blindside Networks, but just on open-source contributor. You might be able to find a way to accelerate the development by reaching out to Blindside Networks.

I meant whether the tag selection functionality is implemented through a regular expression

from scalelite.

I'm thinking about support for passing a regex as meta_server-tag in a future iteration of the feature. Would that be sufficient for your purposes?

Is this implemented in version 1.6.1?

No. Since this improvement of the feature is not useful to our organization, it's nothing that I can contribute super short term. It would rather be a candidate for the next developer summit. Note that I'm not associated with Blindside Networks, but just on open-source contributor. You might be able to find a way to accelerate the development by reaching out to Blindside Networks.

I meant whether the tag selection functionality is implemented through a regular expression

That's what I meant with "improvement of the feature". Only the basic functionality with single explicit tags is implemented.

from scalelite.

I'm thinking about support for passing a regex as meta_server-tag in a future iteration of the feature. Would that be sufficient for your purposes?

In other words, even a simple regex has been pushed into the back burner, not to mention even what I wrote in this request?

from scalelite.

I acknowledge that this might seem like requiring little work to get done, which is probably true, but still I have to justify putting working hours into this without any own benefit. Therefore this just has not the highest priority right now.

from scalelite.