openstack的nova.conf

50阅读 0评论2019-10-28 hiyachen
分类:云计算

nova.conf分为控制节点和计算节点:
控制节点:
[DEFAULT]
my_ip = 10.40.25.52
use_neutron = true
firewall_driver = nova.virt.firewall.NoopFirewallDriver
enabled_apis=osapi_compute,metadata
transport_url = rabbit://openstack:loongson@controller1
[api]
auth_strategy = keystone
[api_database]
connection = mysql+pymysql://nova:loongson@controller1/nova_api
[barbican]
[cache]
[cells]
[cinder]
[compute]
[conductor]
[console]
[consoleauth]
[cors]
[database]
connection = mysql+pymysql://nova:loongson@controller1/nova
[devices]
[ephemeral_storage_encryption]
[filter_scheduler]
https://docs.openstack.org/nova/latest/user/filter-scheduler.html

[glance]
api_servers = http://controller1:9292
[guestfs]
[healthcheck]
[hyperv]
[ironic]
[key_manager]
[keystone]
[keystone_authtoken]
auth_url = http://controller1:5000/v3
memcached_servers = controller1:11211
auth_type = password
project_domain_name = default
user_domain_name = default
project_name = service
username = nova
password = loongson
[libvirt]
[matchmaker_redis]
[metrics]
[mks]
[neutron]
url = http://controller1:9696
auth_url = http://controller1:5000/v3
auth_type = password
project_domain_name = default
user_domain_name = default
region_name = RegionOne
project_name = service
username = neutron
password = loongson
service_metadata_proxy = true
metadata_proxy_shared_secret = loongson
[notifications]
[osapi_v21]
[oslo_concurrency]
lock_path = /var/lib/nova/tmp
[oslo_messaging_amqp]
[oslo_messaging_kafka]
[oslo_messaging_notifications]
[oslo_messaging_rabbit]
[oslo_messaging_zmq]
[oslo_middleware]
[oslo_policy]
[pci]
[placement]
region_name = RegionOne
project_domain_name = default
project_name = service
auth_type = password
user_domain_name = default
auth_url = http://controller1:5000/v3
username = placement
password = loongson
[placement_database]
connection = mysql+pymysql://placement:loongson@controller1/placement
[powervm]
[profiler]
[quota]
[rdp]
[remote_debug]
[scheduler]
driver=filter_scheduler 调度驱动有四种,filter_scheduler(缺省),caching_scheduler(不推荐,未来废弃),chance_scheduler(随机调度,不推荐,未来废弃),fake_scheduler(假借的,用于测试)
discover_hosts_in_cells_interval=300  增加计算节点时,刷新时间间隔,负数(-1)时不刷新,即增加节点不能自动加入集群。
max_placement_results=1000 实例放置的位置,只用于filter_scheduler,小于等于可用的物理计算节点数,默认1000,最小1
workers=默认是可用的cpu总数,最小为0
limit_tenants_to_placement_aggregate=false 限制租户到主机聚合中

placement_aggregate_required_for_tenants=False,limit_tenants_to_placement_aggregate=True时该参数起作用
[serial_console]
[service_user]
[spice]
[upgrade_levels]
[vault]
[vendordata_dynamic_auth]
[vmware]
[vnc]
enabled = true
server_listen = $my_ip
server_proxyclient_address = $my_ip
[workarounds]
[wsgi]
[xenserver]
[xvp]
[zvm]
上一篇:关于ssh-loopback地址
下一篇:GlusterFS分布式存储资料