LAVA Scheduler (deprecated) 2011.06

Milestone information

Project:
LAVA Scheduler (deprecated)
Series:
linaro-11.11
Version:
2011.06
Released:
 
Registrant:
Paul Larson
Release registered:
Active:
No. Drivers cannot target bugs and blueprints to this milestone.  

Download RDF metadata

Activities

Assigned to you:
No blueprints or bugs assigned to you.
Assignees:
No users assigned to blueprints and bugs.
Blueprints:
No blueprints are targeted to this milestone.
Bugs:
No bugs are targeted to this milestone.

Download files for this release

After you've downloaded a file, you can verify its authenticity using its MD5 sum or signature. (How do I verify a download?)

File Description Downloads
download icon lava-scheduler-2011.06.tar.gz (md5, sig) Source code release 57
last downloaded 41 weeks ago
Total downloads: 57

Release notes 

Highlights of this release:
* First release of the LAVA Scheduler
* API for submitting jobs
* Integration with LAVA Server
* A daemon for processing jobs submitted to the database, and running them

For more information about setting up, using, and developing on LAVA, see https://wiki.linaro.org/Platform/Validation/LAVA/Documentation

Changelog 

View the full changelog

2011-06-29 Michael-Doyle Hudson <email address hidden>

 a database-backed jobsource for the scheduler daemon

2011-06-24 Michael-Doyle Hudson <email address hidden>

 merge trunk

2011-06-23 Michael-Doyle Hudson <email address hidden>

 tests for jobComplete

2011-06-23 Michael-Doyle Hudson <email address hidden>

 finish getJobForBoard tests for now

2011-06-23 Michael-Doyle Hudson <email address hidden>

 another test

2011-06-23 Michael-Doyle Hudson <email address hidden>

 some test helper refactoring

2011-06-23 Michael-Doyle Hudson <email address hidden>

 a test for getJobForBoard

2011-06-23 Michael-Doyle Hudson <email address hidden>

 start to test DatabaseJobSource

2011-06-23 Michael-Doyle Hudson <email address hidden>

 dithering over naming

2011-06-23 Michael-Doyle Hudson <email address hidden>

 avoid using defer_to_thread decorator, so i can write tests that do not use threads

2011-06-23 Michael-Doyle Hudson <email address hidden>

 merge trunk (no text changes)

2011-06-23 Michael-Doyle Hudson <email address hidden>

 record start and stop time

2011-06-22 Michael-Doyle Hudson <email address hidden>

 add a comment

2011-06-22 Michael-Doyle Hudson <email address hidden>

 finally an approach to concurrency safety i can like

2011-06-21 Michael-Doyle Hudson <email address hidden>

 merge improvements from daemon-v0

2011-06-17 Michael-Doyle Hudson <email address hidden>

 oops, properly mark the device as idle when a job finishes

2011-06-17 Michael-Doyle Hudson <email address hidden>

 appears to work now!!

2011-06-17 Michael-Doyle Hudson <email address hidden>

 sundry fixes, and the first of what will surely be many errbacks.

2011-06-17 Michael-Doyle Hudson <email address hidden>

 (maybe) implement getJobForBoard

2011-06-17 Michael-Doyle Hudson <email address hidden>

 add admin interface for scheduler models; one fix

2011-06-17 Michael-Doyle Hudson <email address hidden>

 start a db-backed jobsource

2011-06-23 Paul Larson <email address hidden>

 Add copying for AGPL

2011-06-23 Zygmunt Krynicki <email address hidden>

 Use versiontools in setup.py

2011-06-23 Zygmunt Krynicki <email address hidden>

 Add MANIFEST.in

2011-06-23 Michael-Doyle Hudson <email address hidden>

 first cut at a scheduler daemon: this one just uses the filesystem as its datastore

2011-06-21 Michael-Doyle Hudson <email address hidden>

 update some parameter names

2011-06-21 Michael-Doyle Hudson <email address hidden>

 some more tests, and fix some bugs they found

2011-06-21 Michael-Doyle Hudson <email address hidden>

 add more infrastructure; add test

2011-06-21 Michael-Doyle Hudson <email address hidden>

 one more test, plus a double

2011-06-21 Michael-Doyle Hudson <email address hidden>

 two more tests

2011-06-21 Michael-Doyle Hudson <email address hidden>

 initial test, some more docs

2011-06-20 Michael-Doyle Hudson <email address hidden>

 an over-detailed docstring

