Nova AZ與Cinder AZ同步的問(wèn)題
2015年08月26日 湖南景煌網(wǎng)絡(luò)科技有限公司
www.banjiwang.cn
在使用OpenStack云平臺(tái)時(shí),有時(shí)因業(yè)務(wù)架構(gòu)需要拆分不同的Availability Zone可用域,包括計(jì)算Nova和存儲(chǔ)Cinder,并期望可以將兩個(gè)AZ對(duì)應(yīng)起來(lái)。目前多數(shù)OpenStack平臺(tái)或多或少采用了Ceph作為Cinder存儲(chǔ)后端(以及Glance、Swift),并在創(chuàng)建虛擬機(jī)時(shí)選擇從鏡像創(chuàng)建塊存儲(chǔ)。我們希望可以通過(guò)創(chuàng)建不同的Cinder AZ配置不同的Ceph pool,每個(gè)pool關(guān)聯(lián)不同的osd,已便達(dá)到不同用戶創(chuàng)建的虛擬機(jī)操作系統(tǒng)磁盤(pán)在Ceph集群中是分開(kāi)的。
我們啟動(dòng)多個(gè)cinder-volume實(shí)例,配置不同的storage_availalibility_zone,期望是選擇虛擬機(jī)的AZ時(shí)可以匹配Cinder里的AZ,例如:
storage_availability_zone=AZ1
查看源碼/usr/lib/python2.7/site-packages/nova/conf/cinder.py中的設(shè)定,發(fā)現(xiàn)一個(gè)關(guān)鍵參數(shù)cross_az_attach,默認(rèn)值為T(mén)rue,這意味著虛擬機(jī)的磁盤(pán)可以跨域綁定。
cfg.BoolOpt("cross_az_attach", default=True, help=""" Allow attach between instance and volume in different availability zones.If False, volumes attached to an instance must be in the same availabilityzone in Cinder as the instance availability zone in Nova.This also means care should be taken when booting an instance from a volumewhere source is not "volume" because Nova will attempt to create a volume usingthe same availability zone as what is assigned to the instance.If that AZ is not in Cinder (or allow_availability_zone_fallback=False incinder.conf), the volume create request will fail and the instance will failthe build request.By default there is no availability zone restriction on volume attach. """), ]
順藤摸瓜,繼續(xù)查看/usr/lib/python2.7/site-packages/nova/virt/block_device.py,發(fā)現(xiàn)如果cross_az_attach為T(mén)rue,則傳給Cinder的availability_zone為空?。?!如果cross_az_attach為False,那么nova會(huì)給Cinder傳遞實(shí)例的availability_zone。
def _get_volume_create_az_value(instance): """Determine az to use when creating a volume Uses the cinder.cross_az_attach config option to determine the availability zone value to use when creating a volume. :param nova.objects.Instance instance: The instance for which the volume will be created and attached. :returns: The availability_zone value to pass to volume_api.create """ # If we"re allowed to attach a volume in any AZ to an instance in any AZ, # then we don"t care what AZ the volume is in so don"t specify anything. if CONF.cinder.cross_az_attach: return None # Else the volume has to be in the same AZ as the instance otherwise we # fail. If the AZ is not in Cinder the volume create will fail. But on the # other hand if the volume AZ and instance AZ don"t match and # cross_az_attach is False, then volume_api.check_attach will fail too, so # we can"t really win. :) # TODO(mriedem): It would be better from a UX perspective if we could do # some validation in the API layer such that if we know we"re going to # specify the AZ when creating the volume and that AZ is not in Cinder, we # could fail the boot from volume request early with a 400 rather than # fail to build the instance on the compute node which results in a # NoValidHost error. return instance.availability_zone
都清楚了,接下來(lái)配置nova.conf文件,在Cinder部分添加參數(shù)
再次創(chuàng)建虛擬機(jī),發(fā)現(xiàn)Nova的AZ和Cinder的AZ對(duì)應(yīng)上啦,解決!
在Cinder中還有個(gè)參數(shù)是allow_availability_zone_fallback,目的是為了創(chuàng)建虛擬機(jī)時(shí)的Nova AZ在Cinder中不存在時(shí)不報(bào)錯(cuò),而是使用Cinder中default_availability_zone或者storage_availability_zone進(jìn)行創(chuàng)建。代碼在/usr/lib/python2.7/site-packages/cinder/volume/flows/api/create_volume.py中
if availability_zone not in self.availability_zones: if CONF.allow_availability_zone_fallback: original_az = availability_zone availability_zone = ( CONF.default_availability_zone or CONF.storage_availability_zone) LOG.warning(_LW("Availability zone "%(s_az)s" " "not found, falling back to " ""%(s_fallback_az)s"."), {"s_az": original_az, "s_fallback_az": availability_zone}) else: msg = _("Availability zone "%(s_az)s" is invalid.") msg = msg % {"s_az": availability_zone} raise exception.InvalidInput(reason=msg)
但是目測(cè)這個(gè)參數(shù)和cross_az_attach有沖突,因?yàn)槭褂胏ross_az_attach的情況下選擇一個(gè)Cinder里沒(méi)有的但是Nova中含有的AZ,創(chuàng)建結(jié)果還是失敗的,終會(huì)以cross_az_attach作為判斷。