[Sheepdog] Configuring Sheepdog environment

Gustavo Callou grac at cin.ufpe.br
Mon Jun 20 21:37:51 CEST 2011


Dear Sheepdog developers,


 First of all, we would like to thank you for the support.

We have tried to install the sheepdog version that you provided for us.
However, we were not successful with the installation due to the fact that
we could not obtain the result of the command collie node list (e.g.,
something like connection failure). Thus, we adopted the sheepdog version
available at https://github.com/collie/sheepdog(collie-sheepdog-v0.2.3-11-g3410623.tar.gz).
Considering this version, we
were successful to see all machines in the cluster (adopting the command
collie node list). However, the command collie cluster format –copies=2
seems to be not working as it is supposed to (e.g., Invalid error code) .
Besides that, we tried the command collie node info , and the result was:

Id Size Used Use%

cannot get information from any nodes


 Another command “collie cluster info ” seems also to be not working very
well (we could not see the creation time and epoch nodes)

Cluster status: running

 Creation time Epoch Nodes



 In addition, although the command “qemu-img create sheepdog:Callou 4G”
seemed to work, once it has executed the node is out of the cluster. Besides
that, we executed the command “collie vdi list” , and we got:


 name id size used shared creation time vdi id

------------------------------------------------------------------
failed to read a inode header 15507205, 0, 81



 Thus, we are not sure if the vm image was created. In order to put the node
again into the cluster, we had to restart the corosync and sheepdog as well
as to delete an create again the sheepdog storage dir.

Then, we executed the command “collie vdi list” and got:


 name id size used shared creation time vdi id

------------------------------------------------------------------

Floating point exception


 We expect that those information provided above may be useful to find out
what is the problem that might be happening in my sheepdog environment. Do
you have any suggestion?


 Best regards,

Gustavo Callou / Rubens Matos




On Mon, Jun 20, 2011 at 9:36 AM, MORITA Kazutaka <
morita.kazutaka at lab.ntt.co.jp> wrote:

> At Mon, 20 Jun 2011 00:12:59 -0300,
> Gustavo Callou wrote:
> > Dear Sheepdog developers,
> >
> > I’m a Brazilian PhD student from Federal University of Pernambuco and I'm
> > trying to configure the Sheepdog in order to test its features. I have 4
> PCs
> > available to do such test, in which Ubuntu 10.04 64bits version are
> > installed. I'm adopting the Sheepdog package
> > “sheepdog_0.2.2-0ubuntu1_amd64.deb“, downloaded at Ubuntu repositories.
> > However, I’m not sure about the configuration due to the fact that once I
> > have installed the environment, machines sometimes are able to see each
> > other and sometimes not. What I mean is when I execute the command “sudo
> > collie node list”, there are machines that see that there is only one
> node
> > in the cluster (i.e., the host sees itself), others can see 2 nodes, and
> > other sometimes see 3 nodes. Another interesting fact is that, when I
> have
> > restarted the corosync and the sheepdog in all machines, such seen
> > configuration changes.
> >
> > In a nutshell, I have attached in this message the logs from 3 machines
> > (e.g., named sheep1, sheep2, sheep3). Besides, I attached the
> corosync.conf
> > in which I have tried to configure the bindnetaddr with an ip like this
> > 172.20.10.0 as well as adopting the machine ip such as 172.20.10.116.
> >
> > Please, let me know as soon as possible if there is something that is not
> > correctly configurated at the corosync.conf or any other issues that you
> may
> > detect through the nodes logs.
>
> Your corosync.conf looks correct.
>
> From sheep[1-3].log, your Sheepdog directories contains wrong
> information about node membership histories.  I'm not sure why it
> happened, but it would work for you to clean the store directories and
> run 'collie cluster format' again.
>
> I highly recommend to upgrade Sheepdog to version 0.2.3 or use the
> latest development code:
>  https://github.com/collie/sheepdog
>
> It includes many important bug fixes.
>
> Thanks,
>
> Kazutaka
>



-- 
Phd Candidate in Computer Science
Federal University of Pernambuco
http://www.modcs.org
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.wpkg.org/pipermail/sheepdog/attachments/20110620/9779d303/attachment-0003.html>


More information about the sheepdog mailing list