NFVO
NFVO copied to clipboard
[Suggestion] Move some parameters to VDU level
It would make much more sense if some parameters would be moved to VDU level.
For example, two VDUs in the same VNF may need to use different security groups, flavors, lifecycle events, etc ...
Here are some examples:
- securityGroups- currently part of VIM instance definition (!)
- deployment_flavour - currently part of VNF definition
- lifecycle_event - currenty part of VNF definition
- auto_scale_policy - not sure if this one should be moved
What do you think? There may be even more cases...
We are currently refactoring the VIM model. We agree that the security group should be moved to the VNFD/VDU level. Some other parameters are difficult to be moved during this release. We'll keep you updated.
Dear @gc4rella i would like to ask that this group_security parameter at VDU level has been implemented or still in the process????