FWN/Issue167

From FedoraProject

< FWN
Jump to: navigation, search

Contents

Fedora Weekly News Issue 167

Welcome to Fedora Weekly News Issue 167 for the week ending March 8th, 2009.

http://fedoraproject.org/wiki/FWN/Issue167

This week Announcements links to some helpful "Fedora Classroom IRC Logs" including one on using mock. PlanetFedora big-ups several posts including David Lutterkort's explanation of how config file manipulation can be simplified using XPath to query Augeas. Marketing notes the latest meeting log. QualityAssurance reports that the last "Test Day" for Intel graphics chipsets was valuable and advertizes the next for XFCE. Developments summarizes the "Provenpackager Re-Seed" and watches aghast as the "Mono Conflagration Jumps to Blog". Artwork listens to some ideas about a "Theme Song". Virtualization reports the Xen "dom0 Kernel: Better, Still not Ready" and KVM "Snapshot Support Discussed".

If you are interested in contributing to Fedora Weekly News, please see our 'join' page[1]. We welcome reader feedback: fedora-news-list@redhat.com

  1. http://fedoraproject.org/wiki/NewsProject/Join

FWN Editorial Team: Pascal Calarco, Oisin Feeley, Huzaifa Sidhpurwala

Announcements

In this section, we cover announcements from the Fedora Project.

http://www.redhat.com/archives/fedora-announce-list/

http://www.redhat.com/archives/fedora-devel-announce/

http://fedoraproject.org/wiki/FedoraEvents

Contributing Writer: Chris Tyler

Fedora Classroom IRC Logs

Rahul Sundaram noted [1] that IRC logs were available for the Fedora Classroom [2] sessions held on March 7-8:

  1. http://www.redhat.com/archives/fedora-announce-list/2009-March/msg00003.html
  2. http://fedoraproject.org/wiki/Classroom
  3. http://fedoraproject.org/wiki/Introduction_to_bash_shell_scripting_Classroom_%2820090307%29
  4. http://fedoraproject.org/wiki/Training_and_Tips_for_Fedora_Ambassadors_Classroom_%2820090307%29
  5. http://fedoraproject.org/wiki/Fedora_Trademarks_Classroom_%2820090307%29
  6. http://fedoraproject.org/wiki/Perl_Basics_Classroom_%2820090307%29
  7. http://fedoraproject.org/wiki/Using_the_Windows_cross-compiler_Classroom_%2820090308%29
  8. http://fedoraproject.org/wiki/Introduction_to_Mock_Classroom_%2820090308%29

Upcoming Events

March 21: Free Software Embedded/Hardware workshop in Thiruvananthapuram, Kerala, India.

March 23-29: LUGM OpenWeek [1] in Manipal, India.

March 25: Document Freedom Day in Kolkata, India.

March 26: Infotech Niagara Beta Awards[2] in Buffalo, NY, USA.

March 26: Ithaca College EdTech Day[3] in Ithaca, NY USA.

  1. http://fedoraproject.org/wiki/FedoraEvents/LUGMopenweek
  2. http://www.infotechniagara.org/events/?id=193
  3. http://www.ithaca.edu/edtechday/

FUDCon Berlin 2009

FUDCon Berlin[1] will be held from June 26 - 28 in Berlin, Germany.

  1. http://fedoraproject.org/wiki/FUDConBerlin2009

Planet Fedora

In this section, we cover the highlights of Planet Fedora - an aggregation of blogs from Fedora contributors worldwide.

http://planet.fedoraproject.org

Contributing Writer: Adam Batkin

General

Dimitris Glezos analyzed[1] how Fedora's Localization community has grown (hint: a lot).

Will Woods mentioned[2] that in Fedora 11, all of the x86 that were previously .i386 will be replaced with .i586 (with requisite kernel arch changes too).

Jef Spaleta asked[3]: "How do we want casual users to do a Fedora Desktop install?" In other words, should Fedora be pushing new users towards DVD install media, or installable Live CDs?

Joseph Smidt wrote[4] about the massive number of users downloading Fedora. According to the statistics[5], around 100,000 new users have started using Fedora 10 since Fedora 9 (based on unique IPs checking in using yum).

