- Devel - oVirt List Archives

[QE] oVirt 3.5.0 Alpha status
by Sandro Bonazzola 02 May '14

02 May '14

Hi, We're going to start composing oVirt 3.5.0 Alpha on 2014-05-09 08:00 UTC from master branches. The bug tracker [1] shows the following proposed blockers to be reviewed: Bug ID Whiteboard Status Summary 1001100 integration NEW Add log gathering for a new ovirt module (External scheduler) 1073944 integration ASSIGNED Add log gathering for a new ovirt module (External scheduler) 1060198 integration NEW [RFE] add support for Fedora 20 Feature freeze was on 2014-05-01 and the following features should be testable in 3.5.0 Alpha according to Features Status Table [2] infra 1054778 [RFE] Allow to perform fence operations from a host in another DC infra 1090803 [RFE] Change the "Slot" field to "Service Profile" when cisco_ucs is selected as the fencing type infra 1090794 [RFE] Search VMs based on MAC address from web-admin portal infra 1090793 consider the event type while printing events to engine.log infra 1090796 [RFE] Re-work engine ovirt-node host-deploy sequence infra-api 1090797 [RFE] RESTAPI: Add /tags sub-collection for Template resource infra 1090798 [RFE] Admin GUI - Add host uptime information to the "General" tab infra 1090808 [RFE] Ability to dismiss alerts and events from web-admin portal integration 1080402 Allow setup of iSCSI based storage for hosted engine integration 1080992 websocket proxy running on separate host network 1078836 Add a warning when adding display network network 1079719 Display of NIC Slave/Bond fault on Event Log storage 1054241 Store OVF on any domains storage 1083312 Disk alias recycling in web-admin portal virt 1058832 Allow to clone a (down) VM without snapshot/template virt 1031040 can't set different keymap for vnc via runonce option virt 1043471 oVirt guest agent for SLES virt 1083049 add progress bar for vm migration virt 1083065 EL 7 guest compatibility virt Allow guest serial number to be configurable virt 1047624 [RFE] support BIOS boot device menu virt 1083129 allows setting netbios name, locale, language and keyboard settings for windows vm's virt 1080002 [RFE] Enable user defined Windows Sysprep file infra-dwh 1091686 prevent OutOfMemoryError after starting the dwh service. Some more features may be included since they were near to be completed on last sync meeting. The table will be updated on next sync meeting scheduled for 2014-05-07. There are still 284 bugs [3] targeted to 3.5.0. Excluding node and documentation bugs we still have 242 bugs [4] targeted to 3.5.0. Maintainers / Assignee: - Please remember to rebuild your packages before 2014-05-09 08:00 UTC if needed, otherwise nightly snapshot will be taken. - If you find a blocker bug please remember to add it to the tracker [1] - Please start filling release notes, the page has been created here [5] All users: - You're welcome to join us testing this alpha release and getting involved in oVirt Quality Assurance[6]! [1] http://bugzilla.redhat.com/1073943 [2] http://bit.ly/17qBn6F [3] http://red.ht/1pVEk7H [4] http://red.ht/1rLCJwF [5] http://www.ovirt.org/OVirt_3.5_Release_Notes [6] http://www.ovirt.org/OVirt_Quality_Assurance Thanks, -- Sandro Bonazzola Better technology. Faster innovation. Powered by community collaboration. See how it works at redhat.com

1 0

[Features] Special Request for Feature Page Cleanup Projecy
by Brian Proffitt 01 May '14

01 May '14

