Create a Django management command for archivers manipulation

Bug #1419712 reported by Caio Begotti
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Capomastro
Confirmed
Medium
Unassigned

Bug Description

Right now the only part of Capomastro as a service that still has a manual setup in all deployments is the creation of the default archiver. We know most of the times what the archiver is going to be like, so perhaps we should create a Django command like all the other import_* we have so we can create a sane default archiver right after a new deployment, most probably running it from the Juju charm.

Revision history for this message
Daniel Manrique (roadmr) wrote :

Sounds good to me, we should define how versatile we want the command to be. I.e. if we support swift and the environment has swift credentials, do I default to creating a swift archiver? or more realistically, if the configuration has the required data for an ssh archiver, create one, and if not, create a local one (in e.g. /var/lib/capomastro or something).

I'll set it for a bit farther in the future as we still need a bit of work defining this feature.

Changed in capomastro:
status: New → Confirmed
importance: Undecided → Medium
milestone: none → 2015-05
Daniel Manrique (roadmr)
Changed in capomastro:
milestone: 2015-05 → 2015-07
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.