Hi,
Patches to bring back the infrastructure for delayed_jobs are on list.
In the spirit of getting stories on list ahead of time for people to
absorb before the next planning
meeting, here are the stories I'm thinking of tackling next sprint.
As a developer I'd like to have a scheduling tool in our rails
environment that works with delayed_job
- update conductor spec to pull in rubygem-rufus-scheduler
gem is already in fedora
- add an initializer to start the scheduler in conductor rails process
- rake task to stop/start scheduler
* an alternative would be to separate the scheduler into its own
process/daemon, but that feels unnecessary
As a developer I want to move instance status checking from dbomatic
into a background job
- the scheduler would queue a status checking delayed_job for each
provider account
we should be able to take the code directly from dbomatic and
wrap it around a new job
- the scheduler should not add a duplicate job if one is already in
the queue or is running
- tricky part (at least for me) would be getting scheduler
initializer to recognize the jobs and models
from the rails environment
- remove status checking bits from dbomatic
- validate status checking works with known providers: vsphere,
rhev, and ec2
As a administrator I'd like to view the contents of the queues through
the command line
- first phase would be to create a simple rake command that lists the
contents of the queue
- for phase two research creating aeolus-job, like aeolus-image, to
crud jobs
would involve exposing job queue over conductor rest api
explore what would be the use cases for this, as I'm unsure if
this is
needed
- Richard