Gld Development: Difference between revisions

From NovaOrdis Knowledge Base
Jump to navigation Jump to search
Line 54: Line 54:
=TODO=
=TODO=


* <font color=red>Tactical GLD.docx on Desktop. Start from there or transfer from there.</font>
Temporarily, in {{External|https://github.com/NovaOrdis/gld/blob/master/todo/Tactical%20GLD.docx}} as Tactical GLD.docx.

Revision as of 03:11, 11 February 2017

Internal

GitHub

https://github.com/NovaOrdis/gld

Overview

From a project perspective, gld consists of a core and extensions.

The core contains the load driver multi-threaded load engine, logic to coordinate multiple load driver instances and other logic required by the load driver. Al these are packaged as "gld-load-driver" The load driver runtime is not aware of any specific load content generator, it only interacts with a generic set of interfaces, packaged as "gld-api".

In order to develop a load content generator extension, appropriate for a specific use case, and with a specific set of concrete dependencies, the will only need to depend on gld-api.

Core Development

The core (including API and load-driver) is developed independently of extensions. Once a new core version has been released, the extensions that wish to use it should update their <gld.api.version>...</gld.api.version> in the topmost POM.

To get to the work area:

cdgldc

Extension Development

gld Extension Development

Building

TODO

Release Procedure

gld Runtime Release Procedure

TODO

Extension Release Procedure

TODO

Creating a new Extension

TODO

TODO

Temporarily, in

https://github.com/NovaOrdis/gld/blob/master/todo/Tactical%20GLD.docx

as Tactical GLD.docx.