job id preallocation

[opalmer]

Issue by opalmer from Thursday Sep 12, 2013 at 01:09 GMT
Originally opened as opalmer/deprecated-pyfarm-models#5

---

In some cases it is beneficial to be able to grab a job id without populating its information yet.

Additional considerations on implementation:

• Errors produced when attempting to retrieve information on a preallocated job
• Expiration - so we can cleanup entries that were never populated
• Possibility of requiring some information for preallocation. For example you could preallocate a job for a specific jobtype which might require certain fields to be populated.

In addition it may also be possible to use preallocation to do some very basic setup:

from pyfarm.api import job

build, render, post = job.preallocate(type="some_render_type")

At this point each object's attributes could be modified and then posted back to the master without submitting the job. Ideally it could even be used to post-setup a job during something like the build step.

[opalmer]

Comment by opalmer from Sunday Sep 15, 2013 at 22:23 GMT

---

The backend requirement for this has been finished. Another ticket will need to be opened once pyfarm.api is created.

[opalmer]

Comment by opalmer from Thursday Dec 19, 2013 at 06:21 GMT

---

Reopening, #30 broke this and it's something that needs to be revisited anyway because the post-checks are not explicit enough and there's quite a few new parts to the model.