Skip to content

GitLab Next

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
GitLab
GitLab
  • Project overview
    • Project overview
    • Details
    • Activity
    • Releases
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
    • Locked Files
  • Issues 36,965
    • Issues 36,965
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
    • Iterations
  • Merge requests 1,455
    • Merge requests 1,455
  • Requirements
    • Requirements
    • List
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
    • Test Cases
  • Operations
    • Operations
    • Metrics
    • Incidents
    • Environments
  • Packages & Registries
    • Packages & Registries
    • Container Registry
  • Analytics
    • Analytics
    • CI/CD
    • Code Review
    • Insights
    • Issue
    • Repository
    • Value Stream
  • Snippets
    • Snippets
  • Members
    • Members
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • GitLab.org
  • GitLabGitLab
  • Issues
  • #7807

Closed
Open
Created Sep 30, 2018 by Sid Sijbrandij@sytsesOwner

Failure Injection Testing (FIT) or Chaos as part of operations features

Inspired by https://help.gremlin.com/infra-attacks/ and the Netflix https://medium.com/netflix-techblog/fit-failure-injection-testing-35d8e2a9bb2

As a user I under the Operations > Chaos menu I can start infrastructure or network chaos.

Infrastructure chaos

  • CPU Generates high load for one or more CPU cores.
  • Memory Allocates a specific amount of RAM.
  • IO Puts read/write pressure on I/O devices such as hard disks.
  • Disk Writes files to disk to fill it to a specific percentage.
  • Shutdown Reboots or halts the host operating system, allowing you to test, for example, how your system behaves when losing one or more cluster machines.
  • Time travel Changes the host’s system time, which can be used to simulate adjusting to daylight saving time and other time-related events.
  • Process killer An attack which kills the specified process, which can be used to simulate application or dependency crashes.

Network chaos

  • Blackhole Drops all matching network traffic.
  • Latency Injects latency into all matching egress network traffic.
  • Packet loss Induces packet loss into all matching egress network traffic.
  • DNS Blocks access to DNS servers.

/cc @markpundsack @danielgruesso

Edited Sep 30, 2018 by Sid Sijbrandij
Assignee
Assign to
Backlog
Milestone
Backlog
Assign milestone
Time tracking