This only uses NFS to backup the sqlite database state. We can do that on Cinder just as well
Description
Description
Details
Details
Related Changes in Gerrit:
| Status | Subtype | Assigned | Task | ||
|---|---|---|---|---|---|
| Open | None | T272395 Cloud: reduce NAT exceptions from cloud to production | |||
| Resolved | Andrew | T291405 [NFS] Reduce or eliminate bare-metal NFS servers | |||
| Resolved | Andrew | T301280 Move project-specific NFS mounts onto project-local NFS servers | |||
| Resolved | Andrew | T301715 Stop using NFS for the project-proxy cloud-vps project |
Event Timeline
Comment Actions
Change 762509 had a related patch set uploaded (by Andrew Bogott; author: Andrew Bogott):
[operations/puppet@production] dynmamicproxy: move db backups off of nfs and onto a cinder volume
Comment Actions
As an alternative, we could move that SQLite database into the cloudinfra mysql cluster and deal with its backups in T301640
Comment Actions
That's a good idea but also I don't think I want to understand this enough right now to move to a centralized database (right now it's one db per host)
Comment Actions
Change 762509 merged by Andrew Bogott:
[operations/puppet@production] dynmamicproxy: move db backups off of nfs and onto a cinder volume
Comment Actions
Change 762543 had a related patch set uploaded (by Andrew Bogott; author: Andrew Bogott):
[operations/puppet@production] nfs-mounts.yaml.erb: remove nfs mounts for project-proxy
Comment Actions
Change 762543 merged by Andrew Bogott:
[operations/puppet@production] nfs-mounts.yaml.erb: remove nfs mounts for project-proxy