Skip to content

infraguys/genesis_core

Repository files navigation

Tests workflow Build workflow

genesis core svg logo

Welcome to Genesis Core!

The Genesis Core is an open source software that offers a one turnkey solution to deal with infrastructure at all levels - from bare metal and virtual machines to applications and services.

Refer to the wiki for more detailed information.

📦 Installation

There are several ways to install Genesis Core and depend on your purpose you can choose one of them.

Try it out

NOTE: Under development

If you want to try Genesis Core in a few minutes, download the all-in-one stand. It's a ready-to-go virtual machine image with preinstalled Genesis Core and ability to get full functionality such as creating inner(nested) virtual machines, installation elements and many others. This stand may be used for development purposes as well if you are focusing on a new element development.

Basic usage

In a case you would like to run Genesis Core on your own infrastructure, you can use the basic guide for more details.

🚀 Development

Ubuntu:

sudo apt-get install build-essential python3.12-dev python3.12-venv \
    tox libev-dev libvirt-dev

Fedora:

sudo dnf install tox gcc libev-devel libvirt-devel

Initialize virtual environment:

tox -e develop
source .tox/develop/bin/activate

Follow the development guide here for more details.

⚙️ Tests

NOTE: Python version 3.12 is supposed to be used, but you can use other versions

# Unit tests
tox -e py312

# Functional tests
tox -e py312-functional

🔗 Related projects

  • Genesis SDK is a set of tools for developing Genesis elements. You can find it here.
  • Genesis DevTools it's a set oftools to manager life cycle of genesis projects. You can find it here.

💡 Contributing

Contributing to the project is highly appreciated! However, some rules should be followed for successful inclusion of new changes in the project:

  • All changes should be done in a separate branch.
  • Changes should include not only new functionality or bug fixes, but also tests for the new code.
  • After the changes are completed and tested, a Pull Request should be created with a clear description of the new functionality. And add one of the project maintainers as a reviewer.
  • Changes can be merged only after receiving an approve from one of the project maintainers.

About

No description or website provided.

Topics

Resources

Stars

Watchers

Forks

Releases

No releases published

Packages

No packages published

Contributors 4

  •  
  •  
  •  
  •  

Languages