Change Backend and iscsi to bond
eazyadm
25 Posts
June 3, 2022, 7:18 amQuote from eazyadm on June 3, 2022, 7:18 amHi,
we're good to left our testing stage, but we've got new requirements which forces us to change the config.
At the moment, all our Networklinks are native links.
Now, I have to migrate Backend and iSCSI to an LACP link.
We have 3 Monitoring Nodes and 6 active Storage Nodes.
Downtime is no Problem, so my hope is that there is an config file, in which I can change the interface settings, than i shutdown all nodes and start one by one with the new interface configuration, to move eth2 and 3 to bond0 and eth 4 and 5 to bond1 and change the eth mappings to bond0.vlans and bond1.vlans.
Is there any advice how to do this without crashing the whole cluster?
Thanks
Hi,
we're good to left our testing stage, but we've got new requirements which forces us to change the config.
At the moment, all our Networklinks are native links.
Now, I have to migrate Backend and iSCSI to an LACP link.
We have 3 Monitoring Nodes and 6 active Storage Nodes.
Downtime is no Problem, so my hope is that there is an config file, in which I can change the interface settings, than i shutdown all nodes and start one by one with the new interface configuration, to move eth2 and 3 to bond0 and eth 4 and 5 to bond1 and change the eth mappings to bond0.vlans and bond1.vlans.
Is there any advice how to do this without crashing the whole cluster?
Thanks
admin
2,930 Posts
June 3, 2022, 9:39 amQuote from admin on June 3, 2022, 9:39 amTh's is set in the config file:
/opt/petasan/config/cluster_info.json
You could edit the file but safest way is to do a test vm and deploy the first node with the desired configuration then grab this file.
You should be able to perform this node by node so your cluster is up, you will also need to config switch ports in steps. Else if you can afford downtime, it is easier to do it all at once.
If this is a production cluster, it is always better to test your steps on a test cluster, it will only take a couple of minutes to set up a vm cluster on your desktop.
For iSCSI, if you use MPIO on 2 different interfaces, the is no need to use bonds.
Th's is set in the config file:
/opt/petasan/config/cluster_info.json
You could edit the file but safest way is to do a test vm and deploy the first node with the desired configuration then grab this file.
You should be able to perform this node by node so your cluster is up, you will also need to config switch ports in steps. Else if you can afford downtime, it is easier to do it all at once.
If this is a production cluster, it is always better to test your steps on a test cluster, it will only take a couple of minutes to set up a vm cluster on your desktop.
For iSCSI, if you use MPIO on 2 different interfaces, the is no need to use bonds.
eazyadm
25 Posts
June 3, 2022, 3:11 pmQuote from eazyadm on June 3, 2022, 3:11 pmHi,
thanks for your answer, that works!
But I can't chosse the bond interfaces in the gui to use it for smb for example.
And what happens with new nodes? will they get the bond configuration? Or is there a central configuration file which holds that information.
Thanks
Hi,
thanks for your answer, that works!
But I can't chosse the bond interfaces in the gui to use it for smb for example.
And what happens with new nodes? will they get the bond configuration? Or is there a central configuration file which holds that information.
Thanks
admin
2,930 Posts
June 3, 2022, 3:56 pmQuote from admin on June 3, 2022, 3:56 pmYou can, but it is not stored in the config file but stored in Consul, it can be changed any time from the UI. This is true for all services, but backend needs to be defined in the config file ( you need backend up to talk to Consul to get global configuration )
New nodes will get updated configuration..the cluster_config is copied over via ssh, then once the backend is up, the services config is read from Consul.
You can, but it is not stored in the config file but stored in Consul, it can be changed any time from the UI. This is true for all services, but backend needs to be defined in the config file ( you need backend up to talk to Consul to get global configuration )
New nodes will get updated configuration..the cluster_config is copied over via ssh, then once the backend is up, the services config is read from Consul.
eazyadm
25 Posts
June 3, 2022, 5:31 pmQuote from eazyadm on June 3, 2022, 5:31 pmSorry, after a while i got the bond interfaces.
Everything is running quite perfect, thanks for your support
Sorry, after a while i got the bond interfaces.
Everything is running quite perfect, thanks for your support
Change Backend and iscsi to bond
eazyadm
25 Posts
Quote from eazyadm on June 3, 2022, 7:18 amHi,
we're good to left our testing stage, but we've got new requirements which forces us to change the config.
At the moment, all our Networklinks are native links.
Now, I have to migrate Backend and iSCSI to an LACP link.
We have 3 Monitoring Nodes and 6 active Storage Nodes.
Downtime is no Problem, so my hope is that there is an config file, in which I can change the interface settings, than i shutdown all nodes and start one by one with the new interface configuration, to move eth2 and 3 to bond0 and eth 4 and 5 to bond1 and change the eth mappings to bond0.vlans and bond1.vlans.
Is there any advice how to do this without crashing the whole cluster?
Thanks
Hi,
we're good to left our testing stage, but we've got new requirements which forces us to change the config.
At the moment, all our Networklinks are native links.
Now, I have to migrate Backend and iSCSI to an LACP link.
We have 3 Monitoring Nodes and 6 active Storage Nodes.
Downtime is no Problem, so my hope is that there is an config file, in which I can change the interface settings, than i shutdown all nodes and start one by one with the new interface configuration, to move eth2 and 3 to bond0 and eth 4 and 5 to bond1 and change the eth mappings to bond0.vlans and bond1.vlans.
Is there any advice how to do this without crashing the whole cluster?
Thanks
admin
2,930 Posts
Quote from admin on June 3, 2022, 9:39 amTh's is set in the config file:
/opt/petasan/config/cluster_info.json
You could edit the file but safest way is to do a test vm and deploy the first node with the desired configuration then grab this file.
You should be able to perform this node by node so your cluster is up, you will also need to config switch ports in steps. Else if you can afford downtime, it is easier to do it all at once.If this is a production cluster, it is always better to test your steps on a test cluster, it will only take a couple of minutes to set up a vm cluster on your desktop.
For iSCSI, if you use MPIO on 2 different interfaces, the is no need to use bonds.
Th's is set in the config file:
/opt/petasan/config/cluster_info.json
You could edit the file but safest way is to do a test vm and deploy the first node with the desired configuration then grab this file.
You should be able to perform this node by node so your cluster is up, you will also need to config switch ports in steps. Else if you can afford downtime, it is easier to do it all at once.
If this is a production cluster, it is always better to test your steps on a test cluster, it will only take a couple of minutes to set up a vm cluster on your desktop.
For iSCSI, if you use MPIO on 2 different interfaces, the is no need to use bonds.
eazyadm
25 Posts
Quote from eazyadm on June 3, 2022, 3:11 pmHi,
thanks for your answer, that works!
But I can't chosse the bond interfaces in the gui to use it for smb for example.
And what happens with new nodes? will they get the bond configuration? Or is there a central configuration file which holds that information.
Thanks
Hi,
thanks for your answer, that works!
But I can't chosse the bond interfaces in the gui to use it for smb for example.
And what happens with new nodes? will they get the bond configuration? Or is there a central configuration file which holds that information.
Thanks
admin
2,930 Posts
Quote from admin on June 3, 2022, 3:56 pmYou can, but it is not stored in the config file but stored in Consul, it can be changed any time from the UI. This is true for all services, but backend needs to be defined in the config file ( you need backend up to talk to Consul to get global configuration )
New nodes will get updated configuration..the cluster_config is copied over via ssh, then once the backend is up, the services config is read from Consul.
You can, but it is not stored in the config file but stored in Consul, it can be changed any time from the UI. This is true for all services, but backend needs to be defined in the config file ( you need backend up to talk to Consul to get global configuration )
New nodes will get updated configuration..the cluster_config is copied over via ssh, then once the backend is up, the services config is read from Consul.
eazyadm
25 Posts
Quote from eazyadm on June 3, 2022, 5:31 pmSorry, after a while i got the bond interfaces.
Everything is running quite perfect, thanks for your support
Sorry, after a while i got the bond interfaces.
Everything is running quite perfect, thanks for your support