Collaboration Framework For Multicloud System

Collaboration in Multicloud Computing
Environments Framework and
Security Issues
ABSTRACT
A proposed proxy-based multicloud computing framework allows dynamic, on
the fly collaborations and resource sharing among cloud-based services,
addressing trust, policy, and privacy issues without preestablished collaboration
agreements or standardized interfaces. The recent surge in cloud computing
arises from its ability to provide software, infrastructure, and platform services
without requiring large investments or expenses to manage and operate them.
Clouds typically involve service providers, infrastructure/resource providers,
and service users (or clients). They include applications delivered as services, as
well as the hardware and software systems providing these services. Cloud
computing characteristics include a ubiquitous (network-based) access channel;
resource pooling; multitenancy; automatic and elastic provisioning and release of
computing capabilities; and metering of resource usage (typically on a pay-peruse basis). Virtualization of resources such as processors, network, memory, and
storage ensures scalability and high availability of computing capabilities.
Clouds can dynamically provision these virtual resources to hosted applications
or to clients that use them to develop their own applications or to store data.
Rapid provisioning and dynamic reconfiguration of resources help cope with
variable demand and ensure optimum resource utilization.
EXISTING SYSTEM:
Many existing cloud data services provide similar access control models, in
which individual and organizational privacy, a key requirement for digital
identity management, is unprotected. Also, with cloud computing initiatives, the
scope of insider threats, a major source of data theft and privacy breaches, is no
longer limited to the organizational perimeter. Multicloud environments
exacerbate these issues because proxies can access data (which the environment
might dynamically move or partition across different clouds) on behalf of clients.
Revealing sensitive information in identity attributes to proxies that grant them
authorization to access the data on behalf of clients is not an attractive solution.
Thus, assuring the private and consistent management of information relevant to
ABAC becomes more complex in multicloud systems.
PROPOSED SYSTEM:
Our proposed framework for generic cloud collaboration allows clients and
cloud applications to simultaneously use services from and route data among
multiple clouds. This framework supports universal and dynamic collaboration
in a multicloud system. It lets clients simultaneously use services from multiple
clouds without prior business agreements among cloud providers, and without
adopting common standards and specifications. As more organizations adopt
cloud computing, cloud service providers (CSPs) are developing new
technologies to enhance the cloud’s capabilities. Cloud mashups are a recent
trend; mashups combine services from multiple clouds into a single service or
application, possibly with on-premises (client-side) data and services. This
service composition lets CSPs offer new functionalities to clients at lower
development costs.
MODULE DESCRIPTION:
Number of Modules
After careful analysis the system has been identified to have the following modules:
1. Collaboration Framework For Multicloud System Module.
2. Client/Users Module.
3. Cloud Service Provider Module.
4. Proxy Service Provider Module.
1. Collaboration Framework For Multicloud System Module:
Cloud collaboration allows clients and cloud applications to simultaneously use
services from and route data among multiple clouds. This framework supports
universal and dynamic collaboration in a multicloud system. It lets clients
simultaneously use services from multiple clouds without prior business
agreements among cloud providers, and without adopting common standards
and specifications.
2. Client/Users Module:
Client sends a request to cloud C1, which dynamically discovers the need to use
services from clouds C2 and C3. C1 employs proxies to manage these
interactions. A client that wishes to simultaneously use services from multiple
clouds must individually interact with each cloud service, gather intermediate
results, process the collective data, and generate final results. Proxies can
facilitate collaboration without requiring prior agreements between the cloud
service providers. First, the requesting entity chooses proxies to act on its behalf
and to interact with cloud applications. A client or a CSP might employ multiple
proxies to interact with multiple CSPs. It can select proxies based on, for
example, latencies between proxies and clouds or workload conditions at various
proxies.
3.Cloud Service Provider Module:
Cloud service providers (CSPs) deploy proxies as an autonomous cloud system
and offer it as a service to clients. A client employs two proxies to interact with
CSPs C1 and C2. Alternatively, a client initiates a service request with C1, which
then discovers the need for a service from C2. PSP: proxy service provider.
Clients deploy proxies within the infrastructure of their organization. A client
employs two proxies to interact with CSPs C1 and C2. A client initiates a service
request with C1, which then discovers the need for a service from C2.
4. Proxy Service Provider Module:
It involves deploying proxies as an autonomous cloud that offers collaborative
services to clients and CSPs. A group of CSPs that are willing to collaborate can
manage this proxy-as-a-service cloud, or a third-party entity, a proxy service
provider (PSP), can provide management. Clients directly subscribe to the proxy
cloud service and employ them for intercloud collaboration. To protect data at rest
and data in transit, proxies must provide a trusted computing platform that prevents
malicious software from taking control and compromising sensitive client and cloud
application data.
SOFTWARE REQUIREMENTS:
Operating System
: Windows
Technology
: Java and J2EE
Web Technologies
: Html, JavaScript, CSS
IDE
: My Eclipse
Web Server
: Tomcat
Tool kit
: Android Phone
Database
: My SQL
Java Version
: J2SDK1.5
HARDWARE REQUIREMENTS:
Hardware
:
Pentium
Speed
:
1.1 GHz
RAM
:
1GB
Hard Disk
:
20 GB
Floppy Drive
:
1.44 MB
Key Board
:
Standard Windows Keyboard
Mouse
:
Two or Three Button Mouse
Monitor
:
SVGA
Flow Diagram: