[libvirt] CfP for VHPC ‘18 - Papers due May 15 (extended) for the 13th Virtualization in High-Performance Cloud Computing Workshop
by VHPC 18
*Please accept our apologies if you receive multiple copies of this Call
for
Papers====================================================================CALL
FOR PAPERS 13th Workshop on Virtualization in High-Performance Cloud
Computing (VHPC '18)held in conjunction with the International
Supercomputing Conference - High Performance,June 24-28, 2018, Frankfurt,
Germany.(Springer LNCS Proceedings)
====================================================================Date:
June 28, 2018Workshop URL: http://vhpc.org <http://vhpc.org>Paper
Submission Deadline: May 15, 2018 (extended)Springer LNCS, rolling abstract
submissionAbstract/Paper Submission Link:
https://edas.info/newPaper.php?c=24355
<https://edas.info/newPaper.php?c=24355>Special Track: GPU - Accelerator
Virtualization Call for PapersVirtualization technologies constitute a key
enabling factor for flexible resource managementin modern data centers, and
particularly in cloud environments. Cloud providers need tomanage complex
infrastructures in a seamless fashion to support the highly dynamic
andheterogeneous workloads and hosted applications customers deploy.
Similarly, HPCenvironments have been increasingly adopting techniques that
enable flexible managementof vast computing and networking resources, close
to marginal provisioning cost, which isunprecedented in the history of
scientific and commercial computing.Various virtualization technologies
contribute to the overall picture in different ways: machinevirtualization,
with its capability to enable consolidation of multiple underutilized
servers withheterogeneous software and operating systems (OSes), and its
capability to live-migrate afully operating virtual machine (VM) with a
very short downtime, enables novel and dynamicways to manage physical
servers; OS-level virtualization (i.e., containerization), with
itscapability to isolate multiple user-space environments and to allow for
their coexistencewithin the same OS kernel, promises to provide many of
the advantages of machine virtualization with high levels of responsiveness
and performance; I/O Virtualization allows physical network interfaces to
take traffic from multiple VMs or containers; network virtualization, with
its capability to create logical network overlays that are independent of
theunderlying physical topology is furthermore enabling virtualization of
HPC infrastructures. PublicationAccepted papers will be published in a
Springer LNCS proceedings volume.Topics of InterestThe VHPC program
committee solicits original, high-quality submissions related
tovirtualization across the entire software stack with a special focus on
the intersection of HPCand the cloud.Major Topics- Virtualization in
supercomputing environments, HPC clusters, HPC in the cloud and grids-
OS-level virtualization and containers (LXC, Docker, rkt, Singularity,
Shifter, i.a.)- Lightweight/specialized operating systems in conjunction
with virtual machines- Novel unikernels and use cases for virtualized HPC
environments- Performance improvements for or driven by unikernels- Tool
support for unikernels: configuration/build environments, debuggers,
profilers- Hypervisor extensions to mitigate side-channel attacks
([micro-]architectural timing attacks, privilege escalation)- VM &
Container trust and security- Containers inside VMs with hypervisor
isolation- GPU virtualization operationalization- Approaches to GPGPU
virtualization including API remoting and hypervisor abstraction-
Optimizations of virtual machine monitor platforms and hypervisors-
Hypervisor support for heterogeneous resources (GPUs, co-processors, FPGAs,
etc.)- Virtualization support for emerging memory technologies-
Virtualization in enterprise HPC and microvisors- Software defined networks
and network virtualization- Management, deployment of virtualized
environments and orchestration (Kubernetes i.a.)- Workflow-pipeline
container-based composability - Checkpointing facilitation utilizing
containers and VMs - Emerging topics including multi-kernel approaches and
NUMA in hypervisors- Operating MPI in containers/VMs and Unikernels -
Virtualization in data intensive computing (big data) - HPC convergence-
Adaptation of HPC technologies in the cloud (high performance networks,
RDMA, etc.)- Performance measurement, modelling and monitoring of
virtualized/cloud workloads- Latency-and jitter sensitive workloads in
virtualized/containerized environments- I/O virtualization (including
applications, SR-IOV, i.a.) - Hybrid local facility + cloud compute and
based storage systems, cloudbursting- FPGA and many-core accelerator
virtualization- Job scheduling/control/policy and container placement in
virtualized environments- Cloud reliability, fault-tolerance and
high-availability- QoS and SLA in virtualized environments- IaaS platforms,
cloud frameworks and APIs- Energy-efficient and power-aware virtualization-
Configuration management tools for containers (including in OpenStack,
Ansible, i.a.)- ARM-based hypervisors, ARM virtualization extensionsSpecial
Track: GPU - Accelerator VirtualizationGPU virtualization technologies,
performance and benchmarking, integration withworkflow scheduling systems,
integration to cluster managers.GPUs are taking on many HPC workload areas,
especially in deep learning withinmachine learning. In addition, a lot of
workload is being pushed to elastic environments utilizing various
virtualization technologies on different levels like hypervisors (e.g.
VMWare, Xen, KVM), kernel (Docker, Kubernetes) or on the resource
managerlevel (YARN, Mesos). In this track we invite submissions addressing
these problems. Suggested Themes and Topics:Technology - What technologies
and best practices exist for GPU - hardware accelerator virtualization and
usage of hardware accelerators in virtual environments on the hypervisor,
kernel or resource manager levelDevelopers - Real-life experience when
addressing HPC/ML/DL problems with GPUs or hardware accelerators in virtual
environmentsPerformance - Performance comparisons between different
technologies / solutionsThe Workshop on Virtualization in High-Performance
Cloud Computing (VHPC) aims tobring together researchers and industrial
practitioners facing the challenges posed by virtualization in order to
foster discussion, collaboration, mutual exchangeof knowledge and
experience, enabling research to ultimately provide novelsolutions for
virtualized computing systems of tomorrow.The workshop will be one day in
length, composed of 20 min paper presentations, eachfollowed by 10 min
discussion sections, plus lightning talks that are limited to 5
minutes.Presentations may be accompanied by interactive
demonstrations.KeynotesGregory M. Kurtzer, CEO Syslabs Inc. Singularity:
Application containers using operating system environment
virtualization.Josh Simons, HPC Chief Technologist, VMWare, Inc. Practical
Aspects of On-Premises Virtualized High Performance Computing.Important
DatesMay 15, 2018 (extended) - Paper submission deadline (Springer LNCS)May
30, 2018 - Acceptance notification June 28, 2018 - Workshop DayJuly 12,
2018 - Camera-ready version dueChairMichael Alexander (chair), Institute of
Science and Technology, AustriaAnastassios Nanos (co-chair), OnApp,
UKRomeo Kienzler (co-chair), IBM, SwitzerlandProgram committeeStergios
Anastasiadis, University of Ioannina, Greece Jakob Blomer, CERN, Europe
Eduardo César, Universidad Autonoma de Barcelona, SpainStephen Crago, USC
ISI, USATommaso Cucinotta, St. Anna School of Advanced Studies,
ItalyChristoffer Dall, Columbia University, USAFrançois Diakhaté, CEA,
FrancePatrick Dreher, MIT, USA Kyle Hale, Northwestern University, USA
Brian Kocoloski, University of Pittsburgh, USAUday Kurkure, VMware, USAJohn
Lange, University of Pittsburgh, USAGiuseppe Lettieri, University of Pisa,
ItalyQing Liu, Oak Ridge National Laboratory, USANikos Parlavantzas, IRISA,
FranceKevin Pedretti, Sandia National Laboratories, USAAmer Qouneh, Western
New England University, USA Carlos Reaño, Technical University of Valencia,
SpainBorja Sotomayor, University of Chicago, USA Anata Tiwari, San Diego
Supercomputer Center, USAKurt Tutschku, Blekinge Institute of Technology,
Sweden Yasuhiro Watashiba, Osaka University, JapanChao-Tung Yang, Tunghai
University, Taiwan Andrew Younge, Sandia National Laboratory, USANa Zhang,
VMware, USAPaper Submission-PublicationPapers submitted to the workshop
will be reviewed by at least twomembers of the program committee and
external reviewers. Submissionsshould include abstract, keywords, the
e-mail address of thecorresponding author, and must not exceed 10 pages,
including tablesand figures at a main font size no smaller than 11 point.
Submissionof a paper should be regarded as a commitment that, should the
paperbe accepted, at least one of the authors will register and attend
theconference to present the work. Accepted papers will be published in
aSpringer LNCS volume.The format must be according to the Springer LNCS
Style. Initialsubmissions are in PDF; authors of accepted papers will be
requestedto provide source files.Format
Guidelines:ftp://ftp.springer.de/pub/tex/latex/llncs/latex2e/llncs2e.zip
<ftp://ftp.springer.de/pub/tex/latex/llncs/latex2e/llncs2e.zip>Abstract,
Paper Submission Link:https://edas.info/newPaper.php?c=24355
<https://edas.info/newPaper.php?c=24355>Lightning Talks Lightning Talks are
non-paper track, synoptical in nature and are strictly limited to 5
minutes.They can be used to gain early feedback on ongoing research, for
demonstrations, to present research results, early research ideas,
perspectives and positions of interest to the community. Submit abstract
via the main submission link. General InformationThe workshop is one day in
length and will be held in conjunction with the InternationalSupercomputing
Conference - High Performance (ISC) 2018, June 24-28, Frankfurt, Germany.*
6 years, 8 months
[libvirt] [jenkins-ci PATCH] jobs: Unset $CC for Go and MinGW jobs
by Andrea Bolognani
We want $CC to be set so that ccache is used by default, but
some jobs (Go and MinGW) don't like that very much.
Later on, we might consider building a link farm so that we
can use ccache without having to set $CC; for the time being,
work around the issue at the job level.
Signed-off-by: Andrea Bolognani <abologna(a)redhat.com>
---
jobs/autotools.yaml | 7 +++++++
jobs/go.yaml | 8 ++++++++
2 files changed, 15 insertions(+)
diff --git a/jobs/autotools.yaml b/jobs/autotools.yaml
index 98bb1b0..b882803 100644
--- a/jobs/autotools.yaml
+++ b/jobs/autotools.yaml
@@ -223,6 +223,10 @@
- shell: |
{global_env}
{local_env}
+ # The way we perform MinGW builds doesn't play well with the $CC
+ # variable containing whitespace, so we have to unset it here.
+ export CC=
+
mkdir -p build32
cd build32
@@ -235,6 +239,9 @@
- shell: |
{global_env}
{local_env}
+ # See above
+ export CC=
+
mkdir -p build64
cd build64
diff --git a/jobs/go.yaml b/jobs/go.yaml
index 29a9f51..2634cb2 100644
--- a/jobs/go.yaml
+++ b/jobs/go.yaml
@@ -42,6 +42,11 @@
- shell: |
{global_env}
{local_env}
+ # go doesn't handle the $CC variable containing whitespace
+ # correctly, so we have to make sure it's unset when building.
+ # See https://github.com/golang/go/issues/11685
+ export CC=
+
go build -v
publishers:
- email:
@@ -80,6 +85,9 @@
- shell: |
{global_env}
{local_env}
+ # See above
+ export CC=
+
go test $TEST_ARGS
publishers:
- email:
--
2.14.3
6 years, 8 months
[libvirt] [PATCH] qemu: use target.port for isa-serial
by Thilo Cestonaro
A configured target.port is currently totaly ignored, while contsructing
qemu commandline, for all types of serial devices. This patch adds a -device
parameter "index" for the target model isa-serial.
This enables the user to specify which serial device will end in which ttySX
device.
Signed-off-by: Thilo Cestonaro <thilo.cestonaro(a)ts.fujitsu.com>
---
Forgot to sign off! Here with Signed-off-by.
src/qemu/qemu_command.c | 16 ++++++++++++++++
1 file changed, 16 insertions(+)
diff --git a/src/qemu/qemu_command.c b/src/qemu/qemu_command.c
index 514c3ab2e..5f770404b 100644
--- a/src/qemu/qemu_command.c
+++ b/src/qemu/qemu_command.c
@@ -10291,6 +10291,22 @@ qemuBuildSerialChrDeviceStr(char **deviceStr,
virDomainChrSerialTargetModelTypeToString(serial->targetModel),
serial->info.alias, serial->info.alias);
+ switch ((virDomainChrSerialTargetModel) serial->targetModel) {
+ case VIR_DOMAIN_CHR_SERIAL_TARGET_MODEL_ISA_SERIAL:
+ if (serial->target.port != -1)
+ virBufferAsprintf(&cmd, ",index=%d", serial->target.port);
+ break;
+ case VIR_DOMAIN_CHR_SERIAL_TARGET_MODEL_NONE:
+ case VIR_DOMAIN_CHR_SERIAL_TARGET_MODEL_USB_SERIAL:
+ case VIR_DOMAIN_CHR_SERIAL_TARGET_MODEL_PCI_SERIAL:
+ case VIR_DOMAIN_CHR_SERIAL_TARGET_MODEL_SPAPR_VTY:
+ case VIR_DOMAIN_CHR_SERIAL_TARGET_MODEL_PL011:
+ case VIR_DOMAIN_CHR_SERIAL_TARGET_MODEL_SCLPCONSOLE:
+ case VIR_DOMAIN_CHR_SERIAL_TARGET_MODEL_SCLPLMCONSOLE:
+ case VIR_DOMAIN_CHR_SERIAL_TARGET_MODEL_LAST:
+ break;
+ }
+
if (qemuBuildDeviceAddressStr(&cmd, def, &serial->info, qemuCaps) < 0)
goto error;
--
2.15.1
6 years, 8 months
[libvirt] [jenkins-ci PATCH 00/10] guests: Improve enviroment handling
by Andrea Bolognani
The basic goal is to move all environment configuration that
affects builds to a single place which is tracked along with all
other changes to the CI environment.
Patch 8/10 also happens to fix build of packages that depend on
libvirt-perl on FreeBSD now that they've switched to Perl 5.26,
though we haven't run into this specific problem yet due to other
issues in the CI enviroment ;)
Andrea Bolognani (10):
guests: Rename compat -> kludges
guests: Enable ~/.bashrc on FreeBSD
guests: Add custom shell profile
guests: Move ccache configuration to shell profile
guests: Move make configuration to shell profile
guests: Move $PATH configuration to shell profile
guests: Add more enviroment variables to shell profile
guests: Move Perl configuration to shell profile
guests: Add Python configuration to shell profile
guests: Remove per-host make variable
guests/group_vars/all/main.yml | 15 ++++++++++---
guests/host_vars/libvirt-centos-6/main.yml | 3 +++
guests/host_vars/libvirt-centos-7/main.yml | 3 +++
guests/host_vars/libvirt-debian-8/main.yml | 3 +++
guests/host_vars/libvirt-debian-9/main.yml | 3 +++
guests/host_vars/libvirt-debian-sid/main.yml | 3 +++
guests/host_vars/libvirt-fedora-26/main.yml | 3 +++
guests/host_vars/libvirt-fedora-27/main.yml | 3 +++
guests/host_vars/libvirt-fedora-rawhide/main.yml | 3 +++
guests/host_vars/libvirt-freebsd-10/main.yml | 4 +++-
guests/host_vars/libvirt-freebsd-11/main.yml | 4 +++-
guests/host_vars/libvirt-freebsd-current/main.yml | 4 +++-
guests/host_vars/libvirt-ubuntu-14/main.yml | 3 +++
guests/host_vars/libvirt-ubuntu-16/main.yml | 3 +++
guests/site.yml | 2 +-
guests/tasks/{compat.yml => kludges.yml} | 18 +++++++++++++++
guests/tasks/users.yml | 27 +++++++++++------------
guests/templates/bash_profile | 1 +
guests/templates/bashrc | 15 +++++++++++++
jobs/defaults.yaml | 6 -----
20 files changed, 99 insertions(+), 27 deletions(-)
rename guests/tasks/{compat.yml => kludges.yml} (59%)
create mode 100644 guests/templates/bash_profile
create mode 100644 guests/templates/bashrc
--
2.14.3
6 years, 8 months
[libvirt] [PATCH 00/10] Add support for VM Generation ID (vmgenid)
by John Ferlan
As a result of the RFC:
https://www.redhat.com/archives/libvir-list/2018-March/msg01214.html
Patches to support changes for
https://bugzilla.redhat.com/show_bug.cgi?id=1149445
The first patch isn't necessarily related, but since it I was looking
at the all the virUUIDGenerate calls, I figured I'd include it here.
It can be consider separately.
I did leave in the possibility that someone can supply a GUID in the
XML; however, that can be removed - requiring that just the <genid/>
exists and forcing every usage to generate the GUID. The spec isn't
100% clear on whether that's a valid use. One area which I'm still a
little bit fuzzy on is the snapshot functionality. The transitions
while running won't work unless/until the qemu command to set the
genid GUID value are accepted. It'd be tough to fail, but according
to how I've read the spec it'd be required to change the GUID value
and since we cannot do so, failure is the only option.
John Ferlan (10):
Check return status for virUUIDGenerate
conf: Modify last arg to virDomainDefCopy
qemu: Add flags to qemuDomainMigratableDefCheckABIStability
conf: Add VM Generation ID to virDomainDef
conf: Add flag to regenerate genid for virDomainDefCopy
conf: Add VM Generation ID parse/format support
qemu: Add VM Generation ID device capability
qemu: Handle genid processing during startup/launch
qemu: Add VM Generation ID to qemu command line
docs: Add news article for VM Generation ID
docs/formatdomain.html.in | 29 ++++++
docs/news.xml | 12 +++
docs/schemas/domaincommon.rng | 8 ++
src/conf/domain_conf.c | 81 +++++++++++++++-
src/conf/domain_conf.h | 19 +++-
src/conf/network_conf.c | 2 +-
src/conf/secret_conf.c | 2 +-
src/libxl/libxl_domain.c | 4 +-
src/openvz/openvz_conf.c | 2 +-
src/qemu/qemu_capabilities.c | 2 +
src/qemu/qemu_capabilities.h | 1 +
src/qemu/qemu_command.c | 31 ++++++
src/qemu/qemu_domain.c | 23 +++--
src/qemu/qemu_domain.h | 6 +-
src/qemu/qemu_driver.c | 31 ++++--
src/qemu/qemu_migration.c | 4 +-
src/qemu/qemu_process.c | 110 +++++++++++++++++++++-
src/qemu/qemu_process.h | 1 +
src/test/test_driver.c | 6 +-
src/xenconfig/xen_common.c | 2 +-
tests/qemucapabilitiesdata/caps_2.10.0.x86_64.xml | 1 +
tests/qemucapabilitiesdata/caps_2.12.0.x86_64.xml | 1 +
tests/qemucapabilitiesdata/caps_2.9.0.x86_64.xml | 1 +
tests/qemuxml2argvdata/genid-auto.args | 21 +++++
tests/qemuxml2argvdata/genid-auto.xml | 32 +++++++
tests/qemuxml2argvdata/genid.args | 21 +++++
tests/qemuxml2argvdata/genid.xml | 32 +++++++
tests/qemuxml2argvtest.c | 4 +
tests/qemuxml2xmloutdata/genid-active.xml | 32 +++++++
tests/qemuxml2xmloutdata/genid-auto-active.xml | 32 +++++++
tests/qemuxml2xmloutdata/genid-auto-inactive.xml | 32 +++++++
tests/qemuxml2xmloutdata/genid-inactive.xml | 32 +++++++
tests/qemuxml2xmltest.c | 5 +-
33 files changed, 585 insertions(+), 37 deletions(-)
create mode 100644 tests/qemuxml2argvdata/genid-auto.args
create mode 100644 tests/qemuxml2argvdata/genid-auto.xml
create mode 100644 tests/qemuxml2argvdata/genid.args
create mode 100644 tests/qemuxml2argvdata/genid.xml
create mode 100644 tests/qemuxml2xmloutdata/genid-active.xml
create mode 100644 tests/qemuxml2xmloutdata/genid-auto-active.xml
create mode 100644 tests/qemuxml2xmloutdata/genid-auto-inactive.xml
create mode 100644 tests/qemuxml2xmloutdata/genid-inactive.xml
--
2.13.6
6 years, 8 months
[libvirt] [PATCH 0/9] Add Jansson support
by Ján Tomko
Prefer Jansson, but allow fallback/choice of yajl.
Support for yajl can hopefully be dropped after we ditch CentOS 6
which has no Jansson.
Ján Tomko (9):
virmacmaptest: depend on yajl for 'empty' test
virjsontest: Use a more stable floating point number for testing
configure: rename LIBVIRT_*_YAJL to LIBVIRT_*_JSON
Introduce WITH_JSON
Introduce JSON_CFLAGS and JSON_LIBS
virt-json.m4: generalize yajl dependency
build: link setuid_rpc_client against JSON_LIBS
virjson: add support for Jansson
virt-json.m4: simplify QEMU check
configure.ac | 10 +-
m4/virt-json.m4 | 86 ++++++++++++++++
m4/virt-yajl.m4 | 55 -----------
src/Makefile.am | 9 +-
src/qemu/qemu_capabilities.c | 2 +-
src/qemu/qemu_driver.c | 4 +-
src/util/Makefile.inc.am | 4 +-
src/util/virjson.c | 219 +++++++++++++++++++++++++++++++++++++++++
tests/Makefile.am | 12 +--
tests/cputest.c | 16 +--
tests/libxlxml2domconfigtest.c | 4 +-
tests/qemuagenttest.c | 2 +-
tests/qemucapabilitiestest.c | 2 +-
tests/qemucaps2xmltest.c | 2 +-
tests/qemucommandutiltest.c | 2 +-
tests/qemuhelptest.c | 2 +-
tests/qemuhotplugtest.c | 2 +-
tests/qemumonitorjsontest.c | 2 +-
tests/virjsontest.c | 2 +-
tests/virmacmaptest.c | 3 +
tests/virmocklibxl.c | 4 +-
tests/virnetdaemontest.c | 2 +-
tests/virstoragetest.c | 4 +-
23 files changed, 354 insertions(+), 96 deletions(-)
create mode 100644 m4/virt-json.m4
delete mode 100644 m4/virt-yajl.m4
--
2.16.1
6 years, 8 months
[libvirt] [PATCH] conf: Actually make virDomainChrSourceDef an object
by Michal Privoznik
In 2ada9ef1465f we've tried to turn virDomainChrSourceDef into
virObject. Well, this requires 'virObject' member to be stored on
the first position of the struct. This adjustment is missing in
the original commit leading to all sorts of funny memleaks and
data corruptions.
Signed-off-by: Michal Privoznik <mprivozn(a)redhat.com>
---
src/conf/domain_conf.h | 2 ++
1 file changed, 2 insertions(+)
diff --git a/src/conf/domain_conf.h b/src/conf/domain_conf.h
index 89a7131fdb..1426f115ed 100644
--- a/src/conf/domain_conf.h
+++ b/src/conf/domain_conf.h
@@ -57,6 +57,7 @@
# include "virtypedparam.h"
# include "virsavecookie.h"
# include "virresctrl.h"
+# include "virobject.h"
/* forward declarations of all device types, required by
* virDomainDeviceDef
@@ -1180,6 +1181,7 @@ typedef virDomainChrSourceReconnectDef *virDomainChrSourceReconnectDefPtr;
/* The host side information for a character device. */
struct _virDomainChrSourceDef {
+ virObject parent;
int type; /* virDomainChrType */
virObjectPtr privateData;
union {
--
2.16.1
6 years, 8 months
[libvirt] [dbus PATCH 0/6] More methods for Domain interface
by Katerina Koukiou
Katerina Koukiou (6):
Implement Setter for Autostart property for Domain interface
Implement SchedulerType property for Domain Interface
Introduce virtDBusDomainMemoryStatTypeToString helper function
Implement MemoryStats for Domain Interface
Implement AttachDevice method for Domain Interface
Implement DetachDevice method for Domain Interface
data/org.libvirt.Domain.xml | 28 +++++++-
src/domain.c | 166 +++++++++++++++++++++++++++++++++++++++++++-
test/test_domain.py | 10 +++
3 files changed, 201 insertions(+), 3 deletions(-)
--
2.15.0
6 years, 8 months
[libvirt] [jenkins-ci PATCH] guests: Clean up packages after update
by Andrea Bolognani
The package cache can grow to eat up a lot of disk space, and
not removing unused packages can lead to upgrade issues down
the line for fast moving distributions such as Fedora Rawhide.
Signed-off-by: Andrea Bolognani <abologna(a)redhat.com>
---
guests/tasks/base.yml | 19 +++++++++++++++++++
1 file changed, 19 insertions(+)
diff --git a/guests/tasks/base.yml b/guests/tasks/base.yml
index 53cbd65..f419433 100644
--- a/guests/tasks/base.yml
+++ b/guests/tasks/base.yml
@@ -117,6 +117,25 @@
when:
- package_format == 'pkg'
+- name: Clean up packages after update
+ command: yum clean packages -y
+ args:
+ warn: no
+ when:
+ - package_format == 'rpm'
+
+- name: Clean up packages after update
+ apt:
+ autoclean: yes
+ autoremove: yes
+ when:
+ - package_format == 'deb'
+
+- name: Clean up packages after update
+ shell: pkg clean -y && pkg autoremove -y
+ when:
+ - package_format == 'pkg'
+
- name: Configure hostname
hostname:
name: '{{ inventory_hostname }}'
--
2.14.3
6 years, 8 months
[libvirt] [dbus PATCH 0/6] More methods for Domain Interface
by Katerina Koukiou
Katerina Koukiou (6):
Implement Setter for Autostart property for Domain interface
Implement SchedulerType property for Domain Interface
Introduce virtDBusDomainMemoryStatTypeToString helper function
Implement MemoryStats for Domain Interface
Implement AttachDevice method for Domain Interface
Implement DetachDevice method for Domain Interface
data/org.libvirt.Domain.xml | 28 +++++++-
src/domain.c | 166 +++++++++++++++++++++++++++++++++++++++++++-
test/test_domain.py | 10 +++
3 files changed, 201 insertions(+), 3 deletions(-)
--
2.15.0
6 years, 8 months
