Tickets and Pool Default Behaviour
Posted: Thu Jun 08, 2023 1:14 pm
(Related other thread: viewtopic.php?t=3513)
I'm having trouble working out exactly how the ticketing & services works with hosts & pools.
Afanasy's behaviour seems to be to allow everything. For example, if I have a job that consumes one ticket and my farm has no tickets or services defined at all, then every host will be used. Here's an actual example of that in action:
As you can see, even though no tickets or services are defined, Afanasy assumes that all hosts can be used (which is the tickets are in an italic font?), which is not what I thought would happen.
Another example is where I place a single REDSHIFT ticket on a host:
And as you can see, it just renders Redshift and consumed REDSHIFT tickets on every host, even though only one has a REDHISFT ticket.
So, if I'm trying to restrict the Redshift rendering to that single host, how do I do that? Is there any way to tell Afanasy that it can only use hosts that have tickets/services explicitly defined?
I'm having trouble working out exactly how the ticketing & services works with hosts & pools.
Afanasy's behaviour seems to be to allow everything. For example, if I have a job that consumes one ticket and my farm has no tickets or services defined at all, then every host will be used. Here's an actual example of that in action:
As you can see, even though no tickets or services are defined, Afanasy assumes that all hosts can be used (which is the tickets are in an italic font?), which is not what I thought would happen.
Another example is where I place a single REDSHIFT ticket on a host:
And as you can see, it just renders Redshift and consumed REDSHIFT tickets on every host, even though only one has a REDHISFT ticket.
So, if I'm trying to restrict the Redshift rendering to that single host, how do I do that? Is there any way to tell Afanasy that it can only use hosts that have tickets/services explicitly defined?