Copy reviewer scores on trivial rebase/commit msg changes
by iheim@redhat.com
I'd like to enable these - comments welcome:
1. label.Label-Name.copyAllScoresOnTrivialRebase
If true, all scores for the label are copied forward when a new patch
set is uploaded that is a trivial rebase. A new patch set is considered
as trivial rebase if the commit message is the same as in the previous
patch set and if it has the same code delta as the previous patch set.
This is the case if the change was rebased onto a different parent. This
can be used to enable sticky approvals, reducing turn-around for trivial
rebases prior to submitting a change. Defaults to false.
2. label.Label-Name.copyAllScoresIfNoCodeChange
If true, all scores for the label are copied forward when a new patch
set is uploaded that has the same parent commit as the previous patch
set and the same code delta as the previous patch set. This means only
the commit message is different. This can be used to enable sticky
approvals on labels that only depend on the code, reducing turn-around
if only the commit message is changed prior to submitting a change.
Defaults to false.
https://gerrit-review.googlesource.com/Documentation/config-labels.html
10 years, 5 months
[Block Storage] What about the shrinking disk in the vm?
by Qixiaozhen
Hi,all
VDSM have realized the feature of thin provision in its released version.
Volumes have 2 major properties:
1. type - How are the bits written to the underlying volume.
o raw - means a simple raw access a write to offset X will be written on offset X
o qcow2 - means that the storage will be accessed as a qcow2 image and all that this entails
2. allocation - How should VDSM allocated the storage
o preallocated - VDSM will try it's best to guaranty that all the storage that was requested is allocated right away. Some storage configuration may render preallocation pointless.
o sparse/thin provision - space will be allocated for the volume as needed
As is known to all, thin provision means allocating the disk space once the instance writes the data on the area of volume in the first time. The size of the disk will be increasing even though we have deleted the file in the instance.
With the latest feature of qemu, the disk can be shrinked. Ref link: http://dustymabe.com/2013/06/11/recover-space-from-vm-disk-images-by-usin...
Does VDSM have any plan for this?
Thanks,
Qi
________________________________
Xiaozhen Qi
Huawei Technologies Co.,LTD.
IT Product Line CloudOS PDU
China, Xi'an
Mobile: +86-13609283376
Email: qixiaozhen(a)huawei.com
10 years, 5 months
[QE] oVirt 3.4.0 alpha / beta status
by Sandro Bonazzola
Hi,
oVirt 3.4.0 alpha has been released and is actually on QA.
An issue has been found in VDSM so we have updated the packages in alpha repositories for Fedora.
We had an issue with nightly build for EL6 packages yesterday so EL6 repository is not yet updated.
We'll try to sync it today, I'm sorry for the inconvenient.
We'll start composing oVirt 3.4.0 beta on 2014-01-20 14:00 UTC from 3.4 branches.
The bug tracker [1] shows the following bugs blocking the release:
Whiteboard Bug ID Summary
gluster 1038988 Gluster brick sync does not work when host has multiple interfaces
integration 1054080 gracefully warn about unsupported upgrade from legacy releases
network 1054195 [NetworkLabels] Attaching two labeled networks to a cluster result in failure of the latter
There are still 280 bugs [2] targeted to 3.4.0.
Excluding node and documentation bugs we still have 237 bugs [3] targeted to 3.4.0.
Please review them as soon as possible.
Maintainers:
- Please remember to rebuild your packages before 2014-01-21 12:00 UTC if you want them to be included in 3.4.0 beta.
- Please add the bugs to the tracker if you think that 3.4.0 should not be released without them fixed.
- Please provide ETA on blockers bugs
- Please update the target to 3.4.1 or any next release for bugs that won't be in 3.4.0:
it will ease gathering the blocking bugs for next releases.
- Please fill release notes, the page has been created here [4]
- Please update http://www.ovirt.org/OVirt_3.4_TestDay before 2014-01-23
For those who want to help testing the bugs, I suggest to add yourself as QA contact for the bug.
Please also be prepared for upcoming oVirt 3.4.0 Test Day on 2014-01-23!
Thanks to all people already testing 3.4.0 alpha!
[1] https://bugzilla.redhat.com/1024889
[2] http://red.ht/1eIRZXM
[3] http://red.ht/1auBU3r
[4] http://www.ovirt.org/OVirt_3.4.0_release_notes
--
Sandro Bonazzola
Better technology. Faster innovation. Powered by community collaboration.
See how it works at redhat.com
10 years, 5 months
[QE] oVirt 3.3.3 beta / RC status
by Sandro Bonazzola
Hi,
oVirt 3.3.3 beta has been released and is actually on QA.
We'll start composing oVirt 3.3.3 RC on 2014-01-21 12:00 UTC.
The bug tracker [1] shows no bugs blocking the release
The following is a list of the non-blocking bugs still open with target 3.3 - 3.3.3:
Whiteboard Bug ID Summary
integration 902979 ovirt-live - firefox doesn't trust the installed engine
integration 1021805 [RFE] oVirt Live - use motd to show the admin password
integration 1022440 [RFE] AIO - configure the AIO host to be a gluster cluster/host
integration 1026930 Package virtio-win and put it in ovirt repositories
integration 1026933 pre-populate ISO domain with virtio-win ISO
integration 1050084 Tracker: oVirt 3.3.3 release
network 997197 Some AppErrors messages are grammatically incorrect (singular vs plural)
node 906257 USB Flash Drive install of ovirt-node created via dd fails
node 923049 ovirt-node fails to boot from local disk under UEFI mode
node 965583 [RFE] add shortcut key on TUI
node 976675 [wiki] Update contribution page
node 979350 Changes admin password in the first time when log in is failed while finished auto-install
node 979390 [RFE] Split defaults.py into smaller pieces
node 982232 performance page takes >1sec to load (on first load)
node 984441 kdump page crashed before configuring the network after ovirt-node intalled
node 986285 UI crashes when no bond name is given
node 991267 [RFE] Add TUI information to log file.
node 1018374 ovirt-node-iso-3.0.1-1.0.2.vdsm.fc19: Failed on Auto-install
node 1018710 [RFE] Enhance API documentation
node 1032035 [RFE]re-write auto install function for the cim plugin
node 1033286 ovirt-node-plugin-vdsm can not be added to ovirt node el6 base image
storage 987917 [oVirt] [glance] API version not specified in provider dialog
virt 1007940 Cannot clone from snapshot while using GlusterFS as POSIX Storage Domain
Maintainers:
- We'll start composing oVirt 3.3.3 RC on 2014-01-21 12:00 UTC: all non blockers bug still open after the build will be moved to 3.3.4.
- Please add the bugs to the tracker if you think that 3.3.3 should not be released without them fixed.
- Please provide ETA on bugs you add as blockers
- Please re-target all bugs you don't think that should block 3.3.3.
- Please fill release notes, the page has been created here [3]
- Please remember to rebuild your packages before 2014-01-21 12:00 UTC if you want them to be included in 3.3.3 RC.
For those who want to help testing the bugs, I suggest to add yourself as QA contact for the bug and add yourself to the testing page [2].
Thanks to Gianluca Cecchi for his testing of oVirt 3.3.3 beta on Gluster storage!
[1] http://bugzilla.redhat.com/1050084
[2] http://www.ovirt.org/Testing/Ovirt_3.3.3_testing
[3] http://www.ovirt.org/OVirt_3.3.3_release_notes
Thanks,
--
Sandro Bonazzola
Better technology. Faster innovation. Powered by community collaboration.
See how it works at redhat.com
10 years, 5 months
[QE] 3.4.0 Release tracker
by Sandro Bonazzola
Hi,
as you may know, we're planning to build oVirt 3.4.0 beta really soon and release 3.4.0 by end of January.
A tracker bug (https://bugzilla.redhat.com/show_bug.cgi?id=1024889) has been created for this release.
The following is a list of the current blocker bugs with target 3.4.0:
Whiteboard Bug ID Summary
storage 1032686 [RFE] API to save OVF on any location
storage 1032679 [RFE] Single Disk Snapshots
network 987813 [RFE] report BOOTPROTO and BONDING_OPTS independent of netdevice.cfg
The following is a list of the bugs with target 3.4.0 not yet fixed:
Whiteboard Bug ID Summary
gluster 1008980 [oVirt] Option 'Select as SPM' available for a host in gluster-only mode of oVirt
gluster 1038988 Gluster brick sync does not work when host has multiple interfaces
i18n 1033730 [es-ES] need to revise the "create snapshot" translation
infra 870330 Cache records in memory
infra 904029 [engine-manage-domains] should use POSIX parameter form and aliases as values
infra 979231 oVirt Node Upgrade: Support N configuration
infra 986882 tar which is used by host-deploy is missing from fedora minimal installation
infra 995362 [RFE] Support firewalld
infra 1016634 Performance hit as a result of duplicate updates to VdsDynamic in VdsUpdateRuntimeInfo
infra 1023751 [RFE] Create Bin Overrider for application context files changes we do in JRS
infra 1023754 [RFE] add trigger to stop etl connection via engine db value.
infra 1023759 [RFE] re-implement SSO solution based on JRS new SSO interface
infra 1023761 [RFE] Build nightly JRS builds based on latest JRS version
infra 1028793 systemctl start vdsmd blocks if dns server unreachable
infra 1032682 Refactor authentication framework in engine
infra 1035844 [oVirt][infra] Add host/Reinstall radio button text not actionable
infra 1045350 REST error during VM creation via API
infra 1046611 [oVirt][infra] Device custom properties syntax check is wrong
integration 789040 [RFE] Log Collector should be able to run without asking questions
integration 967350 [RFE] port dwh installer to otopi
integration 967351 [RFE] port reports installer to otopi
integration 1023752 [RFE] add upstream support for Centos el6 arch.
integration 1024028 [RFE] add trigger to stop etl connection via engine db value.
integration 1028489 [RFE] pre-populate ISO DOMAIN with rhev-tools-setup.iso (or equiv)
integration 1028913 'service network start' sometimes fails during setup
integration 1037663 F20 - ovirt-log-collector: conflicts with file from package sos-3.0-3.fc20.noarch
integration 1039616 Setting shmmax on F19 is not enough for starting postgres
network 987832 failed to add ovirtmgmt bridge when the host has static ip
network 1001186 With AIO installer and NetworkManager enabled, the ovirtmgmt bridge is not properly configured
network 1010663 override mtu field allows only values up to 9000
network 1018947 Yum update to oVirt 3.3 from 3.1.0 fails on CentOS 6.4 with EPEL dependency on python-inotify
network 1037612 [oVirt][network][RFE] Add "sync" column to hosts sub tab under networks main tab
network 1040580 [RFE] Apply networks changes to multiple hosts
network 1040586 [RFE] Ability to configure network on multiple hosts at once
network 1043220 [oVirt][network][RFE] Add Security-Group support for Neutron based networks
network 1043230 Allow configuring Network QoS on host interfaces
network 1044479 Make an iproute2 network configurator for vdsm
network 1048738 [oVirt][network][RFE] Add subnet support for neutron based networks
network 1048740 [oVirt][network][RFE] Allow deleting Neutron based network (in Neutron)
network 1048880 [vdsm][openstacknet] Migration fails for vNIC using OVS + security groups
sla 994712 Remove underscores for pre-defined policy names
sla 1038616 [RFE] Support for hosted engine
storage 888711 PosixFS issues
storage 961532 [RFE] Handle iSCSI lun resize
storage 1009610 [RFE] Provide clear warning when SPM become inaccessible and needs fencing
storage 1034081 Misleading error message when adding an existing Storage Domain
storage 1038053 [RFE] Allow domain of multiple types in a single Data Center
storage 1045842 After deleting image failed ui display message: Disk gluster-test was successfully removed from...
ux 784779 [webadmin][RFE] Login page. Add a link to welcome page
ux 1014859 [RFE] improve context-sensitive help csv mapping files
ux 1035566 [RFE] [oVirt][webadmin] Change comment column title to icon, and move to right of name
ux 1048916 sub-tab events in different main-tabs are being duplicated
virt 953340 console from rhevm-shell/ovirt-shell using spicec does not work (linux client)
virt 975730 [RFE] pass session id to spice via mime type to allow spice Menu Using REST
virt 987957 [RFE] edit VM dialog - nics appear in random order (not sorted by name)
virt 1031040 [RFE] RunOnce dialog can not set a vnc keymap itself
virt 1033547 [RFE] Configure both SPICE and VNC display console
virt 1035279 Allow to disable SSO per VM
virt 1038587 Show name of the template in General tab for a vm if the vm is deployed from template via clone allocation.
virt 1040088 [RFE] Add FreeBSD to the list of VM operating systems
virt 1043469 ovirt-guest-agent for openSUSE
virt 1043471 ovirt-guest-agent for SLES
virt 1043473 ovirt-guest-agent for Ubuntu
virt 1043474 ovirt-guest-agent for Debian
753296 [RFE] Enable FIPS mode
753306 SR-IOV support
753309 [RFE] Workaround for enable/disable services via persist cmd
806317 [RFE] ovirt-node regenerates kdump ramdisk image on every boot
832000 Reduce number of kargs to enable a better automated installation with PXE
846963 [oVirt-node] Upgrade ovirt-node with "ovirt_upgrade" parameter failed
850386 Introduce new systemd-rpm macros in ovirt-node spec file
893950 Make ovirt-node more FHS
908902 Add specififc log handlers (log files) for transactions and ui
909369 Use blivet during installation
918270 Refactor and isolate block device discovery
918957 [TUI] Confirmation for reboot
947406 Add notice field
947407 Status of caps-lock should be shown near password fields
953870 Migrate to livemedia-creator
966320 ovirt node will also enable ipv4 with dhcp protocol when only setting ipv6 with dhcp
966498 Change sensitivity of widgets recursively
969340 Migrate ovirt-node-installer backend and ovirt-auto-install backend to new code base
974609 Add correct suffixes to scripts
979067 [RFE] Add generic container handling
979078 [RFE] <RETURN> can be used to Save a page
979389 [RFE] use asciidoc for man pages
980064 [RFE] Add mouse support to the console
987824 [RFE] Need to add roll up and down ability to mouse control in multipage
988337 Shown incorrect info for the item "VLAN ID" after configured nic with "vlan".
988341 Should not create bond when report an error in configuration process
995994 Could not add Fedora host when its version becomes "oVirt Node Hypervisor"
997049 Allow nested transactions
1001947 KeyboardInterrupt Exception when click mouse on UI
1001950 RFE: same action on all ovirt-node-install page for press enter
1002176 Not enough debugging informations in log files
1002620 [RFE] Create central augeas object
1003234 password.py: Using "set_admin_password" to change admin password failed in single mode
1005148 [RFE] Add documentation on how to deploy Node with Puppet/Foreman
1007191 RFE: Support "BOOTIF=bondname" in auto-install parameters
1008891 Installer goes to next page after returning from shell
1011901 Report traceback infos about errors when starting ntpdate, rpcidmapd and rpcgssd services ...
1013520 Miss some console info to show status by using "ovirt-node-upgrade" to upgrade ovirt-node
1020227 /var/log/lastlog is missing
1021647 Shared configuration keys to pass management informations
1026646 Better to disable "enter" button works for the fan status table of ipmi page
1027110 Better to disable cim transaction run and prompt ConfirmationDialog when configuring cim without providing password
1027130 edit-node: Better to rename iso_name more simpler when install multiple packages
1027161 plugin info shown incorrectly in plugins page when install multiple packages
1029033 Link status shows disconnected although the cable is plugged.
1032373 [RFE] enhance edit-node man page for uid/gid options help info a bit more
1032374 [RFE] edit-node:Support specify multiple user, uid/group, gid elements changed
1035441 [RFE] Sync versions between ovirt-node and overall ovirt
Please set the target to 3.4.0 and add the bug to the tracker if you think that 3.4.0 should not be released without it fixed.
Please also update the target to 3.4.1 or any next release for bugs that won't be in 3.4.0: it will ease gathering the blocking bugs for next releases.
For those who want to help testing the bugs, I suggest to add yourself as QA contact for the bug.
--
Sandro Bonazzola
Better technology. Faster innovation. Powered by community collaboration.
See how it works at redhat.com
10 years, 5 months
[QE] oVirt 3.3.3 beta status
by Sandro Bonazzola
we're going to branch and build oVirt 3.3.3 beta on Monday 2014-01-13.
A bug tracker is available at [1] and it shows no bugs blocking the release
the following has been proposed as blocker for 3.3.3 or 3.4.0, not targeted to a specific version yet:
Bug 1035314 - vdsm-hook-nestedvt uses kvm_intel-only syntax
The following is a list of the non-blocking bugs still open with target 3.3.3:
Whiteboard Bug ID Summary
Whiteboard Bug ID Summary
infra 987982 When adding a host through the REST API, the error message says that "rootPassword" is required...
infra 1017267 Plaintext user passwords in async_tasks database
infra 1040022 vdsm-tool configurre errors when installing vdsm package
integration 902979 ovirt-live - firefox doesn't trust the installed engine
integration 1021805 [RFE] oVirt Live - use motd to show the admin password
integration 1022440 [RFE] AIO - configure the AIO host to be a gluster cluster/host
integration 1026930 Package virtio-win and put it in ovirt repositories
integration 1026933 pre-populate ISO domain with virtio-win ISO
network 906313 [oVirt-webadmin] [setupNetworks] "No valid Operation for <network_name> and Unassigned Logical Networks panel"
network 987916 [oVirt] [provider] Dialog doesn't update unless focus lost
network 997197 Some AppErrors messages are grammatically incorrect (singular vs plural)
network 1023722 [oVirt-webadmin][network] Network roles in cluster management should be radio buttons
sla 1049343 [oVirt] Disabled Balloon in Add Vm
storage 987917 [oVirt] [glance] API version not specified in provider dialog
ux 906394 [oVirt-webadmin] [network] Loading animation in network main tab 'hosts' and 'vms' subtab is stuck...
virt 1007940 Cannot clone from snapshot while using GlusterFS as POSIX Storage Domain
906257 USB Flash Drive install of ovirt-node created via dd fails
923049 ovirt-node fails to boot from local disk under UEFI mode
965583 [RFE] add shortcut key on TUI
976675 [wiki] Update contribution page
979350 Changes admin password in the first time when log in is failed while finished auto-install
979390 [RFE] Split defaults.py into smaller pieces
982232 performance page takes >1sec to load (on first load)
984441 kdump page crashed before configuring the network after ovirt-node intalled
986285 UI crashes when no bond name is given
991267 [RFE] Add TUI information to log file.
1018374 ovirt-node-iso-3.0.1-1.0.2.vdsm.fc19: Failed on Auto-install
1018710 [RFE] Enhance API documentation
1032035 [RFE]re-write auto install function for the cim plugin
1033286 ovirt-node-plugin-vdsm can not be added to ovirt node el6 base image
Maintainers:
Please add the bugs to the tracker if you think that 3.3.3 should not be released without them fixed.
Please re-target all bugs you don't think that should block 3.3.3.
For those who want to help testing the bugs, I suggest to add yourself as QA contact for the bug and add yourself to the testing page [2].
Maintainers are welcomed to start filling release notes, the page has been created here [3]
[1] http://bugzilla.redhat.com/1050084
[2] http://www.ovirt.org/Testing/Ovirt_3.3.3_testing
[3] http://www.ovirt.org/OVirt_3.3.3_release_notes
Thanks,
--
Sandro Bonazzola
Better technology. Faster innovation. Powered by community collaboration.
See how it works at redhat.com
10 years, 5 months
Re: [vdsm] [Users] Issues installing hosted-engine with 3.4.0 alpha
by Sandro Bonazzola
Il 14/01/2014 03:39, Andrew Lau ha scritto:
> It looks like vdsm is trying to execute:
> vdsm-tool unified_network_persistence_upgrade
>
> But my version of vdsm-tool has it labeled as "upgrade-unified-persistence"
vdsm people, can you check this?
>
> On Tue, Jan 14, 2014 at 1:32 PM, Andrew Lau <andrew(a)andrewklau.com <mailto:andrew@andrewklau.com>> wrote:
>
> Hi,
>
> I'm giving the new hosted-engine feature a try with the new 3.4.0 alpha build on centos 6.5
>
> hosted-engine --deply seems to fail at the 'Environment setup"
> [ ERROR ] Failed to execute stage 'Environment setup': Command '/sbin/service' failed to execute
>
> Within the logs I believe it seems to be related to vdsm. Logs show "VDS daemon is not running"
>
> service vdsm start gives the following error:
>
> initctl: Job is already running: libvirtd
> vdsm: Running mkdirs
> vdsm: Running configure_coredump
> vdsm: Running run_init_hooks
> vdsm: Running gencerts
> vdsm: Running check_is_configured
> libvirt is already configured for vdsm
> sanlock service is already configured
> vdsm: Running validate_configuration
> SUCCESS: ssl configured to true. No conflicts
> vdsm: Running prepare_transient_repository
> vdsm: Running syslog_available
> vdsm: Running nwfilter
> vdsm: Running dummybr
> vdsm: Running load_needed_modules
> vdsm: Running tune_system
> vdsm: Running test_space
> vdsm: Running test_lo
> vdsm: Running restore_nets
> vdsm: Running unified_network_persistence_upgrade
> Usage: /usr/bin/vdsm-tool [options] <action> [arguments]
>
> Valid options:
> -h, --help
>
> Commands in module configurator:
> configure Configure external services for vdsm
> is-configured Determine if module is configured
> validate-config Determine if configuration is valid
>
> Commands in module dummybr:
> dummybr Defines dummy bridge on libvirt network.
>
> Commands in module load_needed_modules:
> load-needed-modules Load needed modules
>
> Commands in module nwfilter:
> nwfilter Defines network filters on libvirt
>
> Commands in module passwd:
> set-saslpasswd Set vdsm password for libvirt connection
>
> Commands in module restore_nets:
> restore-nets Restores the networks to what was
> previously persisted via vdsm.
>
> Commands in module seboolsetup:
> sebool-config Enable the required selinux booleans
> sebool-unconfig Disable the required selinux booleans
>
> Commands in module service:
> service-disable Disable a system service
> service-is-managed Check the existence of a service
> service-reload Notify a system service to reload
> configurations
> service-restart Restart a system service
> service-start Start a system service
> service-status Get status of a system service
> service-stop Stop a system service
>
> Commands in module transient:
> cleanup-transient-repository Cleanup the unused transient disks
> present in the repository. (NOTE: it
> is recommended to NOT execute this
> command when the vdsm daemon is
> running)
> setup-transient-repository Prepare the transient disks
> repository
>
> Commands in module unified_persistence:
> upgrade-unified-persistence Upgrade host networking persistence
> from ifcfg to unified if the
> persistence model is set as unified in
> /usr/lib64/python2.X/site-packages/
> vdsm/config.py
>
> Commands in module upgrade:
>
> Commands in module upgrade_300_networks:
> upgrade-3.0.0-networks Since ovirt-3.0, Vdsm uses libvirt
> networks (with names vdsm-*) to store its
> own networks. Older Vdsms did not have those
> defined, and used only linux bridges. This
> command is kept as an upgrade tool for the
> (very few) people who still have such old
> setups running.
>
> Commands in module validate_ovirt_certs:
> validate-ovirt-certs Validate vdsmcert.pem against cacert.pem.
> If current cacert.pem is invalidate, it will
> find a validate certificate file and replace
> the old cacert.pem with it. And then persist it.
>
> Commands in module vdsm-id:
> vdsm-id Printing host uuid
>
> vdsm: failed to execute unified_network_persistence_upgrade, error code 1
> vdsm start [FAILED]
>
> Any suggestions?
>
> Thanks,
> Andrew
>
>
>
>
> _______________________________________________
> Users mailing list
> Users(a)ovirt.org
> http://lists.ovirt.org/mailman/listinfo/users
>
--
Sandro Bonazzola
Better technology. Faster innovation. Powered by community collaboration.
See how it works at redhat.com
10 years, 5 months
Smarter network_setup hooks
by Dan Kenigsberg
Recently, Miguel Angel Ajo (CCed) has added a nice functionality to the
implementation of setupNetworks in Vdsm: two hook points where added:
before and after the setupNetworks verb takes place.
This is useful because sometimes, Vdsm's configuration is not good
enough for the user. For example, someone may need to set various
ETHTOOL_OPTS on a nic. Now, they can put a script under
/usr/libexec/vdsm/after_network_setup/ that tweak their ifcfg-eth*
files after they have been written by Vdsm.
However, the hook script only knows that *a* change of network
configuration took place. It does not know which change took place, and
has to figure this out on its own.
Enters http://gerrit.ovirt.org/20330 "allow hooks to pass down
dictionaries in json format".
I'd like to discuss it here, as it introduces a new Vdsm/Hook API that
is quite different than what we have for other hooks. Unlike with Vm
and VmDevice creation, where Vdsm uses libvirt's xml definition
internally as well as to communicate with the hooks,
before/after_network_setup have to define their own means of
communication.
I would like to suggest to use the same information passed on the
Engine/Vdsm API, and extend its reach into the hook script. The three
arguments to setupNetworks(networks, bondings, options) would be dumped
as json strings, to be read by the hook script.
This option is very simple to use and implement, it gives the hook all
the information that Vdsm-proper has, and allows for greatest
flexibility for hook writers. This is also the down side of this idea:
hook script may do all kinds of things with this information, some of
them unsupportable, and they should be notified when Engine/Vdsm API
changes.
In my opinion, it is a small price to pay: hooks have always had the
China Store Rule - if you break something, you own it. Hook users must
know what they're doing, and take care not to use deprecated bits of the
API.
What is your opinion? Comments and suggestions are most welcome!
Dan.
10 years, 5 months
gerrit upgrade
by iheim@redhat.com
with gerrit 2.8 released a month ago having our fix for Configurable
external robots.txt file (thanks juan), I'm planning to upgrade next
monday (January 13th) to 2.8.
other noteworthy changes - worth reading those with asterisk(*).
gerrit 2.7[1]
- New /a/tools URL.
This allows users to download the commit-msg hook via the command
line if the Gerrit server requires authentication globally.
- Gerrit Trigger Plugin in Jenkins
WARNING: Upgrading to 2.7 may cause the Gerrit Trigger Plugin in
Jenkins to stop working. Please see the "New Stream Events global
capability" section below.
gerrit 2.8[2]
* New change screen with completely redesigned UI and fully using the
REST API.
Users can choose which one to use in their personal preferences,
either using the site default or explicitly choosing the old one or
new one.
- Secondary indexing with Lucene and Solr.
- Lots of new REST API endpoints.
- New UI extension and JavaScript API for plugins.
- New build system using Facebook’s Buck.
- New core plugin: Download Commands.
- Configurable external robots.txt file.
* Labels can be configured to copy scores forward to new patch sets if
there is no code change.
* Labels can be configured to copy scores forward to new patch sets for
trivial rebases.
* New button to cherry-pick the change to another branch.
* When issuing a rebase via the Web UI, the committer is now the logged
in user, rather than "Gerrit Code Review".
Thanks,
Itamar
[1]
https://gerrit-documentation.storage.googleapis.com/ReleaseNotes/ReleaseN...
[2]
https://gerrit-documentation.storage.googleapis.com/ReleaseNotes/ReleaseN...
10 years, 5 months
Re: [vdsm] [Users] Unable to delete a snapshot
by Sandro Bonazzola
Il 12/01/2014 10:40, Maor Lipchuk ha scritto:
> Adding Sandro to the thread
>
> On 01/12/2014 11:26 AM, Maor Lipchuk wrote:
>> On 01/09/2014 12:29 PM, Nicolas Ecarnot wrote:
>>> Hi Maor, hi everyone,
>>>
>>> Le 07/01/2014 04:09, Maor Lipchuk a écrit :
>>>> Looking at bugzilla, it could be related to
>>>> https://bugzilla.redhat.com/1029069
>>>> (based on the exception described at
>>>> https://bugzilla.redhat.com/show_bug.cgi?id=1029069#c1)
>>>
>>> In my case, there where nothing "live" : the VM was shut down when
>>> creating the snapshot as well as when tyring to delete it.
>> I understand though live storage migration sub flows are, creation of
>> live snapshot, so it could be related.
>>>
>>>> The issue there was fixed after an upgrade to 3.3.1 (as Sander mentioned
>>>> it before in the mailing list)
>>>>
>>>> Could you give it a try and check if that works for you?
>>>
>>> I'm very shy with upgrading my oVirt production framework, but I began
>>> to read some things to upgrade it. Maybe you can lead me to a precise
>>> way to upgrade vdsm?
>> Sandro, do you aware of any documentation which can help in upgrading
>> ovirt, specifically VDSM?
No, I'm not aware of any documentation about it.
However since 3.3.1 is in ovirt-stable if you just need to update vdsm on a system I think that
yum --enablerepo=ovirt-stable update "vdsm*"
on that system should be enough.
CCing Dan and VDSM list for confirming
>>>
>>>> Also it will be great if you could open a bug on that with the full
>>>> VDSM, engine logs and the list of lvs.
>>>
>>> Done :
>>>
>>> https://bugzilla.redhat.com/show_bug.cgi?id=1050901
>> Thanks
>>>
>>
>> _______________________________________________
>> Users mailing list
>> Users(a)ovirt.org
>> http://lists.ovirt.org/mailman/listinfo/users
>>
>
--
Sandro Bonazzola
Better technology. Faster innovation. Powered by community collaboration.
See how it works at redhat.com
10 years, 5 months