2011-06-20 Michael-Doyle Hudson <email address hidden>

 remove the log file

2011-06-17 Michael-Doyle Hudson <email address hidden>

 *cough*

2011-06-17 Michael-Doyle Hudson <email address hidden>

 i missed adding the callback that requested another job when one finished on a board

2011-06-17 Michael-Doyle Hudson <email address hidden>

 partition code some more; add more logging

2011-06-17 Michael-Doyle Hudson <email address hidden>

 start to factor code into separate files

2011-06-16 Michael-Doyle Hudson <email address hidden>

 this is not needed any more

2011-06-16 Michael-Doyle Hudson <email address hidden>

 remove initial implementation

2011-06-16 Michael-Doyle Hudson <email address hidden>

 start looking for jobs on newly found boards

2011-06-16 Michael-Doyle Hudson <email address hidden>

 more logging, more working

2011-06-16 Michael-Doyle Hudson <email address hidden>

 closer to working

2011-06-16 Michael-Doyle Hudson <email address hidden>

 it is sad that i can almost type this sort of thing
 in my sleep

2011-06-15 Michael-Doyle Hudson <email address hidden>

 *cough*

2011-06-15 Michael-Doyle Hudson <email address hidden>

 don't stomp over completed job files

2011-06-15 Michael-Doyle Hudson <email address hidden>

 a slightly more interesting pretend dispatcher

2011-06-15 Michael-Doyle Hudson <email address hidden>

 save output, do not dispatch more than one job at once

2011-06-15 Michael-Doyle Hudson <email address hidden>

 this does stuff

2011-06-15 Michael-Doyle Hudson <email address hidden>

 a start?

2011-06-14 Michael-Doyle Hudson <email address hidden>

 add a submit_job api frontend to job creation

2011-06-14 Michael-Doyle Hudson <email address hidden>

 check that login succeeded in TestTransport

2011-06-14 Michael-Doyle Hudson <email address hidden>

 remove whiny comments

2011-06-13 Michael-Doyle Hudson <email address hidden>

 more comments

2011-06-13 Michael-Doyle Hudson <email address hidden>

 add a comment

2011-06-13 Michael-Doyle Hudson <email address hidden>

 merge trunk, which includes a small change to create-TestJob

2011-06-13 Michael-Doyle Hudson <email address hidden>

 all tests pass at last

2011-06-13 Michael-Doyle Hudson <email address hidden>

 some sort of progress

2011-06-13 Michael-Doyle Hudson <email address hidden>

 some formatting improvements

2011-06-13 Michael-Doyle Hudson <email address hidden>

 "merge" create-TestJob, although it is nearly a null merge

2011-06-13 Michael-Doyle Hudson <email address hidden>

 improvements

2011-06-10 Michael-Doyle Hudson <email address hidden>

 very simple xmlrpc-level test

2011-06-13 Michael-Doyle Hudson <email address hidden>

 Add a method for creating TestJobs, and enough of the model required to do
 that.

2011-06-13 Michael-Doyle Hudson <email address hidden>

 change to a TextField for TestJob.definition

2011-06-13 Michael-Doyle Hudson <email address hidden>

 make the DeviceType.name primary

2011-06-13 Michael-Doyle Hudson <email address hidden>

 comment out stuff that is not tested yet and update docstrings

2011-06-13 Michael-Doyle Hudson <email address hidden>

 repair test

2011-06-10 Michael-Doyle Hudson <email address hidden>

 comment out some stuff that is not tested yet

2011-06-10 Michael-Doyle Hudson <email address hidden>

 one more test

2011-06-10 Michael-Doyle Hudson <email address hidden>

 some more tests and code to pass them

2011-06-10 Michael-Doyle Hudson <email address hidden>

 make test pass

2011-06-10 Michael-Doyle Hudson <email address hidden>

 add some models and one test (which fails)

2011-06-10 Michael-Doyle Hudson <email address hidden>

 expose the api trivially

2011-06-07 Michael-Doyle Hudson <email address hidden>

 expose a trivial api call

2011-05-25 Michael-Doyle Hudson <email address hidden>

 lava-server extenson skeleton

2011-05-25 Michael-Doyle Hudson <email address hidden>

 django-admin startapp lava_scheduler_app

0 blueprints and 0 bugs targeted

There are no feature specifications or bug tasks targeted to this milestone. The project's maintainer, driver, or bug supervisor can target specifications and bug tasks to this milestone to track the things that are expected to be completed for the release.

This milestone contains Public information
Everyone can see this information.