oVirt project proposal: MOM
by agl＠us.ibm.com
Hi all,
http://www.ovirt.org/wiki/Project_Proposal_-_MOM
The link above will take you to the oVirt draft proposal for including Memory
Overcommitment Manager (MOM) as an oVirt sub-project. I wanted to give folks on
this list a chance to discuss MOM and an integration strategy before I ask the
oVirt board to evaluate the proposal. Please take a look if you can and provide
your feedback. Thanks.
--
Adam Litke <agl(a)us.ibm.com>
IBM Linux Technology Center
12 years, 5 months
Installing standalone VDSM
by Itzik Brown
Hi,
I want to use VDSM without RHEV.
I did the following:
I installed VDSM on RHEL6.2Beta using yum and .
Changed ssl = false in /etc/vdsm/vdsm.conf (after copied it from /usr/share/doc/vdsm-4.9/vdsm.conf.sample).
Added spice_tls=0 in /etc/libvirt/qemu.conf.
Then restarted vdsmd.
I ran the following script named start.py:
#!/usr/bin/python
import sys
import uuid
import time
sys.path.append('/usr/share/vdsm')
import vdscli
from storage.sd import LOCALFS_DOMAIN, DATA_DOMAIN
from storage.volume import COW_FORMAT, SPARSE_VOL, LEAF_VOL, BLANK_UUID
spUUID = str(uuid.uuid4())
sdUUID = str(uuid.uuid4())
imgUUID = str(uuid.uuid4())
volUUID = str(uuid.uuid4())
path = "/tmp/localstoragedomain"
# chown vdsm:kvm /tmp/localstoragedomain
s = vdscli.connect()
masterVersion = 1
hostID = 1
def vdsOK(d):
print d
if d['status']['code']:
raise Exception(str(d))
return d
def waitTask(s, taskid):
while vdsOK(s.getTaskStatus(taskid))['taskStatus']['taskState'] != 'finished':
time.sleep(3)
vdsOK(s.clearTask(taskid))
vdsOK(s.connectStorageServer(LOCALFS_DOMAIN, "my favorite pet", [dict(id=1, connection=path)]))
vdsOK(s.createStorageDomain(LOCALFS_DOMAIN, sdUUID, "my local domain", path, DATA_DOMAIN, 0))
vdsOK(s.createStoragePool(LOCALFS_DOMAIN, spUUID, "pool name", sdUUID, [sdUUID], masterVersion))
# connect to an existing pool, and become pool manager.
vdsOK(s.connectStoragePool(spUUID, hostID, "scsikey", sdUUID, masterVersion))
tid = vdsOK(s.spmStart(spUUID, -1, -1, -1, 0))['uuid']
waitTask(s, tid)
sizeGiB = 100
tid = vdsOK(s.createVolume(sdUUID, spUUID, imgUUID, sizeGiB,
COW_FORMAT, SPARSE_VOL, LEAF_VOL,
volUUID, "volly",
BLANK_UUID, BLANK_UUID))['uuid']
waitTask(s, tid)
vmId = str(uuid.uuid4())
vdsOK(
s.create(dict(vmId=vmId,
drives=[dict(poolID=spUUID, domainID=sdUUID, imageID=imgUUID, volumeID=volUUID)],
memSize=256,
display="vnc",
vmName="vm1",
)
)
)
When running it I get the following error:
{'status': {'message': 'OK', 'code': 0}, 'statuslist': [{'status': 451, 'id': 1}]}
{'status': {'message': "Permission settings on the specified path do not allow access to the storage. Verify permission settings on the specified storage path.: 'path = /rhev/data-center/mnt/_tmp_localstoragedomain'", 'code': 469}}
Traceback (most recent call last):
File "/tmp/start.py", line 39, in <module>
vdsOK(s.createStorageDomain(LOCALFS_DOMAIN, sdUUID, "my local domain", path, DATA_DOMAIN, 0))
File "/tmp/start.py", line 29, in vdsOK
raise Exception(str(d))
Exception: {'status': {'message': "Permission settings on the specified path do not allow access to the storage. Verify permission settings on the specified storage path.: 'path = /rhev/data-center/mnt/_tmp_localstoragedomain'", 'code': 469}}
Can someone look at it?
Thanks,
Itzik
12 years, 6 months
VDSM on Fedora
by Itzik Brown
Hi,
I installed Fedora 16 Beta and installed VDSM from yum.
I checked it's status and it's running.
Is there a Howto or a Document with instructions for basic usage so I can start to work with it?
Thanks,
Itzik
12 years, 6 months
hello my friend help me
by Lssah Alim
FORM; AL-ISSAH SALIM
alssahs(a)yahoo.com
God bless you
I am Mr. Al-Issah Salim from Misrata, Libya. I lost my father who was a serving military chief under Col Muammar Gaddafi collapsed regime.
I am presently on exile in UAE and need urgent assistance to present foreign beneficiary to enable me take possession of my family Gold.
All I want is a reliable partner that can come in as my business partner and receive the seven (7) trunk boxes containing Cash, Gold so that we share 50/50. I have all the proofing documents and will be sending it to you upon receipt of your full consent.
May God bless us all as I wait your prompt response confirming your readiness to help me achieve this business for real and good of us all.
Yours truly,
Al-Issah Salim
E-mail;alssahs(a)yahoo.com
12 years, 6 months
Installing vdsm standalone on RHEL6.2
by Itzik Brown
Hi,
I'm trying to install vdsm on RHEL6.2(Beta).
Steps I have done:
git clone git://git.fedorahosted.org/vdsm.git
cd vdsm
./autobuild.sh
Then going to my rpmbuild directory and running rpm -ivh vdsm vdsm-4.9.0-0.189.gb60414c.el6.itzikb1318984224.x86_64.rpm I get the following:
error: Failed dependencies:
fence-agents is needed by vdsm-4.9.0-0.189.gb60414c.el6.itzikb1318984224.x86_64
libvirt >= 0.9.4-13 is needed by vdsm-4.9.0-0.189.gb60414c.el6.itzikb1318984224.x86_64
libvirt-python >= 0.9.4-13 is needed by vdsm-4.9.0-0.189.gb60414c.el6.itzikb1318984224.x86_64
The RHEL6.2 I have doesn't have fence-agents. libvirt /libvirt-python versions are 0.9.4-12.
Tried epel but they don't seem to have libvirt or fence-agents.
I have tried the configure && make && make install approach but had other errors if this the preferred way to install - I'll post the errors.
I'll appreciate any suggestion/guidance.
Itzik
Itzik Brown | 972-74-7129203(o) | 972-54-4685940(m)
Linux System Administrator
Mellanox
www.mellanox.com<http://www.mellanox.com>
12 years, 6 months
Proposal to add message IDs to vdsm.log
by kroberts＠redhat.com
Hi,
I would like to propose enhancing the VDSM source to emit message IDs in
log messages with levels greater than DEBUG (i.e. INFO, ERROR, WARN,
EXCEPTION, and CRITICAL). Messages IDs have been used successfully in
many products and they can aid in debugging, documentation, root cause
analysis, and internationalization.
I have scanned the source and have determined that there are roughly 525
calls to log.[error|warn|info|critical|exception] and I am volunteering
to go through and add IDs to them all but, before I do I want to get
buy-in from the project maintainers. While adding IDs to the messages I
would also enable them for i18n.
I have written a rough plan for adding messages IDs to VDSM below and
I've provided some examples of products/projects that use message IDs.
Examples of Projects that Use Message IDs:
- JBoss 7 is adopting Message IDs for all of its logging. See the
annotations (e.g. @Message(id = 12000, ) in the following piece of source:
https://github.com/jbossas/jboss-as/blob/master/process-controller/src/ma...
- Almost all IBM products use message IDs and they do a fairly good job
of documenting them. Google has indexed them all and you can simply type
them in to a search and get a description of the problem that is
associated with the ID.
http://publib.boulder.ibm.com/infocenter/tivihelp/v42r1/topic/com.ibm.ome...
Example of a Log Statement with a Message ID in Python:
FORMAT = '%(asctime)s %(lineno)s %(levelname)s(%(messageid)s): %(message)s'
logging.basicConfig(format=FORMAT)
logger = logging.getLogger()
logger.warning('NFS problem. Unable to mount.', extra={ 'messageid' :
'VDSM1000'})
// Produces
2011-10-05 13:24:43,180 11 WARNING(VDSM1000): NFS problem. Unable to mount.
Example of a Log Statement with a Message ID in Python with i18n:
logger.warning(_('NFS problem. Unable to mount.'), extra={ 'messageid' :
'VDSM1000'})
Example of an i18n Log Message:
Chinese: 2011年10月5日13:24:43,18011警告（VDSM1000）：NFS问题。无法安装。
English: 2011-10-05 13:24:43,180 11 WARNING(VDSM1000): NFS problem.
Unable to mount.
A Rough Plan for adding Message IDs to VDSM:
Step 0: Decide on a logging format of the ID itself:
- JBoss is using "JBAS#####". I am thinking that VDSM could probably do
something similar "VDSM####".
Step 1: Decide where to list and document all of the IDs.
- It could be as simple as a page on VDSM's fedorahosted wiki.
Step 2: Pin the format of the log messages:
- Currently VDSM allows a user configurable Python log format. We would
need to pin the format so that it includes a substitution variable for
the message ID.
Example: '%(asctime)s %(lineno)s %(levelname)s(%(messageid)s): %(message)s'
Step 4: Plow through the VDSM source and add message IDs.
Cheers,
Keith
12 years, 6 months
