[Engine-devel] Empty cdrom drive.
by Igor Lvovsky
Hi,
I want to discuss $subject on the email just to be sure that we all on the
same page.
So, today in 3.0 vdsm has two ways to create VM with cdrom :
1. If RHEV-M ask to create VM with cdrom, vdsm just create it
2. RHEV-M doesn't ask to create VM with cdrom, vdsm still creates VM with
empty cdrom. Vdsm creates this device as 'hdc' (IDE device, index 2),
because of libvirt restrictions.
In this case RHEV-M will be able to "insert" cdrom on the fly with
changeCD request.
In the new style API we want to get rid from stupid scenario #2, because
we want to be able to create VM without cdrom at all.
It means, that now we need to change a little our scenarios:
1. If RHEV-M ask to create VM with cdrom, vdsm just create it
2. RHEV-M doesn't want to create VM with cdrom, but it want to be able to
"insert" cdrom on the fly after this. Here we have two options:
a. RHEV-M should to pass empty cdrom device on VM creation and use
regular changeCD after that
b. RHEV-M can create VM without cdrom and add cdrom later through
hotplugDisk command.
Note: The new libvirt remove previous restriction on cdrom devices. Now
cdrom can be created as IDE or VIRTIO device in any index.
It means we can easily hotplug it.
Regards,
Igor Lvovsky
12 years, 10 months
[Engine-devel] attempting to deploy ovirt-engine built from source
by Ryan Harper
Hi,
I've been attempting to build and deploy ovirt-engine from source; i've
been following the guide[1] and I'm still having a bit of trouble;
hoping for some help here.
I've got a F16 64-bit server. I'm using the jboss that's available via
the f16 repos:
ovirt-engine-jbossas-1.2-2.fc16.x86_64
which is jboss 7.1 based. I've updated my .m2/settings.xml to match the
install path of the above RPM:
[build@f16-node ear]$ cat ~/.m2/settings.xml
<settings xmlns="http://maven.apache.org/POM/4.0.0"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:schemaLocation="http://maven.apache.org/POM/4.0.0
http://maven.apache.org/xsd/settings-1.0.0.xsd">
<!--**************************** PROFILES ****************************-->
<activeProfiles>
<activeProfile>oVirtEnvSettings</activeProfile>
</activeProfiles>
<profiles>
<profile>
<id>oVirtEnvSettings</id>
<properties>
<jbossHome>/usr/share/jboss-as-7.1.0.Beta1b</jbossHome>
<JAVA_1_6_HOME>/usr/lib/jvm/java-1.6.0-openjdk.x86_64</JAVA_1_6_HOME>
<forkTests>always</forkTests>
</properties>
</profile>
</profiles>
</settings>
engine and the gui build fine with the commands from the wiki. When I attempt
to test the connection and webgui they fail. so I looked out in the
deployment directory and I see the following:
[root@f16-node deployments]# pwd
/usr/share/jboss-as-7.1.0.Beta1b/standalone/deployments
[root@f16-node deployments]# ls -al
total 28
drwxrwxr-x. 3 jboss-as jboss-as 4096 Feb 17 12:28 .
drwxrwxr-x. 8 jboss-as jboss-as 4096 Feb 3 11:19 ..
-rw-rw-r--. 1 jboss-as jboss-as 8868 Dec 1 16:10 README.txt
drwxrwxr-x 15 build build 4096 Feb 17 12:21 engine.ear
-rw-rw-r-- 1 jboss-as jboss-as 2353 Feb 17 12:21 engine.ear.failed
I'm attaching the engine.ear.failed.
1. http://ovirt.org/wiki/Building_oVirt_engine
--
Ryan Harper
Software Engineer; Linux Technology Center
IBM Corp., Austin, Tx
ryanh(a)us.ibm.com
12 years, 10 months
[Engine-devel] New oVirt GIT Repo Request
by Keith Robertson
All,
I would like to move some of the oVirt tools into their own GIT repos so
that they are easier to manage/maintain. In particular, I would like to
move the ovirt-log-collector, ovirt-iso-uploader, and
ovirt-image-uploader each into their own GIT repos.
The Plan:
Step 1: Create naked GIT repos on oVirt.org for the 3 tools.
Step 2: Link git repos to gerrit.
Step 3: Populate naked GIT repos with source and build standalone spec
files for each.
Step 4: In one patch do both a) and b)...
a) Update oVirt manager GIT repo by removing tool source.
b) Update oVirt manager GIT repo such that spec has dependencies on 3
new RPMs.
Optional:
- These three tools share some python classes that are very similar. I
would like to create a GIT repo (perhaps ovirt-tools-common) to contain
these classes so that a fix in one place will fix the issue everywhere.
Perhaps we can also create a naked GIT repo for these common classes
while addressing the primary concerns above.
Please comment,
Keith Robertson
12 years, 10 months
[Engine-devel] bridgeless networks - update
by Roy Golan
following ovirt engine weekly here's a summary of the changes:
1. no validation during vmInterface creation
2. when attaching a network the default value is bridged (GUI responsibility)
3. monitoring - detect mixed configured cluster (network "foo" is bridged on one host and not on another)
and issue an audit log warning with event interval of 1 day
wiki will be updated accordingly.
Thanks,
Roy
12 years, 10 months
[Engine-devel] Unit test failures and RunVmCommand
by Jon Choate
I was trying to fix the broken unit tests so that I can make sure my
changes are not breaking anything. While trying to fix the RunVmCommand
tests I found some logic that I am unsure of.
It seems like with all of the nested conditions in this method the scope
of some of the checks is wrong.
In RunVmCommand.CanRunVm we check the boot sequence. If the vm is set to
only boot from a hard disk, we check to make sure that the vm has a hard
disk and that it is plugged. If both of these are true, we do not
perform any other checks and return that the vm can start.
One of the checks that gets skipped is whether or not the vm is already
running. Do we really want to skip that check?
12 years, 10 months
[Engine-devel] Change jboss listening ip/port configuration
by Ryan Harper
Hi,
I've followed the building engine from source wiki[1] and I've got it
all running (thanks!) but to test things out, I wanted to exercise the
gui and other parts via the web portal. By default, jboss is listening
only to localhost:8080, and I was wondering the right way to change that
to something else?
I see localhost and ports buried down in
./backend/manager/conf/standalone.xml
but not clear if I should be mucking with those and re-deploying or
what.
Thanks for the help,
--
Ryan Harper
Software Engineer; Linux Technology Center
IBM Corp., Austin, Tx
ryanh(a)us.ibm.com
12 years, 10 months
