Hi Jeff,
No sorry, it is not clear to me yet. I don't see how we "ban" the waking up of the "alicepilot" script with the current policy. The way I see it, a user should be able to specify a startup script in the JDL. If a site supports it, it can call this startup script by contextualizing the VM.
Images should not be pre-configured to obtain a workload. How the running instance of an
image obtains a workload is a contextualization option left to the site at which the image is
instantiated.
That is what is written in the policy. I give you an image that is pre-configured that upon instantiation, contacts the ALICE central task queue to obtain a workload. It does NOT contact the batch system of the site. Explain to me, after re-reading the above excerpt from the policy, how this is not banned!!! The image is pre-configured to obtain a workload!
Let's make this very concreet:
- The VO software contains a script called /opt/bin/alicepilot.
- The user specifies in the JDL that this script should be called on boot.
- The site contextualizes the images, in this case it means that a boot script is inserted that calls /opt/bin/alicepilot with user priviliges.
So, it is perfectly possible to get work from a pilot job framework with site contextualization.
What am I missing?
it is perfectly possible to do it via your way, it is also possible to do it my way (the image is simply a pilot job and needs no interaction with the JDL ... specifying the image to run is enough). But my way is banned, why??
JT