http://finance.yahoo.com/news/F5-Integrates-with-VMware-bw-2764290025.html?x=0&.v=1
There were some unanswered questions in terms of # of tenants you can have behind F5 VE (as it supports only 4 interfaces -because the trunking won't work with vCloud Director at this point). Orchestration tool, SAN replication are also needed to be configured properly to make this solution to work. The isession is a cool feature though.
Monday, September 6, 2010
Tuesday, August 31, 2010
vCloud Director demo by GNAX and VMWorld2010
Exclusive vCloud Director demo by GNAX at vmworld2010
http://bit.ly/acyGKW
http://bit.ly/acyGKW
Tuesday, August 3, 2010
Why not Public Cloud yet?
Why not public cloud yet?
Standards and Interoperability:
•There are not standards or interoperability between different public clouds. The security around cloud computing and cloud storage is not matured yet and none of the cloud providers share their infrastructure information if any of your clients ask for due diligence information.
Cost on your existing infrastructure:
Public cloud may be a good option for Development and QA environments however, consider your existing investment on infrastructure as the current cost of running those physical servers may be cheaper than running them in cloud considering their setup costs, OS and application licensing fees. Eventually when you retire our servers, based on their role, you could move them to cloud.
Network Bandwidth:
Traditionally the network is designed to handle local traffic (20% internet; 80% intranet). Moving applications to cloud would change this to (80% internet, 20% intranet) which will result in higher bandwidth costs with your ISP
Contracts with existing Colo data centers:
If you have contracts with data centers that goes for many years you may want to stick to physical servers( and move to Private Clouds) as the cost of terminating existing contracts may overcome the benefits of moving to cloud.
Standards and Interoperability:
•There are not standards or interoperability between different public clouds. The security around cloud computing and cloud storage is not matured yet and none of the cloud providers share their infrastructure information if any of your clients ask for due diligence information.
Cost on your existing infrastructure:
Public cloud may be a good option for Development and QA environments however, consider your existing investment on infrastructure as the current cost of running those physical servers may be cheaper than running them in cloud considering their setup costs, OS and application licensing fees. Eventually when you retire our servers, based on their role, you could move them to cloud.
Network Bandwidth:
Traditionally the network is designed to handle local traffic (20% internet; 80% intranet). Moving applications to cloud would change this to (80% internet, 20% intranet) which will result in higher bandwidth costs with your ISP
Contracts with existing Colo data centers:
If you have contracts with data centers that goes for many years you may want to stick to physical servers( and move to Private Clouds) as the cost of terminating existing contracts may overcome the benefits of moving to cloud.
Monday, June 14, 2010
Cloud Computing - Simplified!
Cloud computing - Simplified – Part 1
The popularity of cloud computing let many vendors and cloud enthusiasts to come up with different definitions. Not to mention this created lot of confusion for the new readers of cloud computing.
In this post, let us look into other commonly used terms related to Cloud computing.
Cloud computing:
In general this can be defined as providing IT services and applications over the Internet with out the organization owning any related IT infrastructure and technology. The application or service is commonly made available through web browser. Organizations pay subscription fees based on the services they use.
Software as a Service (SaaS):
Pay per use delivery of applications over the cloud with out the hassle of capital costs, support and attached annual maintenance fees.
Example: Salesforce.com
Platform as a Service (PaaS):
Development platform on cloud that allows developers to develop, collaborate and release applications and manage them throughout the life cycle without purchasing and managing the development platforms.
Example: Microsoft Azure, Google App engine
Infrastructure as a Service (IaaS):
Infrastructure components such as servers, network and storage are offered as a service on the cloud. Organizations pay for their use of these components.
Example: Rackspace, Amazon EC2, S3
Multi-tenant architecture:
Ability of cloud service to manage multiple clients’ data and processing on one application instance with proper isolation in place. Even though this preferred method of cloud service for scalability , it has its own performance implications.
Multi-instance architecture:
Type of cloud service where one application instance is used for one client. It may not be desirable for scaling-out (horizontal scaling) but comes with improved performance compared to multi-tenant architecture.
In the next post, we will discuss about different cloud providers and how they stand and compete with others.
The popularity of cloud computing let many vendors and cloud enthusiasts to come up with different definitions. Not to mention this created lot of confusion for the new readers of cloud computing.
In this post, let us look into other commonly used terms related to Cloud computing.
Cloud computing:
In general this can be defined as providing IT services and applications over the Internet with out the organization owning any related IT infrastructure and technology. The application or service is commonly made available through web browser. Organizations pay subscription fees based on the services they use.
Software as a Service (SaaS):
Pay per use delivery of applications over the cloud with out the hassle of capital costs, support and attached annual maintenance fees.
Example: Salesforce.com
Platform as a Service (PaaS):
Development platform on cloud that allows developers to develop, collaborate and release applications and manage them throughout the life cycle without purchasing and managing the development platforms.
Example: Microsoft Azure, Google App engine
Infrastructure as a Service (IaaS):
Infrastructure components such as servers, network and storage are offered as a service on the cloud. Organizations pay for their use of these components.
Example: Rackspace, Amazon EC2, S3
Multi-tenant architecture:
Ability of cloud service to manage multiple clients’ data and processing on one application instance with proper isolation in place. Even though this preferred method of cloud service for scalability , it has its own performance implications.
Multi-instance architecture:
Type of cloud service where one application instance is used for one client. It may not be desirable for scaling-out (horizontal scaling) but comes with improved performance compared to multi-tenant architecture.
In the next post, we will discuss about different cloud providers and how they stand and compete with others.
Tuesday, March 2, 2010
Is Healthcare ready for Cloud?
Is Healthcare ready for the cloud?
The cost savings and the flexibility offered by the cloud is driving majority of the organizations in every industry to have a serious look at the cloud computing. Although lot of work is being done around the cloud arena, the highly compliance oriented industries such as health care and financial services are reluctant to migrate to cloud computing for the security and data availability reasons.
A recent study conducted by BridgeHead software shows that more than 80% of respondents are concerned about cloud security and availability. The article with the survey link (available till mid March 2010) is available here.
Even though with the growing concerns of the cloud among the healthcare industry, there are few factors that make business sense for the healthcare industry. Some of them are discussed in this article:
Moving non-critical applications to cloud:
Ever growing compliance requirements keeps the healthcare IT department busy at all the time. During these economic times with tighter budget and lesser resources, it makes sense to move some of the non-critical, non-compliance applications to the cloud. It gives more time to the IT staff to concentrate on the critical, compliance related applications which also provide competitive advantage against their competitors. The lesser Total Cost of Ownership (TCO) enjoyed by moving to cloud can be passed on to their customers by reducing their costs thus providing another competitive advantage.
Moving the risk outside the organization:
Efficient risk management in healthcare involves on-going in-house investment and resources. There are few cloud providers who are specialized and very efficient in handling risks in the industry. In those cases it makes sense to outsource them to the cloud providers to free up internal resources and save cost.
Either way, the key thing to remember in any industry is selection of cloud vendor. Do your research and understand your cloud providers’ SLA and their infrastructure.
There are interesting articles in this area and few of them are listed below:
http://newsblaze.com/story/2010030208042800001.we/topstory.html
http://healthcare.zdnet.com/?p=1025
The cost savings and the flexibility offered by the cloud is driving majority of the organizations in every industry to have a serious look at the cloud computing. Although lot of work is being done around the cloud arena, the highly compliance oriented industries such as health care and financial services are reluctant to migrate to cloud computing for the security and data availability reasons.
A recent study conducted by BridgeHead software shows that more than 80% of respondents are concerned about cloud security and availability. The article with the survey link (available till mid March 2010) is available here.
Even though with the growing concerns of the cloud among the healthcare industry, there are few factors that make business sense for the healthcare industry. Some of them are discussed in this article:
Moving non-critical applications to cloud:
Ever growing compliance requirements keeps the healthcare IT department busy at all the time. During these economic times with tighter budget and lesser resources, it makes sense to move some of the non-critical, non-compliance applications to the cloud. It gives more time to the IT staff to concentrate on the critical, compliance related applications which also provide competitive advantage against their competitors. The lesser Total Cost of Ownership (TCO) enjoyed by moving to cloud can be passed on to their customers by reducing their costs thus providing another competitive advantage.
Moving the risk outside the organization:
Efficient risk management in healthcare involves on-going in-house investment and resources. There are few cloud providers who are specialized and very efficient in handling risks in the industry. In those cases it makes sense to outsource them to the cloud providers to free up internal resources and save cost.
Either way, the key thing to remember in any industry is selection of cloud vendor. Do your research and understand your cloud providers’ SLA and their infrastructure.
There are interesting articles in this area and few of them are listed below:
http://newsblaze.com/story/2010030208042800001.we/topstory.html
http://healthcare.zdnet.com/?p=1025
Subscribe to:
Posts (Atom)
Posts
