Skip to content

Commit

Permalink
Added new files for rsynch Smartdocs
Browse files Browse the repository at this point in the history
  • Loading branch information
Shalaka Harne committed Jan 17, 2024
1 parent 873d4b8 commit cea0e30
Show file tree
Hide file tree
Showing 4 changed files with 212 additions and 4 deletions.
17 changes: 17 additions & 0 deletions DC-copy-file-rsync
Original file line number Diff line number Diff line change
@@ -0,0 +1,17 @@
## ----------------------------
## Doc Config File for the DB Assembly
## ----------------------------
##
## Basics
MAIN="copy-file-with-rsync.asm.xml"
SRC_DIR="articles"
IMG_SRC_DIR="images"

## Profiling
PROFOS="generic"
#PROFARCH="x86_64;zseries;power;aarch64"

## stylesheet location
STYLEROOT="/usr/share/xml/docbook/stylesheet/suse2022-ns"
FALLBACK_STYLEROOT="/usr/share/xml/docbook/stylesheet/suse2021-ns"
DOCBOOK5_RNG_URI="urn:x-suse:rng:v2:geekodoc-flat"
191 changes: 191 additions & 0 deletions articles/copy-file-with-rsync.asm.xml
Original file line number Diff line number Diff line change
@@ -0,0 +1,191 @@
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<!-- file: templates/articles/assembly.xml -->
<?xml-model href="https://cdn.docbook.org/schema/5.2/rng/assemblyxi.rnc"
type="application/relax-ng-compact-syntax"?>
<!DOCTYPE assembly
[
<!ENTITY % entities SYSTEM "../common/generic-entities.ent">
%entities;
]>
<!-- refers to legacy doc: <add github link to legacy doc piece, if applicable> -->
<!-- point back to this document with a similar comment added to your legacy doc piece -->
<!-- refer to README.md for file and id naming conventions -->
<assembly version="5.2" xml:lang="en"
xmlns:xlink="http://www.w3.org/1999/xlink"
xmlns:trans="http://docbook.org/ns/transclusion"
xmlns:its="http://www.w3.org/2005/11/its"
xmlns="http://docbook.org/ns/docbook">
<!-- resources section references all topic chunks used in the final article
-->
<!-- R E S O U R C E S -->
<!-- Glue files -->
<!--><resources>
<resource xml:id="_glue-example" href="../glues/glue.xml">
<description>Glue example</description>
</resource>
<resource xml:id="_glue-more-info" href="../glues/glue-more-info.xml">
<description>Glue for more information</description>
</resource>
<resource xml:id="_glue-whats-next" href="../glues/glue-whats-next.xml">
<description>Glue what's next</description>
</resource>
</resources>
-->
<!-- Concept files -->
<!--
<resources>
<resource xml:id="_concept-example" href="../concepts/concept.xml">
<description>Concept example</description>
</resource>
</resources>
-->

