发起问题

Fernando.S 的档案 - activity

2019-02-01 10:57:26 -0500 获得奖牌  热门的问题 (source)
2018-12-13 14:50:55 -0500 获得奖牌  粉丝
2018-11-26 09:53:54 -0500 获得奖牌  受欢迎的问题 (source)
2018-11-20 11:50:49 -0500 问了问题 Host Aggregate Restrictions.

I'm familiar with restricting specific projects to a host aggregate via AggregateMultiTenancyIsolation filter_tenant_id metadata. I'm also aware you can target a host aggregate using aggregate_instance_extra_specs metadata on the flavor. Unfortunately instances/flavors without that aggregate_instance_extra_specs metadata can still land on that aggregate.

Is there a way to restrict all instances from launching on a host aggregate unless specific metadata is within the flavor. I need another method of restricting host aggregates other than by filter_tenant_id

2018-11-07 08:03:52 -0500 获得奖牌  受欢迎的问题 (source)
2018-11-01 10:07:03 -0500 评论问题 filter_tenant_id limit

Going to assume you report at .. https://bugs.launchpad.net/openstack/

2018-10-31 09:15:57 -0500 问了问题 filter_tenant_id limit

I sadly noticed you can assign no more than 7 project IDs per host aggregate via filter_tenant_id= As our environment grows we definitely need to associate/allow more than 7 tenants per specific aggregate.

error

Invalid input for field/attribute filter_tenant_id. Value is too long.

How are people getting around this? Recommended alternate approach to restricting/allowing specific projects to specific host aggregates?

2018-01-13 01:24:40 -0500 评论问题 block-migration is not working from command line

I'm having the exact same issue, using Newton. Live block migration from gui/horizon works fine. When attempted from command line I get the "Live migration can not be used without shared storage.." error. Nova command fails all together. Having to rely on the GUI is unacceptable.