Gld Development: Difference between revisions

From NovaOrdis Knowledge Base
Jump to navigation Jump to search
No edit summary
Line 30: Line 30:
:[[gld Extension Development]]
:[[gld Extension Development]]
</blockquote>
</blockquote>
=Building=
<font color=red>TODO</font>
=Release Procedure=
==gld Runtime Release Procedure==
<font color=red>TODO</font>
==Extension Release Procedure==
<font color=red>TODO</font>
=Creating a new Extension=
<font color=red>TODO</font>

Revision as of 22:56, 5 September 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. All these are packaged as gld-load-driver-*.jar. 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-*.jar. To develop a load content generator extension, appropriate for a specific use case, and with a specific set of concrete dependencies, the extension 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