Data Center is our focus

We help to build, access and manage your datacenter and server rooms

Structure Cabling

We help structure your cabling, Fiber Optic, UTP, STP and Electrical.

Get ready to the #Cloud

Start your Hyper Converged Infrastructure.

Monitor your infrastructures

Monitor your hardware, software, network (ITOM), maintain your ITSM service .

Our Great People

Great team to support happy customers.

Friday, August 12, 2011

Membangun Modular Data Center

Membangun Modular Data Center merupakan suatu tantangan tersendiri. Bukan hanya karena mungkin ini akan merupakan suatu hal yang baru untuk Indonesia, dimana selama ini, pembuatan dan pengembangan data center seringkali mengalami kendala apabila berkaitan dengan tempat. Maka pemilihan konsep modular data center tidak dapat dielakkan lagi.
Berikut adalah pengalaman menarik yang dilakukan oleh UCLA dalam membangun data center modular mereka.

Inside the Box: UCLA's New Portable Data Center

When UCLA found out that a planned upgrade to its brick and mortar data center was going to surpass the original budget estimate by several million dollars, it began thinking "inside the box"--and chose cargo-container computing.
The latest and potentially most powerful research data center at the University of California Los Angeles (UCLA) was delivered on the back of a flat bed truck from Austin, TX. It was put in place with a crane. The facility resembles the kind of container used to run portable recycling centers. But when it's fully loaded and performing research in physics, economics, genomics, and biochemistry, among other disciplines, the Performance Optimized Datacenter, or POD, will support more than 1,500 compute nodes. This far exceeds the campus' traditional "brick and mortar" data centers in sheer computing power, and yet it fits into a compact space of 40' x 8'.
The story of UCLA's "pod" began in January 2008. At that time, 18 clusters of high performance computing were being delivered from two primary locations, the Math Sciences data center and the Institute for Digital Research and Education (IDRE) data center. Between the two, researchers could run jobs on any combination of about 800 nodes. But capacity was fairly well tapped out, according to Bill Labate, director of UCLA's Academic Technology Services and managing director of IDRE.
IDRE works as a kind of shared service. "People 'buy' nodes and then we integrate them," said Labate. Technically speaking, users don't really buy the nodes and hand them over; IDRE does the purchasing, based on well researched specs that provide high value for a low price; operations are ultimately funded by the 175 research groups in 64 departments and centers on campus that partake of the center's services and equipment.
A Plan for Growth
Given that the IDRE center had physical space available, the Institute put together a proposal to increase computing capacity. It brought in a third-party data center engineering firm to do a quick estimate of what the project would take. The needs were substantial. The goal was to squeeze in 1,600 computer nodes; but the existing power infrastructure could only support about 400 nodes. Somehow, the center would have to be revamped to support the dramatically increased wattage required by those additional nodes and the cooling they'd require. The consulting firm's estimate came to $4.6 million. Based on that number, the university granted IDRE funds to do its build-out.
That's when IDRE knuckled under to sort out various configurations for the project. The center brought in another consulting firm to do a more detailed cost estimate. This time, however, the estimate for 1,600 nodes exceeded $7 million. A second proposal for an 800-node build-out came in at $4 million.
"We were stuck almost $3 million low in budget," Labate said. "We went through a whole series of [scenarios]: What if we only do this many nodes capacity? What if we go to these hot aisle containment systems? It got down to where it was almost ridiculous to do something with this brick and mortar data center."
Computing in a Box
At the same time modular data centers, also called "containerized data centers," were getting media attention. Sun Microsystems had previewed "Project Blackbox," in late 2006. In mid-2008 both HP and IBM began publicizing their modular data centers. All promised to reduce energy usage, a major consideration in data center expansion. According to a 2010 study by Gartner, energy-related costs account for about 12 percent of overall expenditures in the data center, a share that's expected to rise as energy costs themselves rise.
Labate began having conversations with people at other institutions that were trying these new kinds of containerized set-ups, including UC San Diego and Purdue University, both major research universities. "We started thinking, these modular data centers could be a viable alternative."
Due diligence led the university to settle on HP's pod for four compelling reasons: density, price, flexibility, and energy efficiency. The pod could contain 1,500 nodes, nearly the same count as the planned data center build-out; but the price would be only $2 million versus $7 million.
When IDRE was in the middle of its shopping, it discovered that not all modular data centers are alike. "Some of the modular data centers required you to have specific equipment--and as you can imagine, the equipment was specific to the vendor of that particular unit," noted Labate. "That would have forced us to standardize forever on that particular node, which is something we would never want to do. With the HP pod, we can put anything we want in there."
That flexibility is important. The various compute clusters on campus currently carry four brands of equipment in all kinds of configurations. But on a regular basis, IDRE goes out to bid on computing nodes to find the optimal combination of feature set for price. The current choice happens to be HP, he explained. "But that's not to say there might not be another vendor in the future that comes along that meets that price/performance curve."
As of August 2010, the minimum standards for those computer nodes are:
  • 1U, rack-mounted; half-width preferred (two nodes sit side by side in the slot);
  • Dual six-core 2.6 GHz Intel Core i7 or Xeon 2.66GHz CPUs;
  • 4 GB of memory per core;
  • 160 GB to 250 GB hard drive per node;
  • A Gigabit Ethernet port, DDR/QDR InfiniBand interconnect, and PCI-Express slot; and
  • Three-year warranty.
