action #161786
closed
QE-Performance team request 2TB storage for performance test data backup size:S
Added by cachen about 1 month ago.
Updated 30 days ago.
Description
Motivation¶
Backup performance test data from dashboard.qa2.suse.asia to reduce the risk of loosing test result by any incident in the service or physical hardware.
Performance comparison test result and test raw data are presenting in performance dashboard and linking in bug report, loosing the data will critically block performance test/debug progress.
Requirement¶
2TB storage size sharing in storage.qe.prg2.suse.org by both TFTP and NFS way for QE-Performance team to syncing their test results from 10.67.128.0/24.
Contact person¶
@jerrytang Jerry Tang and @JNa Joyce Na
Acceptance Criteria¶
- AC1: 2TB of storage is accessible and available for use by the team
Suggestions¶
- Adapt/use/copy the current NFS+FTP server states from the webui role to the storage role as well and apply for storage.qe.prg2.suse.org
- Ensure the team has access to read and write to the server e.g. sftp using existing keys
- Assignee set to okurz
- Target version set to Ready
Are you sure you want to upload data using TFTP or do you mean FTP?
We can setup an FTP+NFS server on storage.qe.prg2.suse.org and you can upload data there, ok?
okurz wrote in #note-1:
Are you sure you want to upload data using TFTP or do you mean FTP?
We can setup an FTP+NFS server on storage.qe.prg2.suse.org and you can upload data there, ok?
Hello Oliver, thank you for the offer, FTP+NFS is fine!
- Tags set to infra, salt, storage, backup
- Status changed from New to In Progress
- Subject changed from QE-Performance team request 2TB storage for performance test data backup to QE-Performance team request 2TB storage for performance test data backup size:S
- Description updated (diff)
On the host storage.qe.prg2.suse.org I prepared a folder /storage/backup:
mkdir -p /storage/backup
chown .users /storage/backup
chmod g+w /storage/backup
@jerrytang @JNa as the host storage.qe.prg2.suse.org is already under salt-control all user accounts that are in https://gitlab.suse.de/openqa/salt-pillars-openqa/-/blob/master/sshd/users.sls already have ssh access. that you could use for the purpose of storing backups using ssh as an access protocol so for example using ssh/scp/rsync/unison. I think that is enough and also easier than using FTP or NFS. Can you work with that or do you actually need NFS and/or FTP?
- Status changed from In Progress to Feedback
Waiting for response for continuing. I have prepared changes for salt to enable FTP/NFS at least readonly but would only deploy that if necessary.
Yes, that. I will also think about a non personal account with according ssh key
- Status changed from Feedback to In Progress
- Due date set to 2024-06-21
- Status changed from In Progress to Feedback
ok. Then please try out to copy over content using rsync and let me know about problems.
- Due date deleted (
2024-06-21)
- Status changed from Feedback to Resolved
No response. Assuming working when needed.
Also available in: Atom
PDF