问题标签 [openstack-nova]

有谁知道 nova 在创建快照时将运行实例的临时映像放在哪里？由于某种原因，我一目了然的快照图像保持在 SAVING 模式。

我想在 nova-api 中设置一些变量。

设置它的最佳方法是什么？（在nova.conf或其他文件中？）

我可以在/etc/nova/nova.confapi 中设置并获取该变量的值。但是还有其他方法可以为 API 设置环境变量吗？我想os.environ在脚本中访问。（这是正确的访问方式吗？）

据我所知，wsgi我们必须在 apache 的配置文件中进行设置。但是对于新星我找不到文件:(。

在此先感谢您的帮助。

我安装了openstack。所有服务都运行成功。

之后，我更改HOSTNAME为. 然后重启服务。现在我得到了服务的重复条目。/etc/sysconfig/networkmyhost.mydomain

从这些服务中，旧服务没有运行。

我想删除 host 的服务localhost.localdomain。

我检查了nova-manage service --help但没有删除选项:(。

如果您在 Folsom 中点击获取服务器详细信息的 api，您会注意到实体“地址”。

该实体有一个子元素作为网络名称列表。似乎不可能解组对 Java 对象的 JSON 响应，因为响应似乎不遵循模式，因为网络名称将取决于实现。有解决方法还是我出错了？

我正在尝试将 Hyper-V 中的 nova-compute 与 Ubuntu 12.04 上的 devstack 连接，但出现此错误：

CRITICAL nova [-] (OperationalError) (1054, "Unknown column 'instances.server_name' in 'field list'") 'SELECT instances.created_at AS instances_created_at，instances.updated_at AS instances_updated_at，instances.deleted_at AS instances_deleted_at，instances.deleted AS instance_deleted，instances.id AS instances_id，instances.user_id AS instances_user_id，instances.project_id AS instances_project_id，instances.image_ref AS instances_image_ref，instances.kernel_id AS instances_kernel_id，instances.ramdisk_id AS instances_ramdisk_id，instances.server_name AS instances_server_name，instances.launch_index AS instances_launch_index， instance.key_name AS instances_key_name、instances.key_data AS instances_key_data、instances.power_state AS instances_power_state、instances。vm_state AS instances_vm_state、instances.task_state AS instances_task_state、instances.memory_mb AS instances_memory_mb、instances.vcpus AS instances_vcpus、instances.root_gb AS instances_root_gb、instances.ephemeral_gb AS instances_ephemeral_gb、instances.hostname AS instances_hostname、instances.host AS instances_host、instances.instance_type_id AS instance_instance_type_id、instances.user_data AS instances_user_data、instances.reservation_id AS instances_reservation_id、instances.scheduled_at AS instances_scheduled_at、instances.launched_at AS instances_launched_at、instances.terminated_at AS instances_terminated_at、instances.availability_zone AS instances_availability_zone、instances.display_name AS instances_display_name、instances.display_description AS instances_display_description,实例。launch_on AS instances_launched_on，instances.locked AS instances_locked，instances.os_type AS instances_os_type，instances.architecture AS instances_architecture，instances.vm_mode AS instances_vm_mode，instances.uuid AS instances_uuid，instances.root_device_name AS instances_root_device_name，instances.default_ephemeral_device AS instances_default_ephemeral_device，instances.default_swap_device AS instance_default_swap_device、instances.config_drive AS instances_config_drive、instances.access_ip_v4 AS instances_access_ip_v4、instances.access_ip_v6 AS instances_access_ip_v6、instances.auto_disk_config AS instances_auto_disk_config、instances.progress AS instances_progress、instances.shutdown_terminate AS instances_shutdown_terminate、instances.disable_terminate AS instances_disable_terminate、instance_types_1。created_at AS instance_types_1_created_at, instance_types_1.updated_at AS instance_types_1_updated_at, instance_types_1.deleted_at AS instance_types_1_deleted_at, instance_types_1.deleted AS instance_types_1_deleted, instance_types_1.id AS instance_types_1_id, instance_types_1.name AS instance_types_1_name, instance_types_1.memory_mb AS instance_types_1_memory_mb, instance_types_1.vcpus AS instance_types_1_vcpus, instance_types_1.root_gb AS instance_types_1_root_gb, instance_types_1.ephemeral_gb AS instance_types_1_ephemeral_gb, instance_types_1.flavorid AS instance_types_1_flavorid, instance_types_1.swap AS instance_types_1_swap, instance_types_1.rxtx_factor AS instance_types_1_rxtx_factor, instance_types_1.vcpu_weight AS instance_types_1_vcpu_weight, instance_types_1.disabled AS instance_types_1_disabled,instance_types_1.is_public AS instance_types_1_is_public, instance_info_caches_1.created_at AS instance_info_caches_1_created_at, instance_info_caches_1.updated_at AS instance_info_caches_1_updated_at, instance_info_caches_1.deleted_at AS instance_info_caches_1_deleted_at, instance_info_caches_1.deleted AS instance_info_caches_1_deleted, instance_info_caches_1.id AS instance_info_caches_1_id, instance_info_caches_1.network_info AS instance_info_caches_1_network_info, instance_info_caches_1.instance_uuid AS instance_info_caches_1_instance_uuid, security_groups_1. created_at AS security_groups_1_created_at、security_groups_1.updated_at AS security_groups_1_updated_at、security_groups_1.deleted_at AS security_groups_1_deleted_at、security_groups_1.deleted AS security_groups_1_deleted、security_groups_1。id AS security_groups_1_id, security_groups_1.name AS security_groups_1_name, security_groups_1.description AS security_groups_1_description, security_groups_1.user_id AS security_groups_1_user_id, security_groups_1.project_id AS security_groups_1_project_id, instance_metadata_1.created_at AS instance_metadata_1_created_at, instance_metadata_1.updated_at AS instance_metadata_1_updated_at, instance_metadata_1.deleted_at AS instance_metadata_1_deleted_at, instance_metadata_1.deleted AS instance_metadata_1_deleted, instance_metadata_1.id AS instance_metadata_1_id, instance_metadata_1。instance_metadata_1.created_at AS instance_metadata_1_created_at, instance_metadata_1.updated_at AS instance_metadata_1_updated_at, instance_metadata_1.deleted_at AS instance_metadata_1_deleted_at, instance_metadata_1.deleted AS instance_metadata_1_deleted, instance_metadata_1.id AS instance_metadata_1_id, instance._instance_metadata_1.created_at AS instance_metadata_1_created_at, instance_metadata_1.updated_at AS instance_metadata_1_updated_at, instance_metadata_1.deleted_at AS instance_metadata_1_deleted_at, instance_metadata_1.deleted AS instance_metadata_1_deleted, instance_metadata_1.id AS instance_metadata_1_id, instance._keyAS instance_metadata_1_key, instance_metadata_1.value AS instance_metadata_1_value, instance_metadata_1.instance_uuid AS instance_metadata_1_instance_uuid \nFROM instances LEFT OUTER JOIN instance_types AS instance_types_1 ON instances.instance_type_id = instance_types_1.id LEFT OUTER JOIN instance_info_caches AS instance_info_caches_1 ON instance_info_caches_1.instance_uuid = instances.uuid LEFT OUTER JOIN security_group_instance_association AS security_group_instance_association_1 ON security_group_instance_association_1.instance_uuid = instances.uuid AND instances.deleted = %s 左外连接 security_groups AS security_groups_1 ON security_groups_1.id = security_group_instance_association_1.security_group_id AND security_group_instance_association_1.deleted = %s AND security_groups_1。已删除 = %s 左外连接 instance_metadata AS instance_metadata_1 ON instance_metadata_1.instance_uuid = instances.uuid AND instance_metadata_1.deleted = %s \nWHERE instances.deleted = %s AND instances.host = %s' (0, 0, 0, 0, 0, 'WIN-NVR4BLPKAS1')

我最近正在阅读一些 OpenStack 资料，但还没有机会尝试。我感觉到 Openstack 可以通过 API 或仪表板接口管理大量虚拟机。用户可以轻松创建/启动虚拟机。

然后我很困惑。由于底层计算机硬件可能会有所不同，某些计算机可能只能托管一台虚拟机，有些可能只有十台。当用户启动虚拟机时，是用户手动还是 Openstack 自动指定一台硬件计算机来托管虚拟机？无论哪种情况，如何确定硬件计算机的容量？Openstack是否提供设置硬件计算机容量属性的功能？

我正在处理 OpenStack（Folsom），我想部署 OpenStack 以在不同的
计算节点上工作。是否需要在每个节点上运行 Nova Api 服务？

似乎每个计算节点在我的设备中都需要一个 nova-api 服务，但我认为这没有意义。

据我了解，洞云系统只需要一个 nova-api 服务。

请求 -> nova-api -> nova-schedule 来确定使用哪个节点。

我上传了一张图片到glance，一个vhd格式的Ubuntu服务器12.04，当我尝试用nova boot启动那个图片时，我收到了这个：

那么，可能是什么问题？谢谢！

我正在尝试在 RHEL 6.2 上安装 openstack。按照 openstack.org 的安装指南，我正在使用以下命令：

在解决了许多依赖项后，我得到了最终错误：

我从 RHEL 6.2 DVD 安装了 libvirt 0.9.4，但似乎我必须升级 libvirt 0.9.6。如何进行升级？或者我在哪里可以下载 libvirt 0.9.6 rpm？或者我可以使用 yum 来升级 libvirt 吗？

在nova.conf中，我们需要指定computer_driver为kvm或xen。这是否意味着一个 nova 控制器只能支持一种管理程序技术？我可以在同一个云中混合kvm和虚拟机吗？xen