Jeroen van Meeuwen responded[6] to an earlier post (that may have lacked context) by explaining how certain dependency checks would be handled in Cobbler for ris-linux and Windows provisioning.

David Lutterkort explained[7] how you can use Augeas and XPath to easily and uniformly query a system's configuration files.

Bastien Nocera boasted[8] about the new Gnome Volume Applet.

  1. http://dimitris.glezos.com/weblog/2009/03/08/flp-advancement-study
  2. http://qa-rockstar.livejournal.com/7478.html
  3. http://jspaleta.livejournal.com/36540.html
  4. http://californiaquantum.wordpress.com/2009/03/10/another-100000-week-for-fedora-10/
  5. http://fedoraproject.org/wiki/Statistics
  6. http://kanarip.livejournal.com/11912.html
  7. http://watzmann.net/blog/index.php/2009/03/11/querying_system_configuration
  8. http://www.hadess.net/2009/03/our-new-volume-feature.html

Marketing

In this section, we cover the Fedora Marketing Project.

http://fedoraproject.org/wiki/Marketing

Contributing Writer: Kam Salisbury

Marketing Meeting Log for 2009-03-10

The meeting log of the 2009-03-10 Fedora Marketing Meeting was made[1] available.

  1. http://fedoraproject.org/wiki/Meeting:Marketing_meeting_2009-03-10

Fedora 11 Features 80% Complete or Better

The Fedora 11 Features List[1] neared completion.

  1. http://fedoraproject.org/wiki/Releases/11/FeatureList

QualityAssurance

In this section, we cover the activities of the QA team[1].

Contributing Writer: Adam Williamson

  1. http://fedoraproject.org/wiki/QA

Test Days

This week's regular test day[1] was on the Intel graphics card driver, particularly kernel mode setting[2]. Kristian Høgsberg was the developer present. Several people showed up and provided valuable testing for the full set of test cases on various chips, giving a good overview of the current state of the driver in several situations. A follow-up event will be held before the release of Fedora 11 to check on the progress of fixes for the identified issues. Further testing in this area is still very helpful: the Wiki page contains full instructions on performing the range of tests, and the Results table is still available, so anyone with an Intel graphics adapter is encouraged to visit the Wiki page, perform the tests, and file bug reports as appropriate.

Next week will be special, as two test days are scheduled. A special test day is planned for Tuesday[3], on DeviceKit[4] - the partial HAL replacement scheduled to be included in Fedora 11. Anyone can help with this testing, so please come along and help out at the test day! The regular test day[5] will be on the Xfce desktop environment[6], particularly the new 4.6 release that will be part of Fedora 11. If Xfce is your desktop environment of choice, please come along and help make sure it'll be working properly in Fedora 11.

The DeviceKit test day will be held on Tuesday (2009-03-17) and the Xfce test day on Thursday (2009-03-19) in the #fedora-qa channel on Freenode IRC. Please come by to help make sure these features will be in shiny working order for Fedora 11!

  1. http://fedoraproject.org/wiki/QA/Test_Days/2009-03-12
  2. http://fedoraproject.org/wiki/Features/IntelKMS
  3. http://fedoraproject.org/wiki/QA/Test_Days/2009-03-17
  4. http://fedoraproject.org/wiki/Features/DeviceKit
  5. http://fedoraproject.org/wiki/QA/Test_Days/2009-03-19
  6. http://fedoraproject.org/wiki/Xfce

Weekly Meetings

The QA group weekly meeting[1] was held on 2009-03-11. The full log is available[2]. After a bracing discussion on how to send an apparently empty line to IRC, James Laska reported little progress in his work on making the Semantic test result reporting extension for mediawiki available as a package. He also deferred investigation of X.org test suites for next week. Adam Williamson noted that he had discussed one such suite, rendercheck, with Ben Skeggs, and he will make a package available either as a scratch build or in the official repository to be used in the upcoming nouveau Test Day. The group agreed to see if it might be useful for other graphics test events.

Jesse Keating and Will Woods reported that they had not had time to look at a method for identifying bugs caused by GCC 4.4 miscompilation issues. The group evaluated the response to the known bugs in this area, and decided that the responses suggested most issues would be resolved by fixes to GCC itself, and this should not cause major problems.

Adam Williamson reported that he and François Cami had spoken to the intel and radeon driver developers about holding test days for those graphics drivers, and were in the process of organizing both events.

