Cloud Spanning

 Cloud spanning is a cloud delivery model in which

an application requiring a large pool of computing resources is deployed
over multiple cloud environments (private cloud, public cloud
and/or hybrid cloud).

 Unlike cloud bursting, in which an application runs in a private cloud or

data center and bursts into a public cloud when the demand for
computing capacity spikes, cloud spanning allows
application components to be continuously distributed across
multiple cloud computing environments.

 Cloud spanning is primarily implemented in an enterprise computing

environment in which an application requires a large pool of computing
resources.
 This pool can be the combination of internal, external or hybrid cloud
environments.
 For example, an organization might integrate internal private cloud
infrastructure with an external/public cloud storage provider to handle
the spikes in storage demand.
 Similarly, the additional storage capacity can also be sourced from an
enterprise-owned private cloud storage hosted at a different location.
  Although cloud spanning might increase management overhead, it
also reduces vendor lock-in by combining several cloud solutions to
form an enterprise cloud solution.
 Moreover, cloud spanning is an alternative to cloud burst, which seeks
to expand only to external cloud solutions to handle computation
overload.

Architecture Spanning represents the case where the business is expanding its IT
capacity with a cloud provider. This strategy may make sense for a variety of reasons that
include the necessity to burst to the cloud for additional resources or to co-locate data
where it is needed for performance or compliance factors. Note that with this form of
hybrid cloud, the applications may live on infrastructure hosted by a cloud service provider
and the data may reside within the company’s self-hosted data centers.

Need of Cloud Spanning

 Companies can run not only their new cloud-native applications but
also migrate many of their legacy workloads
 take advantage of cost savings and the agility that comes with cloud
computing
 Write Advantages of Hybrid Cloud
Distributed File System ( DFS)
 A distributed file system (DFS) is a file system with data stored on a
server.
 Works on client server architecture
 The data is accessed and processed as if it was stored on the
local client machine.
 The DFS makes it convenient to share
information and files among users on a
network in a controlled and authorized
way.
 The server allows the client users to share
files and store data just like they are
storing the information locally. However,
the servers have full control over the data and give access control to
the clients.
 multiple users share files and storage resources.
 The design and implementation of a distributed file system is more
complex than a conventional file system due to the fact that the users
and storage devices are physically dispersed.
Advantages
 In addition to the functions of the file system of a single-processor
system, the distributed file system supports the following:
1. Remote information sharing
Thus any node, irrespective of the physical location of the file, can access the
file.
efficient and well-managed data and storage sharing
2. User mobility
User should be permitted to work on different nodes.
3. Availability
For better fault-tolerance, files should be available for use even in the event of
temporary failure of one or more nodes of the system. Thus the system should
maintain multiple copies of the files, the existence of which should be
transparent to the user.
4. Diskless workstations
A distributed file system, with its transparent remote-file accessing capability,
allows the use of diskless workstations in a system.
5. Access Control
A DFS makes it possible to restrict access to the file system depending on
access lists
 Desirable features of a distributed file system:
1. Transparency
- Structure transparency
Clients should not know the number or locations of file servers and the
storage devices.
- Access transparency
Both local and remote files should be accessible in the same way.
- Naming transparency
The name of the file should give no hint as to the location of the file
- Replication transparency
If a file is replicated on multiple nodes, both the existence of multiple
copies and their locations should be hidden from the clients.
2. User mobility
Automatically bring the users environment (e.g. users home directory) to the
node where the user logs in.
3. Performance
Performance is measured as the average amount of time needed to satisfy client
requests.It is desirable that the performance of a distributed file system be
comparable to that of a centralized file system.
4 Simplicity and ease of use
User interface to the file system be simple and number of commands should be
as small as possible.
5. Scalability
Growth of nodes and users should not seriously disrupt service.
6. High availability
A distributed file system should continue to function in the face of partial failures
such as a link failure, a node failure, or a storage device crash.
A highly reliable and scalable distributed file system should have multiple and
independent file servers controlling multiple and independent storage devices.
7. High reliability
Probability of loss of stored data should be minimized. System should
automatically generate backup copies of critical files.
8. Data integrity
Concurrent access requests from multiple users who are competing to access the
file must be properly synchronized by the use of some form of concurrency control
mechanism. Atomic transactions can also be provided.
9. Security
Users should be confident of the privacy of their data.
10. Heterogeneity
There should be easy access to shared data on diverse platforms (e.g. Unix
workstation, Wintel platform etc).
Types of DFS