[QE] oVirt 3.4.1 RC status
by Sandro Bonazzola
Hi,
We're going to tart composing oVirt 3.4.1 RC on 2014-04-23 09:00 UTC from 3.4 branches.
The bug tracker [1] shows no blocking bugs for the release
There are still 302 bugs [2] targeted to 3.4.1.
Excluding node and documentation bugs we still have 184 bugs [3] targeted to 3.4.1.
Please review them as soon as possible and retarget them to a future release.
Maintainers / Assignee:
- Please remember to rebuild your packages before 2014-04-23 09:00 UTC if you don't want
to use ovirt-3.4-snapshot packages
- Please add the bugs to the tracker if you think that 3.4.1 should not be released without them fixed.
- Please update the target to any next release for bugs that won't be in 3.4.1:
it will ease gathering the blocking bugs for next releases.
- Please fill release notes, the page has been created here [4]
- If you're going to test this release, please add yourself to the test page [5]
[1] https://bugzilla.redhat.com/1080483
[2] http://red.ht/1gCFOtH
[3] http://red.ht/1laBSUj
[4] http://www.ovirt.org/OVirt_3.4.1_release_notes
[5] http://www.ovirt.org/Testing/oVirt_3.4.1_testing
--
Sandro Bonazzola
Better technology. Faster innovation. Powered by community collaboration.
See how it works at redhat.com
10 years
Re: [ovirt-devel] Fwd: rpm deps
by Dan Kenigsberg
On Wed, Apr 30, 2014 at 09:41:40AM -0400, Piotr Kliczewski wrote:
> Adding to the discussion.
Your CC line was too huge. devel(a)ovirt.org should be used to such
discussions.
>
> Currently vdsm-xmlrpc rpm is required by vdsm and vdsm-cli rpms. Initially I suggested to have vdsm-jsonrpc required by vdsm-api but it do not seems to be good idea.
> I think that we need to add that dept to vdsm rpm in the same way as it is for vdsm-xmlrpc.
>
> I do not understand why we have decided to split jsonrpc code between two rpms:
>
> vdms-api:
> - vdsmapi-schema.json
>
> vdsm-jsonrpc:
> - BindingJsonRpc
> - Bridge
>
> vdsm-yajsonrpc:
> - __init__
> - betterAsyncore
> - stomp
> - stompReactor
>
> I understand that we may have schema in api package but do we really need two packages for jsonrpc?
> Currently we need a package for stomp reactor so I suggest for now to have one json(stomp) rpm and
> create second for amqp when there will be need for it.
I believe that the motivation for the current packaging was that
- yajsonrpc is not strictly vdsm-related. It is a candidate for a
spin-off
- jsonrpc is sever-side only
- api might be needed by clients, too. But I hope we'd have reasonable
inspection to avoid this need.
As long as vdsm can work without jsonrpc, I'd rather that it does not
require the package. When we move away of xmlrpc, we could drop the
xmlrpc requirement, too.
Dan.
10 years
Re: [ovirt-devel] Sanlock fencing reservations
by Dan Kenigsberg
On Wed, Feb 26, 2014 at 11:14:33AM -0500, Saggi Mizrahi wrote:
> 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.
> 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.
>
> Having an independent daemon to perform this task will give more room as to
> how to implement the feature.
Saggi, are you thinking about something similar to fence_sanlockd
http://linux.die.net/man/8/fence_sanlockd and its client fence_sanlock?
Using them, instead of reimplementing parts of them within Vdsm, seem
reasonable in first glance.
However
http://www.ovirt.org/Features/Sanlock_Fencing#Why_not_use_fence_sanlockd.3F
claim that it wastes 2G of storage and requires explicit master domain
upgrade.
Nir, could you explain why so much space is required by sanlockd? Can it
be configured to use smaller area?
>
> 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.
>
> 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.
10 years
[QE] oVirt 3.5.0 Alpha status
by Sandro Bonazzola
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
10 years
[Features] Special Request for Feature Page Cleanup Projecy
by Brian Proffitt
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
10 years
Remove bad tag in your local mom git repos
by Adam Litke
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
10 years
