[Bug 846864] New: Need a list of toolsets and when they are appropriate in the virt Getting Started guide
by Red Hat Bugzilla
https://bugzilla.redhat.com/show_bug.cgi?id=846864
Bug ID: 846864
QA Contact: docs-qa(a)lists.fedoraproject.org
Severity: unspecified
Version: devel
Priority: unspecified
CC: docs(a)lists.fedoraproject.org
Assignee: laine(a)redhat.com
Summary: Need a list of toolsets and when they are appropriate
in the virt Getting Started guide
Regression: ---
Story Points: ---
Classification: Fedora
OS: Unspecified
Reporter: laine(a)redhat.com
Type: Bug
Documentation: ---
Hardware: Unspecified
Mount Type: ---
Status: NEW
Component: virtualization-getting-started-guide
Product: Fedora Documentation
The Getting Started Guide needs an overview of all the different toolsets, and
when each would be appropriate. In particular I'm talking about the following:
1) gnome-boxes
2) virt-manager
3) virsh, virt-install
4) ovirt
5) Should we point some people to OpenStack?
I will write up a first draft of this, and hand it to a qualified docs person
to edit and correctly place in the guide.
--
You are receiving this mail because:
You are the QA Contact for the bug.
8 years, 11 months
[Bug 829952] New: Outdated information about cgconfig service in Resource Management Guide for Fedora 17
by Red Hat Bugzilla
https://bugzilla.redhat.com/show_bug.cgi?id=829952
Bug ID: 829952
QA Contact: docs-qa(a)lists.fedoraproject.org
Severity: unspecified
Version: devel
Priority: unspecified
CC: oglesbyzm(a)gmail.com
Assignee: mprpic(a)redhat.com
Summary: Outdated information about cgconfig service in
Resource Management Guide for Fedora 17
Regression: ---
Story Points: ---
Classification: Fedora
OS: Unspecified
Reporter: brezhnev(a)redhat.com
Type: Bug
Documentation: ---
Hardware: Unspecified
Mount Type: ---
Status: NEW
Component: resource-management-guide
Product: Fedora Documentation
Description of problem:
The Resource Management Guide for Fedora 17 contains outdated information about
cgconfig service in section 2.1 "The cgconfig Service"
The guide states that the cgconfig service is not started by default in Fedora
17. It is not true. In addition, the guide contains phrase "When you start the
service with chkconfig" that is wrong for any release. For Fedora 17 is should
be "When you start the service with the <command>systemctl start</command>
command".
--
You are receiving this mail because:
You are the QA Contact for the bug.
8 years, 11 months
[Bug 1224968] New: All published documents should have a number and a date of publication
by Red Hat Bugzilla
https://bugzilla.redhat.com/show_bug.cgi?id=1224968
Bug ID: 1224968
Summary: All published documents should have a number and a
date of publication
Product: Fedora Documentation
Version: devel
Component: publishing-requests
Severity: low
Assignee: docs-publishers-members(a)fedoraproject.org
Reporter: lsatenstein(a)yahoo.com
QA Contact: docs-qa(a)lists.fedoraproject.org
CC: docs-publishers-members(a)fedoraproject.org
Description of problem:
All documents should have a document and release number. It is not necessary to
follow the ISBN coding, but at least something similar.
When I need or wish to report a correction, or an issue, my version of the
document may not be the version that the maintainer is reviewing, and
therefore, much energy is lost.
Examples, Release Guide or installation guide or other If these guide were not
separated on the web, into categories by links, we may be posting corrections
to guides that are obsolete, or for other reason
Version-Release number of selected component (if applicable):
Not available, except by title.
How reproducible:
Steps to Reproduce:
1.
2.
3.
Actual results:
Document is missing a Document number and date of publication.
Expected results:
Technical, User, and other guides have a documentation number and a published
date (or version).
Additional info:
If a document is updated, which is a reasonable action, the document number,
version and date of release would allow one to know to obsolete his older
version.
--
You are receiving this mail because:
You are the QA Contact for the bug.
8 years, 12 months
[Bug 1224964] New: Kickstart file is not defined. Suggest a rewarding as shown
by Red Hat Bugzilla
https://bugzilla.redhat.com/show_bug.cgi?id=1224964
Bug ID: 1224964
Summary: Kickstart file is not defined. Suggest a rewarding as
shown
Product: Fedora Documentation
Version: devel
Component: installation-quick-start-guide
Severity: low
Assignee: pbokoc(a)redhat.com
Reporter: lsatenstein(a)yahoo.com
QA Contact: docs-qa(a)lists.fedoraproject.org
CC: pbokoc(a)redhat.com, zach(a)oglesby.co
Description of problem:
PDF File Introduction reads
This manual explains how to boot the Fedora installation program,
Anaconda
, and how to install
Fedora 22 on 32 and 64-bit AMD and Intel systems. It also covers advanced
installation methods such
as automated Kickstart installations, booting the installation from a network
location, remote access
to the installation system using VNC, and system upgrades from previous
versions of Fedora. It also
describes common post-installation tasks and explains how to troubleshoot
common issues related to
the installation.
Version-Release number of selected component (if applicable):
How reproducible:
What is a Kickstart?
Expected results:
Add text "parameter file" following Kickstart as follows
This manual explains how to boot the Fedora installation program,
Anaconda
, and how to install
Fedora 22 on 32 and 64-bit AMD and Intel systems. It also covers advanced
installation methods such
as automated Kickstart parameter file installations, booting the installation
from a network location, remote access
to the installation system using VNC, and system upgrades from previous
versions of Fedora. It also
describes common post-installation tasks and explains how to troubleshoot
common issues related to
the installation.
Additional info:
Kickstart is not an industry term, it is specific to and an anaconda parameter
file
VNC is an industrial term so it needs no qualification.
--
You are receiving this mail because:
You are the QA Contact for the bug.
8 years, 12 months