25.01.2015 Views

Download Full Issue in PDF - Academy Publisher

Download Full Issue in PDF - Academy Publisher

Download Full Issue in PDF - Academy Publisher

SHOW MORE
SHOW LESS

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

1578 JOURNAL OF COMPUTERS, VOL. 8, NO. 6, JUNE 2013<br />

time(ms)<br />

300000<br />

250000<br />

200000<br />

150000<br />

100000<br />

50000<br />

upload to cloud<br />

download from cloud<br />

0<br />

0 500 1000 1500 2000 2500 3000 3500<br />

file size(KB)<br />

Figure 9. Relationship between cloud storage capacity and response<br />

time<br />

amount of code(l<strong>in</strong>e)<br />

24000<br />

22000<br />

20000<br />

18000<br />

16000<br />

14000<br />

12000<br />

10000<br />

8000<br />

6000<br />

4000<br />

2000<br />

0<br />

amount of code <strong>in</strong> client<br />

amount of code <strong>in</strong> cloud side<br />

1 2 3 4 5<br />

service ID<br />

Figure 10. Compare amount of code between cloud and client<br />

Fig.10 compares code quantity of 5 services released <strong>in</strong><br />

Section 4.1 (by serial number, they are <strong>in</strong>stant<br />

messag<strong>in</strong>g[16], cloud storage, campus assistant, onl<strong>in</strong>e<br />

words, mobile TV) <strong>in</strong> the clouds and the term<strong>in</strong>al to<br />

compare the amount of computations roughly. As the<br />

figure shows, numerous comput<strong>in</strong>g tasks focus on the<br />

cloud by virtualization, even respective code quantity of<br />

service term<strong>in</strong>al is relatively more; it is also be<br />

concentrated <strong>in</strong> user <strong>in</strong>terface to be processed with. In<br />

addition, fig.10 shows that when service scale is small,<br />

for improv<strong>in</strong>g user experience, the calculation of client<br />

may closer to the cloud. However, more large-scale<br />

applications are more suitable for deployment <strong>in</strong> cloud<br />

comput<strong>in</strong>g virtualization platform.<br />

C. Compare with Related Work<br />

In virtualization architecture, typical system is<br />

designed by Ch<strong>in</strong>ese <strong>Academy</strong> of Sciences, named<br />

Virtual Management Architecture (VMA)[4]. The model<br />

aims to establish a unified resource management<br />

<strong>in</strong>frastructure for enterprises to realize the unified<br />

management of resources, resource systems and ondemand<br />

service of resource. The VMA focuses on<br />

management and use of underly<strong>in</strong>g hardware facilities.<br />

This is completely different <strong>in</strong> form and nature with<br />

MCCAVM <strong>in</strong> this paper.<br />

VMA is a resource management framework model,<br />

based on virtualization technology and equipped with the<br />

technique of <strong>in</strong>dependent schedul<strong>in</strong>g, which unified the<br />

management and use of <strong>in</strong>terface. VMA is made up of a<br />

number of resource management systems; each <strong>in</strong>dividual<br />

resource management system provides a k<strong>in</strong>d of virtual<br />

resource services. VMA provides reasonable and uniform<br />

resource management <strong>in</strong>frastructure of the system by<br />

unify<strong>in</strong>g these virtual resources management functions to<br />

a unified and consistent management platform.<br />

MCCAVM is a Cloud comput<strong>in</strong>g, virtualization model<br />

based on Metadata-driven. Accord<strong>in</strong>g to the formal<br />

def<strong>in</strong>ition of the model, it <strong>in</strong>cludes metadata entities,<br />

metadata management eng<strong>in</strong>e, the bus architecture, <strong>in</strong>putoutput<br />

system and customer term<strong>in</strong>ation. From the<br />

perspective of model development and control, besides<br />

end users, the model role is divided <strong>in</strong>to two major<br />

categories of developers and system operators. Among<br />

them, the development is divided <strong>in</strong>to capability<br />

developers and service developers. Developers use the<br />

<strong>in</strong>terface language to develop capability or service, the<br />

system operator uses the system language to complete the<br />

model management control task, Table 2 shows the<br />

comparison between the two roles.<br />

TABLE II.<br />

COMPARE MCCAVM WITH VMA<br />

MCCAVM<br />

VMA<br />

Model role<br />

Developers, system<br />

operators<br />

Resource users<br />

realization mode Metadata-Driven SOA<br />

Virtual level<br />

Hardware resources ,<br />

software services<br />

Hardware source<br />

objective<br />

Dynamic scalability for<br />

Unified management<br />

capability and service,<br />

of basic resources ,<br />

platform versatility and<br />

on-demand use<br />

capability to control<br />

Hierarchy<br />

Five parts: Metadata<br />

entities ,metadata<br />

management eng<strong>in</strong>e, bus<br />

architecture, <strong>in</strong>put, output<br />

systems and customer-side<br />

<strong>in</strong>terface<br />

Consists of one or<br />

more virtual resources<br />

management services<br />

(VMS) and a system<br />

of registration and<br />

<strong>in</strong>quiry services<br />

( SRCS )<br />

From the table above we can conclude that VMA<br />

focuses on the basic <strong>in</strong>tegration of resources and rational<br />

management. It is equivalent to an <strong>in</strong>tegration of<br />

resources and schedul<strong>in</strong>g platform, which can achieve the<br />

efficient use and reasonable allocation of resources.<br />

MCCAVM achieves a reasonable distribution of<br />

resources, and forms a broader perspective to understand<br />

the connotation and extension of the capability and<br />

service. Through fig.2, we can f<strong>in</strong>d that the capability<br />

<strong>in</strong>cludes not only just basic resources <strong>in</strong> IaaS layer of<br />

cloud comput<strong>in</strong>g, but all the basic hardware and software<br />

<strong>in</strong> MCCAVS. At the same time, all the production based<br />

on the capability or reproduced through the comb<strong>in</strong>ation<br />

of capability are all service, which reflects the idea<br />

EaaS(Everyth<strong>in</strong>g as a Service). And the model realizes<br />

the dynamic expansion of service and capability and hotswappable,<br />

which further enhances the versatility and<br />

scalability of the model.<br />

© 2013 ACADEMY PUBLISHER

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!