Jesse Keating reported that a serious bug in squashfs in the Rawhide kernel was causing Rawhide installation to be impossible. This was to be fixed by a kernel update in the following day's Rawhide (which turned out indeed to be the case). He also reported that initial signing of packages for F11 was in progress in chunks, in order to ease the synchronization load for the mirroring system.

Jesse also reported that work on the substantial rewrite of Anaconda's storage code was in progress. The group agreed that this was quite close to the beta release, and that it seemed possible there could still be substantial problems in the code at the time the beta should be released, so discussed what kind of problems might be acceptable for a beta release and what might not. Despite some concern on the part of Will Woods, the group agreed to evaluate issues on a case-by-case basis, taking care to make sure all issues in this area were added to the beta release blocker bug so they would be evaluated.

The Bugzappers group weekly meeting[3] was held on 2009-03-10. The full log is available[4]. John Poelstra reminded the group to evaluate all bugs with regard to the Fedora 11 blocker ('F11Blocker') and Fedora 11 target ('F11Target') blocker bugs. He also announced that Monday 2009-03-16 will be a bug blocker day, for the maintainers, QA and release engineering groups to go over the list of blocker bugs.

The group agreed to require a short self-introduction email to fedora-test-list as the criterion for becoming a member of the fedorabugs group in FAS. Edward Kirk volunteered to write up this procedure into an SOP, as discussed at the previous meeting.

The group again discussed the Wiki re-design, particularly how the front page should be laid out and how the main information flow should work from there. Everyone agreed that it was important to keep the front page short and simple and lay out a clear linear path for potential new members to follow. The group agreed to wait for Adam Williamson to finish his combination of Edward Kirk's draft[5] and Christopher Beland's draft[6], with reference to the ideas discussed in the meeting. The group also discussed the new Tracking page (since re-arranged to become Components and Triagers [7]), and agreed it was a good layout, but some of the content that had been merged into it should not have been. Adam Williamson suggested that the statistics be updated regularly and automatically via Brennan Ashton's metrics script.

Edward Kirk reported that he had updated the bug workflow graphic[8] to reflect that NEEDINFO is no longer a status, but some members had trouble seeing the updated graphic due to caching issues.

The group discussed the potential new meeting time with reference to the availability matrix[9], but did not yet come to a decision.

The next QA weekly meeting will be held on 2009-03-18 at 1700 UTC (note changed time, in UTC reference frame) in #fedora-meeting, and the next Bugzappers weekly meeting on 2009-03-11 at 1500 UTC in #fedora-meeting.

  1. http://fedoraproject.org/wiki/QA/Meetings
  2. http://wwoods.fedorapeople.org/fedora-qa/fedora-qa-20090311.log.html
  3. http://fedoraproject.org/wiki/BugZappers/Meetings
  4. http://fedoraproject.org/wiki/BugZappers/Meetings/Minutes-2009-Mar-10
  5. http://fedoraproject.org/wiki/User:Tk009/bugzappers
  6. http://fedoraproject.org/wiki/User:Beland/BugZappers
  7. http://fedoraproject.org/wiki/BugZappers/Components_and_Triagers
  8. http://fedoraproject.org/wiki/BugZappers/BugStatusWorkFlow
  9. http://fedoraproject.org/wiki/Bugzappers_meeting_matrix

Bugzappers Wiki Re-organization

Christopher Beland worked hard to revise several areas of the Wiki, including a new Tracking page[1] which combined pages on active triagers, priority triage components, group goals and finding bugs[2]. After feedback from Edward Kirk, John Poelstra and others, this was reduced simply to the Components and Triagers page[3], leaving the others separate for now. Christopher updated these pages also. Adam Williamson submitted his combined new front page draft for the group's review[4].

  1. http://fedoraproject.org/wiki/BugZappers/Tracking
  2. http://www.redhat.com/archives/fedora-test-list/2009-March/msg00437.html
  3. http://fedoraproject.org/wiki/BugZappers/Components_and_Triagers
  4. http://www.redhat.com/archives/fedora-test-list/2009-March/msg00662.html

Advertising Triage Days

