@mdavidsaver can't seem to add you as a reviewer

I do know enough to comment on the ansible-ness of this change, but it looks like the right idea.

Well, #91 was asking for a default setting that applies to all JVMs inside the Training-VM.
This PR implements two specific ones.
Is there a non-confusing way to have generic settings and per-role overrides?

Also, I would prefer the variable names being consistent.

You

Well, #91 was asking for a default setting that applies to all JVMs inside the Training-VM. This PR implements two specific ones. Is there a non-confusing way to have generic settings and per-role overrides?

Also, I would prefer the variable names being consistent.

Could do a java role, but I think there should be quite different settings for ui vs services, so in context of that I think this is fine.

Well, #91 was asking for a default setting that applies to all JVMs inside the Training-VM. This PR implements two specific ones. Is there a non-confusing way to have generic settings and per-role overrides?

Could do a java role, but I think there should be quite different settings for ui vs services, so in context of that I think this is fine.

I can see ui vs. services, but if all services have similar requirements, there could still be a default one that phoebus overrides.

Could do a java role, but I think there should be quite different settings for ui vs services, so in context of that I think this is fine.

Actually, looking at this PR, they are not really "quite different", are they?
(Maybe I don't understand them well enough.)

While in this PR they are not different but, as mentioned by sky, there is good reason for them to be separate.

Which, again, I understand and support.

should we merge and close issue #91 :)

After streamlining the names, please.

Done, using the same that was in archiver appliance