Preparing for Pod Arrival
UCLA placed the order for an HP 40c pod in October 2010. The vendor could have shipped it within six weeks, but, as Labate pointed out, "You have to build a site to put this thing on." Rather than going through the exercise of accepting delivery of a 43,000-pound retrofitted cargo container, stashing it somewhere, then hauling it out again for final placement, the campus told HP to keep the pod in its Austin factory until the site preparation was done.
 A crane lowers UCLAs pod into its new home, a former loading zone.
A crane lowers UCLA's pod into its new home, a former loading zone.
Working closely with the facilities and capital planning staff members, as well as HP, IDRE identified a former loading zone and storage area on the main campus that fit several criteria: The pod would be hidden so as not to mar the aesthetics of the other buildings on campus; it was sizable enough to accommodate not just one but two pods, for the day when UCLA decides to increase its high performance computing capacity; and the site could accommodate the major upgrade to power and chilled water that would be necessary for the running of both the new pod and the future pod.
To support the 110,000 pounds the pod would weigh once the equipment was in place, workers poured a concrete slab that Labate estimated to be between two and three feet thick.
 The portable data center in place. Loaded, it will weigh about 110,000 pounds.
The portable data center in place. Loaded, it will weigh about 110,000 pounds.
Labate noted that HP would have delivered the pod equipped with its computing components, ready to plug in and add to the network. That's the way it's promoted on the Web site: "fully integrated and tested ... as part of a complete data center solution." "We didn't want to go that route," he said. "It came from Austin to L.A. on a truck, and I didn't want to subject my equipment to that stress."
Insulation in the Extreme
Once the site was done and the pod delivered, a crane lifted the pod off the flatbed and onto the slab, and it was ready to outfit. On the interior, the pod holds 22 racks, each 50U tall or about 88 inches, along the 40-foot wall. Opposite is a narrow aisle wide enough for accessing and moving equipment.
To control the climate, blowers on the ceiling force air conditioning downward; hot exhaust goes out the back and rises up, enters the coolers, gets cooled, and sinks down again. Equipment located on the "hot aisle" side of the pod, where all the hot exhaust blows, is actually accessible from the outside. The pod is outfitted with sensors for temperature, chilled water supply, and humidity, as well as leak detectors under the water mains and overhead condensate drip pan.
Describing the pod as "really solid," Labate observed, "When you walk inside, with all of this equipment running and 36 blowers--it's extremely loud. You go outside, and you can't hear a thing. You can't feel anything on the outside. You don't feel cold when you touch the metal."
He estimated that the highly maximized environment saves about a third more power than that which would have been required by a brick and mortar data center.
"It's very Spartan," Labate said. "It's a purpose-built data center with extremely tight engineering for the purpose of being highly energy efficient. It's not something you want 10 or 15 people to try to get into. It's strictly made for the equipment, not the people."
Proximity to the other data centers was fairly unimportant to the placement decision, Labate said. All of the centers are linked over the campus networking backbone for Ethernet connectivity and interconnected by wide area Infiniband for input/output.
Because the pod's monitoring systems--both environmental and on the computing gear--can be managed remotely, Labate anticipated weekly visits to the pod to handle work that needs to be done. "The No. 1 thing is keep as many nodes up and running as possible. If we have a catastrophic failure, we're going to go fix it. But if a hard drive goes out or memory goes bad, we'll queue those up and send somebody out there once a week."
Mishaps and Skeptics
In the 10 weeks the pod has been in place, IDRE has loaded about 250 nodes into the racks--between 15 percent and 20 percent of capacity--which is just about where it needs to be right now. During a recent check, Labate said, the entire system was running at 95 percent--about 733 jobs--across all three data centers. "When you run on this system, you have no idea where you're running, nor do you need to know. That's all handled in the background with a scheduling system."
But there's still a bit of "teething" going on with the new environment. It hasn't been hooked into the campus alarm or fire systems yet. And, Labate added, more people need to get inside to learn about the new layout. In its short time on campus, that newness has already caused a mishap. Twice, the same vendor contracted to maintain the FM-200 fire suppression system has accidentally discharged the gas. "They know how to do FM-200. They're not familiar with the actual pod configuration."
As might be expected, the idea of a pod-based data center was off-putting to some of the data center technical crew, Labate said. "When the rubber meets the road, they have to be the ones to maintain it," he pointed out. "They have to work in it, put equipment in it."
IDRE sent a couple of people to the Austin factory to watch how the container was built. HP brought a pod to a local movie studio and members of IDRE took a piece of equipment there to see how it would fit. Eventually, the skeptics warmed up to the new approach. "They started to realize what it is," he said. "This isn't a building. It isn't a rehearsal studio. It isn't an office. It's a data center, period. That's all it is. It doesn't claim to be anything else."
So while most people were skeptical that this was actually a good decision, Labate noted, "in the end, it turned out to be probably the best decision we could have made."
About the Author
Dian Schaffhauser is a writer who covers technology and business for a number of publications. Contact her at dian@dischaffhauser.com.

