diff options
author | Rob Daugherty <rd472p@att.com> | 2018-04-24 13:53:25 -0400 |
---|---|---|
committer | Rob Daugherty <rd472p@att.com> | 2018-04-24 14:26:12 -0400 |
commit | bb34137b85575dd36121d8cfc63b469e9a2ebf08 (patch) | |
tree | 33b7aba21b0db8bf9511488c10ffa0718c94d42a /bpmn/MSOInfrastructureBPMN/src/main/resources/process/UpdateVfModuleVolumeInfraV1.bpmn | |
parent | 4e40f1186d6dac2bf112ee21dccf5b6a463c00b8 (diff) |
Create VF Module Error
There are multiple issues here.
1) The LCM healthcheck and config-scale-out should be made
conditional upon the VNF orchestration status being Active
or Activated. I'm not going to do that with this commit,
since the logic will probably need to be moved to the
DoCreateVfModule flow. What I will do is bypass the LCM
operations to unblock testing. Another ticket will need
to address the real solution.
2) APP-C gave us an API where the controller type is configured
in their client object, which is NOT what we wanted. As a
result, we have to keep a client object for each controller
type. Our implementation did not do this.
3) Need to support the APP-C client configuration properties
for specifying the SDN-C topic names. I'm refactoring the
APP-C client urn mapping names to make it clear that they
are for configuring the APP-C *client* and not necessarily
for APP-C itself.
Change-Id: I588f3b98b4ee44ba53b4931f9f1a7938ee70bebf
Issue-ID: SO-577
Signed-off-by: Rob Daugherty <rd472p@att.com>
Diffstat (limited to 'bpmn/MSOInfrastructureBPMN/src/main/resources/process/UpdateVfModuleVolumeInfraV1.bpmn')
0 files changed, 0 insertions, 0 deletions