Openstack Multi-region deployment - openstack

I've been trying to deploy Openstack on a multi region setup, with two nodes, one for RegionOne and one for RegionTwo, with the Horizon and Keystone services shared (they both are hosted in RegionOne).
I'm using Ubuntu server Bionic on virtualbox, and devstack for the Openstack config.
Now here's my problem: I've followed the documentation but the configuration for the second region fails, and even though I have the drop down menu to choose between the two regions when I point to the second one I receive the "Unable to retrieve limits information" error.
Following the two localrc files and the images of the errors.
[ Localrc for RegionOne ]
DATABASE_PASSWORD=password
ADMIN_PASSWORD=password
SERVICE_PASSWORD=password
SERVICE_TOKEN=password
RABBIT_PASSWORD=password
SWIFT_REPLICAS=1
SWIFT_HASH=011688b44136573e209e
LOGFILE=/opt/stack/logs/stack.sh.log
LOG_COLOR=True
REGION_NAME=RegionOne
[ Localrc for RegionTwo ]
DATABASE_PASSWORD=password
ADMIN_PASSWORD=password
SERVICE_PASSWORD=password
SERVICE_TOKEN=password
RABBIT_PASSWORD=password
SWIFT_REPLICAS=1
SWIFT_HASH=011688b44136573e209e
LOGFILE=/opt/stack/logs/stack.sh.log
LOG_COLOR=True
disable_service horizon
KEYSTONE_SERVICE_HOST=<KEYSTONE_IP_ADDRESS_FROM_REGION_ONE>
KEYSTONE_AUTH_HOST=<KEYSTONE_IP_ADDRESS_FROM_REGION_ONE>
REGION_NAME=RegionTwo
KEYSTONE_REGION_NAME=RegionOne
THIS is the error I get from RegionTwo
THIS is what I see when I try to access the Horizon dashboard
I tried using different net configurations (nat, host only, hybrid, bridged) and vm dimensions but I really cannot figure out what's wrong. Any help is appreciated.

Related

Why some openstack instances use the commands 'openstack server list|grep [ip]' or 'nova list|grep [ip]' can not be found

Why are some openstack instances found in the "dashboard" and viewed using the command 'nova list --ip [ip]', but not found using the command 'openstack server list|grep [ip]', 'nova list|grep [ip]'?
It is hard to say for sure what the cause of your problem is from the information you provided.
However, nova list and openstack server list both default to listing instances for the current project only. To list instances for all projects, you need to include the --all-tenants or --all-projects option respectively.
Refer to the Nova list command command to select parameter parameters:
--limit
Maximum number of servers to display. If limit == -1, all servers will be displayed. If limit is bigger than 'CONF.api.max_limit' option of Nova API, limit 'CONF.api.max_limit' will be used instead.

plumberDeploy::do_provision() - Error: Size is not available in this region

I am trying to provision droplet on DigitalOcean with plumberDeploy R package.
I am running:
mydrop <- plumberDeploy::do_provision()
And getting back:
THIS ACTION COSTS YOU MONEY!
Provisioning a new server for which you will get a bill from DigitalOcean.
Using default ssh keys: work_R_laptop
Error: Size is not available in this region.
Any ideas how to troubleshoot?
it may not be a solution for the size issue, but you can specify the droplet-id or hostname as a paramter, so I can suggest that you manually create the droplet from DigitalOcean access panel and the run:
id <- plumberDeploy::do_provision("your droplet hostname", example=FALSE).
Then it should run the setup for the given droplet as expected.

openstack network create command gives "The Keystone service is temporarily unavailable" and "The server is currently unavailable"

Currently, we are trying to setup neutron for our cloud server. Since everyone is new to this, we are struggling a bit. When we entered this command:
openstack network create --share --external \
--provider-physical-network provider \
--provider-network-type flat provider
And it throws this error:
Error while executing command: HttpException: 503, The Keystone service is temporarily unavailable.: 503 Service Unavailable: The server is currently unavailable. Please try again at a later time.
We are following openstack docs guide to a T.
Does anyone know what causes this error and how to fix it?
Thanks.
I fixed it, it was a problem with MariaDB. When we updated it from 10.1 to 10.3, I couldn't access my DB, so when I fixed that error it works now.

