2 result(s) displayed for OpenStack (1 - 2 of 2):
By: Andreas Lemke, Alcatel-Lucent Sr. Marketing Manager – Cloud
“GM factories reduce production in aftermath of Japan earthquake 2011”, “Hard disk shortage due to Thailand flooding 2012“, “Drug shortages continue to vex doctors”, “China factory fire sends memory chip prices to three-year high (2013)”. Industrial supply chains are becoming increasingly tenuous as they are thinned out and stretched across the globe. Raw materials are available from fewer and fewer specialized suppliers and warehouses are eliminated for just-in-time production. Small, local incidents affect the supply of goods on a global scale.
In the IT industry we are seeing a similar trend. Enterprises are moving their applications and data to the cloud, but this cloud is often highly centralized and not as resilient, free flowing, or efficient as one might think. Amazon Web Services, the largest cloud provider in the world, is serving their global customers from no more than two handfuls of locations. Netflix and other companies have experienced major outages due to single failures in the cloud they used.
So what does this mean for NFV?
By: David Amzallag - Alcatel-Lucent Vice President, Virtual Telecommunications and CloudBand CTO
While network functions virtualization (NFV) introduces new challenges to security, it also presents unique opportunities for addressing security problems due to the unprecedented scale, flexibility, and central control it affords. Compute, storage, and network resources can be optimally allocated and stitched together as required by the security policy. Our approach to address NFV security is based on a recursive, divide-and-conquer methodology, which involves securing the Alcatel-Lucent CloudBand™ NFV Platform, cloud nodes, and the network that interconnects them. CloudBand uses policy-based placement capabilities enabled by the CloudBand Management System to install virtualized functions in their appropriate security zones, and re-uses the security services provided by NFV applications.
I thought it would be a good idea to describe the journey to this approach together with its "making of" episodes.