We're currently looking to migrate an old and buggy eucalyptus cloud to openstack. We have ~15 machines that are all on the same office-internal network. The instances get their network configuration from an external (not eucalyptus) DHCP server. We run both linux and windows images. The cloud is used exclusively for platform testing from Jenkins.
我们目前正在寻找将旧的有缺陷的桉树云迁移到openstack。我们有大约15台机器都在同一个办公室内部网络上。实例从外部（非eucalyptus）DHCP服务器获取其网络配置。我们运行linux和windows映像。云专门用于Jenkins的平台测试。
Looking into openstack, it seems that out of the three supported networking modes, none really fit our environment. What we are looking for is something like an "unmanaged mode" where openstack launches an instance that is hooked up to eth0 interface on the instances' compute node and which will receive its network configuration from the external DHCP on boot. I.e. the VM's, guest hosts and clients (jenkins) are all on the same network, managed by an external DHCP server.
展望openstack，似乎在三种支持的网络模式中，没有一种真正适合我们的环境。我们正在寻找的是“非托管模式”，其中openstack启动一个实例，该实例连接到实例计算节点上的eth0接口，并且将在引导时从外部DHCP接收其网络配置。即VM，guest虚拟机主机和客户端（jenkins）都在同一网络上，由外部DHCP服务器管理。
Is a scenario like this possible to set up in OpenStack?
这样的场景可以在OpenStack中设置吗？
1 个解决方案
#1
2
It's not commonly used, but the Networking setup that will fit your needs the best is FlatNetworking (not FlatDHCPNetworking). There isn't stellar documentation on configuring that setup to work through your environment, and some pieces (like the nova-metadata service) may be a bit tricky to manage with it, but that should accomplish allowing you to run an OpenStack cloud with an external DHCP provider.
它并不常用，但最适合您需求的网络设置是FlatNetworking（不是FlatDHCPNetworking）。没有关于配置该设置以在您的环境中工作的一流文档，并且某些部分（如nova-metadata服务）可能有点难以管理它，但这应该允许您运行OpenStack云与外部DHCP提供商。
I wrote up the wiki page http://wiki.openstack.org/UnderstandingFlatNetworking some time ago to explain the setup of the various networks and how they operate with regards to NICs on hosting systems. FlatNetworking is effectively the same as FlatDHCPNetworking except that OpenStack doesn't try and run the DHCP service for you.
我前段时间写了维基页面http://wiki.openstack.org/UnderstandingFlatNetworking来解释各种网络的设置以及它们如何在托管系统上运行。 FlatNetworking实际上与FlatDHCPNetworking相同，只是OpenStack不会尝试为您运行DHCP服务。
Note that with this mode, all the VM instances will be on the same network with your OpenStack infrastructure - there's no separation of networks at all.
请注意，使用此模式，所有VM实例将与您的OpenStack基础架构位于同一网络上 - 根本没有网络分离。
#1
2
It's not commonly used, but the Networking setup that will fit your needs the best is FlatNetworking (not FlatDHCPNetworking). There isn't stellar documentation on configuring that setup to work through your environment, and some pieces (like the nova-metadata service) may be a bit tricky to manage with it, but that should accomplish allowing you to run an OpenStack cloud with an external DHCP provider.
它并不常用，但最适合您需求的网络设置是FlatNetworking（不是FlatDHCPNetworking）。没有关于配置该设置以在您的环境中工作的一流文档，并且某些部分（如nova-metadata服务）可能有点难以管理它，但这应该允许您运行OpenStack云与外部DHCP提供商。
I wrote up the wiki page http://wiki.openstack.org/UnderstandingFlatNetworking some time ago to explain the setup of the various networks and how they operate with regards to NICs on hosting systems. FlatNetworking is effectively the same as FlatDHCPNetworking except that OpenStack doesn't try and run the DHCP service for you.
我前段时间写了维基页面http://wiki.openstack.org/UnderstandingFlatNetworking来解释各种网络的设置以及它们如何在托管系统上运行。 FlatNetworking实际上与FlatDHCPNetworking相同，只是OpenStack不会尝试为您运行DHCP服务。
Note that with this mode, all the VM instances will be on the same network with your OpenStack infrastructure - there's no separation of networks at all.
请注意，使用此模式，所有VM实例将与您的OpenStack基础架构位于同一网络上 - 根本没有网络分离。