Closed Bug 1300526 Opened 8 years ago Closed 8 years ago

Implement Amazon EFS as network file system

Categories

(Participation Infrastructure :: Community Ops, task)

task
Not set
normal

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: nemo-yiannis, Assigned: yousef)

References

Details

Amazon EFS [1] looks like a good replacement for our gluster cluster reducing some of the maintenance overhead. Let's evaluate it in our PaaS cluster by using it as persistent storage for some testing WP instances.

Things to check
* Backups and integration with S3/Glacier
* Performance compared to gluster
* Other possible limitations

[1] https://aws.amazon.com/efs/
Blocks: 1267175
Fixed after:

https://github.com/mozilla/partinfra-terraform/pull/38/commits
Assignee: nobody → yousef
Status: NEW → RESOLVED
Closed: 8 years ago
Resolution: --- → FIXED
Status: RESOLVED → REOPENED
Resolution: FIXED → ---
Reopening it since we only tackled the infra part.
Ansible PR opened at https://github.com/mozilla/partinfra-playbooks/pull/53
Summary: Evaluate Amazon EFS as network file system → Implement Amazon EFS as network file system
Implemented in https://github.com/mozilla/partinfra-playbooks/commit/5097da535031e0a0fd1a3a4ef736f32f1135d2de and deployed to prod in https://jenkins.services.mozilla.community/job/ansible-production-release/11/
Status: REOPENED → RESOLVED
Closed: 8 years ago8 years ago
Resolution: --- → FIXED
bonnie++ benchmarks:

efs mounted as volume to docker container:
https://pastebin.mozilla.org/8910652

efs mounted on docker container host
https://pastebin.mozilla.org/8910663
You need to log in before you can comment on or make changes to this bug.