| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| |
|
|
|
|
| |
The heavy JS libraries are only used for a simple navbar. It doesn't
make sense to keep them. Instead, a lightweight local version has been
implemented.
|
| | |
|
| | |
|
| |
|
|
|
|
|
|
|
|
| |
The iPXE client just repeats the same request, a.k.a. "polling".
It is the Shoelaces server that can break the polling loop.
Either by handing out automated boot entry point based on IP address
or DNS PTR record, hand picked boot entry point from Web UI
or due retry maximum reached.
Signed-off-by: Geert Stappers <stappers@stappers.it>
|
| |
|
|
|
|
| |
In commit 1c79728984af was endpoint '/start' added,
now it is tested.
Signed-off-by: Geert Stappers <stappers@stappers.it>
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
* String changes in internal/polling/polling.go
The most important one, from the point of view of human user,
is the addition of telling that a maximum retry has been reached.
The poll script got rid of the way too long line. That is done
by using "iPXE script continueing line character", \, backslash.
Poll interval shorter, from ten seconds to seven seconds,
also from 10000 ms to more readable 7000 ms (clearly three zeros (how
many zeros are in 10000? (four or five?))).
Added information about a loop that only looks like a loop.
A minor `s/iPXE/iPXE client/`.
In directory test/integ-test/expected-results/ are poll-unknown.txt
and poll.txt updated for getting a clean `make test`.
* style: build on top of latest contribution
In particular, mentioning 'maxRetry' exposes implementation code to
the end user, which we should avoid.
Co-authored-by: Raul Benencia <raul@thousandeyes.com>
|
| |
|
|
| |
Signed-off-by: Raul Benencia <raul@thousandeyes.com>
|
| |
|
|
| |
Resolves: #17
|
| | |
|
| |
|
