Skip to content
GitLab
Explore
Sign in
Primary navigation
Search or go to…
Project
S
snf-ganeti
Manage
Activity
Members
Labels
Plan
Issues
0
Issue boards
Milestones
Wiki
Code
Merge requests
0
Repository
Branches
Commits
Tags
Repository graph
Compare revisions
Build
Pipelines
Jobs
Pipeline schedules
Artifacts
Deploy
Releases
Model registry
Operate
Environments
Monitor
Incidents
Analyze
Value stream analytics
Contributor analytics
CI/CD analytics
Repository analytics
Model experiments
Help
Help
Support
GitLab documentation
Compare GitLab plans
Community forum
Contribute to GitLab
Provide feedback
Keyboard shortcuts
?
Snippets
Groups
Projects
Show more breadcrumbs
itminedu
snf-ganeti
Commits
57ef88df
Commit
57ef88df
authored
14 years ago
by
Iustin Pop
Browse files
Options
Downloads
Patches
Plain Diff
Fix a couple of typos in the manpages
Again, thanks to lintian.
parent
0ca66853
No related branches found
Branches containing commit
No related tags found
Tags containing commit
No related merge requests found
Changes
3
Hide whitespace changes
Inline
Side-by-side
Showing
3 changed files
hail.1
+2
-2
2 additions, 2 deletions
hail.1
hbal.1
+1
-1
1 addition, 1 deletion
hbal.1
hspace.1
+2
-2
2 additions, 2 deletions
hspace.1
with
5 additions
and
5 deletions
hail.1
+
2
−
2
View file @
57ef88df
...
...
@@ -32,7 +32,7 @@ select the node which, when chosen as the primary node, gives the best
score.
For dual\(hynode allocations (mirrored instances), we chose the best
pair; this is the only choice where the algoritm is non\(hytrivial
pair; this is the only choice where the algorit
h
m is non\(hytrivial
with regard to cluster size.
For node evacuations (\fImulti-evacuate\fR mode), we iterate over all
...
...
@@ -52,7 +52,7 @@ tags will be read from the cluster tags, configured as follows:
- use their suffix as the prefix for exclusion tags
For example, given a cluster tag like \fBhtools:iextags:service\fR,
all instance tags of the form \fBservice:X\fR will be con
f
idered as
all instance tags of the form \fBservice:X\fR will be con
s
idered as
exclusion tags, meaning that (e.g.) two instances which both have a
tag \fBservice:foo\fR will not be placed on the same primary node.
...
...
This diff is collapsed.
Click to expand it.
hbal.1
+
1
−
1
View file @
57ef88df
...
...
@@ -256,7 +256,7 @@ It is possible to customise the listed information by passing a
comma\(hyseparated list of field names to this option (the field list
is currently undocumented), or to extend the default field list by
prefixing the additional field list with a plus sign. By default, the
node list will contain the
se
information
s
:
node list will contain the
following
information:
.RS
.TP
.B F
...
...
This diff is collapsed.
Click to expand it.
hspace.1
+
2
−
2
View file @
57ef88df
...
...
@@ -164,7 +164,7 @@ example, the cluster might still have 100GiB disk free, but with no
memory left for instances, we cannot allocate another instance, so in
effect the disk space is unallocable. Note that the CPUs here
represent instance virtual CPUs, and in case the \fI--max-cpu\fR
option hasn't been specified this will be -1.
option hasn't been specified this will be
\
-1.
.TP
.I ALLOC_USAGE
...
...
@@ -247,7 +247,7 @@ It is possible to customise the listed information by passing a
comma\(hyseparated list of field names to this option (the field list
is currently undocumented), or to extend the default field list by
prefixing the additional field list with a plus sign. By default, the
node list will contain the
se
information
s
:
node list will contain the
following
information:
.RS
.TP
.B F
...
...
This diff is collapsed.
Click to expand it.
Preview
0%
Loading
Try again
or
attach a new file
.
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Save comment
Cancel
Please
register
or
sign in
to comment