x/solar
Code Issues Proposed changes
Resource management and orchestration engine for distributed systems
142 Commits 1 Branch 3 Tags 5.5 MiB
Python 91.4%
Shell 4.9%
Erlang 1.6%
Ruby 1.1%
HAProxy 0.6%
Other 0.3%
98bb9923a2
Go to file
Evgeniy L 98bb9923a2 Implement ensure mechanism for containers 
Added workaround to stop containers which should
not be on the node, accouding to a file with list
of services which is filled in by ansible's tasks.

It allows to implement scale-down and resource
migration.
2015-04-23 16:07:31 +03:00
docs/spec Add single doc to refrence all of fuel's orchestration logics 2015-04-07 14:37:54 -07:00
examples Implement ensure mechanism for containers 2015-04-23 16:07:31 +03:00
solar Use yaml based instead of template based format for objects filtering 2015-04-22 14:31:17 +03:00
templates Add remove actions for keystone, mariadb, haproxy 2015-04-20 18:26:46 +03:00
.gitignore Add commands to work with prototype using ansible 2015-04-01 17:12:39 -07:00
compose.yml Original schema 2015-03-27 16:58:47 -07:00
config.yml Make paths in ansible extention fully qualified 2015-04-16 15:51:50 -07:00
docker.yml It's not required to pull specific docker image for development env 2015-04-13 16:55:25 +03:00
Dockerfile Add missed items in Dockerfile and kolla.yml 2015-04-16 16:50:58 -07:00
kolla.yml Add missed items in Dockerfile and kolla.yml 2015-04-16 16:50:58 -07:00
LICENSE Initial commit 2015-03-27 15:54:19 -07:00
main.yml Change pudb to python-pudb 2015-04-07 17:15:50 -07:00
README.md Fix up the markup in README 2015-04-16 17:07:11 -07:00
Vagrantfile Update path to vagrant box, because previous was removed 2015-04-14 17:42:10 +03:00

README.md

Setup development env

  • Install virtualbox
  • Install vagrant
  • Setup environment
$ cd fuel-ng
$ vagrant up
  • Login into vm, the code is available in /vagrant directory
$ vagrant ssh
$ solar --help

Solar usage

  • discover nodes, with standard file based discovery
solar discover
  • create profile (global config)
solar profile --create --id prf1 --tags env/test_env

  • assign nodes to profile with tags

  • edit nodes files, in the future we want to provide some cli in order to change the data

vim tmp/storage/nodes-id.yaml
  • add env/test_env in tags list
  • in order to assign resouce to the node use the same the same method, i.e. add in tags list for node your service e.g. service/docker, service/mariadb
  • perform deployment
solar configure --profile prf1 -pa run