|
|
| (3 intermediate revisions by the same user not shown) |
| Line 1: |
Line 1: |
| − | == Winery Code Setup Guide ==
| + | Content moved to http://eclipse.github.io/winery/ |
| − | | + | |
| − | === Repositories ===
| + | |
| − | | + | |
| − | Winery is split into three repositories: [http://git.eclipse.org/c/winery/org.eclipse.winery.misc.git/ misc], [http://git.eclipse.org/c/winery/org.eclipse.winery.models.git/ models], and [http://git.eclipse.org/c/winery/org.eclipse.winery.winery.git/ winery].
| + | |
| − | Check out each of it in a separate folder.
| + | |
| − | Under Windows, we recommend the parent folder to reside the root directory due to long path names during compilation: <tt>c:\wr</tt>
| + | |
| − | | + | |
| − | ==== org.eclipse.winery.misc ====
| + | |
| − | | + | |
| − | Contains documentation, eclipse configuration, graphics, and the high level REST API package
| + | |
| − | | + | |
| − | ==== org.eclipse.winery.models ====
| + | |
| − | | + | |
| − | Contains models:
| + | |
| − | | + | |
| − | * CSAR meta file
| + | |
| − | * Self-service Portal
| + | |
| − | * TOSCA
| + | |
| − | | + | |
| − | ==== org.eclipse.winery.winery ====
| + | |
| − | | + | |
| − | Contains the winery itself.
| + | |
| − | | + | |
| − | === Compilation Instructions ===
| + | |
| − | | + | |
| − | ==== Make Models Available ====
| + | |
| − | | + | |
| − | For each model in <tt>org.eclipse.winery.models</tt> do a <tt>mvn install</tt>.
| + | |
| − | | + | |
| − | ==== Compile Winery ====
| + | |
| − | | + | |
| − | In <tt>org.eclipse.winery.winery</tt>, see the [http://git.eclipse.org/c/winery/org.eclipse.winery.winery.git/plain/README.md README.md] there.
| + | |
| − | | + | |
| − | == Winery Add-ons ==
| + | |
| − | [[Winery Topology Completion]]
| + | |
| − | | + | |
| − | ==== TOSCA Topology Completion ====
| + | |
| − | | + | |
| − | The TOSCA Topology Completion of Winery enables the user to model incomplete TOSCA Topology Templates and complete them automatically.
| + | |
| − | | + | |
| − | In the following we will describe how such incomplete topologies can be modeled and how the Topology Completion can be invoked.
| + | |
| − | | + | |
| − | ====== Modeling incomplete TOSCA Topology Templates ======
| + | |
| − | There are several ways to model incomplete topologies that will be described in the following.
| + | |
| − | | + | |
| − | 1. Modeling incomplete TOSCA Topology Templates using TOSCA Requirements
| + | |
| − | | + | |
| − | TOSCA Requirements make it possible to define restrictions for the topology completion. By adding TOSCA Requirements to Node Templates
| + | |
| − | you can determine which elements may or may not be added to the topology. E.g. by adding the Requirement "SQLDatabaseRequirement" you can predetermine
| + | |
| − | that a "SQLDatabase" Node Template will be added to the topology. Note that in this case a Node Type with a suitable CapabilityDefinition (e.g. SQLDatabaseCapability) has to exist to fulfill the Requirement.
| + | |
| − | | + | |
| − | tbd.
| + | |
| − | | + | |
| − | | + | |
| − | ====== Invoking the TOSCA Topology Completion ======
| + | |
| − | | + | |
| − | To invoke the Topology Completion open an incomplete topology in the topology modeler and select "Complete Topology".
| + | |
| − | In the appearing dialog fill in the save options for the completed topology, the used TOSCA Runtime (exclusively OpenTOSCA at the moment) and if the topology completion shall be processed step-by-step.
| + | |
| − | In case the step-by-step approach is selected, the topology completion algorithm will pause in every step giving feedback about the Node and Relatioship Templates
| + | |
| − | to be inserted.
| + | |
| − | | + | |
| − | After the form has been completed you can start the completion by selecting "Complete Topology" in the dialog.
| + | |
| − | | + | |
| − | After the completion the completed topology will be displayed in the topology modeler or in a new browser window dependent on the save options.
| + | |
