https://bugzilla.redhat.com/show_bug.cgi?id=1008227
Bug ID: 1008227
Summary: SSD cache
Product: Fedora Documentation
Version: devel
Component: docs-requests
Keywords: Tracking
Assignee: nobody(a)fedoraproject.org
Reporter: me(a)petetravis.com
QA Contact: docs-qa(a)lists.fedoraproject.org
CC: agk(a)redhat.com, i.gnatenko.brain(a)gmail.com,
jeremy(a)goop.org, jreznik(a)redhat.com, kzak(a)redhat.com,
nobody(a)fedoraproject.org, rdieter(a)math.unl.edu,
rolf(a)rolffokkens.nl, sparks(a)redhat.com,
stickster(a)gmail.com, zach(a)oglesby.co
Depends On: 998543, 999690, 1000817, 1001120, 1003208, 1000078,
1003207
+++ This bug was initially created as a clone of Bug #998543 +++
This is a tracking bug for Change: SSD cache
For more details, see: http://fedoraproject.org//wiki/Changes/SSD_cache
Using recent kernel (3.9 and later) features for (fast) SSD caching of (slow)
ordinary hard disks.
--- Additional comment from Rolf Fokkens on 2013-08-21 13:35:33 EDT ---
I'll build a bcache-tools RPM and a dm-cache-utils rpm (actually bcache-tools
is already available here: bcache-tools-20130820-0.1.fc19.src.rpm).
I'll follow the procedure as described here:
https://fedoraproject.org/wiki/Join_the_package_collection_maintainers
--- Additional comment from Rolf Fokkens on 2013-08-24 11:51:34 EDT ---
Tried to create a dmcache-utils package as well (Bug 1000078) but it doesn't
look really useful. So I'll focus on bcache-tools first. For that I still need
a sponsor.
--- Additional comment from Rolf Fokkens on 2013-08-27 06:52:40 EDT ---
I closed Bug 1000078 since good userland support requires LVM2 to support
dm-cache. Which will happen 'in the future', but F20 doesn't look feasible to
me.
--- Additional comment from Rolf Fokkens on 2013-08-31 16:21:30 EDT ---
Create Bug 1003207 (bcache support for dracut) which is not blocking for F20,
but probably will be blocking for F21.
--- Additional comment from Rolf Fokkens on 2013-08-31 16:25:06 EDT ---
Create Bug 1003208 (bcache support for anaconda) which is not blocking for F20,
but probably will be blocking for F21.
--- Additional comment from Rolf Fokkens on 2013-09-09 04:18:18 EDT ---
Test day planned: https://fedorahosted.org/fedora-qa/ticket/415
--------------------------------------------------------------
Discussion at
https://lists.fedoraproject.org/pipermail/devel/2013-July/185336.html
Please assess existing documentation for the impact of this Change.
--
You are receiving this mail because:
You are the QA Contact for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=1058066
Bug ID: 1058066
Summary: new virt-xml functionality coming from upstream
libvirt should be documented
Product: Fedora Documentation
Version: devel
Component: virtualization-deployment-and-administrative-guide
Assignee: lnovich(a)redhat.com
Reporter: me(a)petetravis.com
QA Contact: docs-qa(a)lists.fedoraproject.org
CC: lnovich(a)redhat.com
There is a new tool called `virt-xml` that will end up in Fedora soon[1]. It
looks very useful, and should be documented.
[1] https://www.redhat.com/archives/libvir-list/2014-January/msg01226.html
--
You are receiving this mail because:
You are the QA Contact for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=980931
Bug ID: 980931
Summary: The Virtualization Administration Guide Still Uses
UNIX System V Commands
Product: Fedora Documentation
Version: devel
Component: virtualization-administration-guide
Keywords: Documentation
Severity: medium
Priority: unspecified
Assignee: lnovich(a)redhat.com
Reporter: jhradile(a)redhat.com
QA Contact: docs-qa(a)lists.fedoraproject.org
CC: lnovich(a)redhat.com, me(a)petetravis.com
Description of problem:
The Virtualization Administration Guide for Fedora 18 [1] still uses UNIX
System V commands “service” and “chkconfig”. Although these commands still work
and will continue to work in the foreseeable future, users are strongly advised
to learn and use the new command that is shipped with systemd and is part of
the Fedora distribution since version 15.
Version-Release number of selected component (if applicable):
Fedora-Virtualization_Administration_Guide-18-en-US-1.0-1
How reproducible:
Always.
Steps to Reproduce:
Read section 14.3, “Starting and stopping the daemon” [2], to learn how to
configure the vhostmd service to start automatically at boot time.
Actual results:
/sbin/chkconfig vhostmd on
Expected results:
systemctl enable vhostmd.service
Additional info:
http://fedoraproject.org/wiki/SysVinit_to_Systemd_Cheatsheet
-----
[1]
http://docs.fedoraproject.org/en-US/Fedora/18/html-single/Virtualization_Ad…
[2]
http://docs.fedoraproject.org/en-US/Fedora/18/html-single/Virtualization_Ad…
--
You are receiving this mail because:
You are the QA Contact for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=1095977
Bug ID: 1095977
Summary: RFE: static IP assignment
Product: Fedora Documentation
Version: devel
Component: cookbook
Assignee: docs(a)lists.fedoraproject.org
Reporter: me(a)petetravis.com
QA Contact: docs-qa(a)lists.fedoraproject.org
CC: docs(a)lists.fedoraproject.org
Static IP addresses are crucial for applications like DHCP servers or other
infrastructure that can't rely on external assignment. They're also helpful for
home users that want to predictably locate their Fedora installation.
Explain the use case for this and some alternative methods, then the procedure
for setting a setting a static IP using both ifcfg files and graphical methods.
Each method could be explained in a separate article; ie "... on the command
line" and "... with GNOME" and "... with KDE" and so on.
--
You are receiving this mail because:
You are the QA Contact for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=1101798
Bug ID: 1101798
Summary: RFE: Captive portal
Product: Fedora Documentation
Version: devel
Component: cookbook
Assignee: docs(a)lists.fedoraproject.org
Reporter: me(a)petetravis.com
QA Contact: docs-qa(a)lists.fedoraproject.org
CC: docs(a)lists.fedoraproject.org
Create a recipe for configuring a simple captive portal with Fedora that will
require users to acknowledge a terms of use message before allowing connections
to pass.
--
You are receiving this mail because:
You are the QA Contact for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=1101796
Bug ID: 1101796
Summary: RFE: NAT router
Product: Fedora Documentation
Version: devel
Component: cookbook
Assignee: docs(a)lists.fedoraproject.org
Reporter: me(a)petetravis.com
QA Contact: docs-qa(a)lists.fedoraproject.org
CC: docs(a)lists.fedoraproject.org
Create a recipe for using Fedora as a NAT router using Firewalld and
NetworkManager.
--
You are receiving this mail because:
You are the QA Contact for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=1096394
Bug ID: 1096394
Summary: RFE: Thin Client (Tracking Bug)
Product: Fedora Documentation
Version: devel
Component: cookbook
Assignee: docs(a)lists.fedoraproject.org
Reporter: me(a)petetravis.com
QA Contact: docs-qa(a)lists.fedoraproject.org
CC: docs(a)lists.fedoraproject.org
Fedora can be used as a server and client environment for a thin client
deployment. Document the required procedures to do this.
Because of the broad scope and number of procedures involved, this should be
split up into recipes addressing component tasks. This bug will be used to
track the overall progress; please block this bug with any new bugs created for
the purpose.
--
You are receiving this mail because:
You are the QA Contact for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=1095945
Bug ID: 1095945
Summary: RFE: disabling head parking on spinning drives
Product: Fedora Documentation
Version: devel
Component: cookbook
Assignee: docs(a)lists.fedoraproject.org
Reporter: me(a)petetravis.com
QA Contact: docs-qa(a)lists.fedoraproject.org
CC: docs(a)lists.fedoraproject.org
Some drives have aggressive APM, and the resulting frequent head parking can
negatively impact access latency and produce an annoying clicking sound.
Explain the theory, benefits, procedure, and risks of adjusting APM settings
with hdparm.
--
You are receiving this mail because:
You are the QA Contact for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=982899
Bug ID: 982899
Summary: 7.3.1. Establishing a Wired (Ethernet) Connection
Product: Fedora Documentation
Version: devel
Component: system-administrator's-guide
Severity: unspecified
Priority: unspecified
Assignee: jhradile(a)redhat.com
Reporter: im_dracula(a)hotmail.com
QA Contact: docs-qa(a)lists.fedoraproject.org
CC: jhradile(a)redhat.com
Description of problem:
In section 7.3.1:
Default connection no longer called 'em1'
No field for 'connection name'
you can add new settings for the network under different profiles by selecting
'add profile...'
you can remove/reset a profile by going to the 'options' button under the
profile and selecting the 'reset' item on the left, and then choosing to either
'reset' or 'forget'
--
You are receiving this mail because:
You are the QA Contact for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=1198643
Bug ID: 1198643
Summary: Append parameters to grub.cfg
Product: Fedora Documentation
Version: devel
Component: virtualization-guide
Assignee: docs(a)lists.fedoraproject.org
Reporter: geanceretta(a)gmail.com
QA Contact: docs-qa(a)lists.fedoraproject.org
CC: docs(a)lists.fedoraproject.org, lnovich(a)redhat.com,
zach(a)oglesby.co
Description of problem: The instructions[1] of how to append parameters to
Grub's grub.config file is obsolete on recent releases of Fedora. The file
/boot/grub/grub.conf doesn't exist anymore.
The way to do it now is (tested on Fedora 20):
1 - Edit /etc/default/grub
2 - Append information at the line GRUBCMDLINELINUX=" ... console=tty0
console=ttyS0,115200 ... ")
3 - Regenerate the /boot/grub2/grub.cfg file with the command "grub2-mkconfig
-o /boot/grub2/grub.cfg"
Link:
[1]
http://docs.fedoraproject.org/en-US/Fedora/18/html/Virtualization_Administr…
Additional info: The documentation is refered to version 18 where it should
work, but as we don't have a documentation in a most atual release of Fedora
for that subject, you can write a note for the users of most recent releases of
Fedora that came with Grub2, where the procedure is according with that listed
above.
--
You are receiving this mail because:
You are the QA Contact for the bug.