stupro-toscana / stupro_toscana_vorprojekt Goto Github PK

Create the component that links the ther parser, the engine and the cli.

Feeding below model to the parser, no parsing error is thrown. The <DeploymentArtifacts> Element is missing.

Model:

<Node>
            <Name>database</Name>
            <Type>service</Type>
            <ImplementationArtifacts>
                <Create>create</Create>
            </ImplementationArtifacts>
            <DeploymentArtifact key="databaseschema">createdb.sql</DeploymentArtifact>
            <Properties>
                <Property key="user">simpleuser</Property>
                <Property key="password">pass</Property>
                <Property key="databasename">awesomedatabase</Property>
            </Properties>
        </Node>

Log Output:

2017-07-03 20:10:33,365  DEBUG - model.ServiceNode         > Parsed 1 implementation artifacts for node database.
2017-07-03 20:10:33,366  DEBUG - model.ServiceNode         > Parsed 0 deployment artifacts for node database.
2017-07-03 20:10:33,366  DEBUG - model.TOSCAliteModel      > Added service database

In order to allow concurrency and increase performance the engine should support the usage of threads.

Get a profile picture on GitHub and Slack in order to ease communcation

Nice to have: make sure GitHub and Slack avatars are the same

Subissue of #3

Includes the first two tasks of #3

Create a simple PHP - App for test and demonstration purposes.

If model was create set variable that it cannot be called twice

The engine needs to provide methods to create, start and stop the application through a ssh connection.
To establish this connection and send the SSH commands it should use the methods provided by the executor interface.

Progress:

• extraction of properties from the topology
• establishing an SSH connection
• sending SSH commands to the VM(s)
  • create()
  • start()
  • stop()

The .iml files and the .idea folder are not necessary to configure IntelliJ, the IDE generates these files out of the pom.xml. So theres no need for them to be in the repo.
To remove these files from git do the following steps.

1. Get the new .gitignore from master:
   you can run git checkout --patch master .gitignore to get the new file, or just copy and paste to your branch
2. remove the files from git:
   git rm -r --cached .idea
git rm -r --cached *.iml
   this wont remove them from you hard drive only from git
3. stage,commit and push to your branch

thx!

In order to be able to deploy a TOSCAlite model on Ubuntu Machines, the model.xml contained in the deployment archive has to be parsed.
This issue is divided into the following subtasks:

• Develop object-oriented class model for the TOSCAlite model.xml specification. (class diagram)
• Create Java-classes for the specified class diagram.
• Implement the parser itself.
• Document Java code.
• Optional: Implement unit-tests for edge cases.

A static folder (basically its content, bunch of shell scripts) must be transfered to every machine right after establishing initial connection. They need to be available within implementation artifacts.

export PATH="$PATH:/path/to/folder/with/scripts" <-- put this into $HOME/.profile

problem: when using sudo (ubuntu only) you cant access youre old path, but the definde 'secure path' (some scripts need to be performed as root)
solution: Additionally to above PATH extension, this 'secure path' must be modified in /etc/sudoers.

To ensure the correct functionality of the Engine classes, all methods should be tested with an example topology.

Progress:

• creating an example topology (as a data model)
• create() method
  • sorting methods in the Creator class
• start() method
• stop() method

Get Log4j onboard; use SLF4J as interface.

The engine needs to be able to interpret the data model created by the XML parser in order to generate the sequence of deployment operations. This is done by iterating through the nodes and relationships in the data model and determining the dependencies.

• enable interpretation of TOSCAlite models
• create a method to sort Nodes based on parent-child relationships
• integrate the sorted Node list into the create(), start() and stop() methods

A documetation how to build and use the program is requiered.

Todo:

• Installation/Build guide
• How to deploy guide

To begin the implementation of the engine, a code structure must first be designed. This can be done through dummy classes and methods.

Design an easy to use comand line interface for the transformator.

Implement all the bash scripts which are used as implementation artifacts for the test application

Create the cli, to control the engine by a cli.