Ability for bosh addons to exclude errand VMs

[oozie]

Per bosh runtime-config doc an include option exists. Word has it the latest bosh also supports exclude keyword. We'd like for the exclude keyword to allow for exclusion of errand VMs.

Problem: one of our bosh addons has a pretty expensive init step, i.e. it downloads a database locally. This is a pointless operation on an errand VM because the VM goes away. Additionally, that particular errand runs on a nano instance with only 512mb of RAM and causes the CF deployment to fail.

[cppforlife]

i think you could do that via exclude jobs configuration.

…

Sent from my iPhone

On Mar 9, 2017, at 1:44 PM, Slawek Ligus ***@***.***> wrote: Per bosh runtime-config doc an include option exists. Word has it the latest bosh also supports exclude keyword. We'd like for the exclude keyword to allow for exclusion of errand VMs. Problem: one of our bosh addons has a pretty expensive init step, i.e. it downloads a database locally. This is a pointless operation on an errand VM because the VM goes away. Additionally, that particular errand runs on a nano instance with only 512mb of RAM and causes the CF deployment to fail. — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub, or mute the thread.

[cppforlife]

@oozie does that work for you?

[oozie]

Apologies for a delay in responding @cppforlife
I've been trying to figure out how to exclude: only from errand machines, rather than particular jobs/deployments. What I want to avoid is maintaining a blacklist of errands under exclude.
If you have any hints on how to accomplish excluding from errands that would be great.

[jfmyers9]

This has been implemented as of #1902.