Limitation of Public Cloud
• Service availability: Enterprises are very sensitive to whether cloud providers can guarantee adequate availability required by business (especially since enterprises will have little or no control over the physical cloud environment). Further, relying exclusively on a single cloud service provider can also be a single point of failure; most enterprises are reluctant to move to a cloud provider without some business continuity strategy in place. In order to guarantee high availability and avoid single source of failure, multiple cloud providers with independent software stacks could be used. This, however, increases implementation complexity significantly.
• Service lock-in (proprietary APIs à no interoperability): Cloud providers today lack interoperability standards; this ensures that a cloud user cannot easily move applications and data between cloud vendors leading to lock-in scenario. The lock-in is definitely advantageous to cloud providers but cloud users are vulnerable to price increases, reliability problems or, in the worst case, the said provider becoming defunct. Standardizations of APIs not only will mitigate lock-in but also enable same software infrastructure to be used in private and public cloud such that excess computation workload that cannot be handled in the private cloud could be off-loaded to the public cloud (“surge protection”).
• Data confidentiality and auditability: Security and auditability is a significant concern of most enterprises given the public nature of cloud offerings. There are regulatory requirements such as HIPPA or Sorbanes-Oxley that will necessitate auditability of corporate data in the cloud. In addition, some nation's law may mandate cloud providers to keep data within national boundaries or prevent a second country getting access to data via its court system. There is also a significant risk to privacy of personal information as well as information confidentiality of businesses or government organisations when data is located in the cloud.
• Data transfer bottleneck and cost (technology trends): Given the data-intensive nature of applications, data transfer into and out of cloud becomes a major issue with current rate of $100 to $150 per terabyte transferred. This cost can quickly become prohibitive thus making data transfer a major bottleneck to cloud adoption. This is a significant challenge, since over the past decade; the cost of wide area network bandwidth has reduced much more slowly than the cost of computation and storage capacity.
• Performance unpredictability: Multiple Virtual Machines (VMs) can share CPU and main memory quite well but I/O sharing often leads to interference and hence unpredictability in performance.
• Difficulty in debugging large-scale distributed systems: When an application is migrated to the cloud and executed in a large-scale distributed environment, there may be bugs that manifest which cannot be reproduced in small-scale configuration. Detecting and debugging faults in such large-scale distributed deployment is quite a challenge.
• Software licensing: The licensing model for commercial software is a mismatch for cloud computing. Current software licensing limits the computer on which it can be installed and users pay one time plus annual maintenance charges. Thus, many cloud providers have relied upon open source software but key challenge for commercial software vendors is to devise a better licensing model for the cloud.
Thursday, August 20, 2009
Layered apporach in cloud computing
Layer Approach
First Layer – Cloud Computing
The first layer is all the computing power and resources that enterprises need to deliver a service or application, including storage, processing, networks and servers. Some cloud services may use all of these components; others just one or two. This layer is the same as cloud computing
Cloud computing converts the traditional capital expenditure model (CapEx) common in data centers today to an operational expenditure (OpEx) model
Cloud computing is different. It is a specific type of utility computing. Cloud computing is the IT environment—encompassing all elements of the full “stack” of IT and network products (and supporting services)—that enables the development, delivery and consumption of cloud services. Properly defined,
Cloud computing has three key technical characteristics:
Scale: cloud computing systems incorporate tens of thousands of servers, offering processing power vastly greater than a traditional data center.
Flexibility: cloud computing can be used to handle very small or large processing tasks, and can be adjusted in real-time to match demand. If an organization needs 10 servers one day and 5,000 the next, the cloud can handle such a dynamically varying request.
Efficiency: unlike traditional data centers, clouds offer pooled computing power, performing like a single large machine. Sharing tasks across this pool reduces costs and massively improves processing speeds.
Second Layer – Cloud Platform
The middle layer is a platform that enables the enterprise to add specific services that rely on the cloud computing layer for their power. Example platforms include Google Application Engine or Microsoft’s Azure, which provide platforms that are available to developers running services that draw on generic and custom functions. Enterprises would possibly use different platforms for different situations— for example, a platform supplied by a company such as HP, IBM, Dell to manage access to all the technology services in the first layer of the cloud, and a subsequent layer from a company such as TCS to provide industry specific “services” for processes in the third and final layer
Third Layer – Cloud Services
This final layer comprises the cloud services themselves. Services may be internally or Externally facing, and may be developed by the enterprise itself or by a third party. Many services will combine elements of both approaches. For example, companies can use Yahoo!’s FireEagle location service and combine it with their own GPS tracking data to create a shipment tracking service. The resulting service could also be combined with an internal HR service to monitor working hours for drivers to create an entirely new service.
This third layer is important because this is where businesses can differentiate Themselves in a SOA and cloud environment—by buying services, adding value and Selling them, companies can create enormous flexibility and competitive advantage
Cloud services provide the automated processes that are delivered using cloud computing. Cloud services are a specific type of Software-as-a-Service (SaaS)
Cloud Services allows CIOs and CFOs to control costs through these hardware and software leasing environments.
Cloud services used internally through SOA, providing greater efficiency, flexibility and cost-effectiveness
Extensibility: Cloud services can be modified and customized using SOA techniques
Matching Expectations: Cloud services require clear SLAs; deploy these using SOA contract-management techniques
Hardware alone is insufficient to support mission critical or traditional IT data center use of these new operating models. Cloud Services provides the vital layer enabling organizations to leverage PaaS offerings in support of an evolutionary, low-risk transition to SaaS-based COBOL applications, providing the expected level of scalability, security and availability, and meeting service level agreements with the users of such core enterprise systems.
Using Cloud Services, these applications will then be based on the very same code as their other supported platforms, ensuring maximum reach with minimal impact on development.
Cloud Services provides the compatible environment in which to host mission critical business systems.
First Layer – Cloud Computing
The first layer is all the computing power and resources that enterprises need to deliver a service or application, including storage, processing, networks and servers. Some cloud services may use all of these components; others just one or two. This layer is the same as cloud computing
Cloud computing converts the traditional capital expenditure model (CapEx) common in data centers today to an operational expenditure (OpEx) model
Cloud computing is different. It is a specific type of utility computing. Cloud computing is the IT environment—encompassing all elements of the full “stack” of IT and network products (and supporting services)—that enables the development, delivery and consumption of cloud services. Properly defined,
Cloud computing has three key technical characteristics:
Scale: cloud computing systems incorporate tens of thousands of servers, offering processing power vastly greater than a traditional data center.
Flexibility: cloud computing can be used to handle very small or large processing tasks, and can be adjusted in real-time to match demand. If an organization needs 10 servers one day and 5,000 the next, the cloud can handle such a dynamically varying request.
Efficiency: unlike traditional data centers, clouds offer pooled computing power, performing like a single large machine. Sharing tasks across this pool reduces costs and massively improves processing speeds.
Second Layer – Cloud Platform
The middle layer is a platform that enables the enterprise to add specific services that rely on the cloud computing layer for their power. Example platforms include Google Application Engine or Microsoft’s Azure, which provide platforms that are available to developers running services that draw on generic and custom functions. Enterprises would possibly use different platforms for different situations— for example, a platform supplied by a company such as HP, IBM, Dell to manage access to all the technology services in the first layer of the cloud, and a subsequent layer from a company such as TCS to provide industry specific “services” for processes in the third and final layer
Third Layer – Cloud Services
This final layer comprises the cloud services themselves. Services may be internally or Externally facing, and may be developed by the enterprise itself or by a third party. Many services will combine elements of both approaches. For example, companies can use Yahoo!’s FireEagle location service and combine it with their own GPS tracking data to create a shipment tracking service. The resulting service could also be combined with an internal HR service to monitor working hours for drivers to create an entirely new service.
This third layer is important because this is where businesses can differentiate Themselves in a SOA and cloud environment—by buying services, adding value and Selling them, companies can create enormous flexibility and competitive advantage
Cloud services provide the automated processes that are delivered using cloud computing. Cloud services are a specific type of Software-as-a-Service (SaaS)
Cloud Services allows CIOs and CFOs to control costs through these hardware and software leasing environments.
Cloud services used internally through SOA, providing greater efficiency, flexibility and cost-effectiveness
Extensibility: Cloud services can be modified and customized using SOA techniques
Matching Expectations: Cloud services require clear SLAs; deploy these using SOA contract-management techniques
Hardware alone is insufficient to support mission critical or traditional IT data center use of these new operating models. Cloud Services provides the vital layer enabling organizations to leverage PaaS offerings in support of an evolutionary, low-risk transition to SaaS-based COBOL applications, providing the expected level of scalability, security and availability, and meeting service level agreements with the users of such core enterprise systems.
Using Cloud Services, these applications will then be based on the very same code as their other supported platforms, ensuring maximum reach with minimal impact on development.
Cloud Services provides the compatible environment in which to host mission critical business systems.
Difference between Private Cloud and public cloud
The only difference between public and private clouds seems to be ownership. Is there any other distinction that is relevant and important for users to understand?
Answer
Public Cloud
A public cloud is offered as a service, usually over an internet connection.
Public clouds typically charge a monthly usage fee per GB, combined with bandwidth transfer charges.
Users can scale the storage on demand and do not need to purchase storage
hardware.
Service providers manage the infrastructure and pool resources into capacity that customers can claim.
Private Cloud
Private clouds are deployed inside a firewall and managed by the user organization.
Private clouds are built from software running on customer supplied commodity hardware.
The data is typically not shared outside the enterprise and full control is retained by the organization.
Factor to Consider to differentiate private and public cloud
Initial investment
Private Cloud
There is often an assumption that private clouds require a million dollar capital outlay and an investment in volumes of equipment.
The reality is that private clouds can be built for under $5,000 and deployments are simple. Users can download software and have a cloud running in under an hour.
Public Cloud
Public clouds can start as low as $1000
For example, a public cloud makes it easy to backup a single laptop or deploy an application starting at a few GBs. As a company grows, it can lease more
capacity and the cost scales linearly.
Longevity of data
Public cloud
As data ages within the public cloud, the cost continues to rise.
If you are publishing frequently changing or short lived content such as movie trailers or daily newscasts, the flexibility of a public cloud is a good solution.
Private Cloud
Private clouds are licensed like enterprise software
Longevity of data does not increase the cost of the solution which bodes well for archive or content repository applications.
Required performance
Public cloud
Public clouds are accessed over the internet and face the limits of both your and the provider’s bandwidth connection.
This is usually capped around 10MB/s
To scale performance you can initiate additional 10MB/s connections, but doing so increases the bandwidth charges.
Private Cloud
Private clouds are deployed inside the firewall and accessed over the Ethernet LAN at wire speed
It is not uncommon to have read access in the 100 MB/s range per node. Adding nodes
provides additional performance to the cloud.
Files can be replicated to many nodes, each of which can serve requests independently.
Access patterns and locations
Public Cloud
Public cloud offerings typically include replication of data to multiple geographically dispersed locations, sometimes for an extra fee
If your users are global and can benefit from locality of data, a public cloud can sometimes substitute for a content distribution network
Private Cloud
Private clouds are typically deployed in a single location for LAN based access.
Remote users will need to connect over the WAN and work with internet type latencies.
Larger private cloud deployments can include multiple locations and start to approach the public cloud distribution, albeit at a higher initial investment.
Security and data isolation
Public Clouds :
There are many published opinions and dedicated websites that cover security of public cloud offerings. The bottom line is it comes down to control of your data. Public clouds are just that–public.
Isolation of data is only as strong as the virtualization technologies used to build the
cloud and the provider’s firewall.
If you are at all concerned about the data being outside of your company it should not be in a public cloud.
Private Clouds
Private clouds are owned, deployed and managed by internal employees.
Data is isolated based on your requirements and security is based on internal processes
Confidentiality and destruction of data
Public Clouds
Similar to security, confidentiality of data is a factor to consider when choosing a cloud storage solution.
The law is defined based on control of the data.
If the service provider is subpoenaed for your data based on their control of the data, they must comply regardless of your knowledge or objections.
Private Clouds
With private clouds you maintain control and have input, or at least knowledge of legal activities.
When it comes time to destroy or delete the data, it is in your power and can be confirmed by your own team.
Service level agreements
Public Clouds
Public cloud SLAs are published by the provider and are their responsibility.
Remediation is typically a cash payment, and while they will do their best to recover data, there is no guarantee of data availability.
SLAs can also be impacted by internet connectivity. For example, if your link
goes down, you cannot access your data and there is no remediation (unless your
network provider has guaranteed uptime).
Private Clouds
Private clouds have different mechanisms for data availability and service of access.
Most leverage multiple copies of files on multiple nodes and treat each node as a failure domain.
Individual server failures do not bring down the cloud or create data loss, so most SLA
agreements are satisfied.
It is important to have a complete understanding of the architecture and its capabilities when selecting and deploying a private cloud.
Answer
Public Cloud
A public cloud is offered as a service, usually over an internet connection.
Public clouds typically charge a monthly usage fee per GB, combined with bandwidth transfer charges.
Users can scale the storage on demand and do not need to purchase storage
hardware.
Service providers manage the infrastructure and pool resources into capacity that customers can claim.
Private Cloud
Private clouds are deployed inside a firewall and managed by the user organization.
Private clouds are built from software running on customer supplied commodity hardware.
The data is typically not shared outside the enterprise and full control is retained by the organization.
Factor to Consider to differentiate private and public cloud
Initial investment
Private Cloud
There is often an assumption that private clouds require a million dollar capital outlay and an investment in volumes of equipment.
The reality is that private clouds can be built for under $5,000 and deployments are simple. Users can download software and have a cloud running in under an hour.
Public Cloud
Public clouds can start as low as $1000
For example, a public cloud makes it easy to backup a single laptop or deploy an application starting at a few GBs. As a company grows, it can lease more
capacity and the cost scales linearly.
Longevity of data
Public cloud
As data ages within the public cloud, the cost continues to rise.
If you are publishing frequently changing or short lived content such as movie trailers or daily newscasts, the flexibility of a public cloud is a good solution.
Private Cloud
Private clouds are licensed like enterprise software
Longevity of data does not increase the cost of the solution which bodes well for archive or content repository applications.
Required performance
Public cloud
Public clouds are accessed over the internet and face the limits of both your and the provider’s bandwidth connection.
This is usually capped around 10MB/s
To scale performance you can initiate additional 10MB/s connections, but doing so increases the bandwidth charges.
Private Cloud
Private clouds are deployed inside the firewall and accessed over the Ethernet LAN at wire speed
It is not uncommon to have read access in the 100 MB/s range per node. Adding nodes
provides additional performance to the cloud.
Files can be replicated to many nodes, each of which can serve requests independently.
Access patterns and locations
Public Cloud
Public cloud offerings typically include replication of data to multiple geographically dispersed locations, sometimes for an extra fee
If your users are global and can benefit from locality of data, a public cloud can sometimes substitute for a content distribution network
Private Cloud
Private clouds are typically deployed in a single location for LAN based access.
Remote users will need to connect over the WAN and work with internet type latencies.
Larger private cloud deployments can include multiple locations and start to approach the public cloud distribution, albeit at a higher initial investment.
Security and data isolation
Public Clouds :
There are many published opinions and dedicated websites that cover security of public cloud offerings. The bottom line is it comes down to control of your data. Public clouds are just that–public.
Isolation of data is only as strong as the virtualization technologies used to build the
cloud and the provider’s firewall.
If you are at all concerned about the data being outside of your company it should not be in a public cloud.
Private Clouds
Private clouds are owned, deployed and managed by internal employees.
Data is isolated based on your requirements and security is based on internal processes
Confidentiality and destruction of data
Public Clouds
Similar to security, confidentiality of data is a factor to consider when choosing a cloud storage solution.
The law is defined based on control of the data.
If the service provider is subpoenaed for your data based on their control of the data, they must comply regardless of your knowledge or objections.
Private Clouds
With private clouds you maintain control and have input, or at least knowledge of legal activities.
When it comes time to destroy or delete the data, it is in your power and can be confirmed by your own team.
Service level agreements
Public Clouds
Public cloud SLAs are published by the provider and are their responsibility.
Remediation is typically a cash payment, and while they will do their best to recover data, there is no guarantee of data availability.
SLAs can also be impacted by internet connectivity. For example, if your link
goes down, you cannot access your data and there is no remediation (unless your
network provider has guaranteed uptime).
Private Clouds
Private clouds have different mechanisms for data availability and service of access.
Most leverage multiple copies of files on multiple nodes and treat each node as a failure domain.
Individual server failures do not bring down the cloud or create data loss, so most SLA
agreements are satisfied.
It is important to have a complete understanding of the architecture and its capabilities when selecting and deploying a private cloud.
Difference between Private Cloud and public cloud
The only difference between public and private clouds seems to be ownership. Is there any other distinction that is relevant and important for users to understand?
Answer
Public Cloud
A public cloud is offered as a service, usually over an internet connection.
Public clouds typically charge a monthly usage fee per GB, combined with bandwidth transfer charges.
Users can scale the storage on demand and do not need to purchase storage
hardware.
Service providers manage the infrastructure and pool resources into capacity that customers can claim.
Private Cloud
Private clouds are deployed inside a firewall and managed by the user organization.
Private clouds are built from software running on customer supplied commodity hardware.
The data is typically not shared outside the enterprise and full control is retained by the organization.
Factor to Consider to differentiate private and public cloud
Initial investment
Private Cloud
There is often an assumption that private clouds require a million dollar capital outlay and an investment in volumes of equipment.
The reality is that private clouds can be built for under $5,000 and deployments are simple. Users can download software and have a cloud running in under an hour.
Public Cloud
Public clouds can start as low as $1000
For example, a public cloud makes it easy to backup a single laptop or deploy an application starting at a few GBs. As a company grows, it can lease more
capacity and the cost scales linearly.
Longevity of data
Public cloud
As data ages within the public cloud, the cost continues to rise.
If you are publishing frequently changing or short lived content such as movie trailers or daily newscasts, the flexibility of a public cloud is a good solution.
Private Cloud
Private clouds are licensed like enterprise software
Longevity of data does not increase the cost of the solution which bodes well for archive or content repository applications.
Required performance
Public cloud
Public clouds are accessed over the internet and face the limits of both your and the provider’s bandwidth connection.
This is usually capped around 10MB/s
To scale performance you can initiate additional 10MB/s connections, but doing so increases the bandwidth charges.
Private Cloud
Private clouds are deployed inside the firewall and accessed over the Ethernet LAN at wire speed
It is not uncommon to have read access in the 100 MB/s range per node. Adding nodes
provides additional performance to the cloud.
Files can be replicated to many nodes, each of which can serve requests independently.
Access patterns and locations
Public Cloud
Public cloud offerings typically include replication of data to multiple geographically dispersed locations, sometimes for an extra fee
If your users are global and can benefit from locality of data, a public cloud can sometimes substitute for a content distribution network
Private Cloud
Private clouds are typically deployed in a single location for LAN based access.
Remote users will need to connect over the WAN and work with internet type latencies.
Larger private cloud deployments can include multiple locations and start to approach the public cloud distribution, albeit at a higher initial investment.
Security and data isolation
Public Clouds :
There are many published opinions and dedicated websites that cover security of public cloud offerings. The bottom line is it comes down to control of your data. Public clouds are just that–public.
Isolation of data is only as strong as the virtualization technologies used to build the
cloud and the provider’s firewall.
If you are at all concerned about the data being outside of your company it should not be in a public cloud.
Private Clouds
Private clouds are owned, deployed and managed by internal employees.
Data is isolated based on your requirements and security is based on internal processes
Confidentiality and destruction of data
Public Clouds
Similar to security, confidentiality of data is a factor to consider when choosing a cloud storage solution.
The law is defined based on control of the data.
If the service provider is subpoenaed for your data based on their control of the data, they must comply regardless of your knowledge or objections.
Private Clouds
With private clouds you maintain control and have input, or at least knowledge of legal activities.
When it comes time to destroy or delete the data, it is in your power and can be confirmed by your own team.
Service level agreements
Public Clouds
Public cloud SLAs are published by the provider and are their responsibility.
Remediation is typically a cash payment, and while they will do their best to recover data, there is no guarantee of data availability.
SLAs can also be impacted by internet connectivity. For example, if your link
goes down, you cannot access your data and there is no remediation (unless your
network provider has guaranteed uptime).
Private Clouds
Private clouds have different mechanisms for data availability and service of access.
Most leverage multiple copies of files on multiple nodes and treat each node as a failure domain.
Individual server failures do not bring down the cloud or create data loss, so most SLA
agreements are satisfied.
It is important to have a complete understanding of the architecture and its capabilities when selecting and deploying a private cloud.
Answer
Public Cloud
A public cloud is offered as a service, usually over an internet connection.
Public clouds typically charge a monthly usage fee per GB, combined with bandwidth transfer charges.
Users can scale the storage on demand and do not need to purchase storage
hardware.
Service providers manage the infrastructure and pool resources into capacity that customers can claim.
Private Cloud
Private clouds are deployed inside a firewall and managed by the user organization.
Private clouds are built from software running on customer supplied commodity hardware.
The data is typically not shared outside the enterprise and full control is retained by the organization.
Factor to Consider to differentiate private and public cloud
Initial investment
Private Cloud
There is often an assumption that private clouds require a million dollar capital outlay and an investment in volumes of equipment.
The reality is that private clouds can be built for under $5,000 and deployments are simple. Users can download software and have a cloud running in under an hour.
Public Cloud
Public clouds can start as low as $1000
For example, a public cloud makes it easy to backup a single laptop or deploy an application starting at a few GBs. As a company grows, it can lease more
capacity and the cost scales linearly.
Longevity of data
Public cloud
As data ages within the public cloud, the cost continues to rise.
If you are publishing frequently changing or short lived content such as movie trailers or daily newscasts, the flexibility of a public cloud is a good solution.
Private Cloud
Private clouds are licensed like enterprise software
Longevity of data does not increase the cost of the solution which bodes well for archive or content repository applications.
Required performance
Public cloud
Public clouds are accessed over the internet and face the limits of both your and the provider’s bandwidth connection.
This is usually capped around 10MB/s
To scale performance you can initiate additional 10MB/s connections, but doing so increases the bandwidth charges.
Private Cloud
Private clouds are deployed inside the firewall and accessed over the Ethernet LAN at wire speed
It is not uncommon to have read access in the 100 MB/s range per node. Adding nodes
provides additional performance to the cloud.
Files can be replicated to many nodes, each of which can serve requests independently.
Access patterns and locations
Public Cloud
Public cloud offerings typically include replication of data to multiple geographically dispersed locations, sometimes for an extra fee
If your users are global and can benefit from locality of data, a public cloud can sometimes substitute for a content distribution network
Private Cloud
Private clouds are typically deployed in a single location for LAN based access.
Remote users will need to connect over the WAN and work with internet type latencies.
Larger private cloud deployments can include multiple locations and start to approach the public cloud distribution, albeit at a higher initial investment.
Security and data isolation
Public Clouds :
There are many published opinions and dedicated websites that cover security of public cloud offerings. The bottom line is it comes down to control of your data. Public clouds are just that–public.
Isolation of data is only as strong as the virtualization technologies used to build the
cloud and the provider’s firewall.
If you are at all concerned about the data being outside of your company it should not be in a public cloud.
Private Clouds
Private clouds are owned, deployed and managed by internal employees.
Data is isolated based on your requirements and security is based on internal processes
Confidentiality and destruction of data
Public Clouds
Similar to security, confidentiality of data is a factor to consider when choosing a cloud storage solution.
The law is defined based on control of the data.
If the service provider is subpoenaed for your data based on their control of the data, they must comply regardless of your knowledge or objections.
Private Clouds
With private clouds you maintain control and have input, or at least knowledge of legal activities.
When it comes time to destroy or delete the data, it is in your power and can be confirmed by your own team.
Service level agreements
Public Clouds
Public cloud SLAs are published by the provider and are their responsibility.
Remediation is typically a cash payment, and while they will do their best to recover data, there is no guarantee of data availability.
SLAs can also be impacted by internet connectivity. For example, if your link
goes down, you cannot access your data and there is no remediation (unless your
network provider has guaranteed uptime).
Private Clouds
Private clouds have different mechanisms for data availability and service of access.
Most leverage multiple copies of files on multiple nodes and treat each node as a failure domain.
Individual server failures do not bring down the cloud or create data loss, so most SLA
agreements are satisfied.
It is important to have a complete understanding of the architecture and its capabilities when selecting and deploying a private cloud.
Sunday, December 2, 2007
Tuesday, October 23, 2007
Xen and opensolaris
on 24/10/2007, we are trying to create opensolaris b57 as domU on xen-fedora7 dom0
Installation steps-
Issues-
Installation steps-
Issues-
Subscribe to:
Posts (Atom)