A few suggestions

Viewing 2 posts - 1 through 2 (of 2 total)
  • 11th November 2015 at 5:50 pm #14555

    Hello,

    I’ve recently purchased Muster 8, and it’s a fantastic piece of software. I do, however, have some suggestions for features that would be very useful.

    Suggestion 1: Pool based configuration.
    Some of the functionality of this idea is already in place, with Jobs/Hosts level priority and Time rules. I would also like to be able to specify Windows Drive mappings and substitution paths on pools. When a job invokes a pool, the pool would then add the pool-specific drive mappings and substitutions to the instances that it invokes. This would allow me to only need to configure the global drive mappings and substitutions directly on the instances, and project-specific drive mappings and substitutions on the pools. This would also prevent the instances from loading extra Windows drive mappings when they are not needed.

    Suggestion 2: Dispatcher remote control.
    I love the ability to invoke mstsc.exe and putty.exe for the hosts in the instances view. There are also times when I have the need to start a putty session for the dispatcher host. I would greatly appreciate a way to invoke this from the Muster Console.

    Suggestion 3: A Python option for Pre-Job, Post-Job, Pre-Chunk, and Post-Chunk actions.
    Currently, I have global actions set to directly invoke the Python interpreter on my dispatcher host machine in order to run a custom script. Using this method, I am able to access the environment variables that are set by the dispatcher. I would like to be able to create a Python script that would run inside the dispatcher’s context so I could have access to more information than the environment variables.

    Suggestion 4: Plugins list.
    I really appreciate the way that Muster handles different sets of software on different hosts. One feature that would be fantastic is to be able to specify a list of plugins for a piece of software for each host. Say, for instance, we have Nuke installed on all of our hosts, but a specific plugin only on four hosts. It would be fantastic to be able to specify on the Submission panel a list of required plugins to complete the job, and have that job be rendered only by hosts that have those plugins registered. I know I could create a pool consisting of hosts that have a specific plugin, and submit jobs to that pool, but it becomes tedious when we have a large variety of plugins for a range of software installed randomly across a large amount of hosts. Maybe a better way to go about this is to have the ability to register custom capabilities on a per-host basis, and the ability for a job to require host capabilities in order to run.

    I’m still fairly new to Muster, so if there are already ways of doing any of these things, please let me know.
    Thanks!
    -Colin Gimenez

    19th February 2018 at 1:33 pm #16653

    We just completed Muster 9 and taking into serious consideration what’s listed here for a future features release.
    Thanks!

Viewing 2 posts - 1 through 2 (of 2 total)

You must be logged in to reply to this topic.