foreman

server lifecycle automation

From GitHub

an application that automates the lifecycle of servers

Foreman is a free open source project that gives you the power to easily automate repetitive tasks, quickly deploy applications, and proactively manage your servers life cycle, on-premises or in the cloud.

From provisioning and configuration to orchestration and monitoring, Foreman integrates with your existing infrastructure to make operations easier.

• Website: theforeman.org
• ServerFault tag: Foreman
• Issues: Redmine
• Wiki: Foreman wiki
• Forum: Foreman Community
• Chat: We use Libera.Chat IRC channels
  • #theforeman for general support
  • #theforeman-dev for development chat

Using Puppet, Ansible, Chef, Salt and Foreman's smart proxy architecture, you can easily automate repetitive tasks, quickly deploy applications, and proactively manage change, both on-premise with VMs and bare-metal or in the cloud.

Foreman provides comprehensive, interaction facilities including a web frontend, CLI and RESTful API which enables you to build higher level business logic on top of a solid foundation.

Foreman is a mature project, deployed in many organizations, managing from 10s to 10000s of servers. It is used in distributions such as RDO and RHOS (Red Hat OpenStack distribution) and has an extensive library of plugins.

Features

• Automate your mixed infrastructure to make operations enjoyable
• Discover, provision and upgrade your entire bare-metal infrastructure
• Create and manage instances across private and public clouds
• Group your hosts and manage them in bulk, regardless of location
• Review historical changes for auditing or troubleshooting
• Extend as needed via a robust plugin architecture
• Automatically build images (on each platform) per system definition to optimize deployment
• LDAP authentication and RBAC authorization to your infrastructure
• and so much more

Screenshots

Installation

Read the quickstart section of the manual. If you know your setup has some specific needs, read the installation scenarios section.

Documentation

Our main documentation reference is the Foreman manual. If you find some gaps you would like to fill in the manual, please contribute in this repo.

API

We document our API using apipie.The API chapter has more information about accessing the API and the layout of requests and responses. Also see the reference documentation available on our website, or via your own Foreman installation by appending /apidoc to the URL to see the API routes available.

Plugins

Plugins are tools to extend and modify the functionality of Foreman. They are implemented as Rails engines that are packaged as gems and thus easily installed into Foreman.

The plugins page lists all available plugins and has more information about how to install and develop them.

Similarly Named Project

There is a similarly named project on Github called foreman (a CLI tool for running processes).
We've left a note about it here, to help people in case that's the one they're looking for, but ended up here.

How to contribute?

Generally, follow the Foreman guidelines. For code-related contributions, fork this project and send a pull request with all changes. Some things to keep in mind:
* Follow the rules about commit message style and create a Redmine issue. Doing this right will help reviewers to get your contribution merged faster.
* We have a development handbook to help developers understand how Foreman developers code.
* Rubocop will analyze your code, you can run it locally with rake rubocop.
* All of our pull requests run the full test suite in our Jenkins CI system. Please include tests in your pull requests for any additions or changes in functionality.
* Please have a look at Contributing.md for more information.

Media

We keep a repository of talks, tutorials, articles about everything in the Foreman ecosystem in the media section of our web. If you want to get yours published, just submit a pull request to theforeman.org repository

Special thanks

The original authors of this project are Ohad Levy and Paul Kelly.
You can find a more thorough list of people who have contributed to this project at some point in [Contributors](Contributors).

Licensing

See [LICENSE](LICENSE) file.

The Foreman repository/package is licensed under the GNU GPL v3 or newer, with some exceptions.

Copyright (c) 2009-2020 to Ohad Levy, Paul Kelly and their respective owners.

All copyright holders for the Foreman project are in the separate file called Contributors.

Except where specified below, this program and entire repository is free software: you can redistribute it and/or modify it under the terms of the GNU General Public License as published by the Free Software Foundation, either version 3 of the License, or any later version.

This program is distributed in the hope that it will be useful, but WITHOUT ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU General Public License for more details.

You should have received a copy of the GNU General Public License along with this program. If not, see GNU licenses.

The following files and directories are exceptions:

• app/views/unattended/ztp/provision.erb is (c) 2013, Juniper Networks under 2-clause BSD license.
• lib/tasks/convert.rake is (c) 2008, Matson Systems, Inc. under Revised BSD license.
• vendor/assets/fonts/ is (c) 2011-2016, Red Hat Inc. under SIL Open Font License v1.1 or LGPL v2.1 licenses.
• vendor/assets/javascripts/jquery.flot.axislabels.js is (c) 2010 Xuan Luo under MIT license.
• app/assets/images/RancherOS.png is (c) 2018 Rancher Labs, Inc.

All rights reserved.

The [LICENSE](LICENSE) file contains the full text of the GNU GPL v3 license, along with the text for all additional licenses referenced above.