Age | Commit message (Collapse) | Author | Files | Lines |
|
The vesagent has been moved to fcaps module
Change-Id: I938df03374ca887d4f455f206d398491010a9361
Issue-ID: MULTICLOUD-499
Signed-off-by: Xiaohua Zhang <xiaohua.zhang@windriver.com>
|
|
Fix errors in vesagent
Change-Id: I9cb0afda7a17a08246fcee8439e1ef2775609948
Issue-ID: MULTICLOUD-420
Signed-off-by: Xiaohua Zhang <xiaohua.zhang@windriver.com>
|
|
Change-Id: If1748109359b9180aac46e14d3e4261def171460
Issue-ID: Issue-ID: MULTICLOUD-232
Signed-off-by: Bin Yang <bin.yang@windriver.com>
|
|
Dispatch the specific backlog to corresponding handler
caching the runtime state into cache
Change-Id: I5edd682c8138532b496e281c5e3cf4274d3227c0
Issue-ID: MULTICLOUD-230
Signed-off-by: Bin Yang <bin.yang@windriver.com>
|
|
Change-Id: I5ea05e29290a23c290d3e1deb7ef637b06e7c6b7
Issue-ID: MULTICLOUD-230
Signed-off-by: Bin Yang <bin.yang@windriver.com>
|
|
The vesagent configurion logic will trigger the
vesagent worker scheduler via celery
Change-Id: I2504f2ef2672c25416062f63ffdfc5495b9200b4
Issue-ID: MULTICLOUD-230
Signed-off-by: Bin Yang <bin.yang@windriver.com>
|