Skip to content

GitLab

  • Menu
Projects Groups Snippets
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
  • stork stork
  • Project information
    • Project information
    • Activity
    • Labels
    • Planning hierarchy
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 216
    • Issues 216
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 15
    • Merge requests 15
  • Deployments
    • Deployments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Packages & Registries
    • Packages & Registries
    • Container Registry
  • Analytics
    • Analytics
    • Value stream
    • Repository
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Commits
  • Issue Boards
Collapse sidebar
  • ISC Open Source Projects
  • storkstork
  • Issues
  • #642

Closed
Open
Created Dec 06, 2021 by Marcin Siodelski@marcinMaintainer

Assorted ARM fixes before the 1.0 release

2.1 Supported Systems

CentOS 7 - should be CentOS 8 macOS 10.5 - should be MacOS 11.3.1

2.3.2.3. Securing Connections

"should be readable/writable only for the user running the Stork Agent" "should be readable/writable only BY the user running the Stork Agent"

"All credentials must to contains the values for 4 keys" "All credentials must contain the values for 4 keys"

"ip", "port" etc should use the `

2.3.2.10/2.3.2.11

There is an example stork-tool command line. Maybe we should add an alternative using individual switches for password, host etc. There is a known problem when someone uses an invalid URL.

2.4.3.

"There are several components of Stork". Should be: "There are two Stork components"

"By default, all components are installed to the root folder in the current directory." Should be: "By default, all components are installed IN the root folder in the current directory."

2.5. Database Migration Tool

It neglects the tool's cert-export feature.

All chapters:

We use Stork Agent, Stork agent, Stork server and Stork Server. We should probably unify.

  1. Using Stork

The first sentence instructs the user to navigate to localhost:8080 without mentioning that the URL varies depending on the configuration.

3.4.2. Deleting a Machine

"The preferred way to achieve that is to issue the killall stork-agent command" Is it really killall stork-agent?

3.5.8. Kea HA Status

The picture is heavily outdated.

3.5.6.3. Sources of Host Reservations

"This interval is currently not configurable." is not true.

  1. Demo

Lacks BIND9_2 container and premium container.

7.2.1

Using kea-1-7 in the example URL for getting the token. It should rather be 2.0.

Assignee
Assign to
Time tracking