novabootfromvolume在多主機zone下的坑-創新互聯
測試環境：3個計算節點，分別屬于3個zone
[root@controller2 ~(keystone_admin)]# nova availability-zone-list
+-----------------------+----------------------------------------+
| Name | Status |
+-----------------------+----------------------------------------+
| internal | available |
| |- controller2 | |
| | |- nova-conductor | enabled :-) 2016-08-20T14:57:07.000000 |
| | |- nova-scheduler | enabled :-) 2016-08-20T14:57:06.000000 |
| | |- nova-consoleauth | enabled :-) 2016-08-20T14:57:08.000000 |
| | |- nova-cert | enabled :-) 2016-08-20T14:57:07.000000 |
| nova | available |
| |- controller3 | |
| | |- nova-compute | enabled :-) 2016-08-20T14:57:04.000000 |
| ag1 | available |
| |- controller1 | |
| | |- nova-compute | enabled :-) 2016-08-19T23:41:45.000000 |
| ag2 | available |
| |- controller2 | |
| | |- nova-compute | enabled :-) 2016-08-20T14:57:06.000000 |
+-----------------------+----------------------------------------+
測試方式： 啟動虛擬機的時候選擇Booting from p_w_picpath(creates a new volume)測試
產生的原因： cinder無法識別nova的多zone，cinder能獲取的zone信息有：
1、cinder-volume所在的zone
2、cinder.conf配置文件中的兩個參數storage_availability_zone = nova和default_availability_zone = nova
大致過下代碼調用過程：(從nova那邊調用cinder那部分開始)
1、nova/virt/block_device.py -> class DriverImageBlockDevice def attach vol = volume_api.create
2、nova/volume/cinder.py -> class API def create item = client.volumes.create
3、cinder/api/v2/volumes.py -> class VolumeController def create new_volume = self.volume_api.create
4、cinder/volume/api.py -> class API def create flow_engine = create_volume.get_flow
在create函數中cinder獲取能獲得到的zone的信息：
raw_zones = self.list_availability_zones(enable_cache=True)
availability_zones = set([az['name'] for az in raw_zones])
if CONF.storage_availability_zone:
availability_zones.add(CONF.storage_availability_zone)
def list_availability_zones services = objects.ServiceList.get_all_by_topic ->
cinder/objects/service.py（def get_all_by_topic） db.service_get_all_by_topic ->
cinder/db/api.py（def service_get_all_by_topic） IMPL.service_get_all_by_topic ->
cinder/db/sqlalchemy/api.py（def service_get_all_by_topic）
@require_admin_context def service_get_all_by_topic(context, topic, disabled=None): query = model_query( context, models.Service, read_deleted="no").\ # models在這里cinder/db/sqlalchemy/models.py filter_by(topic=topic) # topic默認傳過來的是cinder-volume if disabled is not None: query = query.filter_by(disabled=disabled) return query.all()
查詢數據庫找出cinder-volume所在的zone
5、cinder/volume/flows/api/create_volume.py -> def get_flow
# 這里是taskflow，只需關注add方法里面的東東
def get_flow(db_api, p_w_picpath_service_api, availability_zones, create_what,
scheduler_rpcapi=None, volume_rpcapi=None):
"""Constructs and returns the api entrypoint flow.
This flow will do the following:
1. Inject keys & values for dependent tasks.
2. Extracts and validates the input keys & values.
3. Reserves the quota (reverts quota on any failures).
4. Creates the database entry.
5. Commits the quota.
6. Casts to volume manager or scheduler for further processing.
"""
flow_name = ACTION.replace(":", "_") + "_api"
api_flow = linear_flow.Flow(flow_name)
api_flow.add(ExtractVolumeRequestTask(
p_w_picpath_service_api,
availability_zones,
rebind={'size': 'raw_size',
'availability_zone': 'raw_availability_zone',
'volume_type': 'raw_volume_type'}))
api_flow.add(QuotaReserveTask(),
EntryCreateTask(db_api),
QuotaCommitTask())
if scheduler_rpcapi and volume_rpcapi:
# This will cast it out to either the scheduler or volume manager via
# the rpc apis provided.
api_flow.add(VolumeCastTask(scheduler_rpcapi, volume_rpcapi, db_api))
# Now load (but do not run) the flow using the provided initial data.
return taskflow.engines.load(api_flow, store=create_what)我們關心的在class ExtractVolumeRequestTask里
先看下入口execute方法，為什么看execute方法，你翻下taskflow怎么用的，就懂了
def execute(self, context, size, snapshot, p_w_picpath_id, source_volume,
availability_zone, volume_type, metadata, key_manager,
source_replica, consistencygroup, cgsnapshot):
utils.check_exclusive_options(snapshot=snapshot,
p_w_picpathRef=p_w_picpath_id,
source_volume=source_volume)
policy.enforce_action(context, ACTION)
# TODO(harlowja): what guarantee is there that the snapshot or source
# volume will remain available after we do this initial verification??
snapshot_id = self._extract_snapshot(snapshot)
source_volid = self._extract_source_volume(source_volume)
source_replicaid = self._extract_source_replica(source_replica)
size = self._extract_size(size, source_volume, snapshot)
consistencygroup_id = self._extract_consistencygroup(consistencygroup)
cgsnapshot_id = self._extract_cgsnapshot(cgsnapshot)
self._check_p_w_picpath_metadata(context, p_w_picpath_id, size)
availability_zone = self._extract_availability_zone(availability_zone, # 關心的在這里
snapshot,
source_volume)
# _extract_availability_zone函數
def _extract_availability_zone(self, availability_zone, snapshot,
source_volume):
"""Extracts and returns a validated availability zone.
This function will extract the availability zone (if not provided) from
the snapshot or source_volume and then performs a set of validation
checks on the provided or extracted availability zone and then returns
the validated availability zone.
"""
# Try to extract the availability zone from the corresponding snapshot
# or source volume if either is valid so that we can be in the same
# availability zone as the source.
if availability_zone is None:
if snapshot:
try:
availability_zone = snapshot['volume']['availability_zone']
except (TypeError, KeyError):
pass
if source_volume and availability_zone is None:
try:
availability_zone = source_volume['availability_zone']
except (TypeError, KeyError):
pass
if availability_zone is None:
if CONF.default_availability_zone: # default_availability_zone判斷
availability_zone = CONF.default_availability_zone
else:
# For backwards compatibility use the storage_availability_zone
availability_zone = CONF.storage_availability_zone
if availability_zone not in self.availability_zones: # self.availability_zones就是上述cinder-volume的zone外加cinder.conf中兩個配置參數
if CONF.allow_availability_zone_fallback: # 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) # 沒啟動allow_availability_zone_fallback的話，就拋異常了另外有需要云服務器可以了解下創新互聯scvps.cn，海內外云服務器15元起步，三天無理由+7*72小時售后在線，公司持有idc許可證，提供“云服務器、裸金屬服務器、高防服務器、香港服務器、美國服務器、虛擬主機、免備案服務器”等云主機租用服務以及企業上云的綜合解決方案，具有“安全穩定、簡單易用、服務可用性高、性價比高”等特點與優勢，專為企業上云打造定制，能夠滿足用戶豐富、多元化的應用場景需求。
當前文章：novabootfromvolume在多主機zone下的坑-創新互聯
當前鏈接：http://vcdvsql.cn/article10/pjcdo.html
成都網站建設公司_創新互聯，為您提供Google、企業建站、網站制作、網站改版、定制開發、全網營銷推廣
聲明：本網站發布的內容（圖片、視頻和文字）以用戶投稿、用戶轉載內容為主，如果涉及侵權請盡快告知，我們將會在第一時間刪除。文章觀點不代表本網站立場，如需處理請聯系客服。電話：028-86922220；郵箱：631063699@qq.com。內容未經允許不得轉載，或轉載時需注明來源： 創新互聯
- 家具網站建設解決方案分析 2022-05-04
- SEO優化：關于網站優化被黑的解決方案！ 2022-07-08
- 門戶網站解決方案,及與一般企業網站建設差異性 2016-08-05
- 手機微信網站建設解決方案 2023-03-03
- 創新互聯：結合大數據探討品牌零售數字商業解決方案 2022-11-11
- 百度收錄減少收錄下降原因分析及解決方案 2022-05-29
- 政府網站分析及網站建設解決方案 2023-02-21
- crm系統開發 數據挖掘解決方案 2021-05-11
- FTP無法上傳文件的解決方案 2020-04-24
- 網站建設要注意的幾個問題及解決方案 2022-03-19
- 服裝網站設計解決方案 2021-08-22
- 網站建設中門戶網站的解決方案 2020-05-12