All: It has been requested that we add date/timestamps to the Features pages in order to highlight the age of each page and assist users in determining how fresh information is. After investigating various options to do this within the database or using automated code, it seems that the old-fashioned manual way is still the best option. This is because an automated solution would only insert the needed strings, but not the actual data that pertains to that feature. To divide this work among the community, I have made an inventory of all of the features pages in the oVirt.org site as of 3/30/14, located at http://bit.ly/1iA1HQ3. If everyone can take a look at this sheet (check the tabs on the bottom, too) and find the pages they created or for which they are responsible, the following steps should be taken for pages that are marked "Yes" in "Needs Datestamp": 1. Add the following line to the top of each page, under the first heading: {{Feature|name=[Name of Feature]}|modules=[Node(s) of feature]|version=[oVirt version number]|status=Released}} 2. On the Feature page spreadsheet on Google Docs, change the "Yes" in "Needs Datestamp" to "No." This new Feature template string will add the time and date information to the page automatically. If, along the way, you find features that have been deprecated, or feature pages that are duplicates, these pages should be cleaned up as well. Ideally, this should not take too much time for each individual, and the effort will be a big step towards documentation consistency on the oVirt site. If you have any questions/concerns, send them my way. Thanks, BKP -- Brian Proffitt oVirt Community Manager Project Atomic Community Lead Open Source and Standards, Red Hat - http://community.redhat.com Phone: +1 574 383 9BKP IRC: bkp @ OFTC

2 2

Remove bad tag in your local mom git repos
by Adam Litke 01 May '14

01 May '14

Hi all, Recently it was discovered that the MOM repo git://gerrit.ovirt.org/mom had a bogus 'HEAD' tag. This is dangerous for obvious reasons. We have removed the tag from the server but you may still have it present in your local repository. To remove it just issue the following command from inside your mom source tree: git tag -d HEAD Please let me know if you experience any further issues. -- Adam Litke

1 0

Adjust engine to support arbitrary vlan device name
by Alona Kaplan 01 May '14

01 May '14

Hi all, This refactoring is targeted to 3.5. Please review the feature page and share your thoughts: http://www.ovirt.org/Feature/ArbitraryVlanDeviceName Thanks, Alona

4 5

vdsm installation error on fc20
by Vered Volansky 30 Apr '14

30 Apr '14

Hi, I'm trying to install vdsm on a fedora20 machine with the following error. I've been following http://www.ovirt.org/Download#Fedora_Installation_Instructions . I've also tried "yum clean all" - to no avail. Any idea anybody? Thanks, Vered ====================== ============================================================================================================================================================================================= Package Arch Version Repository Size =================================================================================================================================================================================================================== Installing: vdsm x86_64 4.14.6-0.fc20 ovirt-3.4-stable 752 k Installing for dependencies: vdsm-python x86_64 4.14.6-0.fc20 ovirt-3.4-stable 134 k vdsm-python-zombiereaper noarch 4.14.6-0.fc20 ovirt-3.4-stable 18 k vdsm-xmlrpc noarch 4.14.6-0.fc20 ovirt-3.4-stable 35 k Transaction Summary =================================================================================================================================================================================================================== Install 1 Package (+3 Dependent packages) Total download size: 938 k Installed size: 3.5 M Is this ok [y/d/N]: y Downloading packages: warning: /var/cache/yum/x86_64/20/ovirt-3.4-stable/packages/vdsm-python-4.14.6-0.fc20.x86_64.rpm: Header V4 RSA/SHA1 Signature, key ID fe590cb7: NOKEY ] 117 kB/s | 127 kB 00:00:06 ETA Public key for vdsm-python-4.14.6-0.fc20.x86_64.rpm is not installed (1/4): vdsm-python-4.14.6-0.fc20.x86_64.rpm | 134 kB 00:00:01 (2/4): vdsm-python-zombiereaper-4.14.6-0.fc20.noarch.rpm | 18 kB 00:00:00 (3/4): vdsm-xmlrpc-4.14.6-0.fc20.noarch.rpm | 35 kB 00:00:00 (4/4): vdsm-4.14.6-0.fc20.x86_64.rpm | 752 kB 00:00:03 ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- Total 236 kB/s | 938 kB 00:00:03 Public key for vdsm-python-zombiereaper-4.14.6-0.fc20.noarch.rpm is not installed

2 1

Re: [ovirt-devel] Sanlock fencing reservations
by Nir Soffer 30 Apr '14

30 Apr '14

