suse / doc-susemanager Goto Github PK
View Code? Open in Web Editor NEWSUSE Manager documentation - Deprecated - docs have migrated to the Uyuni-project
Home Page: https://documentation.suse.com/suma/
SUSE Manager documentation - Deprecated - docs have migrated to the Uyuni-project
Home Page: https://documentation.suse.com/suma/
I have noticed an error in the port table in the SUSE Manager documentation:
Correction:
In the port table:
Incorrect: 4505 and 4506 are listed as inbound and outbound
Correct: 4505 and 4506 are inbound only
Notes: The salt master never initiates a connection to the minions.
Richard
Previously, an empty profile was assigned to a HW type group matching to its manufacturer
and product
grains on registration.
After https://github.com/SUSE/spacewalk/pull/6148 is merged, this group assignment is skipped if the empty profile is already assigned to some HW type group (a server group with name with HWTYPE:
prefix).
Best Practices does not document the $ifEmpty
and $optional
attributes which has been shipped in these formulas:
$ifEmpty
is only used here)In particular I am confused what the precise relationship between $default
, $optional
, and $ifEmpty
is.
$ifEmpty
was implemented in https://github.com/SUSE/spacewalk/pull/4261 .
For context, I need this because YaST is adding support for Salt Formulas: FATE#32722
Public cloud document is a little wordy, and should be cleaned up with adoc block structures.
Lana found a bug in how the pdf procedure is rendering, we are not sure if it is due to xslt, or to a formatting issue.
Explore the correct way to make a procedure then check to see how it is rendered in html and pdf.
Best Practices does not document the $key
attribute which has been shipped in these formulas:
For context, I need this because YaST is adding support for Salt Formulas: FATE#32722
Document all fucntions containing the activationkey_ prefix.
https://docreview.nue.suse.com/assets/docs/ref.webui.admin.html#ref.webui.admin.schedules
<- token cleanup is not listed here, maybe we should add it?
We missed the License inclusion during the xml -> adoc migration. It has been converted, but we need to simply link the license to the LICENSE document in our publishing repos.
The current Salt GS is the first draft, it needs revision for clarity.
Add missing help entities to reference > help
It would be advisable to document the task minion-action-cleanup on our documentation.
Doesn't seem to make it clear that it's trying to describe salt-based configuration management, and the traditional configuration management. It's post-fixing some stuff with "[Management]" but that's not very clear what it means.
Just creating this card, so we don't forget to document this:
At the moment I don't know how much we need to document (and even where ๐ the feature overlaps with Retail). I need to discuss this with @aaannz and @jcayouette .
rhnpush -> mgr-push
rhn-virtualization -> mgr-virtualization
rhn-custom-info -> mgr-custom-info
osad -> mgr-osad
rhncfg -> mgr-cfg
spacewalksd -> mgr-daemon
Details at https://github.com/SUSE/spacewalk/pull/5375 (stil WIP)
Keep in mind those are build service packages, which means they will generate subpackages (the real RPM).
According to @Loquacity some changes will be required.
Ping me if you need more details.
We need to clarify when to use db5 replacement macros and which ones are available.
Create a table in the guide adding the available geekodoc macros, for example:
[filename]/etc/hosts
[literal]This is a literal string
Right now it reads:
Multi-core 64-bit CPU
We are having situations where a 2 core CPU, with each core at 1800Mhz is not enough, and we get ISE at some situations because of ProxyTimeouts waiting HTTP responses while playing with the products page at the same time reposync is running.
So the question is: would we support a customer running an Intel Celeron x86_64 with 2 cores, as long as memory and storage are OK?
For example the Celeron 2970M from 2014 (https://ark.intel.com/products/81014)
This is even more critical for Uyuni, as I am pretty sure that some users will be using consumer grade hardware for testing.
Not clear, but as a minimum, maybe we should specify the number of cores (as we do for PowerPC):
Minimum 4 dedicated cores
I am not so sure about the frequency :-(
But anyway, I think this is something to be discussed with engineering as well.
We need a note in the activation key section that you can also bootstrap salt minions.
There is a note in the gs on using the bootstrap script for registering Salt client, however we need to add that activation keys can now be used in the script as well.
Best Practices - FIle Overview description contains some confusing documentation examples about custom formula directories, i have added just two comments for trying to make it more clear.
Custom metadata (information) need to be placed in:
# Replacing `custom` by `custom-formula-name` as it is already documented in other examples probably would be less confusing
/srv/formula_metadata/custom/
All custom folders located in the following directories needs to contain a form.yml file. These files are detected as form recipes and may be applied to groups and systems from the Web UI:
# Is this path correct? it seems that `salt` was added by error or confusion with the states directories
/srv/salt/formula_metadata/custom-formula-name/form.yml
The SUSE Manager 3 Reference Manual still references up2date which was the old package manager used by Red Hat on RHEL 4 in 2005 and never used in a SUSE product. Any reference to it should probably be changed to Zypper or Yum. See https://www.suse.com/documentation/suse-manager/singlehtml/book_suma_reference_manual/book_suma_reference_manual.html for examples.
There is a patch currently being reviewed that will introduce a mechanism to cleanup expired notification messages after a configurable lifetime (default still under review, probably 30 or 60 days). This might need to be mentioned in the docs, I guess:
Docs need to be copied from 2.1 xml sources and places in 3.0/3.1 xml sources.
command-line-tools.adoc
https://github.com/SUSE/doc-susemanager/blob/develop/adoc/command-line-tools.adoc#command-line-toolsA declarative, efficient, and flexible JavaScript library for building user interfaces.
๐ Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
An Open Source Machine Learning Framework for Everyone
The Web framework for perfectionists with deadlines.
A PHP framework for web artisans
Bring data to life with SVG, Canvas and HTML. ๐๐๐
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
Some thing interesting about web. New door for the world.
A server is a program made to process requests and deliver data to clients.
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
Some thing interesting about visualization, use data art
Some thing interesting about game, make everyone happy.
We are working to build community through open source technology. NB: members must have two-factor auth.
Open source projects and samples from Microsoft.
Google โค๏ธ Open Source for everyone.
Alibaba Open Source for everyone
Data-Driven Documents codes.
China tencent open source team.