Tuesday, August 09, 2011

Selamat kepada JOBSTREET INDONESIA

Selamat kepada PT JOBSTREET INDONESIA yang menempati kantor barunya. Dengan menggunakan teknologi structure cabling system, dilengkapi dengan perangkat ruang server serta implementasi Hybrid IP PBX, maka Jobstreet memulai layanannya di tempat barunya.
Kami bangga melayani Anda.

Monday, August 08, 2011

Menggabungkan flash-softphone di website dengan 3CX IPPBX

Menggabungkan flash-softphone di website dengan 3CX Phone System

Salah satu hal yang menarik dari produk-produk yang kami jual adalah ternyata diantara produk tersebut dapat saling berinteraksi. Salah satunya adalah produk OZEKI Webphone dengan 3CX Phone System, silahkan simak dibawah ini.

How to add a Flash softphone to your webpage, if you use 3CX phone system

This guide explains how to connect Ozeki Webphone to 3cx Phone System. This solution provides you an efficient system for managing VoIP calls arriving from your website. Watch the video tutorial and follow the configuration steps to realize this excellent solution.

Video: How to add a Flash softphone to your webpage, if you use 3CX phone system

Ozeki Webphone is a browser to phone solution that uses Voice over IP (VoIP) technology to place calls over the Internet. Ozeki Webphone includes two components: a website component, called Webphone and a server side component called Ozeki Webphone gateway.

Using VoIP technology is less expensive than traditional phone services. A fully featured webpone (such as Ozeki Webphone) offers all the functions of a traditional phone to establish calls. Your Website visitors can use the keypad to dial the assigned phone number and its display will inform them about the exact status of calls. The advantage of a fully featured webphone is that it ensures real calling experience plus its keypad can also be used for IVR or for other telephone functions.

This configuration guide demonstrates how easy to connect Ozeki Webphone to your 3cx PBX.

System architecture

If you follow the configuration guide below you will have a telephone system that works as follows:

Let's see how this system works with the help of an example. Let's say you have two VoIP telephones connected to your PBX. After this configuration below, Ozeki Webphone Manager will also be connected to your PBX as the third extension. So the Ozeki Webphone Manager will be handled as a client such as the VoIP phones.

When a website visitor decide to call you using Ozeki Webphone on your webpage the following will happen:

Figure 1 - Incoming call from the web
  1. Ozeki Webphone Manager will register in the PBX
  2. The incoming call is forwarded to the PBX by the Ozeki Webphone Manager
  3. The assigned phone will be ringing
  4. The connection is created and you can start to talk with your website visitor
That's simple but effective. Now learn the steps how to realize this excellent telephone system!

Configuration steps

Before you start to configure this solution it is assumed that you have already installed the follows:
  • 3cx Phone System
  • IIS with a basic website

Step 1 - Download and install Ozeki Webphone

First of all, I downloaded Ozeki Webphone installer and extracted it to the PC (Figure 2).

Figure 2 - Ozeki Webphone setup
Start Ozeki Webphone Installer. The installer will check the prerequisites. One of the prerequisites is the .Net Framework 4. If you do not have Microsoft .Net Framework 4 installed on your PC then the installer will install this component. Accept the license agreement to start the installation (Figure 3).

Figure 3 - Accept license agreement
The installer downloads and install .Net Framework 4 automatically (Figure 4).

Figure 4 - Installation of .Net Framework 4.0
Then the installation wizard of Ozeki Webphone also starts. First you need to select how do you wish to serve the content that is required for Ozeki Webphone. In this example I use an external webserver so I select I want to serve the content from an external webserver option and click Next (Figure 5).

Figure 5 - Ozeki Webphone installation wizard
After installation the Help window of Ozeki Webphone appears automatically. Here you can find detailed description of the webphone (Figure 6).

