Hi Yuan,<br><br>Thanks for the reply. I am using the latest 0.5.6 and when I look at the man pages for sheep then there is no -b option to use. I had a look at using the -h option and then it lists -b but it doesn't give a proper explanation and syntax. What is the full syntax for the -b option? I just used sheep -b 192.168.1.2 but if I do a collie node info and collie cluster info then it still shows the original bind address from corosync? Will I be able to check somewhere what the actual listening address is? Is this a config setting that can be changed while the cluster is running (maybe using sheepfs?) or must you start sheep with it when starting the cluster?<br>
<br>I also read through all the wiki info again that I can find and do not see any more details around the gateway option and what it allows you to do and how it functions?<br><br>Apologies about all the questions but once I have a full grasp over how everything functions I can write a proper set up guide to get sheepdog running on Ubuntu server nodes as backend storage working with Proxmox.<br>
<br>Thanks.<br><br>Werner<br><br>
<br><div class="gmail_quote">
On 2 April 2013 07:04, Liu Yuan <span dir="ltr"><<a href="mailto:namei.unix@gmail.com" target="_blank">namei.unix@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div>On 04/02/2013 01:15 AM, Werner van der Walt wrote:<br>
> Hi,<br>
><br>
> After having experimented with sheepdog in a lab environment it has<br>
> become clear to me that it uses whatever IP has been set for the<br>
> corosync communications as its advertised cluster IP address. I had a<br>
> look at the documentation and saw that there were two options that<br>
> looked like they may enable you to set an alternative IP address other<br>
> than the one used by corosync.<br>
> The one option was sheep -i <new ip> and the other option sheep -y <new<br>
> ip>. I tried both of these but when I do a collie cluster info then it<br>
> still shows the original corosync IP and not the new set IP. When<br>
> executing the command it does not return any errors so it looks like it<br>
> runs successfully but you can't see any changes taking place whatsoever.<br>
><br>
<br>
</div>-b is used to bind the NIC and -y is used to advertise the specified IP<br>
to other sheep.<br>
<div><br>
> The test machine has 4 nics - 1 for corosync comms, 1 for DRBD<br>
> replication comms, 1 x SAN comms and 1 for the management network. I am<br>
> using pacemaker on this same machine to provide a virtual IP which other<br>
> servers use to connect to and I would like to assign this virtual IP as<br>
> the bind address for sheepdog as well. That way if pacemaker and DRBD<br>
> fails over onto the 2nd node then my sheepdog cluster will still be<br>
> available and usable by my KVM hosts.<br>
><br>
<br>
</div>I don't see the point to use sheepdog with DRBD, sheepdog already<br>
provides high data availability by replication.<br>
<br>
Sheepdog has a gateway only-mode, which just route the VM requests as a<br>
gateway. With gateway-only sheep, you can separate the storage with<br>
computing like SAN.<br>
<div><br>
> Also where would the any sheepdog errors be logged? I checked in<br>
> /var/log/syslog but there is nothing there. I also checked in<br>
> /var/lib/sheepdog/sheep.log but there are no errors in there either.<br>
> Is there a way to enable debug logging so I can check exactly what<br>
> sheepdog is busy doing?<br>
<br>
</div>sheep -h for more information. '-d' to enable debug output and you can<br>
see logs from sheep.log.<br>
<br>
Thanks,<br>
Yuan<br>
<span><font color="#888888"><br>
--<br>
<br>
Privacy & Confidentiality Notice: This communication and the information it<br>
contains is intended for the person or organisation to whom it is<br>
addressed. Its contents are confidential and may be protected by law.<br>
Unauthorised use, copying or disclosure of any of it is unlawful. If you<br>
are not the intended recipient or received this message in error, please<br>
delete it immediately or contact us.<br>
The views and opinions expressed in this email are those of the author and<br>
may not reflect the views and opinions of the author's employer.<br>
<br>
*P** **Please don't print this e-mail unless you really need to*.<br>
</font></span></blockquote></div><br>
<br>
<font size="1"><span style="font-weight:bold"><br>Privacy & Confidentiality Notice: </span></font><font size="2"><font size="1">This communication and the information it contains is intended for the person or organisation to whom it is addressed. Its contents are confidential and may be protected by law. Unauthorised use, copying or disclosure of any of it is unlawful. If you are not the intended recipient or received this message in error, please delete it immediately or contact us.<br>The views and opinions expressed in this email are those of the author and may not reflect the views and opinions of the author's employer.<br></font><br></font><em><font color="#008000"><font face="Webdings"><font size="5"><i><b>P</b></i></font></font></font></em><em><strong><font color="#000080"><font face="Verdana"><font style="font-size:8pt" size="1"><i><b> </b></i></font></font></font></strong></em><font size="1"><em><strong><font color="#008000"><font face="Arial"><font style="font-size:7pt"><i><span style="font-weight:normal">Please
don't
print this e-mail unless you really need to</span></i></font></font></font></strong></em>.</font><br><span style="font-weight:bold"></span>