Friday, June 15, 2012

Proposal Results


A team of experts was assembled to analyze the 9 proposals from 7 vendors. They were Alan McConnell from Grand Rapids, MI, John Hagan from Norfolk, VA and Emad Hammoud from Centreville, VA. We created a scoring grid in a spreadsheet and set about the task.

Preliminary Questions:  These points are general in nature, but reflect the attention paid by the responders,
  1. Did the proposals address the 4 questions asked in the RFQ? -- 3 did, 9 did not.
  2. Did we get Service Level Agreement information?  -- 9 did, 0 did not
Issues related to proposed solution. There are 3 ways that the vendors proposed to solve the problem.
  1. Provide empty virtual servers and all resources in a cloud shared environment. We could then install everything on them until we matched our current environment. This is cheap solution on the cloud side, but extremely expensive to re-create our current servers on new equipment. There is a great probability that we might not be successful.  -- 1 proposal offered this solution. 
  2. Provide physical hardware and a VMWare virtual environment dedicated to our needs. We could copy our existing virtual machines into our dedicated environment and expect them to work. There are some disadvantages. Our physical environment is subject to physical failures such as a disk. The down time could be an issue. Also we are expected to manage infrastructure issues like networking from their firewall in and backups. We also have to monitor the hardware environment. -- 4 proposals offered this type of solution.
  3. Provide a VMWare virtual environment on shared physical resources. Again we could copy our existing virtual machines into our dedicated environment and expect them to work. We wouldn't need to monitor or manage the infrastructure. We could add more resources without worrying about downtime. -- 5 proposals offered this type of solution.
