与生产环境一起创建测试环境

  • 2017年3月22日
  • 9回复
  • 1666年的观点
b
徽章 +2
大家好！

我正在使用AHV，并希望与实际生产环境一起创建我的生产环境的重复。
关键是，我们有一些高度专业的网络软件，需要在实际部署它之前在实际环境中进行测试。
该软件经常进行更新，偶尔更新会造成破坏，需要大量的停机时间和大部分网络的恢复。
因此，我正在寻找的是在AHV中拥有一个受保护的空间，该空间与我们的生产环境相同（但没有与真实网络或Internet的实际互动……只是通过AHV控制台。）

预先感谢您提供的任何帮助！
    \n
    \nI am using AHV and would like to create a duplicate of my production environment alongside the actual production environment.
    \nThe point is that we have some highly specialised network software that needs to be tested as though in the actual environment before we actually deploy it there.
    \nThis software is frequently updated and occasionally an update creates havoc, requiring lots of downtime and restoration of significant portions of the network.
    \nSo what i am looking for is to have a protected space in AHV that thinks and behaves identically to our production environment (but with no actual interaction with the real network or the internet ... just via AHV consoles.)
    \n
    \nThank you in advance for any help you can offer!","quoteUsername":"BermudaJames","translations":{"Common":{"like":"Like","unlike":"Unlike"},"Forum":{"Quote":"Quote","Share":"Share"}}}">

    9回复

    Patrbng
    UserLevel 4
    徽章 +19
    如果我了解您的要求，您正在寻找一种在您的生产AHV群集下嵌套的AHV群集的方法吗？接近它的唯一方法是使用Nutanix CE，但它不会是您的产品环境的镜子，因为它落后于客户AHV周期。但是如果

    我建议也许在一个单独的VLAN上一个小型集群，该集群被防火墙。如果您不需要大量的CPU/存储空间，则可能是1365s的起点。
    \n
    \nI would suggest maybe a small cluster on a seperate vlan that is firewalled away. A 1365S might be a place to start if you don't need a lot of CPU\/Storage.","quoteUsername":"patrbng","translations":{"Common":{"like":"Like","unlike":"Unlike"},"Forum":{"Quote":"Quote","Share":"Share"}}}">
    b
    徽章 +2
    我正在寻找的是如何使用（商业）AHV在我的群集中创建一个单独的环境（容器？）（我们有3个节点和一个小型虚拟网络（仅8个服务器）的NX-1365（我们的NX-1365）。
    这将使我将生产环境的碎片插入“安全空间”，以在生产环境中强化它们之前测试更改。
    我希望该区域中的IP地址和域名与生产环境中的IP地址和域名完全相同，但与生产环境没有任何联系……因此，没有IP冲突等...
    该区域可以访问只要通过控制台。
    \nThis would allow me to clone pieces of my production environment into a 'safe space' for testing changes before implimenting them in the production environment.
    \nI would like the IP addresses and domain names in this area to be exactly the same as they are in the production environment, but have no connection with the production environment ... therefore no IP conflicts etc...
    \nThis area would be accessible only<\/b> via console.","quoteUsername":"BermudaJames","translations":{"Common":{"like":"Like","unlike":"Unlike"},"Forum":{"Quote":"Quote","Share":"Share"}}}">
    Patrbng
    UserLevel 4
    徽章 +19
    我认为将VM克隆并将VM的网络更改为不可用的VLAN将是最简单的。如果每次脚本都应该使其变得非常简单时，则VM是相同的。
    b
    徽章 +2
    我这样做了：
    创建非路由VLAN（192.168.229.x）
    克隆两个服务器
    剥离他们的尼克斯
    在测试VLAN中添加新的NIC
    提供相关地址。
    他们不能互相ping :(

    似乎很简单，但某种程度上不起作用。
    \nCreate non routable VLAN (192.168.229.x)
    \nclone two servers
    \nstrip their NICs
    \nAdd new NIC each in the Test VLAN
    \ngive relevant addresses.
    \nthey cannot ping each other :(
    \n
    \nSeems simple but somehow is not working.","quoteUsername":"BermudaJames","translations":{"Common":{"like":"Like","unlike":"Unlike"},"Forum":{"Quote":"Quote","Share":"Share"}}}">
    Patrbng
    UserLevel 4
    徽章 +19
    是同一主机上的VM'A。VLAN是否在交换机和主机上创建？
    b
    UserLevel 4
    徽章 +17
    百慕大杰这是否意味着您的产品和“安全空间”在同一Nutanix群集上运行？
    BermudaJames<\/a> does it mean both your prod and \"safe space\" run on same Nutanix cluster ?","quoteUsername":"bezeddin","translations":{"Common":{"like":"Like","unlike":"Unlike"},"Forum":{"Quote":"Quote","Share":"Share"}}}">
    b
    徽章 +2
    我们只有一个集群...是的……在与生产环境的独立VLAN上。
    我们的制作是VLAN 0
    测试环境是VLAN 219
    \nOur production is VLAN 0
    \nthe test environment is VLAN 219","quoteUsername":"BermudaJames","translations":{"Common":{"like":"Like","unlike":"Unlike"},"Forum":{"Quote":"Quote","Share":"Share"}}}">
    b
    UserLevel 4
    徽章 +17
    百慕大杰您是否按照patrbng建议配置开关？vlan和port配置
    BermudaJames<\/a> have you configure the switch as per patrbng suggest?vlan and port config","quoteUsername":"bezeddin","translations":{"Common":{"like":"Like","unlike":"Unlike"},"Forum":{"Quote":"Quote","Share":"Share"}}}">
    C
    徽章 +5
    如果您的所有test-vms都活在同一主机上（它们是否适合），这是一个问题吗？如果您可以将它们全部放在同一主机上 - 我会创建一个新的私人开关，将测试vms连接到此私人开关。在Hyper-V上，这是一个允许同一主机上的VM相互交谈，但网络上没有其他任何内容。我认为AHV也有类似的产品。

    在这种情况下，您不必重新拨动，因为流量永远不会离开私人开关。
    \n
    \nIn this case, you don't have to reIP because the traffic never leaves the Private switch.","quoteUsername":"Coleman","translations":{"Common":{"like":"Like","unlike":"Unlike"},"Forum":{"Quote":"Quote","Share":"Share"}}}">

    回复


    Baidu