Changes between Version 1 and Version 2 of DeveloperGuidelines/DeploymentTools


Ignore:
Timestamp:
08/18/14 17:05:11 (10 years ago)
Author:
gnarula
Comment:

--

Legend:

Unmodified
Added
Removed
Modified

  • DeveloperGuidelines/DeploymentTools

    v1 v2  
    1616 * User may add a signle role (all) or multiple roles (db, webserver, eden)
    1717 * User may only associate a single instance (prod/demo) while creating the deployment. Others may be added after succesful deployment of the first one.
    18  * On form submit, a YML file is generated in the yaml/ directory of the application (examples [https://github.com/gnarula/eden_playbook/tree/master/examples] and ansible is ran using the web2py scheduler.
     18 * On form submit, a YML file is generated in the yaml/ directory of the application (examples [https://github.com/sahana/eden_playbook/tree/master/examples] and ansible is ran using the web2py scheduler.
    1919 * The success/failure is reported once the scheduler task is completed.
    20  * If successful, the user may further add instances (eg. demo/test) to the same deployment or issue management tasks using tabs/buttons in the rheader (TODO)
     20 * If successful, the user may further add instances (eg. demo/test) to the same deployment or issue management tasks using tabs/buttons in the rheader
    2121
    2222== Schema ==
    23 
    24 TODO: ER Diagram?
    25 The detailed schema is available at http://paste.ubuntu.com/7872567/
    2623
    2724The setup_deployment table is used to store various attributes related to the deployment.
    … …  
    2926The setup_instance table is used to store the type of instances along with its URL and a FK to scheduler_id. Each time an instance is added to the deployment, a YAML file is created in the background and ansible is called using the web2py scheduler.
    3027
    31 The setup_server_role table is used to store the role (all/db/webserver/eden) of a particular host in the deployment along with its IP and hostname.
     28The setup_server table is used to store the role (all/db/webserver/eden) of a particular host in the deployment along with its IP and hostname.
    3229
    33 The setup_host table acts as a link table to link all the 3 tables above.
    3430
    3531'''Background Workflow'''
    36  * S3SQLInlineComponent/S3SQLInlineLink allows addition of entries in setup_server_role and setup_instance.
     32
     33 * S3SQLInlineComponent/S3SQLInlineLink allows addition of entries in setup_server and setup_instance.
    3734 * After form submission and record creation, an entry is added to the scheduler_task table to run ansible (row id of scheduler_task is stored in setup_instance table). Ansible playbook (yaml file) takes in the values of variables from the user input in the create form.
    3835 * Success/Failure of the deployment is displayed on the "read" method of the deployment