BIM与云计算——技术探索（三）

萧闫子 · 发表于 2014-5-17 14:06:40

BIM and the Cloud

Chris France
CIO, Little Diversified Architectural Consulting

9. Business Continuity, Disaster Recovery, and Security
How many firms back up their user desktops and laptops?  Not many, due to the time and disk requirements.  But IT knows that many people have all kinds of corporate and client information on their laptops.  With the cloud strategy, we were able to keep corporate and client information “in the cloud” where it is backed up and replicated.  Without the cloud, if your laptop is stolen or the hard drive crashes, you are out of commission until your IT department can get you a new laptop or rebuild it after it is repaired.  With an HPGW cloud, if there is a failure, there is no data lost since it is on the SAN.  And there is no downtime.  Little has spare capacity on the cloud just for disaster recovery purposes.  For example, if cloud box LC-0000 goes down (LC stands for Little’s Cloud), IT tells the people assigned to that box to login to LC-5000 and keep on working.  Their profiles and user data migrates over with them.  If their cloud access device (such as their laptop) fails, IT can hand them a spare laptop and they can keep working.  If they are on the road, they can walk into any electronics store and buy a $400 laptop to access the cloud.  And finally, security is greatly enhanced, particularly for the client data.  People can leave their data in the cloud and not have to bring it to the local laptop.  If there is a situation where people need to present and need data locally, it will just be a copy and not the source.
10. Locked Down Corporate Desktops, Unlocked Personal Laptops
How long has IT tried to lock down corporate desktops so that they will be consistently available for business?  Now try to balance that requirement with the people’s need for autonomy, local software innovation, and the ability to respond to clients’ needs without having to check in with IT every time.  Little’s cloud offers the best of both worlds.  We lock down our cloud computers and do not allow any personal applications or data. The local laptop, in effect, becomes our place for personal data, pictures, and applications (such as iTunes).  If people want to back up their laptop, the company recommends that employees purchase their own USB hard drive, or buy a subscription to an online backup service.  If people blow away their local settings and data or their laptop becomes infected with spyware, IT can quickly replace their laptop.  Their business applications and data remain unaffected.
11. Rendering and Animation Farm
Most large design firms have a 3D animation studio where they create photo-realistic renderings of their buildings.  Many take it to the next level of making short movies, fly-throughs, or full cinematic storytelling to give clients a better sense of what their new facility will look like.  These rendering programs have to crunch frame by frame of a video and could take several days to complete. By having a HPGW cloud, these studios can use the cloud at the same time people are using the cloud, just at a lower processor priority (see Figure 4).  When people go home, these programs crank up and fully utilize the CPU all night long.  On some jobs, we have seen rendering times drop from 53 mins/frame to 7.3 secs/frame. With all this additional number crunching ability, regular renderings get done quicker. It is also encouraging Little’s designers to move into “high definition” (HD) rendering to achieve a higher level of quality, client “Wow” factor, and enhanced competitive capability.

登录/注册后可看大图

f00d2006793c065484dfe636de3c9007.jpg (156.86 KB, 下载次数: 0)

下载附件保存到相册

2014-5-17 14:06 上传

Figure 4. The cloud HPGW also does double duty as a rendering farm in addition to running BIM applications.

Implementing a HPGW Cloud Strategy

This section provides an overview of the two main steps we look at Little to create our virtualized High Performance Graphical Workstations. The virtualization of other IT assets such as servers and storage are also crucial to the full workstation cloud strategy. A schematic diagram of the cloud is shown in Figure 5.

登录/注册后可看大图

b863ce95f91f0e88b48bce08b994cd86.jpg (22 KB, 下载次数: 0)

下载附件保存到相册

2014-5-17 14:06 上传

Figure 5. Implementation diagram of the HPGW cloud.

1. Virtualize the Servers and Storage
As a method to save money in buying new server hardware, we began testing VMware’s ESX software.  After an initial pilot on low-risk servers, we worked out tools and techniques and now all servers are placed into a virtual infrastructure. This had led to significant reductions in Little’s hardware expense and we have seen greatly increased operational capabilities such as “instant” provisioning, disaster recovery, and business continuity. It has enabled the IT department to be able to deliver on the corporate challenge to “do more with less.”
Next, Little chose to virtualize its storage to save money and to be able to manage a mountain of data with existing IT staff.  We standardized on the EMC CX500 and have a big pot of disks that are carved as needed for applications and servers. That pot-o-disk is approaching 50 TB on two, redundant EMC’s.
2. Virtualize your High Performance Graphical Workstations
Let me first clarify what I mean when I say “virtualized workstations.” Technically, these workstations are not virtualized like most IT people think of virtualization.  We do not use VMware’s ESX server or any other Virtual Desktop Infrastructure (VDI) like Citrix Zendesktop or VMware View.  We use a utility that allows us to share the Windows 7 64-bit operating system with many users at the same time.  So from an IT perspective, this is a shared piece of hardware.  From an end user’s perspective, it looks and feels like a virtual desktop.
To derive the same virtualization benefits for our desktops that we had realized with our servers and storage, we tested various desktop virtualization products. However, they did not virtualize the Graphics Processing Unit (GPU), which led to poor performance—a cloud that would be slower than users’s laptops.  The key to getting our users to move to a workstation cloud was to provide not just the same experience as their laptop, but an experience that was WAY better than their laptop.  I wanted a workstation cloud that people couldn’t touch with their laptop computers.
What if we took a baby-step towards desktop virtualization and used a hybrid approach?  I had a vision where we could have a smoking fast workstation sitting in a data center that we could get to via various remote desktop protocols.  But this wasn’t good enough.  That approach still needed a one-to-one mapping of people to workstations.  This really didn’t save us any money.  But what if we could turn a single-user workstation into a MULTI-USER workstation—call it a workstation server?  To our end users, it would look virtualized to them and be in the “cloud.”  To the IT staff, it was a piece of shared hardware.  I challenged our IT staff to come up with a concept to build this and they did!  Based on our benchmark testing, we are able to put 10 people on these shared workstations.
Here is the “the secret sauce” of our strategy:
Hardware
   Rack mounted workstation
   (2) 3.0 Ghz Xeon quad-core processors (8 cores total)
   32GB RAM
   1.5GB Video RAM
   Fast local hard drive
   User/design data mapped to virtualized storage on our SAN
   Client access device: their primary Windows laptop
