Hi APPC team,

As part of "K8S based Cloud region support",  new Multi-Cloud plugin is being 
added to talk to K8S based cloud regions to deploy VMs and containers.

Some workloads are immutable and hence Day0 configuration is good enough.
Some workloads can be configurable after they are brought up.

As we understand APPC (one of the roles) is meant for dynamic configuration of 
workloads that are brought up earlier on.
Trying to understand whether anything else to be taken care in K8S plugin in 
Multi-Cloud to enable the dynamic configuration.


1.      How does APPC know that new VNFs with various workloads are brought up? 
Note that a VNF can contain multiple workloads. For example, a security VNF may 
have FW and IPS workloads.  Is there any existing interface between SO and APPC 
to take care of these notifications?

2.      Is the expectation that any new instance of workload (either due to 
auto-restart and auto scale-out in the cloud region) be notified to APPC to 
start the configuration process.

3.      In regards to configuration: Does it support both PUSH (push 
configuration to workloads) and PULL modes(let workload pull the configuration)?

a.      In case of PUSH: How does APPC know the IP address of each workload 
instance to apply configuration to? Does it read IP address information from 
A&AI (vserver)?

4.      What NB API does it have to upload the configuration to APPC by user?

a.      Is the API granularity at the VNF or at the workload level?

b.      Does it support uploading incremental configuration? If so, how is it 
taken care (e2e view)?

5.      Lastly, is there any use case that use APPC for dynamic configuration?  
Some of the use cases I know have hardcoded configuration. Please point out any 
demo if available.


Appreciate any links/answers.

Thanks
Srini



-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.

View/Reply Online (#14026): https://lists.onap.org/g/onap-discuss/message/14026
Mute This Topic: https://lists.onap.org/mt/28302693/21656
Group Owner: [email protected]
Unsubscribe: https://lists.onap.org/g/onap-discuss/unsub  
[[email protected]]
-=-=-=-=-=-=-=-=-=-=-=-

Reply via email to