Figure 6 - Help window of Ozeki Webphone

Step 2 - 3cx configuration

Now start the Windows Management Console of 3cx from Start menu (Figure 7).

Figure 7 - Start Windows Management Console
Login with your username and password (Figure 8).

Figure 8 - Login
Go to Extensions menu and click on Add extension (Figure 9). In this example clients can register in two extensions. To extension 100 a land line telephone will register in, to extension 101 the Webphone Manager will register in our example.

Figure 9 - Add extension
On the configuration form specify the Extension Number. For authentication also enter ID and Password (Figure 10).

Figure 10 - Specify the parameters
Click on OK to save the changes (Figure 11).

Figure 11 - Save changes

Ozeki Webphone settings

Now go to Settings menu in Ozeki Webphone Manager and click on SIP accounts menu item. In this way SIP accounts window appears. Click on Add to add the extension that have been registered in the PBX (Figure 12).

Figure 12 - SIP accounts window
Enter the following parameters: Display name, User name, Register name, Register password. In this example I have registered Ozeki Webphone Manager with extension number 101. In Domain server field enter the IP address of the computer on which the PBX has been installed. Finally, click Save to save changes (Figure 13).

Figure 13 - Add a component
Click on Save in SIP accounts window, as well (Figure 14).

Figure 14 - Save changes
Now I copy the content of Webcontent directory of Ozeki Webphone to the directory of my webserver. To do so go to the install directory (Program Files\Ozeki\Ozeki Webphone) and open Webcontent directory (Figure 15).

Figure 15 - Webcontent directory
I copy the content of Webcontent directory into inetpub\wwwroot\testwebphone directory (Figure 16).

(Webcontent directory contains files that are need to be served for the proper functioning of Webphone. The IIS webserver has the following file structure: C\inetroot\wwwroot\... The files can be found here will be the root directory for the website. For example: index.html. Testwebphone directory will include the webphone (the html).)

Figure 16 - Copy the content of Webcontent directory
In order to create the html file for the webphone go to Ozeki Webphone Manager\Generate html\Fully featured webphone (Figure 17).

Figure 17 - Generate html
In the html generator window select Webphone. The HTML code will be generated. Click on Copy to clipboard (Figure 18).

Figure 18 - Generated html
Now start a simple text editor that is able to save texts into plain text format e.g. Notepad and create a basic html document. Then Paste the generated html code between the body tags (Figure 19).

Figure 19 - Paste the html code
Save the html document (Figure 20).

Figure 20 - Save html document
In this example the html document is saved as "test.html" into wwwroot\testwebphone directory (Figure 21).

Figure 21 - Test.html file
After you saved the html document navigate to the created html file. In this example the path is: http://localhost/testwebphone/test.html (Figure 22).

Figure 22 - Full path to the html document
Finally the Ozeki Webphone interface appears. If the registration is successful then you can see Successfully registered notification on its display (Figure 23).

Figure 23 - Successfully registered webphone

Testing the system

For demonstration I call extension 100 (that is the VoIP hard phone) from the Ozeki Webphone (Figure 24). Use the keypad to enter digits.

Figure 24 - Test call
Then camera and microphone access needs to be allowed (Figure 25).

Figure 25 - Allow camera and microphone access
Finally the land line phone is ringing so the first call is successful (Figure 26).

Figure 26 - Successful call

In conclusion...

Now the configuration is complete and you can start to use your improved telephone system efficiently. You can enjoy the instant benefit: from now on your website visitors can call you from your websites free of charge.

Sunday, August 07, 2011

Kami mencari tim developer

Kami kembali membuka kesempatan bermitra jangka panjang bersama dengan kami untuk meraih masa depan bersama:
1. Asp Programmer
- mengembangkan modul kiosk berbasis ASP
- mengembangkan modul HRIS berbasis ASP
- pengalaman 1 thn di ASP
- menguasai MSSQL
- sistem kontrak 1 thn / freelance onsite

2. PHP programmer
- mengembangkan modul aplikasi MLM, SMS, ERP, SIKA
- pengalaman 1 thn di PHP/MySQL
- mengerti MySQL
- sistem kontrak 1 thn / freelance onsite

3. Application Implementer
- mengerti SDLC
- mengerti dasar PHP/ASP/MSSQL/MySQL
- komunikasi aktif
- bersedia bekerja di client
- sistem kontrak 1 thn

4. Sistem Analyst
- mengerti SDLC
- mengerti Project Management
- mengerti PHP/ASP/Mssql/Mysql.
- sistem kontrak 1 thn / freelance onsite

Silahkan kirimkan cv ke hrd@dayaciptamandiri.com

Kami tunggu segera.
thanks,
Fanky
08121057533

build-access-manage on www.dayaciptamandiri.com