Network configuration
nefelim4ag
2 Posts
March 17, 2017, 12:06 pmQuote from nefelim4ag on March 17, 2017, 12:06 pmAFAIK ceph don't need so much ip's and networks, i.e. i run ceph + iSCSI on general Linux machine with only one ip
Only what i can add to that configuration is a bonding + several vlans (example: vlan for ceph + vlan for iSCSI)
At now i try to build a testing cluster with petasan in VM's and so complex network configuration are useless
May be i can skip some network settings? and i don't found such button?
AFAIK ceph don't need so much ip's and networks, i.e. i run ceph + iSCSI on general Linux machine with only one ip
Only what i can add to that configuration is a bonding + several vlans (example: vlan for ceph + vlan for iSCSI)
At now i try to build a testing cluster with petasan in VM's and so complex network configuration are useless
May be i can skip some network settings? and i don't found such button?
admin
2,930 Posts
March 17, 2017, 12:41 pmQuote from admin on March 17, 2017, 12:41 pmYou have a point that the cluster network in PetaSAN is not trivial...I agree.
Can you build a system with 1 ip per machine, yes but it may not suit many deployments.
-Ceph recommends having 2 subnets, a "public" subnet for client traffic and a "private" subnet for replication/backfill traffic.
-iSCSI MPIO requires 2 subnets.
-The management traffic is recommended to be on a separate subnet in many systems. In some cases this subnet is routed to other external networks.
Note that the cluster network settings needs to be done only once when creating the cluster, after this step things are quite easy. Also note that you can use a min of 2 physical nics. We try to make things easy in PetaSAN, but correctly planning the network needs some effort, but a lot of this relates to the complexity of the system we want to achieve.
You have a point that the cluster network in PetaSAN is not trivial...I agree.
Can you build a system with 1 ip per machine, yes but it may not suit many deployments.
-Ceph recommends having 2 subnets, a "public" subnet for client traffic and a "private" subnet for replication/backfill traffic.
-iSCSI MPIO requires 2 subnets.
-The management traffic is recommended to be on a separate subnet in many systems. In some cases this subnet is routed to other external networks.
Note that the cluster network settings needs to be done only once when creating the cluster, after this step things are quite easy. Also note that you can use a min of 2 physical nics. We try to make things easy in PetaSAN, but correctly planning the network needs some effort, but a lot of this relates to the complexity of the system we want to achieve.
Last edited on March 18, 2017, 8:39 am · #2
Network configuration
nefelim4ag
2 Posts
Quote from nefelim4ag on March 17, 2017, 12:06 pmAFAIK ceph don't need so much ip's and networks, i.e. i run ceph + iSCSI on general Linux machine with only one ip
Only what i can add to that configuration is a bonding + several vlans (example: vlan for ceph + vlan for iSCSI)
At now i try to build a testing cluster with petasan in VM's and so complex network configuration are useless
May be i can skip some network settings? and i don't found such button?
AFAIK ceph don't need so much ip's and networks, i.e. i run ceph + iSCSI on general Linux machine with only one ip
Only what i can add to that configuration is a bonding + several vlans (example: vlan for ceph + vlan for iSCSI)
At now i try to build a testing cluster with petasan in VM's and so complex network configuration are useless
May be i can skip some network settings? and i don't found such button?
admin
2,930 Posts
Quote from admin on March 17, 2017, 12:41 pmYou have a point that the cluster network in PetaSAN is not trivial...I agree.
Can you build a system with 1 ip per machine, yes but it may not suit many deployments.
-Ceph recommends having 2 subnets, a "public" subnet for client traffic and a "private" subnet for replication/backfill traffic.
-iSCSI MPIO requires 2 subnets.
-The management traffic is recommended to be on a separate subnet in many systems. In some cases this subnet is routed to other external networks.
Note that the cluster network settings needs to be done only once when creating the cluster, after this step things are quite easy. Also note that you can use a min of 2 physical nics. We try to make things easy in PetaSAN, but correctly planning the network needs some effort, but a lot of this relates to the complexity of the system we want to achieve.
You have a point that the cluster network in PetaSAN is not trivial...I agree.
Can you build a system with 1 ip per machine, yes but it may not suit many deployments.
-Ceph recommends having 2 subnets, a "public" subnet for client traffic and a "private" subnet for replication/backfill traffic.
-iSCSI MPIO requires 2 subnets.
-The management traffic is recommended to be on a separate subnet in many systems. In some cases this subnet is routed to other external networks.
Note that the cluster network settings needs to be done only once when creating the cluster, after this step things are quite easy. Also note that you can use a min of 2 physical nics. We try to make things easy in PetaSAN, but correctly planning the network needs some effort, but a lot of this relates to the complexity of the system we want to achieve.