Skip to content
GitLab
Projects Groups Topics Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Register
  • Sign in
  • stork stork
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributor statistics
    • Graph
    • Compare revisions
  • Issues 313
    • Issues 313
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 30
    • Merge requests 30
  • Deployments
    • Deployments
    • Releases
  • Packages and registries
    • Packages and registries
    • Container Registry
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • Repository
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Commits
  • Issue Boards
Collapse sidebar
  • ISC Open Source ProjectsISC Open Source Projects
  • storkstork
  • Issues
  • #299
Closed
Open
Issue created May 28, 2020 by Vicky Risk@vickyDeveloper

Where are my leases?

Cathy commented at one point - 'I have no idea where my leases file is!'

We display what database backends are supported by the image, and in the Host reservations table we display at the far right, where the host information is coming from, but we don't yet show anywhere, where the lease backend is.

I think this should be on both the App detail page and on the right side of the Machine information page (where in another ticket I asked for more App information.

Overview
Version	1.7.4
Version Ext	1.7.4
tarball
linked with:
log4cplus 1.1.2
OpenSSL 1.1.1 11 Sep 2018
database:  
MySQL backend 9.1, library 5.7.30
PostgreSQL backend 6.0, library 100012
Memfile backend 2.1
Hooks	
/usr/lib/x86_64-linux-gnu/kea/hooks/libdhcp_lease_cmds.so
/usr/lib/x86_64-linux-gnu/kea/hooks/libdhcp_ha.so
***************
Leases file location: local memfile (or give the path)
Host reservations location: MySQL db (or give the full path)
**************
Uptime	13 days 23 hours 43 minutes 31 seconds
Last Reloaded At	2020-05-08 08:41:

Comment about database: (Can we rename this something like database backends supported? this list is somewhat misleading because these are just the databases that are linked, not necessarily what the daemon is configured to use. Cathy found this confusing.)

Edited Jul 08, 2020 by Tomek Mrugalski
Assignee
Assign to
Time tracking