Christopher Beland pointed out that triage days are not advertised anywhere in the Wiki[1]. Adam Williamson apologized and explained[2] that this is because he is short on time at present as he is taking an internal Red Hat training course during his work days. He welcomed any help from the group in adding information about the triage day events to the Wiki.

  1. http://www.redhat.com/archives/fedora-test-list/2009-March/msg00695.html
  2. http://www.redhat.com/archives/fedora-test-list/2009-March/msg00713.html

Metrics

Christopher Beland reported[1] that he could not access the pages for Brennan Ashton's triage metrics reporting system. Brennan thanked him for the feedback[2] and explained that there was a hardware issue on the server. John Poelstra suggested[3] that the code for the metric system be hosted in the Bugzappers group's git repository.

  1. http://www.redhat.com/archives/fedora-test-list/2009-March/msg00693.html
  2. http://www.redhat.com/archives/fedora-test-list/2009-March/msg00727.html
  3. http://www.redhat.com/archives/fedora-test-list/2009-March/msg00739.html

Developments

In this section the people, personalities and debates on the @fedora-devel mailing list are summarized.

Contributing Writer: Oisin Feeley

GSoC InstantMirror

Warren Togami asked[1] for any interested parties to get involved with a GSoC[2] project to improve repository replication to mirrors.

  1. http://www.redhat.com/archives/fedora-devel-list/2009-March/msg00873.html
  2. http://code.google.com/soc/

Enhance Anaconda to Enable Repositories As Needed ?

Jud Craft reported[1] that installing from the Fedora 10 DVD with the fedora-updates repository enabled resulted in a broken NetworkManager due to a missing dependency on libudev.so.0. Jud pointed out[2] that although he could install the missing library from the DVD the situation would present a serious problem to anyone that tried "[...] a network install with updates [...] the result (a system without network access) can't be fixed without A) network access, or B) another Fedora image (also possibly requiring more network access)."

In answer to Jef Spaleta's questions Jud revealed[3] that: "[libudev.so.0] doesn't seem to actually be installed by the stock F10 image. If I do a plain install (no updates), NetworkManager works fine. Running a `yum update' then pulls down all the updates, as well as `Install libudev0'. So at some point I suppose NetworkManager picked up a dependency on libudev0, but for some reason updating during the installation process doesn't pull this new package in." Kevin Kofler[4] and Jesse Keating[5] both pointed out that: "[T]he updates repo isn't the Everything repo. To really do a proper install with updates you have to enable both the Updates repo and the Everything repo." Kevin added that this was why the install from DVD with updates enabled was not an officially supported method.

Several people, including Thorsten Leemhuis, suggested[6] that modifying the anaconda installer to be aware of which repositories depend on each other would be useful. Jesse Keating was[7] not averse to the idea as long as it could be done in a "[...] distro agnostic way. Avoiding hardcoded hacks specifically for Fedora is one of the goals of anaconda upstream."

Later Jeremy Katz explained[8] that the thinking behind the installer ignoring unsatisfiable dependencies in such cases is to "[...] get someone installed and then let them clean up afterwards[.]"

  1. http://www.redhat.com/archives/fedora-devel-list/2009-March/msg00921.html
  2. http://www.redhat.com/archives/fedora-devel-list/2009-March/msg00929.html
  3. http://www.redhat.com/archives/fedora-devel-list/2009-March/msg00938.html
  4. http://www.redhat.com/archives/fedora-devel-list/2009-March/msg00944.html
  5. http://www.redhat.com/archives/fedora-devel-list/2009-March/msg00947.html
  6. http://www.redhat.com/archives/fedora-devel-list/2009-March/msg00953.html
  7. http://www.redhat.com/archives/fedora-devel-list/2009-March/msg00955.html
  8. http://://www.redhat.com/archives/fedora-devel-list/2009-March/msg00976.html

Password Resets and Inactive Accounts

When Mike McGrath was perturbed[1] that so many FAS account holders had failed to reset their passwords recently a discussion of the entanglement of active account status and passwords followed.

Many respondents posted that they had received the email notifications but had not needed to, or had not had time to, perform their password reset.

[Tom Lane] worried that forcing periodic password resets caused people to weaken security by writing down their passwords but Bruno Wolf III argued[2] that a potentially bigger threat might be "[...] someone forging messages from Mike with deceptive URLs that trick people into changing their passwords using a hostile proxy. Doing things in the current manner is training people to get fooled." He added that cryptographically signing the reset messages was important.

Till Maas requested[3] consistent titling of the password reset notification emails, suggested extending the grace period beyond two weeks and asked that the notification contains the information that the contents of the user's fedorapeople.org home would be moved.

Mike McGrath and others explored[4] possible grace periods and numbers of warning emails.

Patrice Dumas asked why there was a password reset at all and was answered[5] by Jesse Keating that it was "[...] the best way Infra has today to discover all the active and inactive accounts." In response Toshio Kuratomi pointed[6] to an open ticket which nominally deals with how long accounts should be left open if passwords have expired but had become[7] an investigation of how account inactivity can be determined.

After Mike McGrath explained that "[...] we've got thousands of contributors, relatively few of them actually commit to cvs. So we could go around to figure out how to make all of our various auth points report back but that's a lot of work. The account system is the only common point of entry for every contributor [...]" Christopher Aillon suggested[8]: "So let's require to them to simply _log in_ to FAS to reset the timer (you need to do that to change passwords, anyway!)."

  1. http://www.redhat.com/archives/fedora-devel-list/2009-March/msg00509.html
  2. http://www.redhat.com/archives/fedora-devel-list/2009-March/msg00612.html
  3. http://www.redhat.com/archives/fedora-devel-list/2009-March/msg00710.html
  4. http://www.redhat.com/archives/fedora-devel-list/2009-March/msg00779.html
  5. http://www.redhat.com/archives/fedora-devel-list/2009-March/msg00658.html
  6. http://www.redhat.com/archives/fedora-devel-list/2009-March/msg00677.html
  7. http://fedorahosted.org/fedora-infrastructure/ticket/1237
  8. http://www.redhat.com/archives/fedora-devel-list/2009-March/msg00812.html

Mono Conflagration Jumps to Blog

Following the FESCo decision not to replace rhythmbox with banshee as the default media-player in Fedora 11[1] some follow-up clarifications were made by parties to the discussion and the conflagration jumped between @fedora-devel and the personal blog of David Nielsen, the Banshee ex-maintainer and perhaps the main force behind the Mono SIG[2].

Bill Nottingham put forward[3] a concise time-line which attempted to show that the proposal had been handled in a straightforward and usual manner. Bill noted that the Desktop SIG had expressed[4] a lack of enthusiasm early in the process and that the imminent beta-freeze meant that the decision had to be taken without further prolonged discussion.

AdamWilliamson suggested[5] that because Mono's Microsoft links worried many F/OSS developers it would have been a good idea to address such concerns: "[...] explicitly rather than just pretend they don't exist in your initial proposal (the word 'Mono' does not actually occur a single time in the initial version of the Wiki page you posted)."

A question put by Jóhann B. Guðmundsson wondered[6] whether there was anything preventing the Mono SIG from creating their own Fedora spin in which banshee was given pride of place as the default media-player. Rex Dieter confirmed that there were no obstacles on this path.

A proposal to adopt a Code of Conduct modeled upon Ubuntu's was[7] made by Richard W.M. Jones. He also expressed regret that David was leaving Fedora and apparently moving to Ubuntu as referenced[8] by a blog entry. Reading the blog suggest that Foresight Linux seems more to David's taste although one comment does point out[9] that Ubuntu "[...] head community people have been calling for volunteers to increase the work surrounding Mono and have a huge love for banshee[10] and Canonical isn’t anti-mono since some of their new job postings desire Mono as a skill[11]."

Seth Vidal was[12] among those who wondered specifically how such a code could be enforced and also where specifically the Fedora Project could be alleged to have engaged in misconduct on this issue. Reading David's blog seems to suggest both that any rudeness was privately exchanged and that his perception is[13] that "[...] Mono isn't welcome in Fedora, and will always be a second class citizen[.]"

  1. http://fedoraproject.org/wiki/FWN/Issue166#Fedora_11_Default_Mediaplayer_Not_Banshee._Mono_to_Blame_.3F
  2. http://fedoraproject.org/wiki/SIGs/Mono
  3. http://www.redhat.com/archives/fedora-devel-list/2009-March/msg00529.html
  4. http://www.redhat.com/archives/fedora-desktop-list/2009-February/msg00063.html
  5. http://www.redhat.com/archives/fedora-devel-list/2009-March/msg00526.html
  6. http://www.redhat.com/archives/fedora-devel-list/2009-March/msg00523.html
  7. http://www.redhat.com/archives/fedora-devel-list/2009-March/msg00498.html
  8. http://davidnielsen.wordpress.com/2009/03/07/drawing-my-own-conclusion/
  9. http://davidnielsen.wordpress.com/2009/03/07/drawing-my-own-conclusion/#comment-285
  10. http://castrojo.wordpress.com/2009/01/11/monodevelop-rockstar-needed-inquire-within/
  11. http://webapps.ubuntu.com/employment/canonical_GDOS/
  12. http://www.redhat.com/archives/fedora-devel-list/2009-March/msg00504.html
  13. http://davidnielsen.wordpress.com/2009/03/07/drawing-my-own-conclusion/#comment-297

Documentation Betas

John J. McDonough posted[1] that owners of major features should review the Beta release notes. Scott Radvan posted[2] that the Security Guide[3] would benefit from the scrutiny of any interested @fedora-devel readers.

  1. http://www.redhat.com/archives/fedora-devel-list/2009-March/msg00835.html
  2. http://www.redhat.com/archives/fedora-devel-list/2009-March/msg00823.html
  3. http://sradvan.fedorapeople.org/Security_Guide/en-US/

Provenpackager Re-Seed

Jon Stanley asked[1] that everyone read the process by which the "provenpackager" group will be repopulated.

A request by Ralf Corsepius for some definitions led Patrice Dumas to post[2] that: "provenpackagers are people who can change all the packages with opened ACLs. Sponsors are the people who can accept new contributors in fedora." Further discussion led[3] Michael Schwendt to voice a concern that non-responsive maintainers might be shielded from feedback if provenpackagers step in to update and upgrade packages. Kevin Kofler offered[4] the non-responsive maintainer process as a way to rectify any problems with Bugzilla tickets being ignored.

Michael Schwendt questioned[5] Patrice Dumas in greater detail as to why provenpackagers and sponsors are not equal sets.

Further details on how to apply to FESCo to become a provenpackager were elicited[6] from JoshBoyer by Stepan Kaspal.

In a separate thread MichelSalim asked[7] about the preferred way to become a sponsor.

  1. http://www.redhat.com/archives/fedora-devel-list/2009-March/msg00555.html
  2. http://www.redhat.com/archives/fedora-devel-list/2009-March/msg00571.html
  3. http://www.redhat.com/archives/fedora-devel-list/2009-March/msg00581.html
  4. http://www.redhat.com/archives/fedora-devel-list/2009-March/msg00718.html
  5. http://www.redhat.com/archives/fedora-devel-list/2009-March/msg00591.html
  6. http://www.redhat.com/archives/fedora-devel-list/2009-March/msg00594.html
  7. http://www.redhat.com/archives/fedora-devel-list/2009-March/msg00871.html

Closing Bugs NEXTRELEASE

Christoph Wickert requested[1] that all maintainers (and especially Red Hat developers) would "[p]lease fix your bugs [1] in the release they were filed against instead of just closing them NEXTRELASE!"

When Rahul Sundaram responded that it depended on the seriousness of the bug and complexity of back-porting Daniel P. Berrange[2] and Rakesh Pandit[3] acknowledged that such complex cases might exist but that suggested that this was often a cop-out which could discourage users.

Jeremy Katz responded[4] "[...] as the person who has apparently pissed you off this morning [...]" and described the case in point as much more complex than Christoph had claimed. It seemed that Christoph's ability to create LiveCD images of Fedora 11 using Fedora 10 as the development platform had been stymied by changes to syslinux. Jeremy added that even if this single change were reverted Christoph would need a newer kernel and squashfs-tools and more.

Later Jeremy clarified[5] that the combination of livecd-creator + mock were complicated by SELinux but that this had been addressed by recent work.

One complication is that Bodhi uses NEXTRELEASE even for updates to stable releases. After some confusion on this point LukeMacken posted[6] that anyone wanting to change the behavior should file a ticket.

  1. http://www.redhat.com/archives/fedora-devel-list/2009-March/msg00552.html
  2. http://www.redhat.com/archives/fedora-devel-list/2009-March/msg00575.html
  3. http://www.redhat.com/archives/fedora-devel-list/2009-March/msg00572.html
  4. http://www.redhat.com/archives/fedora-devel-list/2009-March/msg00622.html
  5. http://www.redhat.com/archives/fedora-devel-list/2009-March/msg00777.html
  6. http://www.redhat.com/archives/fedora-devel-list/2009-March/msg00672.html

Artwork

In this section, we cover the Fedora Artwork Project.

http://fedoraproject.org/wiki/Artwork

Contributing Writer: Nicu Buculei

Theme Song

Subodh Bhagat proposed[1] a new artistic initiative: a Fedora theme song. Subodh asked: "Do we have something like a theme song for fedora? Either lyrics or a composition?" The intitiative was saluted by Konstantinos Antonakoglou[2]: "Sounds great! I got some music skills (compose and play) too", Henrik Heigl[3]: "I also think of ideas like a contest", Paul Frields[4]: "I think song in general is a great idea. I'm a musician myself and an appreciator of songwriters", and Keiran Smith[5] all of whom have experience in the field.

  1. http://www.redhat.com/archives/fedora-art-list/2009-March/msg00060.html
  2. http://www.redhat.com/archives/fedora-art-list/2009-March/msg00062.html
  3. http://www.redhat.com/archives/fedora-art-list/2009-March/msg00064.html
  4. http://www.redhat.com/archives/fedora-art-list/2009-March/msg00065.html
  5. http://www.redhat.com/archives/fedora-art-list/2009-March/msg00068.html

Artwork for the Beta Release

In preparation for the upcoming Beta release, Paolo Leoni started[1] the work on a website banner by proposing two graphic concepts, a generic one and another based on the graphics for the Beta wallpaper image "The first is a non-themed version, while the second uses a part of Mo's wallpaper mockup." The general opinion was favourable to the themed version and after a few iterations, Máirí­n Duffy concluded[2] with a final version[3], a graphic which all the Fedora enthusiast are invited to use on their blogs.

On a related note, Paul Frields reviewed[4] the Art's Team release tasks[5] and produced a short list "the listed splashes, headers and other art scheduled for March 27 includes" to check the status "Is the listed date of March 27 enough time to produce these various derivations?"

  1. http://www.redhat.com/archives/fedora-art-list/2009-March/msg00072.html
  2. http://www.redhat.com/archives/fedora-art-list/2009-March/msg00088.html
  3. http://fedoraproject.org/wiki/Image:Deepsky-fedora11-beta-banner_2d.png
  4. http://www.redhat.com/archives/fedora-art-list/2009-March/msg00075.html
  5. http://poelstra.fedorapeople.org/schedules/f-11/f-11-art-tasks

Virtualization

In this section, we cover discussion on the @et-mgmnt-tools-list, @fedora-xen-list, @libvirt-list and @ovirt-devel-list of Fedora virtualization technologies.

Contributing Writer: Dale Bewley

Enterprise Management Tools List

This section contains the discussion happening on the et-mgmt-tools list

New Release virt-manager 0.7.0

Cole Robinson announced[1] a new Package-x-generic-16.pngvirt-manager[2] release, version 0.7.0.

Virtual Machine Manager provides a graphical tool for administering virtual machines for KVM, Xen, and QEmu. Start, stop, add or remove virtual devices, connect to a graphical or serial console, and see resource usage statistics for existing VMs on local or remote machines. Uses Package-x-generic-16.pnglibvirt as the backend management API.

New features:

  • Redesigned 'New Virtual Machine' wizard (Jeremy Perry, Tim Allen, Cole Robinson)
  • Option to remove storage when deleting a virtual machine.
  • File browser[3] for libvirt storage pools and volumes, for use when attaching storage to a new or existing guest.
  • Physical device assignment (PCI, USB) for existing virtual machines.
  • Bug fixes and minor improvements.
  1. http://www.redhat.com/archives/et-mgmt-tools/2009-March/msg00058.html
  2. http://virt-manager.org/
  3. http://www.redhat.com/archives/et-mgmt-tools/2009-March/msg00045.html

New Release virtinst 0.4.3

Cole Robinson announced[1] a new Package-x-generic-16.pngpython-virtinst release, version 0.400.3.

virtinst is a module that helps build and install libvirt based virtual machines. It currently supports KVM, QEmu and Xen virtual machines. Package includes several command line utilities, including virt-install (build and install new VMs) and virt-clone (clone an existing virtual machine).

This is largely a bug fix release.

  1. http://www.redhat.com/archives/et-mgmt-tools/2009-March/msg00057.html

Fedora Xen List

This section contains the discussion happening on the fedora-xen list.

dom0 Kernel: Better, Still Not Ready

Itamar Reis Peixoto reported[1] success with Michael Young's latest Package-x-generic-16.pngkernel build[2] and wondered when it could be released.

Michael explained, "The current plan is to wait until basic dom0 support makes it into the vanilla kernel, which should happen for 2.6.30, and then decide if dom0 can be enabled and if the patches for full dom0 support can safely be added without affecting ordinary operation."

"At the moment there are still things that are broken such as X support in some cases, and there are also Fedora patches that have been omitted because they were tricky to merge, so it is too early to start adding dom0 support to official Fedora kernels."

  1. http://www.redhat.com/archives/fedora-xen/2009-March/msg00046.html
  2. http://koji.fedoraproject.org/koji/taskinfo?taskID=1238587

Missing Hypervisor Capabilities Restored

There was progress on a bug discovered[1] last week. This missing file /sys/hypervisor/properties/capabilities has been restored[2], however a bug[3] remained[4] in libvirt or virt-install.

  1. http://fedoraproject.org/wiki/FWN/Issue166#dom0_Kernel_Inches_Closer
  2. http://www.redhat.com/archives/fedora-xen/2009-March/msg00039.html
  3. https://bugzilla.redhat.com/show_bug.cgi?id=489799
  4. http://www.redhat.com/archives/fedora-xen/2009-March/msg00040.html

Libvirt List

This section contains the discussion happening on the libvir-list.

Snapshot Support Discussed

In an attempt to make it easier to backup KVM windows guests, Matt McCowan created[1] a checkpoint virsh function. "Modelled on the virDomainSave[2] function it takes an optional script which it will execute (and pass the name of the domain as an argument) while the domain is paused, then resume the domain." Within this script, a backup of the guest domain could be created.

The patch was seen as too ad-hoc, and not accepted as-is.

Daniel Veillard commented[3] "I think this can help administrators in a controlled situation, but I'm hoping a real snapshotting API will be possible at some point where Package-x-generic-16.pnglibvirt goes though the list of storage resources used by the domain and properly make a snapshot using a storage API or return an error if that's not possible."

Daniel P. Berrange described[4] what he would like to see. "In terms of API I think I'd like to see snapshotting[5] available as part of a more generic save/restore API. I tend to think of the current API as providing 'unmanaged save/restore'". Libvirt does not track saved images, so does not know if a snapshot is available to be started at the restart of libvirtd."

"Thus I think the first step towards a general snapshot facility would be to provide an API for 'managed save/restore' where we explicitly track saved images." "With this, you could configure libvirtd, so that when starting up, it" would "see if the guest was suspended before the previous host shutdown, and if so, then restore from that saved image automatically.[6] Or make it skip autostart completely, if any save images exist, and allow an admin defined initscript to do auto restore from the save image."

  1. http://www.redhat.com/archives/libvir-list/2009-March/msg00177.html
  2. http://libvirt.org/html/libvirt-libvirt.html#virDomainSave
  3. http://www.redhat.com/archives/libvir-list/2009-March/msg00199.html
  4. http://www.redhat.com/archives/libvir-list/2009-March/msg00205.html
  5. http://wiki.libvirt.org/page/TodoVMSnapshots
  6. http://wiki.libvirt.org/page/TodoDaemonRestart

Memory Ballooning Support for QEMU

Daniel Berrange patched[1] the libvirt QEMU driver to fully support memory ballooning. "Memory ballooning allows you to have your guest dynamically change it’s memory usage by evicting unused memory during runtime. This is a useful feature because it reduces the impact your guest can have on memory usage of your host by giving up unused memory back to the host."[2]

  1. http://www.redhat.com/archives/libvir-list/2009-March/msg00200.html
  2. http://www.linux-kvm.com/content/memory-ballooning-feature-coming-soon-kvm