Dissertaç ˜ao de Mestrado Mestrado em Engenharia Informática Jo ...

More documents

Recommendations

Info

6. INTEGRATION WITH VIRTU 6.2. VIRTU Top-Level Analysis Aware of this market shift, Evolve Space Solutions proposed VIRTU, a platform for the creation and management of virtual machines. Before that, the GoVI virtualization tool was developed for the European Space Agency in order to deal with some outstanding problems in their IT infrastructure, such as the large number of underutilized machines, great demand for isolation and a myriad of different hardware platforms. The development on VIRTU ini- tially took on the GoVI infrastructure as a starting point, but eventually evolved to become an independent project, dettached from the former. VIRTU explores interoperability between virtualization solutions, such as Xen [Cit09] or VMware [VMw09]. One way to achieve portability of VMs among different virtualization platforms is to resort to virtualization standards. Open Virtual Machine Format (see Section 2.1.3), which is being developed by the biggest virtualization players, is one of such standards and VIRTU might evolve to support it. Another big opportunity in the virtualization area is the fact that application configuration is still largely a manual task. The complexity of configuring a system with manifold applica- tions, employing different configuration formats, can be frightening for a system administrator. This complexity is only magnified when dealing with a huge system, composed of hundreds, or even thousands of such systems. To ease the system maintenance burden, VIRTU proposes the generic automatic application configuration or, in other words, the ability to configure any application, regardless of its vendor or configuration representation, on the most autonomous and automatic manner. The framework presented by this dissertation, SmART, is the Universidade Nova de Lisboa contribution for project VIRTU. Once SmART was completed, it was integrated with the whole VIRTU tool. 6.2 VIRTU Top-Level Analysis The VIRTU tool [Sol09b] implements the concept of Assembly Instance, which refers to one, or a set of virtual machines that the users will use and manage directly. An Assembly Instance results from the instantiation of an Assembly Configuration, which contains the information used to generate one VM, or a set of VMs. To each VM in an Assembly Configuration corresponds a Virtual Machine Configuration and when an Assembly Configuration is instanced, its VM Configurations are also instanced into VM Instances. Each Virtual Machine Configuration is a combination of Building Blocks and Publication Files. A Building Block is a template element, such as an operating system, application or virtual machine, whereas a Publication File contains the desired configuration of a Building Block. In order to re-use previously existing Assembly Configurations, it is also possible for Assembly Configurations to con- tain other Assembly Configurations. The VIRTU Assembly Configuration model is depicted in Figure 6.1. The configuration of an Assembly Instance is carried at the level of its VM Instances. Inside a VM Instance resides a process which is ran at every VM boot and, for each 68
6. INTEGRATION WITH VIRTU 6.2. VIRTU Top-Level Analysis 34( )*+,-./012-*+ 6/-&7-+.( 6&*89 :/%&-812-*+( ;-&# !""#$%&'( )*+,-./012-*+ 34( )*+,-./012-*+ 6/-&7-+.( 6&*89 :/%&-812-*+( ;-&# 5(5(5 5(5(5 6/-&7-+.( 6&*89 :/%&-812-*+( ;-&# Figure 6.1: VIRTU Assembly Configuration 34( )*+,-./012-*+ Publication File, checks a flag that tells if that Publication File was altered since the last boot. If not, no action is taken for that Building Block. Otherwise, if a Publication File is indeed different, it means the Building Block associated to that Publication File has altered variables or different operating modes and, consequently, the configuration files for that Building Block must be rebuilt. This rebuilding is done by the process itself and once it is finished, the flag is reset. The actors in the VIRTU tool can be administrators or users. Each role is allowed to perform different actions that may be divided in two categories: virtual machine management and user management. An administrator has the permission to manage (i.e., create, edit and delete) the tool’s Building Blocks and Publication Files, to construct Assembly Configurations, to accept Assembly Instance requests from the user and deploy those Assembly Instances and to manage the running Instances, with the option of halting their execution. The administrator may also create and manage the users of the tool. On the other hand, the actions available to users are to configure Publication Files, to request Assembly Instances, to use the virtual machines and control their lifecycle, to share Assembly Instances with other users and to organize them. Beyond that, the user may also change his password. On a broad view, VIRTU may be divided into a handful of logical modules. This division aims at increasing agility and flexibility in the maintenance and optimization of the system resources. A scheme containing the modules is shown in Figure 6.2. The VIRTU Configuration Database stores all information regarding the tool, such as user accounts, the locations of the available Building Blocks, Assembly 69
Page 1:
Universidade Nova de Lisboa Faculda
Page 5:
To my family and friends, who suppo
Page 9:
Sumário Entre os sectores de tecno
Page 12 and 13:
CONTENTS 3.5 Modifying the Configur
Page 15:
List of Figures 2.1 Virtual applian
Page 19 and 20:
List of Listings 1.1 Apache configu
Page 21 and 22:
1 Introduction This dissertation pr
Page 23 and 24:
1. INTRODUCTION 1.2. Problem Descri
Page 25 and 26:
Page 27 and 28:
Page 29:
1. INTRODUCTION 1.5. Document Organ
Page 32 and 33:
2. STATE OF THE ART AND RELATED WOR
Page 34 and 35:
Page 36 and 37:
Page 38 and 39: 2. STATE OF THE ART AND RELATED WOR
Page 41 and 42: 3 An application reconfiguration fr
Page 43 and 44: 3. AN APPLICATION RECONFIGURATION F
Page 55: 3. AN APPLICATION RECONFIGURATION F
Page 58 and 59: 4. AN IMPLEMENTATION 4.2. Parser Ge
Page 60 and 61: 4. AN IMPLEMENTATION 4.4. Data Stru
Page 62 and 63: 4. AN IMPLEMENTATION 4.4. Data Stru
Page 64 and 65: 4. AN IMPLEMENTATION 4.5. Original
Page 66 and 67: 4. AN IMPLEMENTATION 4.6. Generatio
Page 68 and 69: 4. AN IMPLEMENTATION 4.7. Generic t
Page 71 and 72: 5 Framework Evaluation Chapter 3 pr
Page 73 and 74: 5. FRAMEWORK EVALUATION 5.2. Operat
Page 83 and 84: 5. FRAMEWORK EVALUATION 5.3. Perfor
Page 85: 5. FRAMEWORK EVALUATION 5.3. Perfor
Page 90 and 91: 6. INTEGRATION WITH VIRTU 6.3. VIRT
Page 92 and 93: 6. INTEGRATION WITH VIRTU 6.3. VIRT
Page 94 and 95: 6. INTEGRATION WITH VIRTU 6.4. SmAR
Page 96 and 97: 6. INTEGRATION WITH VIRTU 6.4. SmAR
Page 98 and 99: 6. INTEGRATION WITH VIRTU 6.5. Summ
Page 100 and 101: 7. CONCLUSION AND FUTURE WORK 7.1.
Page 103 and 104: A.1 OGC sequence diagram A Appendix
Page 105 and 106: B.1 MySQL Configuration file # # Th
Page 107 and 108: B. APPENDIX - EVALUATION B.1. MySQL
Page 109 and 110: B. APPENDIX - EVALUATION B.2. Apach
Page 139 and 140:
B. APPENDIX - EVALUATION B.2. Apach
Page 141 and 142:
B. APPENDIX - EVALUATION B.3. Eclip
Page 143 and 144:
Page 145 and 146:
Page 147 and 148:
Page 149 and 150:
Page 151 and 152:
Page 153 and 154:
Page 155 and 156:
Page 157 and 158:
Page 159 and 160:
B. APPENDIX - EVALUATION B.4. Perfo
Page 161 and 162:
Page 163 and 164:
Page 165 and 166:
Page 167 and 168:
Page 169 and 170:
Page 171 and 172:
Page 173 and 174:
Page 175 and 176:
Page 177 and 178:
Page 179 and 180:
Bibliography [Ama09] Amazon. Amazon
Page 181:
BIBLIOGRAPHY [Sol09a] Evolve Space
show all

Dissertaç ˜ao de Mestrado Mestrado em Engenharia Informática Jo ...

Create successful ePaper yourself

Delete template?

Save as template?