Ask Your Question

jenia's profile - activity

2021-01-17 06:02:13 -0600 received badge  Famous Question (source)
2020-09-12 11:10:42 -0600 received badge  Famous Question (source)
2020-09-07 17:06:50 -0600 received badge  Popular Question (source)
2020-09-04 15:35:19 -0600 received badge  Notable Question (source)
2020-09-02 23:52:24 -0600 received badge  Popular Question (source)
2020-09-02 23:34:31 -0600 received badge  Notable Question (source)
2020-09-02 23:24:24 -0600 received badge  Popular Question (source)
2020-09-02 09:00:47 -0600 received badge  Enthusiast
2020-09-01 17:05:44 -0600 asked a question local.conf devstack compute and controller networking

Hello.

I'm going through the multi-node devstack tutorial and the local.conf network setup is a little confusing.

First of all, the HOST_IP is set to [1] 192.168.42.12 on the controller node. But this IP is a worker node in the examples.

Does the HOST_IP point to the worker nodes in the local.conf on the controller node?

[[local|localrc]]
HOST_IP=192.168.42.12 # change this per compute node

Furthermore, the netmask for the FLOATING_RANGE is 192.168.42.128/25 which gives the following ranges:

HostMin:   192.168.42.129       11000000.10101000.01111010.1 0000001
HostMax:   192.168.42.254       11000000.10101000.01111010.1 1111110

But the IPs of the workers nodes in the example are 192.168.42.11 which is outside of the range.

Thirdly, does the HOST_IP in the controller nodes point to the IP of the controller itself setup [2] as in

#local.conf:
[[local|localrc]]
HOST_IP=192.168.42.11

#/etc/network/interfaces:
auto eth0
iface eth0 inet static
    address 192.168.42.11
    netmask 255.255.255.0
    gateway 192.168.42.1

And finally, what is the purpose of the FIXED_RANGE=10.4.128.0/20?

P.S. Hyperlinks cannot be set in this GUI so I left the numbered references at the bottom like in a book

[1] https://docs.openstack.org/devstack/latest/guides/multinode-lab.html#configure-compute-nodes (https://docs.openstack.org/devstack/l...)

[2] https://docs.openstack.org/devstack/latest/guides/multinode-lab.html#network-configuration (https://docs.openstack.org/devstack/l...)

2020-08-30 21:19:19 -0600 answered a question Centos 8 Stream minimal, "broute incompatible, use nft"

I looked at the file called `worlddump.py and removed broute from it. So far, looks like it works

2020-08-30 14:26:52 -0600 asked a question Centos 8 Stream minimal, "broute incompatible, use nft"

Hello.

I'm going through the devstack tutorial and I have install the Centos 8 Stream minimal OS on my VM on which I want to https://docs.openstack.org/devstack/latest/guides/single-machine.html (install) OpenStack.

However, I get this error when I run the stack.sh script:

/bin/python3.6/opt/stack/devstack/tools/worlddump.py -d /opt/stack/logs/ebtables v1.8.4 (nf_tables): table broute is incompatible, use nft tool.

I tried starting the nftables daemon:

systemctl start nftables
systemctl enable nftables

Ran the script again and I get the same error.

Can someone please suggest a solution to this problem?

I'm using Centos-8 Steam and I selected the minimal install option from the https://mirrors.edge.kernel.org/centos/8-stream/isos/x86_64/ (CentOS-Stream-8-x86_64-20200827-boot.iso) .

2020-08-30 14:19:33 -0600 received badge  Scholar (source)
2020-08-30 12:16:23 -0600 received badge  Supporter (source)
2020-08-29 12:17:42 -0600 received badge  Editor (source)
2020-08-29 12:16:41 -0600 asked a question Multi-Node Lab tutorial

I'm going through OpenStack https://docs.openstack.org/devstack/latest/guides/multinode-lab.html (tutorial)

In the subsection "Set Up Ssh" it says "Set up the stack user on each node with an ssh key for access". Do I need to spawn up the worker nodes (VMs) myself rather than using the cluster controller to spin up the worker nodes?

If I need to spin up the workers nodes myself, I suppose I need to give them the following IPs (for example):

auto eth0 iface eth0 inet static
    address 192.168.42.129
    netmask 255.255.255.0
    gateway 192.168.42.1

and

auto eth0 iface eth0 inet static
    address 192.168.42.130
    netmask 255.255.255.0
    gateway 192.168.42.1

Furthermore, what is the role of the gateway?

It's like a jump node or something?

2020-06-27 20:28:06 -0600 answered a question Cannot boot centos image

I figured it out :)

The CentOS-7-x86_64-GenericCloud.qcow2 is a virtual machine rather than a bootable kernel.

I got confused and instead of importing that file into Virtual Machine Managed as an existing VM, I was importing it as a kind of bootable kernel (is if it were an ISO image of the kernel).

2020-06-27 20:09:10 -0600 received badge  Famous Question (source)
2020-06-27 20:09:10 -0600 received badge  Famous Question (source)
2020-06-07 08:08:49 -0600 commented question Cannot boot centos image

@Bernd Bausch ok. I downloaded (and extracted the raw file) CentOS-7-x86_64-GenericCloud.raw.tar.gz. Still. Exact same issue. I don't understand what the problem may be.

2020-06-07 00:50:28 -0600 received badge  Popular Question (source)
2020-06-07 00:50:28 -0600 received badge  Notable Question (source)
2020-06-06 19:50:00 -0600 commented question Cannot boot centos image

Definitely not. I didn't realize that it's for a different CPU than the regular X86. i just took the smallest/most-up-to-date image that was on the list. Thanks for the tip!!

2020-06-06 18:12:20 -0600 asked a question Cannot boot centos image

Hello

I'm going through the OpenStack https://docs.openstack.org/install-guide/overview.html#example-architecture (installation guide) and I want to create the Controller Node.

Therefore I created a VM using QEMU and I wanted to boot in CentsOS using this image CentOS-7-ppc64le-GenericCloud.qcow2.xz from http://cloud.centos.org/centos/7/images/ (offical OpenStack image list):

But I get "No bootable device" https://drive.google.com/file/d/1cp5xgxuLL00CQ-3XHS8T3h19-tlgL7OF/view?usp=sharing (error).

Why? I'm not getting it. I thought I needed to boot the OS from the image CentOS-7-ppc64le-GenericCloud.qcow2.xz and install the components there that make it into the controller node