云計算平臺虛擬機-wenkub
2023-07-08 14:57:13 本頁面
【正文】 nd cally we show how the virtual cluster is built and tailored to t virtual technique presented in this paper,known as the Virtual Organization Cluster Model,shows great potential for cloud our implementation, we used a minimalist installation of Slackware Linux12on14pute nodes,ensuring minimal host prototype Virtual Organization Cluster is posed of28virtual putes nodes,each running Condor,and of testing the prototype were encouraging,with the exception of network performance.Categories and Subject Descriptors: [Computer Systems Organization]:Performance of Systems Design studies。s particular application.Similarly,Virtual Organizations(VO39。 et al. (aType1(bType2then deploy it to a VSP39。s[Keahey et ].Destroying a virtual cluster is as simple as sending SIGKILL to each hypervisor and deleting the image from disk.KVM supports the standard Linux TUN/TAP model for Ethernet using this model,each VM gets its own networking resources,making it indistinguishable from a physical machine. Compute NodesCentral to the Virtual Organization Cluster Model(VOCMis the Virtual Organization Cluster(VOC,which is posed of Virtual Compute Nodes( Virtual Organization(VOthat wishes to utilize the pute facilities provided by a Virtualization Service Provider(VSPmust provide a VM image or set of VM images,along with some general con guration each image will potentially be used to spawn multiple VM39。 et al.(1A virtual head node,which was con gured with the Condor central managerand submit daemons(condor_collector,condor_negotiator,condor_schedd, Ganglia monitoring daemon(gmond,and Ganglia meta daemon(gmetad.(2A virtual pute element,which was con gured with the Condor job starter(condor_startd,MPICH2,ATLAS(tuned for the virtual CPU,and Ganglia monitoring daemon(gmond.Our model VOC was designed as an Open Science Grid(OSGpute element. The virtual head node used Condor to distribute ining OSG jobs to the virtual pute elements. MODELPreparing the physical(as opposed to virtualcluster for VOC support required con guring the host OS,setting up support services,con guring networking services,and con guring storage our prototype implementation,support services included a Lightweight Directory Access Protocol(LDAPserver for centralized administration of hosts and physical user accounts,a Dynamic Host Con guration Protocol(DHCPserver for assigning IPv4addresses to nodes,and a Domain Name Server(DNSfor host resolution. OS con gurationWhen providing virtualization services,the host OS should be minimalist in order to reserve as many resources as possible for the this end,Slackware Linux 12was chosen as the host custom kernel was piled to enable support for KVM and additional network unnecessary hardware drivers and other features were left out of the kernel to minimize its memory driver modules also were built for the custom kernel.For maintainability reasons,all the Slackware nodes were installed via PXE boot and a custom automated install allowed the whole cluster to be recreated quickly in case of added nodes,hardware failure,or administrator additional software was maintained in the form of Slackware packages to allow for rapid deployment across the entire cluster. Support ServicesCon guration information for each VCN was stored in an LDAP database to provide a centralized administration VCN was
研究報告相關(guān)推薦
鄂ICP備17016276號-1