You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: README.md
+7-26Lines changed: 7 additions & 26 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -8,7 +8,10 @@ This is a bespoke Prometheus exporter used to enable the monitoring of Pacemaker
8
8
1.[Features](#features)
9
9
2.[Installation](#installation)
10
10
3.[Usage](#usage)
11
-
4.[Development](#development)
11
+
1.[Metrics](doc/metrics.md)
12
+
5.[Contributing](#contributing)
13
+
1.[Design](doc/design.md)
14
+
2.[Development](doc/development.md)
12
15
5.[License](#license)
13
16
14
17
## Features
@@ -32,7 +35,6 @@ The project can be installed in many ways, including but not limited to:
32
35
2.[Go](#go)
33
36
3.[RPM](#rpm)
34
37
35
-
36
38
### Manual clone & build
37
39
38
40
```
@@ -73,6 +75,8 @@ It will export the metrics under the `/metrics` path, on port `9664` by default.
73
75
While the exporter can run outside a HA cluster node, it won't export any metric it can't collect; e.g. it won't export DRBD metrics if it can't be locally inspected with `drbdsetup`.
74
76
A warning message will inform the user of such cases.
75
77
78
+
Please, refer to [doc/metrics.md](doc/metrics.md) for extensive details about all the exported metrics.
79
+
76
80
**Hint:**
77
81
You can deploy a full HA Cluster via Terraform with [SUSE/ha-sap-terraform-deployments](https://github.com/SUSE/ha-sap-terraform-deployments).
We recommend having a look at the [design document](doc/design.md) before contributing.
106
-
107
-
#### Makefile
108
-
109
-
Most development tasks can be accomplished via [make](Makefile).
110
-
111
-
The default target will clean, analyse, test and build the amd64 binary into the `build/bin` directory.
112
-
113
-
You can also cross-compile to the various architectures we support with `make build-all`.
114
-
115
-
##### Open Build Service releases
116
-
117
-
The CI will automatically publish GitHub releases to SUSE's Open Build Service: to perform a new release, just publish a new GH release or push a git tag. Tags must always follow the [SemVer](https://semver.org/) scheme.
118
-
119
-
If you wish to produce an OBS working directory locally, after you have configured [`osc`](https://en.opensuse.org/openSUSE:OSC) locally, you can run:
120
-
```
121
-
make obs-workdir
122
-
```
123
-
This will checkout the OBS project and prepare a release in the `build/obs` directory.
124
-
125
-
Note that, by default, `dev` is used as the RPM `Version` field, as well as a suffix for all the binary file names.
126
-
To prepare an actual release, you can use the `VERSION` environment variable to set this value to an actual release tag.
127
-
128
-
To commit the release to OBS, run `make obs-commit`.
109
+
We recommend having a look at the [design document](doc/design.md) and the [development notes](doc/development.md) before contributing.
Most development tasks can be accomplished via [make](../Makefile).
10
+
11
+
For starters, you can run the default target with just `make`.
12
+
13
+
The default target will clean, analyse, test and build the amd64 binary into the `build/bin` directory.
14
+
15
+
You can also cross-compile to the various architectures we support with `make build-all`.
16
+
17
+
18
+
## OBS Packaging
19
+
20
+
The CI will automatically publish GitHub releases to SUSE's Open Build Service: to perform a new release, just publish a new GH release or push a git tag. Tags must always follow the [SemVer](https://semver.org/) scheme.
21
+
22
+
If you wish to produce an OBS working directory locally, having configured [`osc`](https://en.opensuse.org/openSUSE:OSC) already, you can run:
23
+
```
24
+
make obs-workdir
25
+
```
26
+
This will checkout the OBS project and prepare a new OBS commit in the `build/obs` directory.
27
+
28
+
Note that, by default, the current Git working directory HEAD reference is used to download the sources from the remote, so this reference must have been pushed beforehand.
29
+
30
+
You can use the `OSB_PROJECT`, `OBS_PACKAGE`, `REPOSITORY` and `VERSION` environment variables to change the behaviour of OBS-related make targets.
31
+
32
+
For example, if you were on a feature branch of your own fork, you may want to change these variables, so:
33
+
```bash
34
+
git push feature/yxz # don't forget to make changes remotely available
35
+
export OBS_PROJECT=home:JohnDoe
36
+
export OBS_PACKAGE=my_project_branch
37
+
export REPOSITORY=johndoe/my_forked_repo
38
+
export VERSION=feature/yxz
39
+
make obs-workdir
40
+
```
41
+
will prepare to commit on OBS into `home:JohnDoe/my_project_branch` by checking out the branch `feature/yxz` from `github.com/johndoe/my_forked_repo`.
42
+
43
+
At last, to actually perform the commit into OBS, run `make obs-commit`.
0 commit comments