Project

General

Profile

Actions

Story #7934

closed

[Keep] Test S3 block storage on AWS

Added by Brett Smith almost 7 years ago. Updated almost 7 years ago.

Status:
Resolved
Priority:
Normal
Assigned To:
Category:
-
Target version:
Start date:
02/01/2016
Due date:
% Done:

100%

Estimated time:
(Total: 0.00 h)
Story points:
1.0

Description

  • convert our test cluster on AWS to S3 backed storage
  • run a few test pipelines

Subtasks 4 (0 open4 closed)

Task #8335: Review / merge 7934-4xhpq-s3 in puppet treeResolvedNico César02/01/2016

Actions
Task #8260: Create some volumes, make appropriate configsResolvedTom Clegg02/01/2016

Actions
Task #8266: Update 4xp run scriptsResolvedTom Clegg02/01/2016

Actions
Task #8269: Run a test pipelineResolvedTom Clegg02/03/2016

Actions

Related issues

Blocked by Arvados - Story #7393: [Keep] Prototype S3 blob storageResolvedTom Clegg09/23/2015

Actions
Actions #1

Updated by Ward Vandewege almost 7 years ago

  • Description updated (diff)
  • Assigned To set to Tom Clegg
  • Target version set to 2016-02-03 Sprint
  • Story points set to 1.0
Actions #2

Updated by Tom Clegg almost 7 years ago

  • Status changed from New to In Progress
Actions #3

Updated by Nico César almost 7 years ago

I'm reviewing def93d4e3c614709602cb7052acb0349b2e11e46 on puppet repo

I notice "-s3-access-key-file=/etc/keepstore/amazon_s3_access.key and -s3-secret-key-file=/etc/keepstore/amazon_s3_secret.key" as new parameter.

it comes to my mind why 2 files? is harder to administer and the access/secret bundle goes hand-by-hand. You can't get a new secret for a already existing access. So it will make more sense to me to have either:

1. all config in one file including credentials
2. if the credentials are a sensitive information I prefer 1 key with the access and secret i.e.

-s3-auth-file=/etc/keepstore/amazon_s3_auth.key
Actions #4

Updated by Nico César almost 7 years ago

Nico Cesar wrote:

I'm reviewing def93d4e3c614709602cb7052acb0349b2e11e46 on puppet repo

forgot to make the note in this ticket. This shouldn't stop the merge, but it's nice to have all the config in one place

Actions #5

Updated by Tom Clegg almost 7 years ago

  • Status changed from In Progress to Resolved
Actions

Also available in: Atom PDF