Keystone error 401 output to every command/Keystone don't know Default Openstack Domain

I am currently trying to install Openstack for the first time.
I followed the installation guide given by Openstack (here)
The basic setup is done , and I am now trying to install the four "basic" services of Openstack : Keystone, Glance , Nova and Neutron.
But I have an error with Keystone , I followed the tutorial , but when I am trying to test Keystone , by launching even the simplest command (openstack role create myrole for example)
I have the following message
The request you have made requires authentication. (HTTP 401) (Request-ID: req-e9164787-381f-4f69-af7f-7ea4932c3a0b)
You can find here all the command I previously entered here , here is the command openstack domain list --debug output and here the Keystone.log
As you can see in the keystone.log , I have the message
2019-01-16 20:45:53.064 7056 WARNING keystone.auth.core [req-fd1b7466-cf24-406f-82ce-2549156ae4d6 - - - - -] Could not find domain: default.: DomainNotFound: Could not find domain: default.
It seems that Keystone do not know the Default Domain , how can I change that.
I have already tried "Default" and "default' (with and without the lower-case) , but no change.
I cannot even create another domain , or create a Token (I read on other thread that it might be the problem source)
Let me know if you need anything more , and thanks in advance !

Error on configuring Devstack compute nodes: Service n-net is not running

While installing Devstack on a compute node in a multi-node devstack lab environment error encountered: Service n-net is not running.
The local.conf file has localrc as:
HOST_IP=192.168.42.12 # change this per compute node
FLAT_INTERFACE=eth0
FIXED_RANGE=10.4.128.0/20
FIXED_NETWORK_SIZE=4096
FLOATING_RANGE=192.168.42.128/25
MULTI_HOST=1
LOGFILE=/opt/stack/logs/stack.sh.log
ADMIN_PASSWORD=labstack
DATABASE_PASSWORD=supersecret
RABBIT_PASSWORD=supersecret
SERVICE_PASSWORD=supersecret
DATABASE_TYPE=mysql
SERVICE_HOST=192.168.42.11
MYSQL_HOST=$SERVICE_HOST
RABBIT_HOST=$SERVICE_HOST
GLANCE_HOSTPORT=$SERVICE_HOST:9292
ENABLED_SERVICES=n-cpu,n-net,n-api-meta,c-vol
NOVA_VNC_ENABLED=True
NOVNCPROXY_URL="http://$SERVICE_HOST:6080/vnc_auto.html"
VNCSERVER_LISTEN=$HOST_IP
VNCSERVER_PROXYCLIENT_ADDRESS=$VNCSERVER_LISTEN
Please help me removing this error.
P.S: I must use nova-net and not neutron for interaction between the controller and the compute nodes.
For the Ocata release I founded a solution (2-node setup). An import part is the placement-api since the Newton update (14.0.0), so first of all enable this in all your nodes:
local.conf:
enable_service placement-api
First run ./stack.sh on your controller node and after that installation run it on the other nodes.
Also here you will see the error Service n-net is not running...
Now edit your nova.conf file in /etc/nova/nova.conf because there will be no database and database_api section:
[database]
connection=mysql+pymysql://root:DB_PASS#IP_OF_CONTROLLER_NODE/nova
[api_database]
connection=mysql+pymysql://root:DB_PASS#IP_OF_CONTROLLER_NODE/nova_api
When adding these, you can check if it works with following command:
stack#jerico-02:/devstack$ nova-manage --debug host list
host zone
0.0.0.0 internal
jerico-03 internal
jerico-02 nova
Also in the dashboard the new compute (hypervisor) shows up!
Hope it helps!
(Tested on Ubuntu Server 16.04 LTS with devstack and OpenStack Ocata)

Resources