1. Optimal Design of Resilient Virtual Networks [Invited]
Abstract:
Due to the independent operation of cloud infrastructures and
communication networks, global cloud services face limitations in the end-
to-end quality of experience (QoE). Network virtualization enables end-to-
end QoE by combining the control of network and cloud resources. In a
network-virtualization architecture involving different business roles, there
are two important questions: how to design an end-to-end resilient virtual
network for cloud services given the service requests and the available
resources of the physical layer, and at which layer to provision resilience.
The existing literature on virtual network design usually lacks the
separation of the business roles and the corresponding layers, and hence,
cannot offer an answer to these questions. In this invited paper, we address
both questions by proposing novel resilient virtual network design models
for flexible and cost-efficient virtual networks having resilience either at
the virtual or the physical layer, or using a combination of both, and by
analyzing the performance of the proposed resilience alternatives both via
analysis and extensive simulations.
Existing System:
2. Therefore, cloud providers offer solutions to address these concerns.
However, such solutions are focused on performance and connectivity
within the cloud and only insufficiently address communication networks,
which can cause unacceptable latencies and service outages. Since
communication networks and cloud domains are typically operated by
different entities, it is difficult at the moment to offer end-to-end QoE
guarantees for cloud services. Furthermore, services are typically provided
by a single cloud provider. In the event of a complete datacenter (DC)
failure, the recovery of services may cause long outages depending on the
geographic diversity and availability of the cloud provider’s resources.
Proposed System:
A VNO receives the cloud service requests from the SPs and designs and
requests the establishment of a VNet to satisfy these requests using the
advertised virtual resources of the PIPs. It can operate one or several
VNets, which are mapped onto the physical infrastructure of one or more
PIPs. AVNet can consist of both network and cloud resources. The VNO
needs to pay a certain fee for the rent of the virtual resources and the setup
of the VNet. Interfaces, information sharing, and the pricing policy
between the VNO and the PIP depend on their business models and
contract.
The aim of a VNO in general is to design cost-efficient VNets, while a PIP’s
aim is to maximize profit from utilizing its resources serving multiple
VNOs. Note that, throughout this paper, the term virtual network cost
refers to the total price of renting the virtual resources and establishing a
virtual network, i.e., the fee a VNO needs to pay to the PIP(s) for renting
certain virtual resources and the setup of a virtual network using these
resources.
3. Hardware Requirements:
• System : Pentium IV 2.4 GHz.
• Hard Disk : 40 GB.
• Floppy Drive : 1.44 Mb.
• Monitor : 15 VGA Colour.
• Mouse : Logitech.
• RAM : 256 Mb.
Software Requirements:
• Operating system : - Windows XP.
• Front End : - JSP
• Back End : - SQL Server
Software Requirements:
• Operating system : - Windows XP.
• Front End : - .Net
• Back End : - SQL Server