[one-users] strange issue installing OpenNebula 3.2

Ruben Diez rdiez at cesga.es
Tue Jan 17 08:02:35 PST 2012


Hi:

We compiled the new OpenNebula 3.2 with "scons sqlite=no mysql=yes"

Then we install one into the oneadmin user home directory, in this way:

oneadmin at onesrv04:~/opennebula-3.2.0$ whoami
oneadmin
oneadmin at onesrv04:~/opennebula-3.2.0$ echo $HOME
/srv/cloud/one
oneadmin at onesrv04:~/opennebula-3.2.0$ pwd
/srv/cloud/one/opennebula-3.2.0
oneadmin at onesrv04:~/opennebula-3.2.0$ env |grep ONE
ONE_AUTH=/srv/cloud/one/.one/one_auth
ONE_XMLRPC=http://localhost:2633/RPC2
ONE_LOCATION=/srv/cloud/one
oneadmin at onesrv04:~/opennebula-3.2.0$ ./install.sh -u oneadmin -g cloud 
-d /srv/cloud/one/ -c -s -o


But: in the installed OpenNebula stuff seems to be some file lost...

oneadmin at onesrv04:~$ pwd  
/srv/cloud/one
oneadmin at onesrv04:~$ ls
bin  etc  lib  opennebula-3.2.0
oneadmin at onesrv04:~$ ls etc
cli  group.default
oneadmin at onesrv04:~$ ls lib
ruby
oneadmin at onesrv04:~$ ls bin
econe-describe-images      econe-register       
econe-terminate-instances  occi-compute    occi-storage  onegroup    
oneimage     oneuser  onevm    onezone
econe-describe-instances  econe-run-instances  econe-upload          
occi-network    oneacl          onehost    onetemplate  onevdc   onevnet


Is this normal??
What about the etc/oned.conf and related conf files under etc??
What about tm_commands and mads???
What about the var directory??

Are they created after very first "one start" execution??

We prefer waiting for a clean installation from scratch before make the 
database migration....

Regards.




More information about the Users mailing list