如何通过 SSH 进入我的 Nova 计算节点

如何通过 SSH 进入我的 Nova 计算节点

我使用 MAAS 和 Landscape 运行 Openstack。我在尝试启动实例时遇到错误,错误:未找到有效主机。可用主机不足。问题。

在尝试排除故障时,我尝试找到 Nova-Compute.log 文件,但我需要先到达那里,而且我似乎无法弄清楚它在哪台 LXD 机器上。

我从运行 conjure-up 的 MAAS 服务器获得:

juju list-machines  
Machine  State    DNS            Inst id              Series  AZ       Message  
0        started  192.168.2.138  te3f68               xenial  default  Deployed  
0/lxd/0  started  192.168.2.139  juju-a150c6-0-lxd-0  xenial           Container   started    
0/lxd/1  started  192.168.2.140  juju-a150c6-0-lxd-1  xenial           Container   started  
0/lxd/2  started  192.168.2.141  juju-a150c6-0-lxd-2  xenial           Container started  
0/lxd/3  started  192.168.2.142  juju-a150c6-0-lxd-3  xenial           Container started  

如果我使用 juju ssh 连接到 0,我最终会进入我的 Juju 控制器,但如果我从那里执行 Juju list machines,它会说 Juju 未安装。似乎
唯一运行 Juju 的机器是 0/lxd/1,但当我使用 Juju list-machines 时,我得到:

juju list-machines  
ERROR No model in focus.  
Please use "juju models" to see models available to you.
You can set current model by running "juju switch"
or specify any other model on the command line using the "-m" flag.*  

但是,在已用 IP 下的 MAAS 子网选项卡下,我可以看到跨 MAAS 节点部署的虚拟机:**我已突出显示 MAAS 服务器。Quiet-Boa 是我使用 Conjure-up 引导到的节点,我假设它是 Juju 控制器,而 trusty-Cicada 是我在 Landscape 中部署到的节点。其余三个节点是 Nova、Ceph 等的安装位置。如何知道什么安装在哪里?弄清楚后如何通过 SSH 连接到节点?**

Used

