Feature #15780
Update server storage planning needs for 2019-2020
Start date:
2018-08-09
Due date:
% Done:
100%
Description
On Feature #11806 we planned storage until the end of 2018 and in September 2017 we purchased what was needed. We need to do this analysis again.
Things to take into account:
Subtasks
Related issues
Related to Tails - |
Resolved | 2016-09-19 | |
Related to Tails - |
Resolved | 2018-10-03 | |
Blocks Tails - Feature #13284: Core work: Sysadmin (Adapt our infrastructure) | Confirmed | 2017-06-30 |
History
#1 Updated by intrigeri 2018-08-09 14:23:40
- related to
Feature #11806: Update server storage planning needs for at least 2017 added
#2 Updated by intrigeri 2018-08-09 14:23:46
- related to #15779 added
#3 Updated by intrigeri 2018-08-09 14:25:12
- Parent task set to
Bug #11680
#4 Updated by intrigeri 2018-08-09 14:26:20
- Subject changed from Update server storage planning needs for at least 2019 to Update server storage planning needs for 2019-2020
- Description updated
#5 Updated by intrigeri 2018-08-09 14:27:15
- blocks Feature #13284: Core work: Sysadmin (Adapt our infrastructure) added
#6 Updated by intrigeri 2018-08-19 16:27:01
- Target version changed from Tails_3.9 to Tails_3.10.1
It might be that #15779 is solved without having to do this so I’ll take it (somewhat) easy.
#7 Updated by intrigeri 2018-09-27 12:05:42
If my proposal for #15779 is approved, we won’t have to do this work and can simply reject this ticket.
#8 Updated by bertagaz 2018-10-03 09:34:26
- related to
Bug #16025: jenkins-data-disk is running out of diskspace again added
#9 Updated by bertagaz 2018-10-03 09:49:57
I missed the last updates, so I’ve updated te spreadsheet anyway, to see wat our option were for Bug #16025. Spoiler: things are quite relaxed for now.
#10 Updated by intrigeri 2018-10-11 11:09:18
- Status changed from Confirmed to Rejected
- Assignee deleted (
intrigeri) - % Done changed from 0 to 100
intrigeri wrote:
> If my proposal for #15779 is approved, we won’t have to do this work and can simply reject this ticket.
This is indeed what happened.