services:dccmirrors
Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision | Last revision Both sides next revision | ||
|
services:dccmirrors [2017/04/27 18:46] dgalloway |
services:dccmirrors [2017/06/07 16:53] dgalloway |
||
|---|---|---|---|
| Line 4: | Line 4: | ||
| ===== Purpose/Background ===== | ===== Purpose/Background ===== | ||
| - | 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 to uncover difficulties in installing and maintaining the product. |
| Setup notes: https://docs.google.com/document/d/197cRnSA8QF1vYcAejvIT6tCG9Vi1nhUWrX987HTg7P4/edit | Setup notes: https://docs.google.com/document/d/197cRnSA8QF1vYcAejvIT6tCG9Vi1nhUWrX987HTg7P4/edit | ||
| Line 10: | Line 10: | ||
| ===== Architecture ===== | ===== Architecture ===== | ||
| ==== Systems ==== | ==== Systems ==== | ||
| - | There are two clusters. One uses RGW and one uses RBD as the backend/client. Both have MONs running on VMs in [[services:RHEV]]. Their public gateways are also VMs in RHEV. | + | There are two clusters. One uses RGW and one uses RBD as the client. Both have 3 MONs running on VMs in [[services:RHEV]]. Their public gateways are also VMs in RHEV. |
| - | There are affinity rules in place in RHEV to ensure the MONs all run on separate baremetal hyperisors. The same goes for the RBD and RGW VMs. | + | There are affinity rules in place to ensure the RGW and RBD public gateways all run on separate baremetal hyperisors. |
| + | There are also affinity rules in place in RHEV to ensure the MONs all run on separate baremetal hyperisors. | ||
| + | |||
| + | === RBD Cluster === | ||
| The RBD cluster's OSDs run on mira046, mira052, and mira084. | The RBD cluster's OSDs run on mira046, mira052, and mira084. | ||
| + | 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's OSDs run on mira102, mira103, and mira106. | The RGW cluster's OSDs run on mira102, mira103, and mira106. | ||
| + | |||
| + | According to Red Hat [[https://access.redhat.com/documentation/en-us/red_hat_ceph_storage/2/html-single/object_gateway_guide_for_red_hat_enterprise_linux/#configuring_gateways_for_static_web_hosting|downstream docs]], at least two gateway hosts (dl-rgw-pub{01,02}) and two HAProxy servers (dl-rgw-ha{01,02}) are required to serve a static website. | ||
| ==== 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's public VM has a NIC on front and a NIC on the WAN VLAN. | ||
| - | Each cluster's public gateway is running on a VM in RHEV with an interface on the front and public VLANs. | + | The RGW cluster's HAProxy VMs have a NIC on front and a NIC on the WAN VLAN. The RGW clients themselves only have a NIC on the front VLAN. |
services/dccmirrors.txt · Last modified: 2017/06/13 15:58 by dgalloway
Page Tools
Except where otherwise noted, content on this wiki is licensed under the following license: CC Attribution-Share Alike 4.0 International
