services:dccmirrors
Differences
This shows you the differences between two versions of the page.
| Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
| services:dccmirrors [2017/04/27 18:45] – [Systems] dgalloway | services:dccmirrors [2017/06/13 15:58] (current) – dgalloway | ||
|---|---|---|---|
| Line 4: | Line 4: | ||
| ===== Purpose/ | ===== Purpose/ | ||
| - | The goal of this project is to use/dogfood downstream RHCS to uncover difficulties in installing and maintaining the product. | + | The goal of this project is to use/dogfood downstream RHCS software, docs, and ceph-ansible |
| Setup notes: https:// | Setup notes: https:// | ||
| Line 10: | Line 10: | ||
| ===== Architecture ===== | ===== Architecture ===== | ||
| ==== Systems ==== | ==== Systems ==== | ||
| - | There are two clusters. | + | There are two clusters. |
| - | There are affinity rules in place in RHEV to ensure the MONs all run on separate baremetal | + | There are affinity rules in place to ensure the RGW and RBD public gateways |
| + | There are also affinity rules in place in RHEV to ensure the MONs all run on separate baremetal hyperisors. | ||
| + | |||
| + | === RBD Cluster === | ||
| The RBD cluster' | The RBD cluster' | ||
| + | The MONs run on dl-rbd-mon{01..03}.front.sepia.ceph.com. | ||
| + | |||
| + | Since the RBD cluster is just serving a single block device, only one public VM (dl-rbd-pub) is required. | ||
| + | |||
| + | === RGW Cluster === | ||
| The RGW cluster' | The RGW cluster' | ||
| + | |||
| + | According to Red Hat [[https:// | ||
| ==== Networking ==== | ==== Networking ==== | ||
| - | The clusters were set up to have all traffic go over the front VLAN. | + | The clusters were set up to have all Ceph traffic go over the front VLAN. |
| + | |||
| + | The RBD cluster' | ||
| - | Each cluster' | + | The RGW cluster' |
services/dccmirrors.1493318730.txt.gz · Last modified: by dgalloway
