Docs update following LaunchJob renaming.

This commit is contained in:
Chris Church 2013-04-17 21:53:45 -04:00
parent 883449f4a5
commit 71dbb9c818
2 changed files with 6 additions and 8 deletions

10
TODO.md
View File

@ -4,9 +4,7 @@ TODO items for ansible commander
4/2 NOTES
=========
* supervisord to start celery, modify ansible playbook to set up supervisord <- ChrisC
* host relationships in DB, last launch job status per host, etc (self.play.inventory) <- ChrisC
* stats attributes on launch job status (??) -- which hosts succeeded, failed, etc (through relationship) <-- Chris C
* make launch job rest triggerable & launch job statuses readable. launch_job.start() <-- MPD
* make job rest triggerable & job status readable. now happens just by creating a new job <-- MPD
* do we need something other than default playbook (ProjectOptions) <-- me, later
* way to send cntrl-c to kill job (method on job?) <-- ChrisC, low priority
* documentation on how to run with callbacks from NOT a launchjob <-- ChrisC
@ -23,16 +21,16 @@ sorting?
if you delete a subgroup, hosts go up to parent
verify unique_together on inventory and host name
make a way to start a launch job via the API.
make a way to start a job via the API (create a new job)
future feature of being able to create SavedLaunchJob templates.
future feature of being able to create job templates -- supported in db by JobTemplate
REST TODO
---------
* credentials objects & permissions
* tags (later)
* audit trails (later)
* launch jobs triggering <-- important
* jobs triggering <-- important
* related resources on everything that makes sense <--- important
* expose log data from callback (decide on structure)

View File

@ -77,8 +77,8 @@ Save Login Credentials and Grant Role (Team) Based Permissions
Launch Playbooks and View Results
---------------------------------
* Create a launch job request by posting project, permission, and credential to /api/v1/launch_jobs/
* Monitor the job results at /api/v1/launch_results/X (API subject to change)
* Create a job request by posting project, permission, and credential to /api/v1/jobs/
* Monitor the job results at /api/v1/jobs/X (API subject to change)
* See the history of runs on each host at /api/v1/hosts/X/events/ or /api/v1/groups/X/events/ or /api/v1/inventories/X/events/
Audit API based Activity, Search For Resources