Adding a new phsical server to a AllinOne Opennebula config

Hi all,

I’ve parsed a lot of docs trying to figure out how to extend a one node Opennebula config (sunstone/worker on the same server) with another physical host.
So far adding the node let met see the CPU/MEM ressources correctly but I can’t find how to add the datastore
located on the new server.
The remote storage is LVM, if I add it (using LVM config) I see the Datastore but can’t get the storage capacity and so on.
Trying to create a VM on the new host just doesn’t work, same for testing migration.

Any clue/howto available ? As the docs only talk about separate front-end + several nodes.

Thanks a lot

Hi,

when you add LVM datastore you have to define BRIDGE_LIST, which is list of server or one server address where LVM can be managed.

So if you have new node with address 192.168.2.2, then you should add this IP to BRIDGE_LIST.
(I use dns names, so in my config is “node1 node2 node3” and frontend has this names with particular IP addresses in /etc/hosts)

Also, you need NFS server on host where opennebula engine is running
You need to mount this nfs storage to new node to /var/lib/opennebula
Configure no password ssh access

Hi and thanks for your answer.

Does this mean that from the AllinOne I share via NFS DS 0 an 1 and from the new added server I share my storage via NFS to the AllinOne server ?
And then I declare the storage as “shared” or just LVM ?

Thanks

Hi, no. You need to share system storage and whole opennebula dir via NFS, so you share these storage from allinone server to new node.

How to install NFS on frontend
How to install new compute node
Passwordless SSH

Where your LVM storage is located? On new compute node? If so then just add new LVM storage and don’t forget add BRIDGE_LIST param with address of that node.

In this case, “AllInOne” server connect via SSH to new compute node to manage LVM volumes and also to instantiate new VMs. New VMs also need system storage, so you need to mount NFS storage, which is exported from “AllInOne” server.

Hi, yes new storage is on the new node.
My ds file ise like this:

NAME= ael2-lab
DS_MAD = lvm
TM_MAD = lvm
VG_NAME = datastore1-lv_datastore1
HOST = ael2-lab
BRIDGE_LIST = ael-lab

But this doesn’t seem to work:

ID NAME SIZE AVAIL CLUSTER IMAGES TYPE DS TM STAT
0 system 5.5T 62% AEL-Labs1 0 sys - shared on
1 default 5.5T 62% AEL-Labs1 16 img fs shared on
2 files 5.5T 62% AEL-Labs1 0 fil fs ssh on
121 ael2-lab 0M - - 0 img lvm lvm on

no store size displayed

Nfs mount is ready on the new node
And the host is displaying correct infos (meme/CPU’s).

oneadmin can ssh from frontend to new server without password.

though onedanim can’t do lvscan command for example, sudo requires a password

Should the disk type changed to ssh ?

Here a log output I have on the frontend:

Thu Aug 27 15:40:58 2015 [Z0][ImM][I]: Command execution fail: /var/lib/one/remotes/datastore/lvm/monitor PERTX0RSSVZFUl9BQ1RJT05fREFUQT48REFUQVNUT1JFPjxJRD4xMjQ8L0lEPjxVSUQ+MDwvVUlEPjxHSUQ+MDwvR0lEPjxVTkFNRT5vbmVhZG1pbjwvVU5BTUU+PEdOQU1FPm9uZWFkbWluPC9HTkFNRT48TkFNRT5hZWwyLWxhYjwvTkFNRT48UEVSTUlTU0lPTlM+PE9XTkVSX1U+MTwvT1dORVJfVT48T1dORVJfTT4xPC9PV05FUl9NPjxPV05FUl9BPjA8L09XTkVSX0E+PEdST1VQX1U+MTwvR1JPVVBfVT48R1JPVVBfTT4wPC9HUk9VUF9NPjxHUk9VUF9BPjA8L0dST1VQX0E+PE9USEVSX1U+MDwvT1RIRVJfVT48T1RIRVJfTT4wPC9PVEhFUl9NPjxPVEhFUl9BPjA8L09USEVSX0E+PC9QRVJNSVNTSU9OUz48RFNfTUFEPjwhW0NEQVRBW2x2bV1dPjwvRFNfTUFEPjxUTV9NQUQ+PCFbQ0RBVEFbbHZtXV0+PC9UTV9NQUQ+PEJBU0VfUEFUSD48IVtDREFUQVsvdmFyL2xpYi9vbmUvL2RhdGFzdG9yZXMvMTI0XV0+PC9CQVNFX1BBVEg+PFRZUEU+MDwvVFlQRT48RElTS19UWVBFPjA8L0RJU0tfVFlQRT48U1RBVEU+MDwvU1RBVEU+PENMVVNURVJfSUQ+LTE8L0NMVVNURVJfSUQ+PENMVVNURVI+PC9DTFVTVEVSPjxUT1RBTF9NQj4wPC9UT1RBTF9NQj48RlJFRV9NQj4wPC9GUkVFX01CPjxVU0VEX01CPjA8L1VTRURfTUI+PElNQUdFUz48L0lNQUdFUz48VEVNUExBVEU+PEJBU0VfUEFUSD48IVtDREFUQVsvdmFyL2xpYi9vbmUvL2RhdGFzdG9yZXMvXV0+PC9CQVNFX1BBVEg+PEJSSURHRV9MSVNUPjwhW0NEQVRBW2FlbC1sYWJdXT48L0JSSURHRV9MSVNUPjxDTE9ORV9UQVJHRVQ+PCFbQ0RBVEFbU0VMRl1dPjwvQ0xPTkVfVEFSR0VUPjxEQVRBU1RPUkVfTE9DQVRJT04+PCFbQ0RBVEFbL0RTdG9yZV1dPjwvREFUQVNUT1JFX0xPQ0FUSU9OPjxESVNLX1RZUEU+PCFbQ0RBVEFbRklMRV1dPjwvRElTS19UWVBFPjxEU19NQUQ+PCFbQ0RBVEFbbHZtXV0+PC9EU19NQUQ+PEhPU1Q+PCFbQ0RBVEFbYWVsMi1sYWJdXT48L0hPU1Q+PExOX1RBUkdFVD48IVtDREFUQVtOT05FXV0+PC9MTl9UQVJHRVQ+PFRNX01BRD48IVtDREFUQVtsdm1dXT48L1RNX01BRD48VkdfTkFNRT48IVtDREFUQVtkYXRhc3RvcmUxXV0+PC9WR19OQU1FPjwvVEVNUExBVEU+PC9EQVRBU1RPUkU+PC9EU19EUklWRVJfQUNUSU9OX0RBVEE+ 124

Ok I got it “working” now I see the resources well:

root@AELHP:/var/lib/one# onedatastore list
ID NAME SIZE AVAIL CLUSTER IMAGES TYPE DS TM STAT
0 system 5.5T 62% AEL-Labs1 0 sys - shared on
1 default 5.5T 62% AEL-Labs1 16 img fs shared on
2 files 5.5T 62% AEL-Labs1 0 fil fs ssh on
130 ael2-lab 28.6T 0% AEL-Labs1 0 img lvm lvm on

Will open another thread for my new issue.

Thanks for your help

mmm in fact there still an issue…

DS is view as full … which is not :frowning: