Fedora News on Zikula
by Eric Christensen
Last Wednesday the Zikula team met to discuss our current progress for
rolling out Zikula as the CMS replacement for docs.fp.o. During that
meeting it was discussed that the News Project is also interested in
using Zikula as well.
We've created a development status page[1] for Zikula which includes
information on our meetings, links to the previous meeting minutes, and
a list of modules that are needed to be packaged. I'd like for someone
from the News project to join us at our meetings so we can better learn
what is needed to make Zikula work for News!
I'd also like to point out that there are many different modules[2]
available for Zikula. If you see something that you'd like to
incorporate into the News instance of Zikula please feel free to put it
on the list[1] under "Required for Fedora Weekly News". If you would
like to package it we have template SPEC files available to help.
Otherwise let Eric (Sparks)[3] or David (KE4QQQ)[4] know that it needs
to be packaged and we'll put it on the to-do list.
I'd appreciate someone contacting me (either on this list, the logistics
list, or direct) so I will have a point-of-contact for this project.
[1] https://fedoraproject.org/wiki/Zikula
[2] http://community.zikula.org/module-Extensions.htm
[3] https://fedoraproject.org/wiki/User:Sparks
[4] https://fedoraproject.org/wiki/User:Ke4qqq
Thanks,
Eric
14 years, 7 months
Zikula needs
by Paul W. Frields
Pascal (and anyone else interested),
As you know, there's a team of people working on fielding a content
management system, Zikula, for use by various Fedora teams. Some
teams already have established requirements. I'd like to establish a
list of what your team would like to do with Zikula as well. If that
list already exists somewhere, feel free to point me to it. If not,
this would be a good time for us to put it together.
* Ideally, how often does the team want to see news produced?
* Would you want to produce a continuous feed, or have a regular
publication date?
* Are there wish-list features in publishing the wiki doesn't offer
that the Zikula CMS might provide? (RSS, community story
submission, others...)
I'm open to a set meeting time, or we can hash this out on the list
here. Ideally, I'd like to have this input gathered by Monday night,
so I can pass it on to the rest of the Zikula team.
--
Paul W. Frields http://paul.frields.org/
gpg fingerprint: 3DA6 A0AC 6D58 FEC4 0233 5906 ACDB C937 BD11 3717
http://redhat.com/ - - - - http://pfrields.fedorapeople.org/
irc.freenode.net: stickster @ #fedora-docs, #fedora-devel, #fredlug
14 years, 8 months
sorry about announcements beat
by Max Spevack
I had a very busy week, a very busy weekend (work-related stuff), and I
was on a plane on Monday, and simply didn't have the opportunity to get
to the announcements beat.
I'll pick it up next week. My apologies.
--Max
14 years, 9 months
Fedora Weekly News 186
by Pascal Calarco
* 1 Fedora Weekly News Issue 186
o 1.1 Planet Fedora
+ 1.1.1 General
+ 1.1.2 POSSE Roundup
o 1.2 QualityAssurance
+ 1.2.1 Test Days
+ 1.2.2 Weekly meetings
+ 1.2.3 F12 Alpha blocker bug review meeting
+ 1.2.4 Xfce spin testing
+ 1.2.5 KDE QA tester request
+ 1.2.6 Bugzilla semantics debate
o 1.3 Translation
+ 1.3.1 F12 Translation Team Schedule Proposal
+ 1.3.2 Translation Quick Start Guide Updated
+ 1.3.3 Publican Version of Minor Fedora Documents Made Available
+ 1.3.4 New Members in FLP
o 1.4 Artwork
+ 1.4.1 Evaluating the Gallery
+ 1.4.2 A Small Icon Request
+ 1.4.3 Fedora 12 Theming Progress
o 1.5 Virtualization
+ 1.5.1 Fedora Virtualization List
# 1.5.1.1 New Release libguestfs 1.0.64
# 1.5.1.2 Swap Use in Guests
# 1.5.1.3 Clustering libvirt Hosts
+ 1.5.2 Virtualization Tools List
# 1.5.2.1 Virtual Machine Cloning
# 1.5.2.2 Virt Manager UI Rework
# 1.5.2.3 Support for Processor Affinity
# 1.5.2.4 Virt What?
- Fedora Weekly News Issue 186 -
Welcome to Fedora Weekly News Issue 186[1] for the week ending July 26,
2009.
In this week's issue, we begin with news from the Fedora Planet,
including tips on running Fedora 11 on an Intel Mac, tethering Fedora 11
to an iPhone, and another in the series of XI2 Recipes. Quality
Assurance reports on last week's Fit and Finish test day on power
management and suspend/resume, as well as much detail on QA-related
weekly meetings. Translation brings us detail of the Fedora 12
Translation Schedule, a new Translation Quick Start Guide, as well as
new Publican version of some Fedora documentation In Artwork/Design
news, testing details of the new gallery and an update on Fedora 12
theming, amongst other topics. This issue rounds out with Fedora
virtualization goodness, including details on new versions of
libguestfs, virt-what and redesigns of the virt-manager UI, as well as
details on how to cluster libvirt hosts. We hope you enjoy this week's FWN!
If you are interested in contributing to Fedora Weekly News, please see
our 'join' page[2]. We welcome reader feedback: fedora-news-list(a)redhat.com
The Fedora News team is collaborating with Marketing and Docs to come up
with a new exciting platform for disseminating news and views on Fedora,
called Fedora Insight. If you are interested, please join the list and
let us know how you would like to assist with this effort.
FWN Editorial Team: Pascal Calarco, Adam Williamson
1. http://fedoraproject.org/wiki/FWN/Issue186
2. http://fedoraproject.org/wiki/NewsProject/Join
-- Planet Fedora --
In this section, we cover the highlights of Planet Fedora[1] - an
aggregation of blogs from Fedora contributors worldwide.
Contributing Writer: Adam Batkin
1. http://planet.fedoraproject.org
--- General ---
Greg DeKoenigsberg responded[1] to slashdot[2] to correct what Nicholas
Negroponte actually said regarding the Sugar UI and OLPC. "But what we
did...was we had Sugar do the power management, we had Sugar do the
wireless management -- it became sort of an omelet. The Bios talked
directly with Sugar, so Sugar became a bit of a mess. It should have
been much cleaner, like the way they offer [it] on a stick now."
Jef Spaleta was excited[3] by the news that all of Launchpad has finally
been open sourced by Canonical.
Harish Pillay questioned[4] Microsoft's true motives behind contributing
GPL patches to the Linux kernel. Martin Sourada quoted[5] Linus'
response to the general feeling of hatred toward Microsoft in the Linux
community.
Daniel Walsh explained[6] how the SELinux "unconfined" domain works.
Peter Hutterer added[7] part 5 to the XI2 Recipes series, explaining
"grabs" and part 6[8], showing examples dealing with the client pointer.
Steven Moix provided[9] a few tips for natively running Fedora 11 on an
Intel Mac.
Jesse Keating described[10] how to tether an iPhone to Fedora over
bluetooth, for a truly wires-free internet experience.
1. http://gregdek.livejournal.com/52052.html
2.
http://linux.slashdot.org/story/09/07/20/1628228/Negroponte-Sees-Sugar-As...
3. http://jspaleta.livejournal.com/45216.html
4. http://harishpillay.livejournal.com/162161.html
5. http://mso-chronicles.blogspot.com/2009/07/true-meaning-of-open.html
6. http://danwalsh.livejournal.com/30084.html
7. http://who-t.blogspot.com/2009/07/xi2-recipes-part-5.html
8. http://who-t.blogspot.com/2009/07/xi2-recipes-part-6.html
9.
http://www.alphatek.info/2009/07/22/natively-run-fedora-11-on-an-intel-mac/
10. http://jkeating.livejournal.com/75270.html
--- POSSE Roundup ---
The Professors Open Source Summer Experience[1] just finished its Summer
2009 session, and here is a roundup of some of the Planet posts from the
event.
* http://gregdek.livejournal.com/52300.html
* http://blog.melchua.com/2009/07/21/posse-monday-how-seneca-got-involved/
*
http://blog.melchua.com/2009/07/21/posse-monday-helping-students-find-pro...
*
http://blog.melchua.com/2009/07/22/posse-tuesday-contributor-types-and-ma...
* http://blog.melchua.com/2009/07/22/posse-wednesday-our-classroom-setup/
* http://michaeldehaan.net/2009/07/24/fedora-has-a-posse/
1. http://teachingopensource.org/index.php/POSSE
-- Quality Assurance --
In this section, we cover the activities of the QA team[1].
Contributing Writer: Adam Williamson
1. http://fedoraproject.org/wiki/QA
--- Test Days ---
There was no main track Test Day last week. The Fit and Finish project's
Test Day track continued with its second Test Day, on power management
and suspend/resume[1]. The event was a success, with several testers
turning out, many bugs filed, and some fixed during the day or soon
afterwards, especially relating to laptops with multiple batteries.
No Test Day is scheduled for next week. If you would like to propose a
main track Test Day for the Fedora 12 cycle, please contact the QA team
via email or IRC, or file a ticket in QA Trac[2].
1.
https://fedoraproject.org/wiki/Test_Day:2009-07-21_Fit_and_Finish:Batteri...
2. https://fedorahosted.org/fedora-qa/
--- Weekly meetings ---
The QA group weekly meeting[1] was held on 2009-07-22. The full log is
available[2]. James Laska reported that he had published a blog post
asking people to help with the process of writing Debugging pages[3].
Adam Williamson mentioned that he had looked into creating some of the
desired pages, but did not know what kind of information was actually
required for any of the components concerned. Jesse Keating suggested
doing an informal interview-style session with maintainers to discover
what information is needed, and then having QA take responsibility for
turning that information into a finished Wiki page.
James Laska had created a meeting time matrix[4] for the purpose of
re-scheduling the QA meeting to make it possible for as many group
members as possible to attend. The group agreed that the new meeting day
and time should be Mondays at 16:00 UTC, moved from Wednesdays at 16:00 UTC.
James Laska noted that a Fedora 12 Alpha blocker bug review meeting was
scheduled for Friday 2009-07-24. It was agreed that Adam Williamson
would send out an announcement of the meeting, and James would send out
a recap after it had finished. Jesse Keating mentioned it would be good
to do some Rawhide install testing prior to the meeting, but a
combination of two significant bugs was preventing almost any Rawhide
install from working.
James Laska explained that a test compose for Fedora 12 Alpha was
scheduled for 2009-07-29, and Liam Li had made an announcement
requesting help on install testing[5]. Jesse Keating pointed out that it
would not be easy for the general public to take part, as the test
compose would not be generally distributed. This led to another long
discussion about the practicality of distributing time-critical test
composes to the public. No definite conclusion was reached, but a
tentative agreement was made to look into a system which would allow
access to such composes to members of the QA group in FAS.
Jóhann Guðmundsson noted that there were some problems with Dracut, the
nash/mkinitrd replacement being introduced as a feature in Fedora 12. It
has no implementation plan by which the progress of the feature can be
externally measured, and no detailed contingency plan beyond 'revert to
mkinitrd'. Jóhann agreed to contact the feature mantainer, Harald Hoyer,
to help develop a full test plan and contingency plan.
Will Woods reported on the progress of the AutoQA project. He has now
automated the first four test cases in the Rawhide Acceptance Test
Plan[6], and is now working on automating the installation tests. He
noted that separate i386, x86-64 and PowerPC test hosts would be
necessary for some tests, and that PPC might be difficult in the absence
of the Fedora standard libvirt virtualization framework on that
platform. Jesse Keating worried that the installation tests may be
adding too much complexity to the system, and asked how much faster the
process would be if only repository level tests were considered. Adam
Williamson pointed out that the full set of repository level tests were
the ones that had already been automated. Will promised that they would
be updated to send the results somewhere publicly accessible soon.
Sebastian Dziallas brought up the topic of a Test Day for the Sugar on a
Stick project[7] - essentially for the integration of Sugar with a stock
Fedora distribution. It was agreed that the SoaS project would host the
Test Day themselves using the SOP created for this purpose[8]. A
tentative date of 2009-09-03 was agreed for the test day.
The Bugzappers group weekly meeting[9] was held on 2009-07-21. The full
log is available[10]. No-one had heard from Brennan Ashton regarding the
status of the triage metrics project. Adam Williamson agreed to contact
him by email to find out the current status, and ask if he would be
interested in having a co-maintainer on the project, in the interest of
smoother development.
The group discussed the current draft of the critical path-based triage
component list[11]. There was a general feeling that the list was very
long and might contain components that, practically speaking, would not
benefit hugely from triage. It also seemed to contain at least some
binary (rather than source) package names, while Bugzilla is based on
source package names. Niels Haase and Matej Cepl volunteered to adjust
the list to use source package names, and break it up into groups for
ease of digestion, for further review at next week's meeting.
Adam Williamson gave an update on the status of the kernel bug triage
project. He admitted it had not progressed very far as he had been
focussing on anaconda triage. He outlined a plan under which a volunteer
would, as a test, triage bugs on one particular component of the kernel,
to see if the process could be made to work. Edward Kirk thought the
proposal a sound one, and Adam agreed to try and put in into practice in
the next week.
Finally, the group discussed the 'Bugzilla Semantics' proposal Adam
Williamson had made to the mailing list, involving various ways in which
the triage process could be tweaked and the use of the NEW and ASSIGNED
states changed. Initially discussion was in favour of retaining the
status quo, but Jesse Keating and Josh Boyer made it clear that the
development groups they were involved in used ASSIGNED in a different
way to its use by the Bugzappers group, and they would prefer if
Bugzappers marked bugs as having been triaged in some other way, so
their groups could take advantage of the triage process. It became clear
that there would be both benefits and costs involved in changing the
triage process. Adam Williamson agreed to send a follow-up email to the
mailing list to summarize the current state of the debate, and to see if
a consensus could be found on a future path.
The next QA weekly meeting will be held on 2009-07-27 at 1600 UTC in
#fedora-meeting, and the next Bugzappers weekly meeting on 2009-07-28 at
1500 UTC in #fedora-meeting.
1. http://fedoraproject.org/wiki/QA/Meetings
2. http://fedoraproject.org/wiki/QA/Meetings/20090722
3. http://jlaska.livejournal.com/5693.html
4. http://fedoraproject.org/wiki/QA_Meeting_Matrix
5. http://www.redhat.com/archives/fedora-test-list/2009-July/msg00429.html
6. http://fedoraproject.org/wiki/QA:Rawhide_Acceptance_Test_Plan
7. http://wiki.sugarlabs.org/go/Sugar_on_a_Stick
8. http://fedoraproject.org/wiki/User:Adamwill/Draft_test_day_SOP
9. http://fedoraproject.org/wiki/BugZappers/Meetings
10.
http://meetbot.fedoraproject.org/fedora-meeting/2009-07-21/fedora-meeting...
11. http://fedoraproject.org/wiki/User:Arxs/CPCL
--- F12 Alpha blocker bug review meeting ---
Adam Williamson announced[1] the second blocker bug review meeting for
Fedora 12, to be held on 2009-07-24, mainly to review blocker bug status
for the upcoming Alpha release. Later, James Laska posted a recap of the
meeting[2].
1. http://www.redhat.com/archives/fedora-test-list/2009-July/msg00472.html
2. http://www.redhat.com/archives/fedora-test-list/2009-July/msg00498.html
--- Xfce spin testing ---
Adam Miller announced[1] the second test live image with the Xfce
desktop, and would appreciate testing and reporting of problems. He
noted that the known bugs in Anaconda at the time of the compose may
make the image very difficult to install, but it should be usable on
most hardware as a live boot.
1. http://www.redhat.com/archives/fedora-test-list/2009-July/msg00391.html
--- KDE QA tester request ---
Kevin Kofler posted a request[1] for volunteers to help with KDE
testing. He noted that the requirements for testers were quite low, and
asked interested people to reply to the fedora-kde mailing list or
#fedora-kde on IRC. Two people, Aioanei Rares and Marco Crosio, were
quick to volunteer, and were accepted as the new KDE testers.
1. http://www.redhat.com/archives/fedora-test-list/2009-July/msg00423.html
--- Bugzilla semantics debate ---
The Bugzilla semantics debate[1] continued throughout the week,
especially following the input from developers at the QA meeting (see
above) and the subsequent summary[2] posted by Adam Williamson. He
proposed three options: leaving the current triage process unchanged and
encouraging development teams who currently use ASSIGNED to mean a bug
has been accepted by a certain developer to use ON_QA instead; changing
Bugzappers practice to use a keyword to mark triaged bugs going forward,
but leave all existing bugs as they are; or changing Bugzappers practice
going forwards and also attempting to 'fix' existing bug reports to use
the keyword where appropriate. Jesse Keating seemed to favor the second
option[3], and John Poelstra agreed[4].
1. http://www.redhat.com/archives/fedora-test-list/2009-July/msg00309.html
2. http://www.redhat.com/archives/fedora-test-list/2009-July/msg00411.html
3. http://www.redhat.com/archives/fedora-test-list/2009-July/msg00412.html
4. http://www.redhat.com/archives/fedora-test-list/2009-July/msg00415.html
-- Translation --
This section covers the news surrounding the Fedora Translation (L10n)
Project[1].
Contributing Writer: Runa Bhattacharjee
1. http://fedoraproject.org/wiki/L10N
--- F12 Translation Team Schedule Proposal ---
The Fedora 12 Translation schedule has been drafted by John Poelstra and
shared[1] in the fedora-trans mailing list for feedback from the FLP.
Dimitris Glezos suggested[2] that the string freeze date can be pushed
back from 1.5 months prior to translation deadline to 1 month and to
rename the Release Notes translation task to indicate it as 'beta'.
Ankit Patel mentioned the need for a translation review period ahead of
the final packaging of the translated modules.
Additionally, John Poelstra and Paul Frields both requested[3] the
presence of a member from the FLSCo at the Release Readiness meetings.
1. https://www.redhat.com/archives/fedora-trans-list/2009-July/msg00033.html
2. https://www.redhat.com/archives/fedora-trans-list/2009-July/msg00034.html
3. https://www.redhat.com/archives/fedora-trans-list/2009-July/msg00036.html
--- Translation Quick Start Guide Updated ---
The maintainer of the Translation Quick Start Guide (TQSG), Noriko
Mizumoto informed[1] about the availability of the updated version of
this book. Some minor errors in the main document and a few translated
versions were also corrected after the updation[2].
1. https://www.redhat.com/archives/fedora-trans-list/2009-July/msg00051.html
2. https://www.redhat.com/archives/fedora-trans-list/2009-July/msg00065.html
--- Publican Version of Minor Fedora Documents Made Available ---
Ruediger Landmann announced the availability of a few existing Fedora
documents in a Publican ready format[1].
1. https://www.redhat.com/archives/fedora-trans-list/2009-July/msg00041.html
--- New Members in FLP ---
Noah Lee (Korean)[1], Robert Antoni Buj Gelonch (Catalan)[2], Josip
Šumečki (Croation)[3] joined the Fedora Localization Project recently.
1. https://www.redhat.com/archives/fedora-trans-list/2009-July/msg00035.html
2. https://www.redhat.com/archives/fedora-trans-list/2009-July/msg00058.html
3. https://www.redhat.com/archives/fedora-trans-list/2009-July/msg00074.html
-- Artwork --
In this section, we cover the Fedora Design Team[1].
Contributing Writer: Nicu Buculei
1. http://fedoraproject.org/wiki/Artwork
--- Evaluating the Gallery ---
After some time spent with the gallery test instance[1], Nicu Buculei
shared[2] of @design-team his impressions: "the current authentication
is a killer[...], is not easy to mass upload[...], there are only a few
[plugins] available[...], some operations are cumbersome". He also
showed concern about the small involvement of the team in testing "I see
only very few of us played with the gallery, which make me doubt it is a
popular/useful/wanted feature". In reply, Martin Sourada explained[3] it
by the little time passed and summer vacancies "given that it's been
around 11 days since Mo announced this[...] and seeing how many people
are active here during the summer vacations, it's quite understandable
that not many of us have tried it yet". After Martin questioned[4] the
legality of publishing wallpapers from old released, Paul Frields
intervened and confirmed[5] those are free: " these contributions to
Fedora should fall under a license that allows reuse, redistribution,
and remixes, although I suspect it's not Creative Commons."
1. http://publictest7.fedoraproject.org/gallery2/
2.
http://lists.fedoraproject.org/pipermail/design-team/2009-July/000487.html
3.
http://lists.fedoraproject.org/pipermail/design-team/2009-July/000489.html
4.
http://lists.fedoraproject.org/pipermail/design-team/2009-July/000492.html
5.
http://lists.fedoraproject.org/pipermail/design-team/2009-July/000504.html
--- A Small Icon Request ---
Matthias Clasen addressed[1] what he calls "a small icon request" to
@design-team: "With Gnome 2.28 in F12, it will be possible to have
different icons for the xdg dirs[...] It would be pretty cool if we
could create icons for this in a style that matches the existing
user-home icon in our default icon theme (ie the folder icon with an
overlayed embled in the Mist theme)" and in reply Andreas Nilsson
pointed[2] this is worked upstream by Lapo Calamandrei "It seems like
Lapo Calamandrei wanted to take care of this and create some 256x256
icons in the process. Hopefully this will land in gnome-themes soonish
(and in good time for 2.28/F12)."
1.
http://lists.fedoraproject.org/pipermail/design-team/2009-July/000499.html
2.
http://lists.fedoraproject.org/pipermail/design-team/2009-July/000505.html
--- Fedora 12 Theming Progress ---
Martin Sourada announced[1] a wiki page for hosting Fedora 12 theme
proposals "we've taken over the F12_Artwork wiki page[2] created by
bioinfornatics, cleaned it up and added the designs concepts I've found
in the design-team archives". He also announced the official page
holding a despription of the artwork process [3] and reminded the time
until the next deadline is passing fast "Also, according to our current
Schedule, we are past the concept submission deadline and have about
another eight days for working on the wallpapers we want to review for
F12 Alpha inclusion", encouraging people to submit their works "if you
have a design concept you like, focus your work onto it and help making
it awesome :-)"
On theming related news, MERCIER Jonathan asked for feedback[4] about
one of his design ideas "it's make with Blender, i can give blend file
what did you think about this image ?" and Nicu Buculei shared[5] some
mosaic photos[6] he thought may be interesting "I have no idea which
architectural style is this, but yesterday evening (around the 'golden
hour') when passing near a group of fountains in the center of my city I
noticed the mosaic and i *had to* take some photos ans share them with
the rest of the gang."
1.
http://lists.fedoraproject.org/pipermail/design-team/2009-July/000494.html
2. https://fedoraproject.org/wiki/F12_Artwork
3. https://fedoraproject.org/wiki/Design/Release_Artwork_Process
4.
http://lists.fedoraproject.org/pipermail/design-team/2009-July/000511.html
5.
http://lists.fedoraproject.org/pipermail/design-team/2009-July/000513.html
6. http://fedora.nicubunu.ro/photos/mosaic/
-- Virtualization --
In this section, we cover discussion of Fedora virtualization
technologies on the @fedora-virt, @fedora-xen-list, @libguestfs,
@libvirt-list, @virt-tools-list, and @ovirt-devel-list lists.
Contributing Writer: Dale Bewley
--- Fedora Virtualization List ---
This section contains the discussion happening on the fedora-virt list.
---- New Release libguestfs 1.0.64 ----
Richard Jones announced [1] the release of
image:Echo-package-16px.pnglibguestfs 1.0.64.
New Features:
* New tool: virt-cat. This tool lets you copy out files from a guest.[2]
* Added libguestfs-test-tool which is a tool you can use to diagnose
qemu / kernel booting problems, and also make bug reports more useful.
* [Sys::Guestfs::Lib] split $os->{version} into $os->{major_version} and
$os->{minor_version}. Add feature tags. (Matt Booth).
* Allow TMPDIR to be used to override the location of temporary files.
* Implement the guestfs_read_file call.
* New calls guestfs_mkmountpoint and guestfs_rmmountpoint to allow some
specialized read-only or nested filesystems to be mounted, particularly
for examining live CDs.[3]
* New call guestfs_mountpoints to return a hash of device -> mountpoint.
* Many documentation fixes, including an "API Overview"[4] section which
will help developers navigate parts of the now very large libguestfs API.
* Add ~ and ~username expansion in guestfish (RHBZ #511372).
* Add kernel modules for reading DOS filesystems (Guido Gunther).
* Add i18n support for Perl strings.
1. http://www.redhat.com/archives/libguestfs/2009-July/msg00059.html
2. http://libguestfs.org/virt-cat.1.html#examples
3.
http://rwmj.wordpress.com/2009/07/15/unpack-the-russian-doll-of-a-f11-liv...
4. http://libguestfs.org/guestfs.3.html#api_overview
---- Swap Use in Guests ----
Rich Mahn asked[1] "How big should the swap parititons be on virtual
machines under qemu, qemu/kvm?" "It seems to me that if the VM actually
needs swap space, it would be more efficient to allocate more
virual[sic] memory to it."
Richard Jones found[2] this to be an interesting question, but argued
"One place I think you're wrong is the assumption that adding more
memory to a VM is better than having the VM use a swap disk. The reason
would be that the VM's memory manager will assume that the [from its
point of view] physical memory will be much faster than swap, and so
will arrange memory vs swap use accordingly. But this assumption isn't
true, this so-called physical memory is really just as slow as swap!"
Richared pointed out Kernel Shared Memory[3] further complicates things.
Dor Laor added[4]"Guest swapping is a reasonable scenario that should be
allowed and supported." On the question of oversubscribing host memory
to guests, Dor said "You can overcommit VM memory and it might be good
if you have many VMs that have low memory foot print. If it is not the
case, you better not do it."
1. http://www.redhat.com/archives/fedora-virt/2009-July/msg00173.html
2. http://www.redhat.com/archives/fedora-virt/2009-July/msg00178.html
3. http://lwn.net/Articles/306704/
4. http://www.redhat.com/archives/fedora-virt/2009-July/msg00182.html
---- Clustering libvirt Hosts ----
Gianluca Cecchi asked[1] "is there any pointer about how to set up a
cluster of Qemu/KVM hosts?" "What are the uuid tags into the xml for? Do
they have to be identical for clusters or do they have to be absolutely
different for a sort of "identification" of host (as the term seems to
suggest)?"
Richard Jones pointed out oVirt[2] "which is an open source management
tool designed precisely for looking after networks of virt hosts. It is
based on libvirt, and they have looked at and solved many of the issues
you raise."
Guido Günther answered[3] "In principle they don't have to be the same
across hosts since you can identify the network by name and the volumes
by their path but I prefer to keep them in sync (using shared nfs in my
case)."
1. http://www.redhat.com/archives/fedora-virt/2009-July/msg00161.html
2. http://ovirt.org/
3. http://www.redhat.com/archives/fedora-virt/2009-July/msg00177.html
--- Virtualization Tools List ---
This section contains the discussion happening on the virt-tools-list list.
---- Virtual Machine Cloning ----
Cole Robinson with some UI designs from Jeremy Perry patched[1]
image:Echo-package-16px.pngvirt-manager to include a virtual machine
cloning wizard.
1. http://www.redhat.com/archives/virt-tools-list/2009-July/msg00017.html
---- Virt Manager UI Rework ----
Cole Robinson has "been reworking the main manager view in virt-manager"
and asked[1] for comments.
In another UI tweak, Cole created[2] a system tray icon that "can be
used to quit the app, or start, stop, pause, or open a VM."
1. http://www.redhat.com/archives/virt-tools-list/2009-July/msg00035.html
2. http://www.redhat.com/archives/virt-tools-list/2009-July/msg00042.html
---- Support for Processor Affinity ----
Michal Novotny submitted[1] a patch to virt-manager which enables
pinning a guest to a select physical CPU.
1. http://www.redhat.com/archives/virt-tools-list/2009-July/msg00031.html
---- Virt What? ----
Another week, another release[1] from Richard Jones.
virt-what[2] "is a collection of code snippets to allow you to determine
what sort of virtualization you are running inside."
"The new version can tell the difference between QEMU and KVM, and can
tell if you are running inside a Xen fullvirt guest."
1. http://www.redhat.com/archives/virt-tools-list/2009-July/msg00034.html
2. http://et.redhat.com/~rjones/virt-what/
--- end FWN 186 ---
Pascal Calarco, Fedora Ambassador, Indiana, USA
14 years, 9 months
qa beat in
by Adam Williamson
qa beat is done for 186. thanks!
--
Adam Williamson
Fedora QA Community Monkey
IRC: adamw | Fedora Talk: adamwill AT fedoraproject DOT org
http://www.happyassassin.net
14 years, 9 months
Fedora Weekly News 185
by Pascal Calarco
* 1 Fedora Weekly News Issue 185
o 1.1 Announcements
+ 1.1.1 Fedora 12 (Constantine)
+ 1.1.2 Upcoming Events
o 1.2 Planet Fedora
+ 1.2.1 General
o 1.3 Ambassadors
+ 1.3.1 Event in Tripura, India
+ 1.3.2 Get on the map
+ 1.3.3 Get the word out about your F11 event
o 1.4 QualityAssurance
+ 1.4.1 Test Days
+ 1.4.2 Weekly meetings
+ 1.4.3 F12 Alpha blocker bug review meeting
+ 1.4.4 Updated list of components for priority triage
+ 1.4.5 Xfce spin testing
+ 1.4.6 What to do with Fedora 11 target bugs
+ 1.4.7 QA meeting time/date adjustment
+ 1.4.8 Anaconda triage project progress
+ 1.4.9 Bugzilla semantics debate
o 1.5 Artwork
+ 1.5.1 Schedule for Fedora 12
+ 1.5.2 Wallpapers
o 1.6 Virtualization
+ 1.6.1 Enterprise Management Tools List
# 1.6.1.1 Good Bye to ET-Mgmt-Tools List
+ 1.6.2 Fedora Virtualization List
# 1.6.2.1 Virtual Machine Disk Setup Tips
+ 1.6.3 Libguestfs List
# 1.6.3.1 New Release libguestfs 1.0.59
# 1.6.3.2 New Hypervisor Migration Tool virt-v2v
+ 1.6.4 Libvirt List
# 1.6.4.1 Split RPC Dispatching from Remote API
Handlers
# 1.6.4.2 Allow QEMU VMs to be Run Unprivileged
# 1.6.4.3 cgroups Support in QEMU Driver
# 1.6.4.4 Experimental Tunnelled Migration
- Fedora Weekly News Issue 185 -
Welcome to Fedora Weekly News Issue 185[1] for the week ending July 19,
2009.
Highlights from this week's issue include an overview of feature details
for Fedora 12 (Constantine) in our Announcements beat, followed by news
from all over the Fedora Planet, including instructions on how to
install Chromium (the open source version of Google's Chrome browser) on
Fedora, thoughts on the Association for Competitive Technology's recent
accusations against the European Commission "of having a bias in favor
of open source", and a review of Hannah Montana Linux, along with much
more. This week's Ambassadors beat features an event report from
Tripura, India and highlights the worldwide Fedora Ambassador map --
find your closest Ambassadors! The Quality Assurance beat features
details on the second upcoming Fit and Finish Test Day, to focus on
power management and suspend/resume in Fedora with opportunities to
participate in the testing. Also a review of this past week's meetings,
Fedora 12 bug blocker review and Fedora 11 bug triage. The Art beat this
week features details on the Fedora 12 design schedule and also more
detail on wallpaper development that FWN has reported on in recent
weeks. This week's issue rounds out with much Fedora virtualization news
goodness, including details on transition from the Enterprise Management
Tools lists, some very helpful Fedora virtual machine disk setup tips,
and details of new versions of libguestfs and virt-v2v. This is but a
sampling of this week's content and we hope you enjoy this week's issue!
If you are interested in contributing to Fedora Weekly News, please see
our 'join' page[2]. We welcome reader feedback:
fedora-news-list(a)redhat.com The Fedora News team is collaborating with
Marketing and Docs to come up with a new exciting platform for
disseminating news and views on Fedora, tentatively called Fedora
Insight. If you are interested, please join the list and let us know how
you would like to assist with this effort.
FWN Editorial Team: Pascal Calarco, Adam Williamson
1. http://fedoraproject.org/wiki/FWN/Issue185
2. http://fedoraproject.org/wiki/NewsProject/Join
-- Announcements --
In this section, we cover announcements from the Fedora Project[1] [2] [3].
Contributing Writer: Max Spevack
1. http://www.redhat.com/archives/fedora-announce-list/
2. http://www.redhat.com/archives/fedora-devel-announce/
3. http://fedoraproject.org/wiki/Events
--- Fedora 12 (Constantine) ---
The main topic on the announcement lists this past week was Fedora 12's
feature process. John Poelstra[1] sent out several emails about features.
An initial note[2] was sent on July 14th listing feature pages that were
in need of an update, and that list included 15 features.
On July 16th, a second email was sent, requesting that the Fedora
Engineering Steering Committee drop the features[3] that had not been
updated. The list of 15 had by this point been narrowed down to only 5,
meaning that 2/3 of the features were updated as requested. By July
17th, all but 3 of the 15 features had been updated[4].
As FWN goes to press, the feature freeze is scheduled for July 28th[5].
Please make sure that your Fedora 12 features[6] are in the proper
status and ready for FESCo[7].
1. https://fedoraproject.org/wiki/User:Poelstra
2.
http://www.redhat.com/archives/fedora-devel-announce/2009-July/msg00009.html
3.
http://www.redhat.com/archives/fedora-devel-announce/2009-July/msg00010.html
4.
http://www.redhat.com/archives/fedora-devel-announce/2009-July/msg00012.html
5.
http://www.redhat.com/archives/fedora-devel-announce/2009-July/msg00014.html
6. https://fedoraproject.org/wiki/Category:FeatureAcceptedF12
7. https://fedoraproject.org/wiki/Category:FeatureReadyForFesco
--- Upcoming Events ---
Consider attending or volunteering at an event near you!
* North America (NA)[1]
* Central & South America (LATAM)[2]
* Europe, Middle East, and Africa (EMEA)[3]
* India, Asia, Australia (India/APJ)[4]
1.
http://fedoraproject.org/wiki/Events#FY10_Q2_.28June_2009_-_August_2009.29
2.
http://fedoraproject.org/wiki/Events#FY10_Q2_.28June_2009_-_August_2009.29_2
3.
http://fedoraproject.org/wiki/Events#FY10_Q2_.28June_2009_-_August_2009.29_3
4.
http://fedoraproject.org/wiki/Events#FY10_Q2_.28June_2009_-_August_2009.29_4
-- Planet Fedora --
In this section, we cover the highlights of Planet Fedora[1] - an
aggregation of blogs from Fedora contributors worldwide.
Contributing Writer: Adam Batkin
1. http://planet.fedoraproject.org
--- General ---
James Morris mentioned[1] how Red Hat has handled a recent 2.6.30 kernel
null pointer vulnerability, and who it affects (probably no RHEL customers).
Luca Foppiano described[2] how to configure Twinkle, the QT VoIP client,
to work with Fedora Talk.
Peter Hutterer continued[3] the XI2 Recipes series with "the common
input events and the data they include". Peter also explained[4][5] some
additional details about new XLib APIs to handle cookies and associated
data.
Paul W. Frields wrote[6] about configuring and optimizing postfix for
remote/disconnected operation.
Kevin Higgins posted[7] photos from the Vancouver Fedora 11 Release Party.
Michael Tiemann questioned[8] the Association for Competitive
Technology's recent accusations against the European Commission "of
having a bias in favor of open source."
Greg DeKoenigsberg suggested[9] that "creating a strong 'patch culture'"
for Spacewalk (and by extension, open source projects in general) can be
accomplished by setting a strong example. "People behave as they see
others behave."
Luke Macken posted[10] some pretty pictures of Fedora 9 package update
metrics.
Seth Vidal came up with[11] a list of "critical path" packages "that
require special care when updating in rawhide and releases". For more
information, see the Critical Path Packages Proposal.
Daniel Walsh added[12] another SELinux how-to, to the ongoing series,
this time fixing a "denial message about vpnc_t trying to read a file
labeled user_home_t."
Matthew Garrett chimed in[13] about RMS' recent comments regarding the
"cult of the virgin of emacs".
Máirín Duffy displayed[14] mockups of a net system-config-selinux dialog
mockup.
Marc Ferguson instructed[15] how to install Chromium (the Open Source
project version of Google's Chrome web browser) on Fedora 11.
James Laska called out[16] for anyone interested in joining the Fedora
QA efforts, and pointed out some exemplary guides on the Fedora Wiki to
assist in debugging particular projects.
Karsten Wade explained[17] some background around the Fedora
Infrastructure team's implementation of Zikula, a new content management
system that will be used for various Fedora teams.
Andrew Vermilya Jamison reviewed[18] KDE4 on Fedora, from the
perspective of a Gnome user.
Julian Aloofi reviewed[19] Hannah Montana Linux. Scary.
1.
http://blog.namei.org/2009/07/18/a-brief-note-on-the-2630-kernel-null-poi...
2. http://blog.foppiano.org/2009/07/12/twinkle-configuration-howto/
3. http://who-t.blogspot.com/2009/07/xi2-recipes-part-4.html
4. http://who-t.blogspot.com/2009/07/xlib-cookie-events.html
5. http://who-t.blogspot.com/2009/07/xi2-and-xlib-cookies.html
6. http://marilyn.frields.org:8080/~paul/wordpress/?p=2616
7.
http://crossbytes.wordpress.com/2009/07/13/vancouver-fedora-11-release-pa...
8. http://opensource.org/node/447
9. http://gregdek.livejournal.com/51507.html
10. http://lewk.org/blog/f9-updates.html
11.
http://skvidal.wordpress.com/2009/07/14/critical-path-package-owners/
12. http://danwalsh.livejournal.com/29790.html
13. http://mjg59.livejournal.com/113408.html
14. http://mairin.wordpress.com/2009/07/15/system-config-selinux-mocks/
15. http://www.fergytech.com/2009/07/a-chromium-rpm-on-fedora-11/
16. http://jlaska.livejournal.com/5693.html
17.
http://iquaid.org/2009/07/16/fedora-zikula-infrastructure-of-freedom-ftw/
18. http://blogs.andyjamison.com/andy/?p=85
19. http://julianaloofi.wordpress.com/2009/07/17/distro-review-hm-linux/
-- Ambassadors --
In this section, we cover Fedora Ambassadors Project[1].
Contributing Writer: Larry Cafiero
1. http://fedoraproject.org/wiki/Ambassadors
--- Event in Tripura, India ---
Shakthi Kannan conducted a Fedora workshop ("GNUtsav") at National
Institute of Technology (NIT), Agartala, Tripura, India on July 18-19, 2009.
Shakthi says, "I would like to thank the Fedora project for sponsoring
the event. Special thanks to the student volunteers who worked hard in
organizing the event. Mention must be made for the support of the
faculty, Prof. Swapan Debbarma, Prof. Anupam Jamatia ("ajnr" on
freenode), and Prof. Dwijen Rudrapal."
Shakthi's presentation sessions included:
* i-want-2-do-project. tell-me-wat-2-do-fedora.
* Badam Halwa of Embedded Systems
* di-git-ally managing love letters
* Fedora Electronic Lab (demo)
* Packaging RPM -- Red hot, Paneer (butter) Masala
The presentations are available from:
http://www.shakthimaan.com/downloads.html
As customary, here are few photos that Shakthi took during the trip:
http://www.shakthimaan.com/Mambo/gallery/album57
--- Get on the map ---
Want to find the nearest ambassador? How about one in Romania? Now you can.
Susmit Shannigrahi reports that finding out the nearest ambassadors,
which was once a tedious task, is now as simple as viewing a map. The
map is at https://fedoraproject.org/membership-map and instructions on
how to place yourself on the map can be found at
https://fedoraproject.org/wiki/Fedora_ambassadors_map
--- Get the word out about your F11 event ---
Fedora 11 was released on Tuesday, June 9, and with it a variety of
activities around the release will be forthcoming. As such, with the
recent release of Fedora 11, this is a reminder that posting your event
on Fedora Weekly News can help get the word out. Contact FWN Ambassador
correspondent Larry Cafiero at lcafiero-AT-fedoraproject-DOT-org with
announcements of upcoming events -- and don't forget to e-mail reports
after the events as well.
-- 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 ---
There was no Test Day last week.
No Test Day is scheduled on the main track next week. However, the new
Fit and Finish[1] Test Day track will be holding its second event[2], on
power management and suspend/resume. The Test Day page already includes
several test scenarios, and a live CD for testing will soon be
available. The Fit and Finish project is a great effort to improve the
details of the Fedora project, so please show up to support this event!
The Test Day will be held on 2009-07-21 (Tuesday) in IRC
#fedora-fit-and-finish (note this is not the same channel where main
track Test Days take place).
If you would like to propose a main track Test Day for the Fedora 12
cycle, please contact the QA team via email or IRC, or file a ticket in
QA Trac[3].
1. http://fedoraproject.org/wiki/Fit_and_Finish
2.
https://fedoraproject.org/wiki/Test_Day:2009-07-21_Fit_and_Finish:Batteri...
3. https://fedorahosted.org/fedora-qa/
--- Weekly meetings ---
The QA group weekly meeting[1] was held on 2009-07-15. The full log is
available[2]. James Laska reported that he had filed tickets to track
the creation of the three Debugging pages identified as desirable by
Christopher Beland, and would mail the list to try and attract
volunteers to work on the pages.
James also noted he is still working on the Goals page[3], using a
personal space draft[4], but was not yet ready to go into production
with it.
James and Jesse Keating reported on the revisions to the Fedora 12
schedule in terms of QA and release engineering. The latest revised
schedules are available: QA[5] and release engineering[6].
James reminded the group about the then-forthcoming Alpha Blocker Bug
Day, which would be held on 2009-07-17. Adam Williamson suggested
reviewing F12Blocker bugs (which block only the final release) to see if
they should be promoted to blocking the Alpha release also. James
brought up the question of the criteria for Alpha blocker bugs. After
some discussion, there was general agreement to work on the basis of
considering only high-severity bugs in critical path components (as
defined by the Critical Path Packages Proposal[7]) as Alpha blockers.
James mentioned that the Fedora 12 Test Day schedule is still currently
lightly populated, but he and Adam have several events planned which
have not yet been set down to specific dates.
Will Woods reported on the progress of the AutoQA project. He has now
completed writing the test cases for the Rawhide Acceptance Test
Plan[8]. He is now starting to work on writing automated tests for these
cases, using autotest. He pointed out that progress information can also
be found in AutoQA trac[9].
Finally, the group discussed changing the meeting day and/or time. Adam
suggested creating a matrix of possible times and having each interested
member fill out the times at which they are available, as has been done
by other groups in the past. James offered to create the matrix and
notify the mailing list so that people could fill it in once it was ready.
Jóhann Guðmundsson pointed out that the QA group could potentially be
affected by the ongoing question about the use of Fedora trademarks in
non-official spins, as it frequently generates non-official spins for
use in Test Days. The group agreed to monitor this on an ongoing basis.
The Bugzappers group weekly meeting[10] was held on 2009-07-14. The full
log is available[11]. Richard June apologized for not having asked
Brennan Ashton for an update on the triage metrics project.
The group reviewed Niels Haase's proposed expanded list of priority
triage components[12]. Edward Kirk thought that some of the components
were not truly critical. The list was tabled for review when Niels could
be present at a meeting.
The group discussed the latest version of Matej Cepl's greasemonkey
script. It seems to have been deployed by several triagers with no
problems so far.
Other topics were tabled due to the absence of several group members for
various reasons.
The next QA weekly meeting will be held on 2009-07-22 at 1600 UTC in
#fedora-meeting, and the next Bugzappers weekly meeting on 2009-07-21 at
1500 UTC in #fedora-meeting.
1. http://fedoraproject.org/wiki/QA/Meetings
2. http://fedoraproject.org/wiki/QA/Meetings/20090715
3. http://fedoraproject.org/wiki/QA/Goals
4. http://fedoraproject.org/wiki/User:Jlaska/Draft
5.
http://poelstra.fedorapeople.org/schedules/f-12/f-12-quality-tasks.html
6.
http://poelstra.fedorapeople.org/schedules/f-12/f-12-releng-tasks.html
7. http://fedoraproject.org/wiki/Critical_Path_Packages_Proposal
8. http://fedoraproject.org/wiki/QA:Rawhide_Acceptance_Test_Plan
9. https://fedorahosted.org/autoqa/milestone/israwhidebroken.com
10. http://fedoraproject.org/wiki/BugZappers/Meetings
11.
http://meetbot.fedoraproject.org/fedora-meeting/2009-07-14/fedora-meeting...
12. http://fedoraproject.org/wiki/User:Arxs/CPCL
--- F12 Alpha blocker bug review meeting ---
John Poelstra announced[1] the first blocker bug review meeting for
Fedora 12, to be held on 2009-07-17, mainly to review blocker bug status
for the upcoming Alpha release. Later, Adam Williamson posted a recap of
the meeting[2], recording that it had been well attended and had been
able to review the whole F12 Alpha and main blocker lists, remove some
from the lists, promote some to block the Alpha release, and check on
the development status of several bugs.
1.
http://www.redhat.com/archives/fedora-test-list/2009-July/msg00239.html
2.
http://www.redhat.com/archives/fedora-test-list/2009-July/msg00347.html
--- Updated list of components for priority triage ---
Niels Haase announced[1] that he had updated his proposed expansion of
the list of priority components for the Bugzappers group to focus on
triaging[2], based on the Critical Path Packages Proposal, as previously
approved at Bugzappers meetings.
1.
http://www.redhat.com/archives/fedora-test-list/2009-July/msg00255.html
2. http://fedoraproject.org/wiki/User:Arxs/CPCL
--- Xfce spin testing ---
Adam Miller announced[1] that, he would be building a test live image
with the Xfce desktop roughly each week, and would appreciate testing
and reporting of problems. He also included a link to the first build.
1.
http://www.redhat.com/archives/fedora-test-list/2009-July/msg00251.html
--- What to do with Fedora 11 target bugs ---
John Poelstra pointed out[1] that the F11Target bug[2] was still open
(and depending on 321 bugs), and asked what people thought should be
done about it. Niels Haase suggested[3] moving all that had been triaged
to F12Target. Mark McLoughlin suggested[4] having F11Target block
F12Target, effectively moving the bugs to F12Target wholesale. Matthias
Clasen opined that "I don't think it makes sense to accumulate hundreds
of bugs on the target tracker, if they only end up getting pushed from
release to release"[5]. Adam Williamson agreed, and suggested[6] just
closing the tracker bug, as had been done for Fedora 9 and Fedora 10. No
final decision was yet reached.
1.
http://www.redhat.com/archives/fedora-test-list/2009-July/msg00259.html
2. http://bugzilla.redhat.com/show_bug.cgi?id=446451
3.
http://www.redhat.com/archives/fedora-test-list/2009-July/msg00260.html
4.
http://www.redhat.com/archives/fedora-test-list/2009-July/msg00265.html
5.
https://www.redhat.com/archives/fedora-test-list/2009-July/msg00267.html
6.
http://www.redhat.com/archives/fedora-test-list/2009-July/msg00270.html
--- QA meeting time/date adjustment ---
As discussed at the weekly meeting, James Laska announced[1] that he had
created a matrix to track possible new times and days for the QA group
weekly meeting, and asked everyone interested in attending the meetings
to fill out the matrix with the days and times when they are available.
1.
https://www.redhat.com/archives/fedora-test-list/2009-July/msg00304.html
--- Anaconda triage project progress ---
Adam Williamson reported[1] on the progress of the ongoing project to
integrate anaconda triage into the Bugzappers group and workflow. He
thanked Andy Lindeberg for her efforts in joining the mailing list,
weekly meetings and IRC channel, and in working to codify the current
workflow used to triage anaconda bugs. He recorded that meeting and
email discussions had revealed little in the way of fundamental
conflicts between the official Bugzappers workflow[2] and the Anaconda
workflow[3]. He had therefore modified the components and triagers
page[4] to list the Anaconda workflow page as the special instructions
for triaging anaconda, and note that additional triagers are now welcome
for anaconda if someone has a burning desire to work on it, although
Andy is currently covering the area very effectively.
1.
http://www.redhat.com/archives/fedora-test-list/2009-July/msg00308.html
2. http://fedoraproject.org/wiki/BugZappers/BugStatusWorkFlow
3. http://fedoraproject.org/wiki/Anaconda/AnacondaBugWorkflow
4. http://fedoraproject.org/wiki/BugZappers/Components_and_Triagers
--- Bugzilla semantics debate ---
Adam Williamson asked the list[1] about a question he had been
discussing with Andy Lindeberg, regarding the semantics of the NEW and
ASSIGNED states in Bugzilla. He proposed the use of a keyword (instead
of the ASSIGNED state) to indicate a bug has been triaged, and either
removing the ASSIGNED state entirely, or noting in the workflow page
that it has no real function and is effectively equivalent to NEW. This
led to an enthusiastic debate, with many other proposals made, although
all seemed to agree that the current state of ASSIGNED meaning that a
bug has been triaged is not optimal. No final consensus was yet reached
on what changes, if any, to propose to the configuration of Bugzilla
and/or the official workflow.
1.
http://www.redhat.com/archives/fedora-test-list/2009-July/msg00309.html
-- Artwork --
In this section, we cover the Fedora Design Team[1].
Contributing Writer: Nicu Buculei
1. http://fedoraproject.org/wiki/Artwork
--- Schedule for Fedora 12 ---
After an IRC conference with the Design Team leader Máirín Duffy and
Paul Frields, John Poelstra posted[1] on the mailing list a schedule[2]
for Fedora 12 "Some of the key ideas for the planning and schedule for
this release are to focus on the importance of the wallpaper and
iteratively improve it.... making sure it is in the alpha and then
releasing updated packaged versions in rawhide each week."
The debate heated a bit when William Jon McCann arrogantly repeated[3]
for a number of items "Not relevant to the desktop spin", prompting a
reply[4] from Máirín "This schedule is for the design team, not for the
desktop spin. The KDE spin does need this splash, so we help produce it
for them. We work on designs for all of Fedora, all spins including KDE
and Electronics Lab and EDU, as well as the main website and various web
applications."
1.
http://lists.fedoraproject.org/pipermail/design-team/2009-July/000438.html
2.
http://poelstra.fedorapeople.org/schedules/f-12/f-12-design-tasks.html
3.
http://lists.fedoraproject.org/pipermail/design-team/2009-July/000468.html
4.
http://lists.fedoraproject.org/pipermail/design-team/2009-July/000469.html
--- Wallpapers ---
Following an IRC session with Máirín Duffy and Nicu Buculei, María
Leandro posted[1] a set of *very cute* design proposals for the
Education/Kids wallpaper. She also blogged[2] about the designs.
María also advanced[3] a photo-manipulation concept based on the
'Constantine' theme. After a round of inquiries[4] she cleared[5] the
license of the source photos. However, as Máirín Duffy observed[6], a
photomanipulation is not preferred as default "We would much prefer a
vector-based graphic as the default wallpaper. As María said, her XCF
was 69 MB. This would make it very difficult for others to work on the
file."
1.
http://lists.fedoraproject.org/pipermail/design-team/2009-July/000477.html
2. http://tatica.org/2009/07/15/wallpapers-fedora-para-ninos/
3.
http://lists.fedoraproject.org/pipermail/design-team/2009-July/000447.html
4.
http://lists.fedoraproject.org/pipermail/design-team/2009-July/000452.html
5.
http://lists.fedoraproject.org/pipermail/design-team/2009-July/000474.html
6.
http://lists.fedoraproject.org/pipermail/design-team/2009-July/000463.html
-- Virtualization --
In this section, we cover discussion of Fedora virtualization
technologies on the @et-mgmnt-tools-list, @fedora-virt,
@fedora-xen-list, @libguestfs, @libvirt-list, @virt-tools-list, and
@ovirt-devel-list lists.
Contributing Writer: Dale Bewley
--- Enterprise Management Tools List ---
This section contains the discussion happening on the et-mgmt-tools list
---- Good Bye to ET-Mgmt-Tools List ----
Daniel Berrange announced[1] the end of life for the et-mgmt-tools list
and the birth of the @virt-tools-list. "In retrospect this was a really
bad choice of names for a mailing list and causes endless confusion for
people wrt what to discuss where. Most of the emerging technology
projects have lists of their own
(image:Echo-package-16px.pngcobbler[2][3],
image:Echo-package-16px.pngaugeas[4],
image:Echo-package-16px.pnglibguestfs[5],
image:Echo-package-16px.pnglibvirt[6]) and it is about time that
image:Echo-package-16px.pngvirt-manager and friends joined them."
"To that end we have created a new mailing list 'virt-tools-list'[7].
This will be the new home for all developer & user discussions relating
to the following applications:"
* virt-manager
* virt-viewer
* virt-install
* virt-clone
* virt-image
* virt-convert
1. http://www.redhat.com/archives/et-mgmt-tools/2009-July/msg00046.html
2. http://fedorahosted.org/mailman/listinfo/cobbler
3. http://fedorahosted.org/mailman/listinfo/cobbler-devel
4. http://www.redhat.com/mailman/listinfo/augeas-devel
5. http://www.redhat.com/mailman/listinfo/libguestfs
6. http://www.redhat.com/mailman/listinfo/libvir-list
7. http://www.redhat.com/mailman/listinfo/virt-tools-list
--- Fedora Virtualization List ---
This section contains the discussion happening on the fedora-virt list.
---- Virtual Machine Disk Setup Tips ----
Rich Mahn recognized[1] "that the best performance for virtual disks is
with the backing storage on the host being a parititon or LV. Since I
want some flexibility I will use LVs, with virtio disks on most of the
VMs." But Rich had several questions (paraphrased below) about how best
to configure the backing stores for virtual machines and the disks
within them. Daniel Berrange provided some answers (also paraphrased below).
* Q: If each VM needs three file systems: /boot, root, and swap.
"Is it better to create three LVs (each) on the hosts, and treat it as
three separate disks on the VMs?"
A: "There's no point separating /boot & root onto separate virtual
disks." "The only separation I'd do is for the OS system disks, vs
application data disks..." This makes it easier to provision a new VM
with the latest disto and reassign the data disk to the new guest.
* Q: "Do I get better performance/stability by NOT using lvm on the
VMs?"
A: "LVM makes is easier to resize guest FS. eg add a second disk to
the guest, format it as a LVM PV and add it to your VG. That's pretty
much only wayto add more capacity on a running guest."
* Q: "Do I get the best performance/stability by creating an LV for
each disk I need, and then NOT partitioning it on the VM, but using the
whole disk for a file system?"
A: "Anaconda will refuse to install onto a raw disk, it mandates
partitioning. Second point is that not using a partition table can cause
unexpected problems..."
* Q: "Are these issues too miniscule in their effects that I
probably shouldn't even be worrying about" trying to avoid using
partitions and LVM?
A: "That's certainly my opinion. Sure you get some performance but
you loose the great administrative flexibility of LVM."
1. http://www.redhat.com/archives/fedora-virt/2009-July/msg00141.html
--- Libguestfs List ---
This section contains the discussion happening on the libguestfs list.
---- New Release libguestfs 1.0.59 ----
Richard Jones announced[1] the release of
image:Echo-package-16px.pnglibguestfs 1.0.59.
New Features:
* Support for Linux extended attributes.
* Allow guestfish to be controlled remotely, so you can use one
guestfish instance in a long-running shell script.
* Support for reiserfs.
* New function 'guestfs_zfile' -- 'file' inside compressed files.
* New guestfish command 'reopen' -- reopen guestfish connection.
* guestfish -x option (echo commands).
* New function 'guestfs_version' to get the library version.
See previous release announcement for 1.0.57 in FWN#184[2] and be sure
to see the project homepage[3] for extensive usage examples.
1. http://www.redhat.com/archives/libguestfs/2009-July/msg00023.html
2.
http://fedoraproject.org/wiki/FWN/Issue184#New_Mailing_List_and_New_Relea...
3. http://libguestfs.org/
---- New Hypervisor Migration Tool virt-v2v ----
Matthew Booth posted[1] his "initial thoughts on the design for the v2v
tool". This tool will be used to implement the planned Fedora 12 feature
"Xen to KVM Migration"[2].
1. http://www.redhat.com/archives/libguestfs/2009-July/msg00024.html
2. http://fedoraproject.org/wiki/Features/Xen_to_KVM_migration
--- Libvirt List ---
This section contains the discussion happening on the libvir-list.
---- Split RPC Dispatching from Remote API Handlers ----
Daniel Berrange posted[1] a set of 9 patches. "The current libvirtd
remote protocol dispatch code is written in such a way that assumes the
only incoming messages from clients are method calls. This makes it very
hard to support data streams. This patch series does an incrmental
refactoring of alot of code to allow data streams to be easily wired in."
1. http://www.redhat.com/archives/libvir-list/2009-July/msg00303.html
---- Allow QEMU VMs to be Run Unprivileged ----
Daniel Berrange submitted[1] a patch which "makes it such that the"
privileged "libvirtd daemon can run unprivileged QEMU guests. The
default remains unchanged with QEMU running as root:root, but the
package maintainer can request an alternative default user at build
time, and the sysadmin can also override this at install time with
/etc/libvirt/qemu.conf."
This patch is in support of the planned Fedora 12 feature
"VirtPrivileges"[2].
1. http://www.redhat.com/archives/libvir-list/2009-July/msg00390.html
2. http://fedoraproject.org/wiki/Features/VirtPrivileges
---- cgroups Support in QEMU Driver ----
Daniel Berrange added[1] "cgroups[2] support to the QEMU driver."
1. http://www.redhat.com/archives/libvir-list/2009-July/msg00435.html
2. http://www.mjmwired.net/kernel/Documentation/cgroups.txt
---- Experimental Tunnelled Migration ----
Chris Lalancette posted[1] "the current version of the tunnelled
migration patch, based upon Daniel Berrange's generic datastream work.
In order to use this work, you must first grab danpb's data-streams git
branch[2]". Chris's work on secure guest migration was covered in FWN
#168[3].
1. http://www.redhat.com/archives/libvir-list/2009-July/msg00433.html
2. http://gitorious.org/~berrange/libvirt/staging
3.
http://fedoraproject.org/wiki/FWN/Issue168#Secure_Guest_Migration_Draft_P...
--- end FWN #185 ---
Pascal Calarco, Fedora Ambassador, Indiana, USA
https://fedoraproject.org/wiki/User:Pcalarco
14 years, 9 months
Re: RSS feed
by Pascal Calarco
Hi Kamil --
Thanks for your interest! There currently is not an RSS feed for FWN beats or stories, but this is something we are working on in conjunction with the Marketing and Docs team to get FWN content into a Zikula-based CMS which will provide RSS and other features. This is still in the discussion stages, but we should hopefully have something to show in the next few weeks.
- pascal
----- Original Message -----
From: fedora-news-list-bounces(a)redhat.com <fedora-news-list-bounces(a)redhat.com>
To: fedora-news-list(a)redhat.com <fedora-news-list(a)redhat.com>
Sent: Mon Jul 20 09:00:29 2009
Subject: RSS feed
Hello,
I haven't found anywhere on the FWN wiki [1] an RSS/Atom feed of the latest FWN Issues. Is there something like that somewhere?
Thanks.
[1] http://fedoraproject.org/wiki/FWN
_______________________________________________
Fedora-news-list mailing list
Fedora-news-list(a)redhat.com
https://www.redhat.com/mailman/listinfo/fedora-news-list
14 years, 9 months
Re: FWN 185
by Pascal Calarco
Sure, no problem Adam. We usually send out around noon or often a bit later on Monday, so that's fine. Thanks much!
- pascal
----- Original Message -----
From: fedora-news-list-bounces(a)redhat.com <fedora-news-list-bounces(a)redhat.com>
To: fedora-news-list(a)redhat.com <fedora-news-list(a)redhat.com>
Sent: Sun Jul 19 22:01:56 2009
Subject: Re: FWN 185
Sorry I'm running a bit late. I'm not used to being in the Eastern time
zone, so I have about half of Planet Fedora done, and can have the rest
done by probably 10AM Eastern if you can wait that long...
Thanks,
-Adam Batkin
_______________________________________________
Fedora-news-list mailing list
Fedora-news-list(a)redhat.com
https://www.redhat.com/mailman/listinfo/fedora-news-list
14 years, 9 months
