Administration #260
Identification of Storage
| Status: | Feedback | Start date: | ||
|---|---|---|---|---|
| Priority: | Normal | Due date: | ||
| Assignee: | Frank Guthausen | % Done: | 0% | |
| Category: | - | Estimated time: | 0.50 h | |
| Target version: | Repertoire 6) Post Production |
Description
At least, as soon, as we use more than one VM-Storage, the storage should be tracked in the database.
I already added a filed hostname for that purpose.
How is VM-Web supposed to access the information, which VM-Storage is mounted in ./storage?
For multiple physical machines we need even more information.
Is an URL enough, or should it be an IP or both?
History
#1 Updated by Alexander Blum about 7 years ago
- Tracker changed from Administration to Verarbeitung
#2 Updated by Alexander Blum about 7 years ago
- Tracker changed from Verarbeitung to Administration
#3 Updated by Alexander Blum about 7 years ago
- Priority changed from Normal to Hoch
- Target version set to 4) Production phase I
#4 Updated by Alexander Blum about 7 years ago
- Target version changed from 4) Production phase I to 1) Testing phase I
#5 Updated by Alexander Blum about 7 years ago
- Assignee set to Frank Guthausen
#6 Updated by Alexander Blum about 7 years ago
- Status changed from Neu to Feedback
#7 Updated by Sarah Stoffels over 6 years ago
- Priority changed from Hoch to Normal
- Target version deleted (
1) Testing phase I)
Wird erst bei Skalierung benötigt, ist für bereits archivierte Daten im Nachhinein nicht mehr relevant, sondern für das Processing.
#8 Updated by Alexander Blum over 5 years ago
- Target version set to 6) Post Production
#9 Updated by Alexander Blum over 4 years ago
- Target version changed from 6) Post Production to Repertoire 6) Post Production
#10 Updated by Alexander Blum over 4 years ago
- Project changed from repertoire to collecting_society