Normally I do:
ipython
from vdsm import vdscli
connection = vdscli.connect()
connection.setupNetworks(...)
Now you can check out configNetwork.py:setupNetworks and call it
according to its signature. No need to guess how the CLI works...
- Original Message -
- Original Message
master:
http://gerrit.ovirt.org/#/c/23044/
ovirt-3.3:
http://gerrit.ovirt.org/#/c/23045/
Assaf Muller, Cloud Networking Engineer
Red Hat
- Original Message -
From: Assaf Muller amul...@redhat.com
To: Balamurugan Arumugam barum...@redhat.com, Dan Kenigsberg
dan...@redhat.com
Cc: VDSM
to reproduce the
error no matter which order I tried
to start things up. We could solve the error without understanding the issue
(Which is no fun) and just make sure
that upgrade.log is created with vdsm:kvm permissions.
Assaf Muller, Cloud Networking Engineer
Red Hat
- Original Message
I'm unable to reproduce the issue at this time.
Assaf Muller, Cloud Networking Engineer
Red Hat
- Original Message -
From: Assaf Muller amul...@redhat.com
To: Antoni Segura Puimedon asegu...@redhat.com
Cc: vdsm-devel vdsm-de...@fedorahosted.org
Sent: Wednesday, December 4, 2013 12:12
While implementing a new form of network configuration persistence I needed a
way to run 'upgrade code'.
That is, I need the ability to run a piece of code exactly once, on the first
boot of VDSM.
My use case is related to unified network persistence - We intend to persist
network information
Here you go:
vdsClient -s 0 setupNetworks
networks='{rhevm:{bonding:bond2,bootproto:dhcp,bridged:True}}'
bondings='{bond2:{nics:eth1+eth2}}'
- Original Message -
From: Sandro Bonazzola sbona...@redhat.com
To: VDSM Project Development vdsm-devel@lists.fedorahosted.org
Sent: Thursday,
: Assaf Muller amul...@redhat.com
| | To: Michal Skrivanek michal.skriva...@redhat.com
| | Cc: vdsm-devel@lists.fedorahosted.org Development
| | vdsm-devel@lists.fedorahosted.org
| | Sent: Thursday, May 23, 2013 2:12:47 PM
| | Subject: Re: [vdsm] Migration regression on master
michal.skriva...@redhat.com
To: Vinzenz Feenstra vfeen...@redhat.com, Assaf Muller
amul...@redhat.com
Cc: vdsm-devel@lists.fedorahosted.org Development
vdsm-devel@lists.fedorahosted.org, Dan Kenigsberg dan...@redhat.com
Sent: Wednesday, May 22, 2013 3:56:22 PM
Subject: Re: [vdsm] Migration regression
Hi all,
Right now we have the ability to define VM-wide properties that may be used by
hooks.
It is time we have the same functionality on a device basis:
http://www.ovirt.org/Features/Device_Custom_Properties
For example: If the VM has 2 disks called disk1 and disk2, and two NICs called
