ovirt-shell or ovirt-cli usage ..

It is quite some time I am receiving queries on ovirt-shell/ cli usage. Even-though I didn’t store those questions with me, I thought I will point something on this topic. Soon I will come up with more notes on this topic. Upto that, this is a place holder draft. But, dont get disappointed, you have …

Read more

Managing gluster from ovirt !

In past weeks, I received some queries on gluster and ovirt integration .. People are seriously looking for its integration or details on , whats there now and where its moving.. I informed them about the work being done on this area, how-ever before I get more queries on this , I thought, I will …

Read more

Understand Quota in Ovirt ( /RHEV ) 3.1

Day by day, Ovirt is embedded with new features which make Ovirt an awesome piece of software … Ovirt 3.1 has added  a new feature called ‘QUOTA’, quota new feature which enhance Ovirt/ RHEV project with its 3.1 version. It is really handy when you have to define acls for your setup.  Better usage of …

Read more

Ovirt Videos ( ovirt architecture, gui , hypervisor/node) ..etc

Hey my friends, Videos are always better place to learn about a technology 🙂  ..  You can watch “ovirt” videos from below urls.. I am sure it will help you to achieve good understanding on ovirt-{engine, node, architecture..etc} 1) OVIRT ARCHITECTURE ( Overview ) ovirt introduction   virtualization in an ovirt way   2) OVIRT …

Read more

Persist a file in an Ovirt node

As you know ‘ovirt-node‘ is almost a live CD image.. How-ever there are some files which are persisted by default in ovirt node..

 

If you would like to make a file persisted/stable in ovirt node ( Live CD image hypervisor)  execute below command in the hypervisor.

Ex:

#persist <filename>

 

 

 

 

 

Difference between “Non Responsive” && “Non Operational” hypervisor status in ovirt GUI

I think this tip will help you to understand the difference between these statuses..

  *      Non-operational:
It means there is something wrong with the configuration of the hypervisor.  The ovirt-engine can still communicate with the hypervisor though.

It can be a failure in the connectivity of hypervisor to any of the cluster’s ( ex: logical network, storage domain..etc ) components.  So check hypervisor is capable of working with all the components defined for a cluster.

*      Non-responsive:

means that the Ovirt Engine cannot communicate with the hypervisor via vdsm.

Luns are not visible in ovirt GUI when creating storage domain?

There could be different reasons which caused this behaviour.. How-ever make sure that you did cross-chek below requirements before assigning or when creating storage domain.
1. The LUN should be raw (no filesystem,no LVM, no data)
2. The LUN should be larger than 10Gb in size
3. The LUN should be r/w accessible from the SPM host.

 

Once you passed above checks, the Lun should be visible in the GUI. Also, if you have used that lun  previously for storage domain creation, you will be mostly into “Point 1” in above requirement.