Is it mean to add/delete more NFVI resources to already running VNF/VNFCs such as adding/deleting cores to running VMs/containers..?
I guess you are expecting that Multi-Cloud would provide API to do this. Don't you think it also requires changes in other components to take advantage of this capability?
The API to create / delete resource such as image, network, VM, etc.. already exist. In addition the Extension Management section expose specific capabilities via API which are available on one or more of the VIM/cloud but not in all. For example some of the VIMs do support dynamic resource addition / removal such as cores and networking interfaces which will be available through this extension section.
Thanks Gil. Good to know R1 Multi-VIM has this facility. I guess this is not being used by either VF-C, SO or APP-C in R1.
I am wondering whether this kind of feature being considered in NFV use cases. I thought scale-out (by bringing more VNFC instances to take up the increasing load) is popular mechanism being thought in NFV world. Is dynamic scale-up being considered in any NFV use case?
As mentioned above, both scaling are supported via the extension section in Multi-VIM/Cloud in R1, so if upper layer like VF-C, SO or APP-C want to sue it, there should not be any prevention from doing it. In the long run the Multi-VIM/Cloud team would look into how we bring this via a standardized way rather then cloud specific extension. Part of this will be the scope of R2, as R2 will focus on S3P (Stability, Security, Scalability and Performance). To what level its also dependent on the capacity that projects like SO, APP-C, and VF-C has to work on this from there side as they are the consumers of this capability.
5 Comments
Srinivasa Addepalli
Just to understand further:
I guess you are expecting that Multi-Cloud would provide API to do this. Don't you think it also requires changes in other components to take advantage of this capability?
Gil Hellmann
The link below is to the multi-VIM/Cloud age where you can find all the generic APIs implemented for R1:
The API to create / delete resource such as image, network, VM, etc.. already exist. In addition the Extension Management section expose specific capabilities via API which are available on one or more of the VIM/cloud but not in all. For example some of the VIMs do support dynamic resource addition / removal such as cores and networking interfaces which will be available through this extension section.
Srinivasa Addepalli
Thanks Gil. Good to know R1 Multi-VIM has this facility. I guess this is not being used by either VF-C, SO or APP-C in R1.
I am wondering whether this kind of feature being considered in NFV use cases. I thought scale-out (by bringing more VNFC instances to take up the increasing load) is popular mechanism being thought in NFV world. Is dynamic scale-up being considered in any NFV use case?
ramki krishnan
Hi Srini,
Aligning with cloud native thinking, scale-out will be a priority requirement. Scale-up is an optional requirement.
Thanks,
Ramki
Gil Hellmann
As mentioned above, both scaling are supported via the extension section in Multi-VIM/Cloud in R1, so if upper layer like VF-C, SO or APP-C want to sue it, there should not be any prevention from doing it. In the long run the Multi-VIM/Cloud team would look into how we bring this via a standardized way rather then cloud specific extension. Part of this will be the scope of R2, as R2 will focus on S3P (Stability, Security, Scalability and Performance). To what level its also dependent on the capacity that projects like SO, APP-C, and VF-C has to work on this from there side as they are the consumers of this capability.