Skip to content

GitLab

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
stork
stork
  • Project overview
    • Project overview
    • Details
    • Activity
    • Releases
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 145
    • Issues 145
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
  • Merge Requests 2
    • Merge Requests 2
  • Operations
    • Operations
    • Incidents
  • Packages & Registries
    • Packages & Registries
    • Container Registry
  • Analytics
    • Analytics
    • Repository
    • Value Stream
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Members
    • Members
  • Collapse sidebar
  • Activity
  • Graph
  • Create a new issue
  • Commits
  • Issue Boards
  • ISC Open Source Projects
  • storkstork
  • Issues
  • #250

Closed
Open
Opened Apr 22, 2020 by Tomek Mrugalski@tomek🛰Owner

Easier Kea sabotage (demo only)

Ok, sabotage is maybe not the best word, but now that I have your attention, here's what the problem is:

we want to kill and later revive Kea server that is working in HA pair, so the HA problems demonstration is easier.

During the demo I did the following:

  1. docker-compose exec agent-kea-ha2 /bin/bash
  2. edit /etc/supervisor.conf. In [kea-dhcp4] section I modified autorestart = false
  3. kill 1 (supervisor process). This restarted the container (and kicked me out in the process)
  4. I was now able to get in again (docker-compose ...) and then kill kea: killall kea-dhcp4 <observe how Stork detects HA failures, wait a bit>
  5. start kea with kea-dhcp4 -c /etc/kea/kea-dhcp4.conf

The absolute minimum we could do is this:

  1. tweak docker recipes to build the containers with autorestart disabled
  2. maybe tweak the DHCP traffic generator, to make it easier to start/stop the service.

Alternatively, we should describe somewhere how non-developer can stop and start Kea service in the container. I don't know, maybe it would be easier to figure some easy way to stop/start the whole container altogether?

In any case there should be some wiki update regarding how to do it.

Edited May 05, 2020 by Tomek Mrugalski
Assignee
Assign to
Outstanding
Milestone
Outstanding
Assign milestone
Time tracking
None
Due date
None
Reference: isc-projects/stork#250