----- Original Message ----- > From: "Saggi Mizrahi" <smizrahi(a)redhat.com> > To: "arch" <arch(a)ovirt.org> > Cc: "Nir Soffer" <nsoffer(a)redhat.com>, "David Teigland" <teigland(a)redhat.com> > Sent: Wednesday, February 26, 2014 6:14:33 PM > Subject: Sanlock fencing reservations > > I've recently been introduced to the this feature and I was wondering is this > really > the correct way to go for solving this particular problem. > > My main issue is with making two unrelated flow dependent. Hi Saggi, Sorry for the late response. The flows are related - sanlock already fencing as part of the lease and resources keeping. > By pushing this into the existing sanlock data structures you limit yourself > in the future from changing either to optimize or even solve problems for a > single use case. I agree, we have 196 unused bits in the sanlock lease, which can be used for other needs if we don't used them the new host_message api. We can keep the extra space forever - or use it now. > > Having an independent daemon to perform this task will give more room as to > how to implement the feature. I agree, but we are not designing this system from scratch, and adding this feature to the existing daemon is easy and makes sense. I thinks this is a good trade-off. > > I don't want to reach a situation where we need to change a sanlock struct > and not be able to do it as it makes problems with fencing flows. This is the price for choosing this way. > > I believe in the mantra that things should do one thing and do it well. > This feels like an ad-hoc solution to a very niche problem. > > > Further more, it kind of seems like a mailbox issue. > Leaving a fencing request is just a message. In the > future I can see it just being a suspend-to-disk request > so that you don't even have to fence the host in such cases. > > The only reason I see people putting it to sanlock is > that it's a daemon that reads from disk and has does fencing. > > I agree that in VDSMs current state putting this in the mailbox > is unreliable to say the least but it doesn't mean that we can't > have a small independent daemon to do the task until we get > messaging in VDSM to a stable state. > > IMHO it's better than having it as and ad-hoc feature to sanlock. > A feature which we can't remove later as someone might depend on it. > A feature that might limit us or that we might even abandon once we > have more reliable disk based messaging in VDSM. > I don't think we need another daemon that duplicate most of what sanlock is doing now, and I would not mix critical messages (fencing) with everyday messages in such new messaging solution. Regards, Nir

1 0

oVirt sources tagging
by Sandro Bonazzola 30 Apr '14

30 Apr '14

Hi, today I've seen that ovirt-hosted-engine-ha was missing proper tagging of version released. I've not checked all projects so this is just a reminder. Maintainers, please ensure that all previous releases are properly tagged (at least GA ones, but RC and beta are recommended too) and please remember to tag each time you release a new tarball. Thanks, -- Sandro Bonazzola Better technology. Faster innovation. Powered by community collaboration. See how it works at redhat.com

1 0

UI plugins using REST API
by Vojtech Szocs 30 Apr '14

30 Apr '14

Hi guys, just a quick note on UI plugin vs. REST API integration, there are currently two ways to work with REST API: * (standard) /ovirt-engine/api * (legacy) /api Please don't use the legacy URL, since "sessionId" that is acquired via RestApiSessionAcquired event handler [1] works only for the standard URL. (Also, don't forget to include "Prefer:persistent-auth" header when making calls that shouldn't close the session.) [1] http://www.ovirt.org/Features/UIPlugins#REST_API_integration Regards, Vojtech

4 7

oVirt 3.4.1 branching
by Sandro Bonazzola 30 Apr '14

30 Apr '14

Hi, we're going to create ovirt-engine-3.4.1 branch tomorrow morning 08:00 UTC in order to allow 3.4.2 development starting on 3.4 branch while we prepare for 3.4.1 GA release. So starting tomorrow morning, if you have patches targeted to 3.4.1 you'll need to push them on 3.4.1 branch too. Thanks, -- Sandro Bonazzola Better technology. Faster innovation. Powered by community collaboration. See how it works at redhat.com

1 1

short recap of today's vdsm call (29.4.2014)
by Dan Kenigsberg 29 Apr '14

29 Apr '14

Few things mentioned on today's call: - ovirt-3.3 is no longer supported: only security patches need to be merged there. - fenceSpmStorage turned into noop - intenetionally - infra code is expected to move around to its own subdir, as warned 2 weeks ago. - with pthreading used, any os.fork() causes a nasty warning Bug 1084500 - threading._after_fork spews "cannot notify on un-acquired lock" when os.fork is called from a thread - a huge json-rpc by Piotr needs to be broken to manageable pieces and reviewed. - Adam to create json-to-yaml schema conversion script (as a backward task) - sanlock fencing - Saggi's worries are to be addressed on the mailing list thread.

1 0