Software
   Microsoft Windows 7, 64-bit desktop operating system
   Utility software for multi-user access, load balancing of CPU, network, and memory resources.
   Remote Desktop Protocol (RDP) used for client remote access
Based on a company the size of Little (225 people), we can provide design services on 20 HPGW cloud computers. These workstations will NOT need to be refreshed every 2 yrs like users’ individual laptops.  We are guestimating that we’ll refresh every 4-5 yrs, with maybe a component upgrade in the interim.  Our primary laptops will only need to be replaced when they die—and we’re hoping to get 4 years out of them.  With most of the computing load moved off our laptops, when we do need to replace laptops they will cost $800-$1000 rather than $2200-$2500.  I figured it was better to spend $1M over 10 years rather than $3M to buy desktop computing hardware.
Does this solution work internationally?  Technically it does, but I would say practically it does not.  The network latency across oceans is really too great to get a smooth desktop experience.  I have logged into the cloud from my aircard and it was OK.  Typing was slow, but you can do basic things.  The latency on my aircard was 180ms and that is similar to what one would experience over the oceans.  So depending on how globally you are working now, it may be better.  But it is not the “same as being there” performance. Within the US, however, the performance is rock solid, with coast-to-coast latencies of 50-55ms.  It works so well that we were able to run our Los Angeles office entirely in the cloud with no local storage, as mentioned earlier.  If a company has an international footprint, you could set up clouds on each continent so you would not have to cross the ocean to work.
Here is a list of the lessons we have learned so far from production users on the cloud:
   With multiple users using the same workstation, we were able to see how underutilized our laptops really are.  Most of the time, they are sitting idle when people are in meetings or out in the field.  This makes laptops ripe for consolidation.
   Not all users’ computing needs are the same—some consume much more memory and CPU than others.  The IT staff worked with them to see if the need is legitimate or if there was a training issue.
   Memory was the biggest constraint.  Early on, we had a “cloud burst” by having too many people consuming memory on one box.  We locked up the box.  By reducing the number of designers per box from 8 to 7 and adding more memory, the cloud bursts were eliminated.
   Some applications do not lend themselves well to a remote desktop strategy.  We had to tweak our AutoCAD program because the mouse-pointer “cross hair” caused too much data to be sent—and this is tiresome if a user is working in AutoCAD all day long.  Real-time video compositing also works better with local hardware.  Be sure to test your mission critical applications.  The cloud approach is better, but not perfect.
   We can drive utilization of these boxes to nearly 100%.  When people aren’t using them, we turn these into our “rendering farm” that generates computer animations.  Since these processes run at a lower priority than our user applications, they can be running at the same time as people are designing.  Any additional capacity is used for new users and disaster recovery purposes.
   Running on the cloud is faster from home than a laptop hooked into a broadband cable service.
   People forget where they leave their stuff.  IT people take remote desktops for granted since they use them every day.  It takes a little coaching and practice on the users’ part to realize what’s going on.  But once they catch on, they are all over this new computing method.

Conclusion

At Little, our high performance graphical workstation cloud strategy has realized all eleven business benefits discussed earlier and we will continue to improve and come up with more. I see this private, hybrid, HPGW cloud to be invaluable until the main software vendors have created software that can truly virtualize the GPU. When that time comes, perhaps in the next 3 to 4 year, we will upgrade our cloud infrastructure to be able to run 225 designers on only two physical high performance graphical workstations. We can only dream.

About the Author

Chris France is the CIO for Little Diversified Architectural Consulting, located in Charlotte NC. He has specialized in Information Technology for over two decades. He started his career at IBM Federal Systems as a software and systems engineer and progressed to project manager of major DOD systems. From IBM, he traveled to Charlotte to work for Bank of America where he led efforts to merge and consolidate the information technology of major bank acquisitions. Prior to becoming the CIO of Little, he consulted in the technology-intense Wachovia Capital Markets.

As CIO of Little, Chris not only leads the firm’s Information Technology Strategy, Planning and Operations, but he also works with clients to ensure that their diverse technology needs are addressed and incorporated during the design process of their new facility.

Note: AECbytes content should not be reproduced on any other website, blog, print publication, or newsletter without permission.

来源：AECbytes.com

帐号		自动登录	找回密码
密码			注册

BIM与云计算——技术探索（三）

相关帖子

社区QQ达人