<!-- Tasks -->
<!--
<resources>
<resource xml:id="_task-example" href="../tasks/task.xml">
<description>Task example</description>
</resource>
</resources>
-->
<!-- References -->
<!--
<resources>
<resource xml:id="_reference-example" href="../references/reference.xml">
<description>Reference example</description>
</resource>
</resources>
-->
<!-- Legal -->
<resources>
<resource href="../common/legal.xml" xml:id="_legal">
<description>Legal Notice</description>
</resource>
<resource href="../common/license_gfdl1.2.xml" xml:id="_gfdl">
<description>GNU Free Documentation License</description>
</resource>
</resources>
<!-- S T R U C T U R E -->
<structure renderas="article" xml:id="article-example" xml:lang="en">
<merge>
<title>Copy Files using rsync command</title>
<!-- <subtitle>Subtitle if necessary</subtitle> -->
<!-- Create changelog to enable versioning; add most recent entries at the top. -->
<revhistory>
<title>Changelog</title>
<revision><revnumber>1</revnumber><date>2024-01-08</date>
<revdescription>
<para>
Initial Draft
</para>
</revdescription>
</revision>
</revhistory>
<!-- TODO: provide a listing of possible and validatable meta entry values. Maybe in our geekodoc repo? -->
<!-- add author's e-mail -->
<meta name="Shalaka Harne" content="[email protected]" its:translate="no"/>
<!-- ISO date of last update as YYYY-MM-DD
<meta name="updated" content="2023-11-11" its:translate="no"/> -->
<!-- this does not work yet. Use the dm tags listed below for now
<meta name="bugtracker" its:translate="no">
<phrase role="url">https://bugzilla.suse.com/enter_bug.cgi</phrase>
<phrase role="component">Non-product-specific documentation</phrase>
<phrase role="product">Smart Docs</phrase>
<phrase role="assignee">[email protected]</phrase>
</meta>
-->
<!-- not supported, yet. Use dm: tag for now
<meta name="translation" its:translate="no">
<phrase role="trans">yes</phrase>
<phrase role="language">de-de,cs-cz</phrase>
</meta>
-->
<!-- enter the platform identifier or a list of
identifiers, separated by ; -->
<meta name="architecture" content="x86;power" its:translate="no"/>
<meta name="productname" its:translate="no">
<!-- enter product name and version --><productname version="15-SP5">&sles;</productname>
</meta>
<meta name="title" its:translate="yes">Copy files and directories using rsync command.</meta>
<meta name="description" its:translate="yes">An overview of copying files and directories using rsynch command.</meta>
<meta name="social-descr" its:translate="yes">File copy using rsync</meta>
<!-- suitable category, comma-separated list of categories -->
<meta name="category" content="Systems Management" its:translate="no"/>
<dm:docmanager xmlns:dm="urn:x-suse:ns:docmanager">
<dm:bugtracker>
<dm:url>https://bugzilla.suse.com/enter_bug.cgi</dm:url>
<dm:component>Smart Docs</dm:component>
<dm:product>Documentation</dm:product>
<dm:assignee>[email protected]</dm:assignee>
</dm:bugtracker>
<dm:translation>yes</dm:translation>
</dm:docmanager>
<abstract>
<variablelist>
<varlistentry>
<term>WHAT?</term>
<listitem>
<para>
Describe your topic in one sentence.
</para>
</listitem>
</varlistentry>
<varlistentry>
<term>WHY?</term>
<listitem>
<para>
State the reason why one should read this.
</para>
</listitem>
</varlistentry>
<varlistentry>
<term>EFFORT</term>
<listitem>
<para>
What's the effort one has to put in?
</para>
</listitem>
</varlistentry>
<varlistentry>
<term>GOAL</term>
<listitem>
<para>
What's the reader's take-away from this article?
</para>
</listitem>
</varlistentry>
<varlistentry>
<term>REQUIREMENTS</term>
<listitem>
<itemizedlist>
<listitem>
<para>
List the requirements to accomplish the task(s) described below.
</para>
</listitem>
</itemizedlist>
</listitem>
</varlistentry>
</variablelist>
</abstract>
</merge>
<!-- pull in all the topic files you need -->
<!-- pick the appropriate type of include to match your needs -->
<!-- pull in a topic as is -->
<module resourceref="_glue-example" renderas="section"/>
<!-- pull in a topic and switch the title -->
<module resourceref="_concept-example" renderas="section">
<merge>
<title>You are a very special concept now!</title>
</merge>
</module>
<module resourceref="_task-example" renderas="section"/>
<module resourceref="_reference-example" renderas="section"/>
<module resourceref="_glue-more-info" renderas="section"/>
<module resourceref="_glue-whats-next" renderas="section"/>
<module resourceref="_legal"/>
<module resourceref="_gfdl">
<output renderas="appendix"/>
</module>
</structure>
</assembly>
4 changes: 2 additions & 2 deletions articles/manage-vm-on-commandline.asm.xml
Original file line number Diff line number Diff line change
Expand Up @@ -83,8 +83,8 @@
<!-- TODO: provide a listing of possible and validatable meta entry values. Maybe in our geekodoc repo? -->
<!-- add author's e-mail -->
<meta name="maintainer" content="[email protected]" its:translate="no"/>
<!-- ISO date of last update as YYYY-MM-DD -->
<meta name="updated" content="2023-09-19" its:translate="no"/>
<!-- ISO date of last update as YYYY-MM-DD
<meta name="updated" content="2023-09-19" its:translate="no"/>-->
<!-- this does not work yet. Use the dm tags listed below for now
<meta name="bugtracker" its:translate="no">
<phrase role="url">https://bugzilla.suse.com/enter_bug.cgi</phrase>
Expand Down
4 changes: 2 additions & 2 deletions concepts/manage-vm-on-commandline-concept.xml
Original file line number Diff line number Diff line change
Expand Up @@ -33,9 +33,9 @@

<para>You can configure virtual machines managed by &libvirt; using command-line or using Virtual Machine Manager. Interoperability between libvirt and libvirt-based applications are tested and is an essential part of SUSE's support stance.
</para>
<para>&libvirt; tools are designed to work with the &libvirt; API and support various virtualization technologies and hypervisors. Some of the commonly used tools for libvirt are virsh, virt-manager, virt-install, virt-clone, virt-image, and so on.</para>
<para>&libvirt; tools are designed to work with the &libvirt; API and support various virtualization technologies and hypervisors. Some of the commonly used tools for libvirt are virsh, virt-install, remote-viewer, virt-clone, virt-host-validate, virt-manager virt-image, and so on. Libvirt supports using graphical user interface and commands to write XML configurations.</para>
<para>Using the &libvirt;-based tools is the recommended way of managing VM Guests. For example, you can use <command>virsh</command> to configure virtual machines (VM) on the command line as an alternative to using the graphical &vmm;. You can also manage virtual disks using this tool.</para>
<para>The management of virtual machines on command line provides more control over the host machines than using the graphical interface applications.</para>
<para>The management of virtual machines on command line provides more control over the host machines than using the graphical interface applications as it allows scripting and automation.</para>
</section>

<section><title>Benefits of using &libvirt;</title>
Expand Down

0 comments on commit cea0e30

Please sign in to comment.