openstack seems to start services on host ip not "virtual ip"

Bug #1921013 reported by Simon J Mudd
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
MicroStack
New
Undecided
Unassigned

Bug Description

feedback for:

$ sudo snap list microstack
Name Version Rev Tracking Publisher Notes
microstack ussuri 222 latest/beta canonical✓ devmode

my private ip is 192.168.X.Y
my username: myuser
my hostname: myhost

myuser@myhost:~$ sudo microstack init --auto --control
2021-03-23 22:37:55,693 - microstack_init - INFO - Configuring clustering ...
2021-03-23 22:37:55,761 - microstack_init - INFO - Setting up as a control node.
2021-03-23 22:37:58,456 - microstack_init - INFO - Configuring networking ...
2021-03-23 22:38:04,967 - microstack_init - INFO - Opening horizon dashboard up to *
2021-03-23 22:38:05,871 - microstack_init - INFO - Waiting for RabbitMQ to start ...
Waiting for 192.168.X.Y:5672
2021-03-23 22:38:11,455 - microstack_init - INFO - RabbitMQ started!
2021-03-23 22:38:11,455 - microstack_init - INFO - Configuring RabbitMQ ...
2021-03-23 22:38:12,498 - microstack_init - INFO - RabbitMQ Configured!
2021-03-23 22:38:12,515 - microstack_init - INFO - Waiting for MySQL server to start ...
Waiting for 192.168.X.Y:3306
2021-03-23 22:38:19,137 - microstack_init - INFO - Mysql server started! Creating databases ...
2021-03-23 22:38:21,050 - microstack_init - INFO - Configuring Keystone Fernet Keys ...
2021-03-23 22:38:36,291 - microstack_init - INFO - Bootstrapping Keystone ...
2021-03-23 22:38:45,007 - microstack_init - INFO - Creating service project ...
2021-03-23 22:38:50,778 - microstack_init - INFO - Keystone configured!
2021-03-23 22:38:50,803 - microstack_init - INFO - Configuring the Placement service...
2021-03-23 22:39:11,581 - microstack_init - INFO - Running Placement DB migrations...
2021-03-23 22:39:15,354 - microstack_init - INFO - Configuring nova control plane services ...
2021-03-23 22:39:27,208 - microstack_init - INFO - Running Nova API DB migrations (this may take a lot of time)...
2021-03-23 22:39:52,106 - microstack_init - INFO - Running Nova DB migrations (this may take a lot of time)...
Waiting for 192.168.X.Y:8774
2021-03-23 22:40:48,171 - microstack_init - INFO - Creating default flavors...
2021-03-23 22:41:14,633 - microstack_init - INFO - Configuring nova compute hypervisor ...
2021-03-23 22:41:16,394 - microstack_init - INFO - Configuring the Spice HTML5 console service...
2021-03-23 22:41:17,033 - microstack_init - INFO - Configuring Neutron
Waiting for 192.168.X.Y:9696
2021-03-23 22:42:46,745 - microstack_init - INFO - Configuring Glance ...
Waiting for 192.168.X.Y:9292
2021-03-23 22:43:26,235 - microstack_init - INFO - Adding cirros image ...
2021-03-23 22:43:29,380 - microstack_init - INFO - Creating security group rules ...
2021-03-23 22:43:39,681 - microstack_init - INFO - Configuring the Cinder services...
2021-03-23 22:44:40,310 - microstack_init - INFO - Running Cinder DB migrations...
2021-03-23 22:44:52,283 - microstack_init - INFO - restarting libvirt and virtlogd ...
2021-03-23 22:44:59,761 - microstack_init - INFO - Complete. Marked microstack as initialized!

If openstack is intended to run on a different ip 10.20.20.1 then why do you bind the services to the host's primary ip?

Should you not check if there are already processes bound to those ports? (e.g. mysql might be already present) from an existing install?

How do you access port 8080 remotely? Using something like ssh -L8080:10.20.20.1:8080 myhost ?
It would be good to have suggestions on how to do this?

No status command. It would be good to have this to validate that the default settings and processes are running as expected. e.g. mimic microk8s.status behaviour and provide a sudo microstack status command.

It would be convenient perhaps if an existing mysql installation is present to be able to provide instructions on how to use that rather than running another mysql instance on the server.

I see nothing listening on :8080 so need to poke around and try and figure out what's going on.
Thanks for spending the time to do this as microk8s is really good for learning and while I tested devstack it took a very long time to build and deploy so the snap offering looks much better.

Tags: feedback
Revision history for this message
Simon J Mudd (sjmudd) wrote :

I missed this is running on:

$ lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description: Ubuntu 20.04.2 LTS
Release: 20.04
Codename: focal

tags: added: feedback
Revision history for this message
Simon J Mudd (sjmudd) wrote :

This potentially looks like a bug:

root@myhost:/var/snap/microstack/current/snap-openstack# ls -l
total 1
-rw-r--r-- 1 root root 0 Mar 23 20:35 setup.lock
root@mad19:/var/snap/microstack/current/snap-openstack# at setup.lock

Command 'at' not found, but can be installed with:

apt install at

root@myhost:/var/snap/microstack/current/snap-openstack

Clearly I don't use `at` much and so did not have it installed.

Revision history for this message
Simon J Mudd (sjmudd) wrote :

With microk8s I can do microk8s stop and then restart with microk8s start.
I see it would be good to have a similar command for microstack.

Revision history for this message
Simon J Mudd (sjmudd) wrote :

I misread the port to listen on and openstack did come up.

The instructions suggest using the command line to do catalog list but that doesn't seem to work as requires authentication and I must have missed how to set that up so got:

myuser@myhost:~$ sudo microstack.openstack catalog list
The request you have made requires authentication. (HTTP 401) (Request-ID: req-e8023950-828c-4b79-9b55-3365939875fb)

Clearly some of this is user error, but there seem to be a few things I see that are not expected.

Revision history for this message
Simon J Mudd (sjmudd) wrote :

For routing to the internal network I installed openfrr+ospf and then I could reach the 10.20.20.1 address directly from a remote server. If routing is configured this address is reachable.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.