Skip to content

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
    • Help
    • Support
    • Submit feedback
    • Contribute to GitLab
  • Sign in
beat.web
beat.web
  • Project overview
    • Project overview
    • Details
    • Activity
    • Releases
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 54
    • Issues 54
    • List
    • Boards
    • Labels
    • Milestones
  • Merge Requests 2
    • Merge Requests 2
  • CI / CD
    • CI / CD
    • Pipelines
    • Jobs
    • Schedules
  • Analytics
    • Analytics
    • CI / CD
    • Repository
    • Value Stream
  • Members
    • Members
  • Collapse sidebar
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
  • beat
  • beat.webbeat.web
  • Issues
  • #21

Closed
Open
Opened Sep 02, 2014 by André Anjos@andre.anjos💬
  • Report abuse
  • New issue
Report abuse New issue

New django action for experiment deletion

We should add a new django admin action (https://docs.djangoproject.com/en/dev/ref/contrib/admin/actions/) for treating Experiment objects in the BEAT django DB.

In case this action is clicked by the administrator, it allows him/her to:

  • Delete the Experiment + all associated results
  • Clean-up the cache from the experiment:
    • Clean-up local cache entries in the Django DB
    • Send a message to the scheduler to delete certain cache files (see biometric/beat.scheduler#10). Notice you don't need to cancel any experiment (in case they are running). The scheduler shall be able to handle this gracefully.

If another experiment shares cache files with the experiment being deleted, then:

  1. The cache files of that experiment are also cleaned-up
  2. The experiment is marked as "Pending", so the user can re-run it at a later stage (unless the experiment was also running, in which case it will be cancelled by the scheduler automatically).

We understand this is a rather drastic action, but may be required in case of severe cache corruption.

Assignee
Assign to
Tutorial for the FG2015 Conference
Milestone
Tutorial for the FG2015 Conference
Assign milestone
Time tracking
None
Due date
None
0
Labels
None
Assign labels
  • View project labels
Reference: beat/beat.web#21