Hi, I've worked on Centos and have no idea about Debian based installation, but I think you need to share /var/lib/one, because there are some other files/folders than images which are being used. for example, /var/lib/one/.one/ is the path to authentication files, which servers should see in a shared storage model to login without being asked for password.
Thanks Davood On Wed, Nov 30, 2011 at 10:48 AM, matheus tor4 <matheusi...@gmail.com>wrote: > Hello guys, > > I'm here again. > > I choosed to use .deb package instalation instead build source code. > > But, when I execute $ sudo dpkg -i opennebula_3.0.0-1_amd64.deb > I get this error message: > > Desempacotando opennebula (de opennebula_3.0.0-1_amd64.deb) ... > dpkg: erro processando opennebula_3.0.0-1_amd64.deb (--install): > erro estabelecendo posse de '/var/lib/one/remotes.dpkg-new': Opera��o n�o > permitida > Processando gatilhos para ureadahead ... > Processando gatilhos para man-db ... > Erros foram encontrados durante o processamento de: > opennebula_3.0.0-1_amd64.deb > > (Sorry, it is in brazilian portuguese) > > Summarizing we got a error like: > > dpkg: error processing opennebula_3.0.0-1_amd64.deb (- install): > error setting ownership of '/ var / lib / one / remotes.dpkg-new': > Operation not allowed > > I'm not so sure, but I believe that occurs because the shared file system. > As all the files have a different owner, the front-end cannot write > anything in this directory. > > So, the question is: > > Have I wich to share only the directory /var/lib/one/images, or the whole > /var/lib/one? > Does exist a file to put permissions of the shared directory? > > Very thanks guys. > > Best regards > > On Tue, Nov 29, 2011 at 8:59 AM, matheus tor4 <matheusi...@gmail.com>wrote: > >> Hello everybody. >> >> Very thanks for the help until now. >> >> I'm using this thread to put all my doubts ok? >> So, if anyone wish follow me in this adventure "Building my first cloud", >> only have to look this tread to see my status at the moment. >> >> My doubt now is: >> >> Wich is better? >> - Use .deb to install the openNebula in the hosts and in the front-end. >> Remember I'm using a Ubuntu Desktop 10.04 (32bits) as Front End and using >> Ubuntu Server 11.04 (64 bits) as Hosts. >> - Building and compile source, because is more safer, and it is more >> close to procedure shown on OpenNebula official documentation. >> >> Thanks >> >> Regards, >> >> Matheus Torquato >> >> >> >> >> On Sun, Nov 27, 2011 at 4:56 PM, Fabian Wenk <fab...@wenks.ch> wrote: >> >>> Hello Matheus >>> >>> >>> On 27.11.2011 17:49, matheus tor4 wrote: >>> >>>> At the time I'm using the second strategy: Using a Core2Duo as a >>>> Front-End >>>> and release all >>>> resources of the server to be use by cloud. >>>> I choose this option because it is more close to the proposal of >>>> official >>>> OpenNebula Documentation. >>>> I hope it works now! >>>> >>>> So I use one of my servers (With VT) as a Image Repository too. >>>> >>> >>> This is up to you, but I would keep the image repository on the front >>> end or eventually on the second system without VT. So you could use the two >>> systems with VT as two identical cluster nodes. >>> >>> >>> And now I have a little more question: >>>> >>>> With a NFS server configured. I have the Image Repository sharing its >>>> directory /var/lib/one. My doubt is: >>>> - Have I to insert the shared directory in the file /etc/fstab on all my >>>> nodes? So the node already have this directory avaiable when the machine >>>> starts. >>>> >>> >>> Yes, and also on the front end. >>> >>> >>> - Or Haven't I to do this? Does the directory only be mount when it is >>>> necessary? (sudo mount ...) >>>> >>> >>> It needs to be already mounted when OpenNebula will deploy a VM. >>> >>> >>> And, if I edit the /etc/fstab, Do I have to do this in the node >>>> ImageRepository+Cluster at the same time? I hope not, because the >>>> directory >>>> is on the machine >>>> >>> >>> I am not sure about OpenNebula 3.0, but with 2.2 the image repository >>> and also the VM_DIR folder need to be mounted in the same path as they are >>> on the front end. >>> >>> >>> >>> bye >>> Fabian >>> ______________________________**_________________ >>> Users mailing list >>> Users@lists.opennebula.org >>> http://lists.opennebula.org/**listinfo.cgi/users-opennebula.**org<http://lists.opennebula.org/listinfo.cgi/users-opennebula.org> >>> >> >> > > _______________________________________________ > Users mailing list > Users@lists.opennebula.org > http://lists.opennebula.org/listinfo.cgi/users-opennebula.org > >
_______________________________________________ Users mailing list Users@lists.opennebula.org http://lists.opennebula.org/listinfo.cgi/users-opennebula.org