IP Address  Type    Node    Interface   Usage   Owner   Last seen  
192.168.2.2 Automatic   **new-tuna**    eno1    Machine erniel29    Fri, 04 Aug. 2017 13:03:51  
192.168.2.3 Static  juju-c13c4c-0-lxd-0 eth0    Device  erniel29    Fri, 04 Aug. 2017 13:04:01  
192.168.2.50    Static  MaaS    enp0s25 Rack and region controller  MAAS    Fri, 04 Aug. 2017 10:40:15  
192.168.2.101   Automatic   **fair-dingo**  eno1    Machine erniel29    Fri, 04 Aug. 2017 12:53:55  
192.168.2.103   Static  juju-c13c4c-1-lxd-3 eth0    Device  erniel29    Fri, 04 Aug. 2017 13:14:29   
192.168.2.104   Static  juju-c13c4c-2-lxd-2 eth0    Device  erniel29    Fri, 04 Aug. 2017 13:15:01  
192.168.2.105   Static  juju-c13c4c-0-lxd-5 eth0    Device  erniel29    Fri, 04 Aug. 2017 13:05:45
192.168.2.106   Automatic   **tight-wahoo** eno1    Machine erniel29    Fri, 04 Aug. 2017 13:04:06
192.168.2.107   Static  juju-c13c4c-2-lxd-4 eth0    Device  erniel29    Fri, 04 Aug. 2017 13:13:09
192.168.2.108   Static  juju-c13c4c-0-lxd-3 eth0    Device  erniel29    Fri, 04 Aug. 2017 13:05:10
192.168.2.109   Static  juju-c13c4c-0-lxd-1 eth0    Device  erniel29    Fri, 04 Aug. 2017 13:04:42
192.168.2.110   Static  juju-c13c4c-0-lxd-2 eth0    Device  erniel29    Fri, 04 Aug. 2017 13:04:55
192.168.2.111   Static  juju-c13c4c-1-lxd-0 eth0    Device  erniel29    Fri, 04 Aug. 2017 13:15:03
192.168.2.112   Static  juju-c13c4c-1-lxd-2 eth0    Device  erniel29    Fri, 04 Aug. 2017 13:13:10
192.168.2.113   Static  juju-c13c4c-1-lxd-4 eth0    Device  erniel29    Fri, 04 Aug. 2017 13:14:43
192.168.2.114   Static  juju-c13c4c-2-lxd-0 eth0    Device  erniel29    Fri, 04 Aug. 2017 13:14:30
192.168.2.115   Static  juju-c13c4c-0-lxd-4 eth0    Device  erniel29    Fri, 04 Aug. 2017 13:05:28
192.168.2.116   Static  juju-c13c4c-2-lxd-3 eth0    Device  erniel29    Fri, 04 Aug. 2017 13:15:17
192.168.2.118   Static  juju-c13c4c-2-lxd-1 eth0    Device  erniel29    Fri, 04 Aug. 2017 13:14:46
192.168.2.119   Static  juju-c13c4c-1-lxd-1 eth0    Device  erniel29    Fri, 04 Aug. 2017 13:15:27
192.168.2.137   Automatic   **quiet-boa**   eno1    Machine erniel29    Fri, 04 Aug. 2017 11:45:10
192.168.2.138   Automatic   **trusty-cicada**   eno1    Machine erniel29    Fri, 04 Aug. 2017 11:55:43
192.168.2.139   Static  juju-a150c6-0-lxd-0 eth0    Device  erniel29    Fri, 04 Aug. 2017 12:06:52
192.168.2.140   Static  juju-a150c6-0-lxd-1 eth0    Device  erniel29    Fri, 04 Aug. 2017 12:09:10
192.168.2.141   Static  juju-a150c6-0-lxd-2 eth0    Device  erniel29    Fri, 04 Aug. 2017 12:09:25
192.168.2.142   Static  juju-a150c6-0-lxd-3 eth0    Device  erniel29    Fri, 04 Aug. 2017 12:09:42  
192.168.2.206   Observed        Unknown BMC MAAS    Thu, 03 Aug. 2017 16:28:55  
192.168.2.207   Observed        Unknown BMC MAAS    Thu, 03 Aug. 2017 16:29:23  
192.168.2.208   Observed        Unknown BMC MAAS    Thu, 03 Aug. 2017 16:29:30  
192.168.2.214   Observed        Unknown BMC MAAS    Thu, 03 Aug. 2017 16:28:48  
192.168.2.215   Static

最后,我的主要问题是我不太了解机器之间的关系以及谁控制什么。我一直在 Conjure-up 文档、Juju 文档和 MAAS 文档之间来回查找,但我似乎可以找到整个系统的连贯架构解释。

我希望得到一些帮助来了解如何通过 SSH 进入各种 LXD。

更新:我运行了 Nova s​​ervice-list 并得到:

$ nova service-list  
+----+----------------+---------------------+----------+---------+-------+----------------------------+-----------------+  
| Id | Binary         | Host                | Zone     | Status  | State | Updated_at                 | Disabled Reason |
+----+----------------+---------------------+----------+---------+-------+----------------------------+-----------------+  
| 1  | nova-scheduler | juju-c13c4c-0-lxd-3 | internal | enabled | up    | 2017-08-04T20:00:26.000000 | -               |  
| 2  | nova-cert      | juju-c13c4c-0-lxd-3 | internal | enabled | up    | 2017-08-04T20:00:24.000000 | -               |  
| 3  | nova-conductor | juju-c13c4c-0-lxd-3 | internal | enabled | up    | 2017-08-04T20:00:24.000000 | -               |  
| 11 | nova-compute   | new-tuna            | nova     | enabled | up    | 2017-08-04T20:00:20.000000 | -               |  
| 12 | nova-compute   | tight-wahoo         | nova     | enabled | up    | 2017-08-04T20:00:19.000000 | -               |  
+----+----------------+---------------------+----------+---------+-------+----------------------------+-----------------+  

那么这是否意味着 Nova 计算是在裸机上?此外,我还修复了原始问题,即无有效主机错误。我更换了路由器,这似乎奏效了。但我仍然想知道如何获取所有节点。

相关内容