not always engines are at subsequent/serial hostname

[marco69v]

due to the envirnment where it was build, orchestrator works well if the engines are on hosts (without the network suffix, this is another issue) that are of kind:

engine001
engine002
engine003 and so on. if the name are different with no serial is the most problem. if are in sequence but are not starting from 1 it can be managed into the scheduler.bash but must be reviewed to be more elastic