Much has been made of how businesses can enhance their IT performance by migrating to a private cloud. But more and more enterprise level organizations are realizing that the promise of the cloud isnât always realized after implementation. This is partly because much of the marketing around the private cloud talks about potential savings and increases in performance that are based on best case scenarios.Â The actual âon-the-groundâ numbers vary quite a bit.Â The good news is that there are a number of steps most organizations can take optimize the performance of the private cloud itself. Here are a few to get you started:
- Negotiate your SLAs with care
- Smart cloud users always monitor performance
- Time to upgrade your WAN?
- Take advantage of automation
By: Jason Tee
Software licensing under virtualisation remains a grey area and many organisations are likely to have a significant shortfall in their software licensing compliance making them particularly vulnerable in a software audit, warned a licensing management service provider, License Dashboard.
A study it conducted among UK organisations in December 2012 revealed that nearly all respondents (97%) had virtualised their servers and more than half (58%) said they used dynamic provisioning â a flexible approach where virtual machinesÂ (VMs) are deployed from a centralised administrative console by any central IT administrator.
Using dynamic provisioning (such as VMwareâs Distributed Resources Scheduler – DRS) has the potential to increase an organisationâs server licensing requirements by up to 500% at the click of a button, warned License Dashboard.
I recently caught an episode of a documentary series my kids were watching on MTV, called âCatfish.â In the show, people who were in online-only relationships tried to find out if the person theyâd been chatting with was actually who she/he claimed to be. It wonât come as a surprise to anyone that they usually werenât. Think the Manti Teâo hoax.
As someone in the IT world, I began to think about other ways in which the virtual and physical IT worlds donât always line up. As we turn to virtualization and the Cloud, we often struggle to integrate physical devices to support virtual systems. And just like in âCatfish,â the reality is often not what weâd hoped.
This is particularly true for SANs. Weâre going from a one server, one application world to one in which many systems all access the same storage. The performance of traditional SANs has often been inadequate, and the difference between locally attached and virtually provisioned storage can be very noticeable.
Why is that? What aspects of traditional SANs are in conflict with virtual infrastructures? The fundamental problem is a lack of what I call âVM awareness.â
- Physical vs. Virtual System Performance (â¦ Real People vs. Facebook Profiles)
- Bridging the Physical and Virtual (â¦ Know Who Youâre Talking To)
- Merging the Physical and Virtual (â¦ Reality Check)
- First, your SAN needs to be able to handle a large number of IOPS.
- Second, your storage needs to be able to prioritize data
- Third, the system needs to deduplicate data blocks.
- Lastly, storage management needs to integrate with VM management.
By: Zenith Infotech
For many enterprises, the safest on-ramp to cloud computing is to build a private cloud. Private clouds don’t have as many security, compliance and data-ownership challenges as public ones, but they are not risk free.
Legacy environments, cost overruns and application performance can all undermine your private cloud initiatives. That doesnât mean you should rethink the decision to build a private cloud, but it does mean you need to carefully think through the challengesâand be realistic about potential benefits.
If you understand the challenges you’ll face and plan ahead to overcome them, building a private cloud will put you on the road to a streamlined, efficient and flexible IT infrastructure.
To help you succeed when it comes time to build your own private cloud, here are five tips from private cloud experts:
- Avoid Forklift Upgrades.
- Determine How You Will Measure Success.
- Plan for the Future Growth and Changing Makeup of Your Organization.
- Strive to MeetâOr Beatâthe Performance of Your Previous Architecture.
- Figure Out Who Will Pay for What.
By: Jeff Vance
Whenever discussing cloud computing systems, ÑÎ¿Ï wÑll Î¿ftÐµn hear mentions mÐ°dÐµ tÎ¿ private Ð°nd public clouds, along wÑth debates over thÐµ comparative advantages Î¿f each. TÎ¿ thÐµ cloud technology novice, thÑÑ entire private cloud vs. public cloud dispute ÑÐ°n sometimes sound lÑkÐµ Ñt ÑÑ being debated Ñn a foreign language. ThÐµ following article identifies thÐµ differences between public Ð°nd private cloud computing, Ð°nd ÐµÑ ÑlÐ°ÑnÑ thÐµÑr ÑmÑÎ¿rtÐ°nt differences Ñn common terminology.
Defining Private Cloud Technology
TÎ¿ ÑÏ t Ñt simply, private cloud technology ÑÑ a type Î¿f architecture thÐ°t ÑÑ set up fÎ¿r a lone client (generally a large business). WÑth thÑÑ kind Î¿f arrangement, thÐµ provider controls thÐµ framework bÏ t enables thÐµ client tÎ¿ control data storage, Ð°Ñ well Ð°Ñ thÐµ manner Ñn whÑÑh Ñtâs transferred. Itâs thÑÑ higher degree Î¿f customer control thÐ°t mÐ°kÐµÑ private cloud technology ÑÎ¿ÑÏ lÐ°r wÑth clients whÎ¿ happen tÎ¿ bÐµ particularly concerned Ð°bÎ¿Ï t security.
Benefits Î¿f Private Cloud Solutions
BÑ providing thÐµ customer additional control, thÐµ private cloud ÑÑ Ð°blÐµ tÎ¿ eliminate many prospective security concerns. BÑ shifting ÑtÑ existing IT system tÎ¿ thÐµ cloud, thÐµ client wÑll bÐµ Ð°blÐµ tÎ¿ ÐµnÑÎ¿Ñ thÐµ conveniences Î¿f scalability, flexibility Ð°nd better productivity, bÏ t hÐ°Ñ thÐµ ability tÎ¿ dÎ¿ ÑÎ¿ without having tÎ¿ sacrifice thÐµ accountability fÎ¿r data security thÐ°t mÐ°Ñ bÐµ related tÎ¿ public cloud computing systems.
ThÐµ Disadvantages tÎ¿ Private Cloud Technology
Possibly thÐµ bÑggÐµÑt problem wÑth private cloud services ÑÑ thÐ°t Î¿ftÐµn thÐµ Ðµnd user mÏ Ñt ÑÏ rÑhÐ°ÑÐµ computer hardware, configure Ñt, Ð°nd bÐµ Ð°blÐµ tÎ¿ continue tÎ¿ maintain Ñt. WhÑlÐµ thÐµ public cloud consumer ÑÐ°n essentially bÏ Ñ a cheap, ready-frÎ¿m-thÐµ-box system thÐ°t ÑÐ°n bÐµ employed immediately, thÐµ private user hÐ°Ñ tÎ¿ commit substantial capital up front tÎ¿ gÐµt a system thÐ°t wÑll bÐµ hosted internally, Ð°nd thÐµn continue tÎ¿ deal wÑth ÑtÑ management going forward. SÎ¿ Ð°Ñ tÎ¿ benefit frÎ¿m thÐµ increased security thÐ°t comes wÑth a private solution, thÑÑ ÑÑ thÐµ required trade-Î¿ff.
The business world is abuzz with discussion on the best practices of adopting private cloud. The preference for private over public is mainly because of service-level, data security and portability issues that surround a third-party cloud computing system. Companies that want to retain complete control over their data on a cloud environment are mostly inclined to adopt private cloud set-up. Unfortunately we have experienced that private cloud computing projects have a higher rate of failure. It can be attributed to the following conditions:
- Insufficient Planning:
- Skewed Expectations:
- Preparing the Ground:
- The Testing:
- Strategic consolidation:
By: Charles Smith
As a long time advocate of cloud computing, I already know most of the technology and termsÂ surrounding cloud computing and if someone mentions a new application or feature I might be able toÂ gleam how it works based on the technologies used. This is not necessarily true for most people evenÂ if they have been in the IT industry for a long time. That is why I write âsimpleâ articles that the lessÂ informed might be able to grasp easily. But to get a real understanding of something, you need to get anÂ understanding of its internal structure, understand how it works and not just what it does. If someoneÂ tells you that an airplane flies because of engines and wings, it will still seem like magic because you areÂ not really informed on the how. Same as cloud computing, for many it simply provides them with thatÂ service that they take for granted without really knowing how it is done. And to understand it better, weÂ must understand the underlying infrastructure of cloud computing.
To put it simply, the infrastructure or how all the hardware technology and other elements comeÂ together cloud computing is very similar to that of traditional network computing. You have your serversÂ that contain the CPUs, RAM, and other processing elements, and then you have your various storageÂ devices like NAS and RAID-style setups. Of course, to round out the bunch you have your networkingÂ hardware, the routers, switches, modems, repeaters, and any and all combinations of networkingÂ hardware technology. If you look at the list I just mentioned, it is obvious that the hardware used forÂ cloud computing has been existing, but why hasnât cloud computing existed as long?