The next step was to evaluate the 5 proposals that offered the true cloud characteristics. (http://en.wikipedia.org/wiki/Cloud_computing). Since all of the solutions were based on VMWare, we assumed that all would be equal. Also the quality and physical location of the data centers was assumed to be equal.  We placed a premium on the proposals that provided assistance to the customer in the following areas:
  1. Assistance with Cloud Migration. Do procedures, manuals, videos exist that provide guidance to the customer that enables the on-boarding process to be as smooth as possible? Our IT staff must agree to the strategy for moving. Operations need to continue with the least interruption possible. Orderly guidance here will reduce the effort and cost substantially. -- 2 proposals addressed this issue, 3 did not.
  2. Training for our IT staff in using the proposed environment. Do training materials, videos, manuals exist that will enable our IT staff to pick up their responsibilities in the new environment? Our operations must continue, applications need updating and generally we need to quickly understand how run things after migration.  -- 2 proposals addressed this issue, 3 did not.
At this point we selected two proposals that matched all requirements except price. For all 9 proposals the prices ranged from $87 to $422/VM/month. Some proposals had set up fees and other didn't. Our team chose not to base our selection on price, because of the different pricing schemes that were provided. In some cases you had a flat fee for stated CPU, RAM, storage and bandwidth. We could put up as many VMs as could use the environment. We would buy more resources as needed. Other pricing schemes talked about individual VMs. In summary, pricing was not a factor is our selection.

Our team has selected finalists as the proposals from VirtaCore and Vigilant Hosting. They are the most responsive to our RFQ. We are convinced that these vendors can take computers from any small to medium size organization and make them work on the cloud with all of the cloud advantages. Their assistance with migration and training will make the process smooth and painless. We will study these companies in more detail in the next post.

I would like to thanks my analysts and all of the vendors who participated in this RFQ project. The time and effort spent has been worthwhile.






Next Post: After A Break        





Monday, June 4, 2012

The RFQ Responses Are In

Review RFQ:  http://datacallsystems.com/rfq-2516-002a.asp

Of the 22 vendors contacted, 7 made proposals.

I would like to thank the following vendors for their proposals:

VirtaCore

Vigilant Hosting

Peer1

Go Grid

Bit Refinery

Connectria

SkyTap



The following were contact, but chose not to submit a proposal:

Amazon Elastic Web Services (EC2) - Rackspace Cloud  - Windows Azure

NJVC FedRamp government cloud - iWeb - SkyTap - VMRacks - GridSouth -  

Progent VMWare Services - Evozon - HMon - Lunahost -Bluelock -  

 - Virtual Machines - VMware Hosted - Greentree Hosting

 

Proposal Review


Some of my technical associates and I will be reviewing the proposals over the next two days. We will be communicating with the vendors for any clarifications that are needed.  The summary of our conculsions will be posted next.





Next Post: Proposal Results
 
Additional resources:

Proposal Support         



Wednesday, May 16, 2012

Getting Pricing Is Slow


I have determined that personally contacting each vendor is too slow. I have prepared an RFQ from my company at http://datacallsystems.com/rfq-2516-002a.asp . I will fill out a Contact Us form at each vendor's web site and wait and see what I get back.

I am adding some additional vendors:





Next Post: Waiting for Propsals
 
Additional resources:

Thinking Out Cloud          Cloud Storage - Pricing and Features          Cloud Pricing War Begins



Friday, April 27, 2012

Getting Some Prices


We have come a long way on our journey toward getting on the cloud. We have inventoried our existing computing power, anticipated our moving costs and analyzed whether we should even move to the cloud. Now it's time to compare costs and how we will manage our computing power on the cloud.

Remember what we know about our computing power. We need it when searching for prices.

           Disk:           RAM:                 CPU:

Server 1:  C: 20, D: 20 -- 2 GB (2.99 Ghz)   -- 5160 XEON - 3.00 GHz
Server 2:  C: 8         -- 2 GB (2.99 Ghz)   -- 5160 XEON - 3.00 GHz
Server 3:  C: 14        -- 1 GB (3.00 Ghz)   -- 5160 XEON - 3.00 GHz
Server 4:  C: 20, D: 30 -- 3.5 GB (3.00 Ghz) -- 5160 XEON - 3.00 GHz
Bandwidth: 5 minute peak  In: 0.9 MB   Out: 6.4 MB

All Windows Servers and we have licenses.

-- A small warning -- My analysis confirms that there are no simple ways to select the right cloud vendor. It is currently a daunting challenge, but it is worth the effort.

I have chosen to explore the following cloud vendors:
Each of these vendors seems to have at least a part of my solution.

I will explore my experience with each one in succeeding posts.




Next Post: Getting Pricing Is Slow
 
Additional resources:

Thinking Out Cloud          Cloud Storage - Pricing and Features          Cloud Pricing War Begins



Tuesday, April 10, 2012

Non Cost Considerations

We now have collected enough measurements about our existing environment to communicate intelligently with a cloud provider. Now its time to consider any other things that might indicate that we shouldn't move to the cloud. I'm going to throw out all that I can think of. I welcome your suggestions too.

We can't move to the cloud because
  • I need to see my computers everyday. This makes me feel safe.
  • We process very secure information for the government. I don't think the cloud is safe enough.
  • My brother in law is currently watching over my computers. He wouldn't have anything to do.
  • We use the heat from our computers to keep our baked goods warm.
Some of my favorites from 65 Reasons Not To Move To The Cloud:
  • Your career would be negatively impacted without a large IT budget and staff.
  • You would be bored – No more coordinating the configuration, test, development, and integration of hardware and software? What would you do all day?
  • You’re really fond of your consultants and systems integrators and would miss them terribly.
  • Your internal security is 100% guaranteed – much more secure than having your data in the Cloud. You’d bet your life on it.
  • Your internal infrastructure is much more reliable than that of the leading Cloud Service Providers.
David Linthicum has listed some good ones in To Move or Not to Move

Top 10 reasons ... to be careful about:

  1. Security is largely immature, and currently requires specialized expertise.
  2. Much of the technology is proprietary, and thus can cause lock-in.
  3. Your dependent on the cloud computing provider for your IT resources, thus you could be exposed around outages and other service interruptions.
  4. Using the Internet can cause network latency with some cloud applications.
  5. In some cases cloud providers are more expensive than on-premise systems.
  6. Not in control of costs if subscription prices go up in the future.
  7. Integration between on-premise and cloud-based systems can be problematic.
  8. Compliance issues could raise the risks of using cloud computing.
  9. Data privacy issues could arise, if your cloud provider seeks to monetize the data in their system.
  10. M&A activity around cloud providers, could mean constantly adjusting and readjusting your cloud computing solutions
If our benefits outweigh the riskd, then let's proceed to pricing our cloud needs.



Next Post: Getting Some Prices

 
Additional resources:

65 Reasons Not To Move           Myths about Cloud Computing          To Move or Not to Move

Monday, April 9, 2012

Other Cost Considerations


We now have a pretty good picture of our cloud needs. Before we start getting prices, lets consider some other issues:
  1. Besides cloud rental costs, what else should we consider?
          Do we have talent on staff to assist in the planning of the move to the cloud? In addition to the cloud resources we will need to make changes to our Internet protocol (IP) addresses and our Domain Name Server records. If we don't have the staff, we will need to hire consultants.

    2.  How do we move our existing computing power to the cloud?

         Related to staff for planning the move, do we have staff who can convert our existing computing power into a form that is transportable to the cloud. If not, consultants will be needed.

 


Next Post: Non Cost Considerations

Additional resources:

Cloud Switch Blog      Cloud Sigma     Double Take