[PATCH] fix spec file for sblim-sfcb and systemctl
by Daniel Veillard
Right now the spec file is completely tied to tog-pegasus,
this should allow the spec file to be compatible with sblim-sfcb
too. This also switches to systemctl which is now used in Fedora.
I would actually like some feedback on the patch if someone
has an environment to test with sblim-sfcb
Also I noted that if I built the package with sblim-sfcb installed
it failed in the make install phase with the following error:
----------------------------------------------------------
/bin/sh /u/veillard/rpms/BUILD/libvirt-cim-0.6.1/install-sh -c -m 644 -t
"/u/veillard/rpms/BUILDROOT/libvirt-cim-0.6.1-2.fc18.x86_64/usr/share/libvirt-cim"
./schema/RegisteredProfile.registration
./schema/ElementConformsToProfile.registration
./schema/ReferencedProfile.registration
if [[ sfcb != pegasus ]]; then \
sed -i '/^# --/,/^# --!/d'
.//u/veillard/rpms/BUILDROOT/libvirt-cim-0.6.1-2.fc18.x86_64/usr/share/libvirt-cim/RegisteredProfile.registration
.//u/veillard/rpms/BUILDROOT/libvirt-cim-0.6.1-2.fc18.x86_64/usr/share/libvirt-cim/ElementConformsToProfile.registration
.//u/veillard/rpms/BUILDROOT/libvirt-cim-0.6.1-2.fc18.x86_64/usr/share/libvirt-cim/ReferencedProfile.registration;
\
fi
sed: can't read
.//u/veillard/rpms/BUILDROOT/libvirt-cim-0.6.1-2.fc18.x86_64/usr/share/libvirt-cim/RegisteredProfile.registration:
No such file or directory
sed: can't read
.//u/veillard/rpms/BUILDROOT/libvirt-cim-0.6.1-2.fc18.x86_64/usr/share/libvirt-cim/ElementConformsToProfile.registration:
No such file or directory
sed: can't read
.//u/veillard/rpms/BUILDROOT/libvirt-cim-0.6.1-2.fc18.x86_64/usr/share/libvirt-cim/ReferencedProfile.registration:
No such file or directory
make[2]: *** [install-data-local] Error 2
make[2]: Leaving directory `/home/veillard/rpms/BUILD/libvirt-cim-0.6.1'
make[1]: *** [install-am] Error 2
make[1]: Leaving directory `/home/veillard/rpms/BUILD/libvirt-cim-0.6.1'
make: *** [install-recursive] Error 1
----------------------------------------------------------
Any idea ?
thanks,
Daniel
--- libvirt-cim.spec 2012-02-10 13:49:31.679905149 +0800
+++ libvirt-cim.spec 2012-03-09 14:41:45.617781910 +0800
@@ -12,7 +12,8 @@
Requires: libxml2 >= 2.6.0
Requires: libvirt >= 0.9.0
Requires: unzip
-Requires: tog-pegasus
+# either tog-pegasus or sblim-sfcb should provide cim-server
+Requires: cim-server
BuildRequires: libcmpiutil >= 0.5.4
BuildRequires: tog-pegasus-devel
BuildRequires: libvirt-devel >= 0.9.0
@@ -85,8 +86,18 @@
%{_datadir}/%{name}/install_base_schema.sh %{_datadir}/%{name}
-/etc/init.d/tog-pegasus condrestart
+if [ "`systemctl is-active tog-pegasus.service`" = "active" ]
+then
+ systemctl restart tog-pegasus.service
+fi
+
+if [ "`systemctl is-active sblim-sfcb.service`" = "active" ]
+then
+ systemctl restart sblim-sfcb.service
+fi
+if [ -x /usr/sbin/cimserver ]
+then
%{_datadir}/%{name}/provider-register.sh -t pegasus \
-n root/virt \
-r %{REGISTRATION} -m %{SCHEMA} >/dev/null 2>&1 || true
@@ -102,8 +113,29 @@
%{_datadir}/%{name}/provider-register.sh -t pegasus \
-n root/cimv2\
-r %{CIMV2_REG} -m %{CIMV2_MOF} -v >/dev/null 2>&1 || true
+fi
+if [ -x /usr/sbin/sfcbd ]
+then
+%{_datadir}/%{name}/provider-register.sh -t sfcb \
+ -n root/virt \
+ -r %{REGISTRATION} -m %{SCHEMA} >/dev/null 2>&1 || true
+%{_datadir}/%{name}/provider-register.sh -t sfcb \
+ -n root/virt \
+ -r %{REGISTRATION} -m %{SCHEMA} >/dev/null 2>&1 || true
+%{_datadir}/%{name}/provider-register.sh -t sfcb \
+ -n root/interop \
+ -r %{INTEROP_REG} -m %{INTEROP_MOF} -v >/dev/null 2>&1 || true
+%{_datadir}/%{name}/provider-register.sh -t sfcb \
+ -n root/PG_InterOp \
+ -r %{PGINTEROP_REG} -m %{PGINTEROP_MOF} -v >/dev/null 2>&1 || true
+%{_datadir}/%{name}/provider-register.sh -t sfcb \
+ -n root/cimv2\
+ -r %{CIMV2_REG} -m %{CIMV2_MOF} -v >/dev/null 2>&1 || true
+fi
%preun
+if [ -x /usr/sbin/cimserver ]
+then
%{_datadir}/%{name}/provider-register.sh -d -t pegasus \
-n root/virt \
-r %{REGISTRATION} -m %{SCHEMA} >/dev/null 2>&1 || true
@@ -116,6 +148,22 @@
%{_datadir}/%{name}/provider-register.sh -d -t pegasus \
-n root/cimv2 \
-r %{CIMV2_REG} -m %{CIMV2_MOF} >/dev/null 2>&1 || true
+fi
+if [ -x /usr/sbin/sfcbd ]
+then
+%{_datadir}/%{name}/provider-register.sh -d -t sfcb \
+ -n root/virt \
+ -r %{REGISTRATION} -m %{SCHEMA} >/dev/null 2>&1 || true
+%{_datadir}/%{name}/provider-register.sh -d -t sfcb \
+ -n root/interop \
+ -r %{INTEROP_REG} -m %{INTEROP_MOF} >/dev/null 2>&1 || true
+%{_datadir}/%{name}/provider-register.sh -d -t sfcb \
+ -n root/PG_InterOp \
+ -r %{PGINTEROP_REG} -m %{PGINTEROP_MOF} >/dev/null 2>&1 || true
+%{_datadir}/%{name}/provider-register.sh -d -t sfcb \
+ -n root/cimv2 \
+ -r %{CIMV2_REG} -m %{CIMV2_MOF} >/dev/null 2>&1 || true
+fi
%postun -p /sbin/ldconfig
--
Daniel Veillard | libxml Gnome XML XSLT toolkit http://xmlsoft.org/
daniel(a)veillard.com | Rpmfind RPM search engine http://rpmfind.net/
http://veillard.com/ | virtualization library http://libvirt.org/
12 years, 5 months
[PATCHv2 0/3] Make Shutdown and Reboot state changes jobs
by Eduardo Lima (Etrunko)
From: "Eduardo Lima (Etrunko)" <eblima(a)br.ibm.com>
This code is based on the VSMigrationService for the job creation and on
ComputerSystemIndication for the job thread, which will listen for the
respective domain event to mark the job as finished.
I am still not able to test this feature in my environment, every call to
CBGetInstance fails with code error 100. This is happening in other places of
the codebase, not only the ComputerSystem provider, but also ElementConfors,
for instance. Please use the test case send in previous email for reference.
Differences from v1:
- Fix conditional causing Reqstate not being set
- Fix domain event id for shutdown
- Now instead of using the domain events for both shutdown and reboot, there is
an intermediate patch, that will deal with the shutdown case by polling for
the domain state until it reflects the desired state.
This workaround won't work for the reboot case, because is is not possible to
monitor the reboot event if not using the domain event callbacks. The third
patch of the series contains the complete solution for both cases.
Eduardo Lima (Etrunko) (3):
VSMigrationService: Move job state definitions to svpc_types.h
ComputerSystem: Make Shutdown state change a job
ComputerSystem: Reboot state change also a job
schema/ComputerSystem.mof | 9 ++
src/Virt_ComputerSystem.c | 304 +++++++++++++++++++++++++++++++++++++++--
src/Virt_VSMigrationService.c | 14 +--
src/svpc_types.h | 13 ++
4 files changed, 321 insertions(+), 19 deletions(-)
--
1.7.7.6
12 years, 5 months
regarding creating VM using libvirt-cim
by Raghunatha Reddy P (raghunp)
Hi All,
I am very new to libvirt-cim. We wanted to create a VM using
libvirt-cim using CIM schemas. Could you please detail the steps
involved in this task, procedures, softwares to be installed and run,
docs, wikipages, blogs..etc.
Thanks in advance.
Best Regards
Raghu
-----Original Message-----
From: libvirt-cim-bounces(a)redhat.com
[mailto:libvirt-cim-bounces@redhat.com] On Behalf Of
libvirt-cim-request(a)redhat.com
Sent: 30 May 2012 10:50
To: Raghunatha Reddy P (raghunp)
Subject: Welcome to the "Libvirt-cim" mailing list
Welcome to the Libvirt-cim(a)redhat.com mailing list!
To post to this list, send your email to:
libvirt-cim(a)redhat.com
General information about the mailing list is at:
https://www.redhat.com/mailman/listinfo/libvirt-cim
If you ever want to unsubscribe or change your options (eg, switch to or
from digest mode, change your password, etc.), visit your subscription
page at:
https://www.redhat.com/mailman/options/libvirt-cim/raghunp%40cisco.com
You can also make such adjustments via email by sending a message to:
Libvirt-cim-request(a)redhat.com
with the word `help' in the subject or body (don't include the quotes),
and you will get back a message with instructions.
You must know your password to change your options (including changing
the password, itself) or to unsubscribe. It is:
reddy123
Normally, Mailman will remind you of your redhat.com mailing list
passwords once every month, although you can disable this if you prefer.
This reminder will also include instructions on how to unsubscribe or
change your account options. There is also a button on your options
page that will email your current password to you.
12 years, 6 months
[cimtest] [PATCH] make cimtest be able to run multi groups of tests
by Wenchao Xia
This patch make the cimtest to execute a special combination of
test groups, for eg:
CIM_NS=root/virt CIM_USER=root CIM_PASS=1 ./runtests libvirt-cim -i localhost -c -d -v KVM -g "ComputerSystemIndication,ElementConforms"
It is important to use it to check errors under certain condition.
Using ',' is not a perfect solution, but it is the easiest way now.
Signed-off-by: Wenchao Xia <xiawenc(a)linux.vnet.ibm.com>
---
lib/VirtLib/groups.py | 12 ++++++++++++
suites/libvirt-cim/main.py | 6 ++++--
2 files changed, 16 insertions(+), 2 deletions(-)
diff --git a/lib/VirtLib/groups.py b/lib/VirtLib/groups.py
index 41d94c8..9e09d62 100644
--- a/lib/VirtLib/groups.py
+++ b/lib/VirtLib/groups.py
@@ -83,6 +83,18 @@ def get_group_test_list(test_suite, group):
return ret
+def get_grouplist_test_list(test_suite, grouplist):
+ """Return a list of dictionaries for a specific group.
+ It will contain the group and test filename
+ """
+ ret = []
+
+ for group in grouplist:
+ temp = get_group_test_list(test_suite, group)
+ ret.extend(temp)
+
+ return ret
+
def list_all_tests(test_suite):
"""Return a list of dictionaries, containing the group and test filename
"""
diff --git a/suites/libvirt-cim/main.py b/suites/libvirt-cim/main.py
index a4e33e6..725cbc8 100644
--- a/suites/libvirt-cim/main.py
+++ b/suites/libvirt-cim/main.py
@@ -51,7 +51,8 @@ parser.add_option("-m", "--target_url", dest="t_url", default="localhost:5988",
parser.add_option("-p", "--port", dest="port", type="int", default=5988,
help="CIMOM port (default: 5988)")
parser.add_option("-g", "--group", dest="group",
- help="Specific test group (default: None)")
+ help='''Specific test group (default: None), multi
+ test group could be spcified as -t "groupa,groupb" ''')
parser.add_option("-t", "--test", dest="test",
help="Specific test case (default: None). \
Must specify --group or -g to use this option")
@@ -225,7 +226,8 @@ def main(options, args):
test_list = groups.get_one_test(TEST_SUITE, options.group,
options.test)
else:
- test_list = groups.get_group_test_list(TEST_SUITE, options.group)
+ #test_list = groups.get_group_test_list(TEST_SUITE, options.group)
+ test_list = groups.get_grouplist_test_list(TEST_SUITE, options.group.split(','))
if not test_list:
print "Test %s:%s not found" % (options.group, options.test)
--
1.7.1
12 years, 6 months
test mail.
by Wayne Xia
Just a mail to test if the maillist is still alive, pls ignore
--
Best Regards
Wayne Xia
mail:xiawenc@linux.vnet.ibm.com
tel:86-010-82450803
12 years, 6 months
Future of libvirt-cim
by Daniel Veillard
I don't now why but the list manager bounced and discarded the
mail from Anthony to this list, so I'm sending it again.
As stated I'm fine taking over maintainance for the project
(releases, some patch review and commits) but if there is a regain
of activity and someone show commitment I will be fine handing
maintainance over :-)
W.r.t. closing the list, I think we need a grace period to allow
people to express dissent if needed (the libvir-list has far more
traffic) and I will send a couple of reminders before closing if there
is no opposition.
I guess the fist thing I will do is push the patch from Klaus
fixing the build with sblim-sfcb,
feedback welcome !
Daniel
----- Forwarded message from Anthony Liguori <aliguori(a)us.ibm.com> -----
> Date: Tue, 08 May 2012 20:46:09 -0500
> From: Anthony Liguori <aliguori(a)us.ibm.com>
> To: libvirt-cim(a)redhat.com
> CC: Daniel Veillard <veillard(a)redhat.com>, Dave Allan <dallan(a)redhat.com>
> Subject: Future of libvirt-cim
>
> Hi,
>
> As some of you may have noticed by the lack of activity on the
> libvirt-cim ML over the past month, we have decided at IBM to focus
> on direct consumption of libvirt and oVirt related interfaces
> meaning that we've stopped actively working on libvirt-cim.
>
> Having discussed it a little bit with DV et al, I think it would
> make sense to close this mailing list and move the traffic to the
> main libvirt as is done with the other libvirt sub projects.
>
> I also think it would make sense to open up commit access to have
> the same rules as the main libvirt repository does.
>
> Does that sound reasonable?
>
> Regards,
>
> Anthony Liguori
----- End forwarded message -----
--
Daniel Veillard | libxml Gnome XML XSLT toolkit http://xmlsoft.org/
daniel(a)veillard.com | Rpmfind RPM search engine http://rpmfind.net/
http://veillard.com/ | virtualization library http://libvirt.org/
12 years, 7 months