Deploy node 3 long time
Pages: 1 2
pedro6161
36 Posts
December 24, 2020, 6:12 pmQuote from pedro6161 on December 24, 2020, 6:12 pmSweet, now is working with LACP, thanks Admin
anyway i have another questions :
- Can i put load balancer in front of CIFS and NFS services ? to avoid round-robin on DNS, so no need add multiple ip address on DNS ?
- still confuse regarding S3 with RGW, if i enable manual, can use existing OSD or i have to create another pool OSD ?
- after deployment wizard complete, are still require the network interface same for all those server ? since 1 of my server only have 4 interface and the rest have 6 interface, that's why before deploy wizard i add dummy interface, but i don't know do i need enable every time the dummy interface before PetaSAN service running ?
Sweet, now is working with LACP, thanks Admin
anyway i have another questions :
- Can i put load balancer in front of CIFS and NFS services ? to avoid round-robin on DNS, so no need add multiple ip address on DNS ?
- still confuse regarding S3 with RGW, if i enable manual, can use existing OSD or i have to create another pool OSD ?
- after deployment wizard complete, are still require the network interface same for all those server ? since 1 of my server only have 4 interface and the rest have 6 interface, that's why before deploy wizard i add dummy interface, but i don't know do i need enable every time the dummy interface before PetaSAN service running ?
admin
2,930 Posts
December 25, 2020, 10:13 pmQuote from admin on December 25, 2020, 10:13 pm1- it could work if the load balancer has sticky sessions to so that once a client connects to a specific gateway, all requests from this client will go the that specific gateway to preserve session state.
2-You do not need to add new OSDs. You need to add pools for rgw, a single OSD can serve many pools of types: rgw, rbd, cephfs. If you do not add the rgw pools yourself, the rgw gateway service will add them for you when it first starts, it is better to add them yourself to have more control.
3- no need to have servers have the same interfaces and no need for dummy interfaces. All servers need to have the core interfaces for management and backend (you can also have management and backend on the same interface if you wish), but apart for the core interfaces, the required interfaces per node is determined by what services it will run and what interfaces are defined for such services. You could, if you wish, define all services and backend to run on same interface. Another useful tool, if you use several interfaces and have different hardware across your nodes, you can re-name / re-order the interfaces per node from the blue console menu.
1- it could work if the load balancer has sticky sessions to so that once a client connects to a specific gateway, all requests from this client will go the that specific gateway to preserve session state.
2-You do not need to add new OSDs. You need to add pools for rgw, a single OSD can serve many pools of types: rgw, rbd, cephfs. If you do not add the rgw pools yourself, the rgw gateway service will add them for you when it first starts, it is better to add them yourself to have more control.
3- no need to have servers have the same interfaces and no need for dummy interfaces. All servers need to have the core interfaces for management and backend (you can also have management and backend on the same interface if you wish), but apart for the core interfaces, the required interfaces per node is determined by what services it will run and what interfaces are defined for such services. You could, if you wish, define all services and backend to run on same interface. Another useful tool, if you use several interfaces and have different hardware across your nodes, you can re-name / re-order the interfaces per node from the blue console menu.
Pages: 1 2
Deploy node 3 long time
pedro6161
36 Posts
Quote from pedro6161 on December 24, 2020, 6:12 pmSweet, now is working with LACP, thanks Admin
anyway i have another questions :
- Can i put load balancer in front of CIFS and NFS services ? to avoid round-robin on DNS, so no need add multiple ip address on DNS ?
- still confuse regarding S3 with RGW, if i enable manual, can use existing OSD or i have to create another pool OSD ?
- after deployment wizard complete, are still require the network interface same for all those server ? since 1 of my server only have 4 interface and the rest have 6 interface, that's why before deploy wizard i add dummy interface, but i don't know do i need enable every time the dummy interface before PetaSAN service running ?
Sweet, now is working with LACP, thanks Admin
anyway i have another questions :
- Can i put load balancer in front of CIFS and NFS services ? to avoid round-robin on DNS, so no need add multiple ip address on DNS ?
- still confuse regarding S3 with RGW, if i enable manual, can use existing OSD or i have to create another pool OSD ?
- after deployment wizard complete, are still require the network interface same for all those server ? since 1 of my server only have 4 interface and the rest have 6 interface, that's why before deploy wizard i add dummy interface, but i don't know do i need enable every time the dummy interface before PetaSAN service running ?
admin
2,930 Posts
Quote from admin on December 25, 2020, 10:13 pm1- it could work if the load balancer has sticky sessions to so that once a client connects to a specific gateway, all requests from this client will go the that specific gateway to preserve session state.
2-You do not need to add new OSDs. You need to add pools for rgw, a single OSD can serve many pools of types: rgw, rbd, cephfs. If you do not add the rgw pools yourself, the rgw gateway service will add them for you when it first starts, it is better to add them yourself to have more control.
3- no need to have servers have the same interfaces and no need for dummy interfaces. All servers need to have the core interfaces for management and backend (you can also have management and backend on the same interface if you wish), but apart for the core interfaces, the required interfaces per node is determined by what services it will run and what interfaces are defined for such services. You could, if you wish, define all services and backend to run on same interface. Another useful tool, if you use several interfaces and have different hardware across your nodes, you can re-name / re-order the interfaces per node from the blue console menu.
1- it could work if the load balancer has sticky sessions to so that once a client connects to a specific gateway, all requests from this client will go the that specific gateway to preserve session state.
2-You do not need to add new OSDs. You need to add pools for rgw, a single OSD can serve many pools of types: rgw, rbd, cephfs. If you do not add the rgw pools yourself, the rgw gateway service will add them for you when it first starts, it is better to add them yourself to have more control.
3- no need to have servers have the same interfaces and no need for dummy interfaces. All servers need to have the core interfaces for management and backend (you can also have management and backend on the same interface if you wish), but apart for the core interfaces, the required interfaces per node is determined by what services it will run and what interfaces are defined for such services. You could, if you wish, define all services and backend to run on same interface. Another useful tool, if you use several interfaces and have different hardware across your nodes, you can re-name / re-order the interfaces per node from the blue console menu.