Mirantis/f2s

Name: f2s

Owner: Mirantis Inc.

Description: null

Created: 2016-02-25 16:20:36.0

Updated: 2016-03-03 11:24:28.0

Pushed: 2016-03-17 20:43:35.0

Homepage: null

Size: 448

Language: Python

GitHub Committers

UserMost Recent Commit# Commits

Other Committers

UserEmailMost Recent Commit# Commits

README

How to install on fuel master?

If solar package is not available yet install solar from pip:

install gcc-c++
install virtualenv
ualenv venv
ce venv/bin/activate

install solar

configure solar:

All of this things will be automated by solar eventually

r /etc/solar
 solar_db: sqlite:////tmp/solar.db > /etc/solar/solar.conf

nerate solar resources from library tasks
t2r --dir /tmp/f2s --lib /etc/puppet/modules

eate solar Resource defintions repository
r -p /var/lib/solar/repositories
r repo import /tmp/f2s -n f2s
r repo update f2s f2s/created

one solar-resources and create repositories
clone https://github.com/openstack/solar-resources.git
r repo import solar-resources/resources

before doing any deployment using solar - provision nodes

ovision a node by fuel
 node --node 1 --provision

workflow

epare all configuration in fuel and then use fsclient to copy fuel env
th all configured nodes, -f flag adds master and null preudo role
ient env 1 -f
 u want to copy only specific list of nodes - use
ient env 1 1 2 3

itc to usual solar workflow
r ch stage
r ch process
r or run-once last

Handling updates

  1. adding a new node

    vironment 1 with node 4 was created
    ient env 1 4 -f
    en node with uid 3 needs to be added, but running next command wont be enough
    ient env 1 3
     will create only new node, without updating edges for 4th node that points to
    d, correct way to handle it will be
    ient env 1 3 4
    
  2. adding a role to a deployed node (any partial changes of fuel graph)

    tch graph and make sure that fuel_data is changed, on change of
    el_data - stages will be inserted in the graph
    ient env 1 4
    

    Updating partially graph has some caveats - sometime nailgun may rely on skipped tasks to preserve correct order of execution, however if some of such tasks were commited with 1st role - solar may generate incorrect graph from nailgun point of view. For now it is not clear how to address this issue. For an example of such issue - create controller, commit it with solar, and then add cinder to the same node. You will see that tasks ntp-client and top-role-cinder can be run in parallel, which should be the case - they are in different stages.


This work is supported by the National Institutes of Health's National Center for Advancing Translational Sciences, Grant Number U24TR002306. This work is solely the responsibility of the creators and does not necessarily represent the official views of the National Institutes of Health.