1
66%
master: 66%

Ran 28 Nov 2016 11:22PM UTC

Files 89

Run time 7s

Badge

Embed ▾

Committed 28 Nov 2016 11:16PM UTC coverage: 63.954% (-0.2%) from 64.114%

Job # COVERALLS_TOKEN=mwTn1pOFqEOUT13vylZNHq53NanoMznO7

Build Type

push

travis-ci

Committed by

tpepper

Commit Message

ciao-controller: add volumes to newInstance/newConfig

The controller's startWorkload creates an instance with a config,
where the config is articulated based on the struct payloads.Start,
which includes an array of payloads StorageResource type objects.
Each storage.BlockDevice in the array of instance volumes coming into
startWorkload() for instance creation needs mapped to a similar object in
the Start yaml for the instance config.  This is slightly complicated
by controller having a 3rd similar data types.StorageResources and
the need for controller to track existing volumes in the similar-ish
BlockData struct and volume-to-instance mappings with the similar-ish
StorageAttachments struct.

For the most part, existing code passes an empty volumes array into
newConfig.  From the compute API, a startWorkload() -> newInstance() ->
newConfig() should result in a set of StorageResources in the Start yaml
payload, with some variations including having the controller create the
volume.  Others will have ciao-launcher create a volume.  In either case,
ciao-launcher would take the appropriate steps to attach the volume to the
instance of the workload, whether VM, container or bare metal.

Signed-off-by: Tim Pepper <timothy.c.pepper@linux.intel.com>

Run Details

12033 of 18815 relevant lines covered (63.95%)

0.69 hits per line

01org / ciao / 394 / 1
66%
master: 66%

README BADGES
x

Markdown

Textile

RDoc

HTML

Rst

Source Files on job 394.1 (COVERALLS_TOKEN=mwTn1pOFqEOUT13vylZNHq53NanoMznO7)

01org / ciao / 394 / 1 66% master: 66%

README BADGES x

Markdown

Textile

RDoc

HTML

Rst

Source Files on job 394.1 (COVERALLS_TOKEN=mwTn1pOFqEOUT13vylZNHq53NanoMznO7)

01org / ciao / 394 / 1
66%
master: 66%

README BADGES
x