[{“cellsNumber”:2,”row”:”Acronym”,”lhsI”:”Virtual%20Packet%20Core%20Distribute%20Instance%20-%20based%20on%20the%20VMware”,”rhsI”:”Virtual%20Packet%20Core%20Distribute%20Instance%20-%20based%20on%20the%26nbsp%3BOpenstack%20%28%20Starting%20from%20Kilo%20Release%29″},{“cellsNumber”:2,”row”:”Definition”,”lhsI”:”The%20VPC-DI%20is%20the%20vendor%20specific%20terminology%20for%20Cisco%20Packet%20Core%20where%20VPC-DI%26nbsp%3Ballows%20multiple%20VMs%20%28%20Control%20and%20Session%20functions%20VMs%29%20to%20act%20as%20a%20single%20StarOS%20%28%20Operating%20System%20for%20Cisco%20packet%20Core%29%20instance%20with%20shared%20interfaces%2C%20shared%20service%20addresses%2C%20load%20balancing%2C%20redundancy%2C%20and%20a%20single%20point%20of%20management.%26nbsp%3B%3Cbr%20/%3EThe%20VPC-DI%20architecture%26nbsp%3Bis%20not%20depending%20on%20what%20kind%20of%20the%20Virtualization%20or%20VIM%20layer%20is%20used%2C%20where%20it%20can%20be%20deployed%20on%20VMware%20or%20Openstack.”,”rhsI”:”The%20VPC-DI%20is%20the%20vendor%20specific%20terminology%20for%20Cisco%20Packet%20Core%20where%20VPC-DI%20allows%20multiple%20VMs%20%28%20Control%20and%20Session%20functions%29%20to%20act%20as%20a%20single%20StarOS%20%28%20Operating%20System%20for%20Cisco%20packet%20Core%29%20instance%20with%20shared%20interfaces%2C%20shared%20service%20addresses%2C%20load%20balancing%2C%20redundancy%2C%20and%20a%20single%20point%20of%20management.%20%3Cbr%20/%3EThe%20VPC-DI%20architecture%20is%20not%20depending%20on%20what%20kind%20of%20the%20Virtualization%20or%20VIM%20layer%20is%20used%2C%20where%20it%20can%20be%20deployed%20on%20VMware%20or%20Openstack.”},{“cellsNumber”:2,”row”:”Scope”,”lhsI”:”The%20VPC-DI%20which%20based%20on%20the%20VMware%20is%20used%20when%20the%20operator%20looking%20to%20only%20virtualized%20their%26nbsp%3Bmobility%20application%20and%20as%20the%20first%20step%20towards%20the%20virtualization%20world%2C%20It%26nbsp%3Bdoesn%27t%26nbsp%3Bcare%26nbsp%3Babout%20the%20Life%20cycle%20management%20for%20the%20VNF%2C%20no%20additional%20HW%20will%20be%20required%20here.”,”rhsI”:”The%20VPC-DI%20which%20based%20on%20the%20Openstack%20is%20used%20when%20the%20operator%20looking%20to%20move%20their%20mobility%20application%20into%20Telco%20Cloud%20or%20fully%20virtualized%20and%20life%20cycle%20management%20is%20required%20%28%20Instantiate%2C%20scaling%20%2C%20monitor%2C%20auto%20healing%2C%20terminate%29%2C%20in%20this%20case%20the%20additional%20HW%20will%20be%20added%20in%20the%20solution%20for%20openstack%20layer%20%28%20Controller%20and%20Installer%29%2C%20however%20the%20VPC-DI%26nbsp%3Barchitecture%20will%20be%20the%20same%20as%20the%20VMware%20installation%26nbsp%3B”}]

Please login or Register to submit your answer