Ask Your Question

jbdkz100's profile - activity

2018-12-19 08:16:33 -0600 received badge  Famous Question (source)
2018-12-19 08:16:33 -0600 received badge  Notable Question (source)
2017-06-18 14:56:43 -0600 received badge  Popular Question (source)
2017-06-17 15:58:28 -0600 answered a question Openstack Neutron Instances not getting IP addresses

Resolved, after activating firewalld logging, I found out that the VXLAN upd port 8472 was the problem, I opened the port on both the controller and the compute node, and instances are not getting DHCP leases.

2017-06-17 15:57:18 -0600 answered a question Newton: Instances not getting IP address assigned when Firewall is on.

Resolved, after activating firewalld logging, I found out that the VXLAN upd port 8472 was the problem, I opened the port on both the controller and the compute node, and instances are not getting DHCP leases.

2017-06-14 21:33:52 -0600 asked a question Newton: Instances not getting IP address assigned when Firewall is on.

I have built a test Openstack Environment, identical to the Newton install guide, on virtual servers running CentOS7, I chose networking option 2, self-service network, as explained in the guide (see link):

https://docs.openstack.org/newton/install-guide-rdo/neutron-controller-install-option2.html

My Cirros instances only get assigned a DHCP address when the CentOS7 firewall is disabled on both Controller and Compute.

NICs on both Controller and Compute are in the public zone. I have issued the following commands on both for DHCP, VXLAN ports: firewall-cmd --zone=public --add-port=53/udp --permanent firewall-cmd --zone=public --add-port=67/udp --permanent firewall-cmd --zone=public --add-port=68/udp --permanent firewall-cmd --zone=public --add-port=4789/udp --permanent firewall-cmd --zone=public --add-service=dhcp --permanent firewall-cmd --reload

In addition, I opened up all firewall ports as specified in the following link:

http://docs.openstack.org/newton/config-reference/firewalls-default-ports.html

2017-06-04 05:58:16 -0600 received badge  Taxonomist
2017-01-30 10:05:15 -0600 received badge  Famous Question (source)
2017-01-29 09:53:56 -0600 commented question Openstack Neutron Instances not getting IP addresses

I have already opened up all ports on controller and compute in this Newton firewall guide: http://docs.openstack.org/newton/config-reference/firewalls-default-ports.html

2017-01-29 09:53:08 -0600 commented question Openstack Neutron Instances not getting IP addresses

I have chosen Network Option 2, or self service network in the install guide:

http://docs.openstack.org/newton/install-guide-rdo/overview.html#network2

VXLAN is enabled. Is UDP 4786 the only port I need to open?

2017-01-29 02:31:49 -0600 received badge  Notable Question (source)
2017-01-28 23:50:54 -0600 received badge  Popular Question (source)
2017-01-27 15:23:39 -0600 asked a question Openstack Neutron Instances not getting IP addresses

I have built a test Openstack Environment, identical to the Newton install guide:

http://docs.openstack.org/newton/install-guide-rdo/

My Cirros images only get assigned a DHCP address when the CentOS7 firewall is disabled on both Controller and Compute.

NICs on both Controller and Compute are in the public zone. I have issued the following commands on both for DHCP ports:

firewall-cmd --zone=public --add-port=67/udp --permanent
firewall-cmd --zone=public --add-port=68/udp --permanent
firewall-cmd --reload

In addition, I have also issued the following commands on Controller and Compute:

firewall-cmd --zone=public --add-service=dhcp --permanent
firewall-cmd --reload
2017-01-18 10:00:22 -0600 received badge  Famous Question (source)
2016-12-23 11:03:43 -0600 asked a question Which Linux distro to use?

I want to install Newton in a test environment so as to teach myself about Openstack. I want install Newton on a Linux distro most widely used by a Managed Cloud Providers as I would eventually be seeking employment in this industry.

In searching the Internet, I have found several articles that Openstack is most widely installed on Ubuntu yet through research it looks like Rackspace is running it on RHEL.

Are there certain industries that one Linux distro is used more than another?

2016-11-01 09:43:58 -0600 received badge  Popular Question (source)
2016-11-01 09:43:54 -0600 received badge  Enthusiast
2016-10-30 14:43:51 -0600 asked a question Can't get to management network using Floating IP

I have setup a test environment using the "OpenStack Installation Guide for Red Hat Enterprise Linux and CentOS" for Mitaka.

OpenStack Installation Guide for Red Hat Enterprise Linux and CentOS

I chose Option 2 for networking, which supports attaching instances to self-service networks.

Management Network: 10.0.0.0/24

Provider Network: 192.168.0.0/24

I have create two instances based on the Cirros image. Each Cirros Linux image can ping the other.

I have defined a floating IP address pool using the following commands:

 neutron net-create ext-net --router:external=True Create an external network for the pool.
Neutron subnet-create --allocation-pool start=10.0.0.40,end=10.0.0.50 --gateway 10.0.0.2 --disabled-dhcp est-net 10.0.0.0/24

I have create a router connecting "ext-net" to Local Network 10.0.0.0/24. I chose 192.168.0.1 as the IP address of the Internal Interface.

I have checked out Floating IP 10.0.0.44 and assigned it to a Cirros Linux instance. I am unable to ping anything on the 10.0.0.0/24 network.

Here is the traceroute from the instance with the floating IP:

TraceRoute

2016-10-24 14:18:09 -0600 received badge  Notable Question (source)
2016-10-12 10:11:58 -0600 answered a question Failed to connect to server (code: 1006)

Resolved!

my_ip parameter in /ect/nova/nova.conf on controller node was set to the wrong IP address. It was set to the management IP address of the compute node by mistake. I changed it to the management IP address of the controller node and now it is working.

2016-10-12 10:09:02 -0600 received badge  Popular Question (source)
2016-10-11 15:29:56 -0600 asked a question Failed to connect to server (code: 1006)

I have created an OpenStack test environment based on the Martika release using the following instructions:

http://docs.openstack.org/mitaka/inst...

My test environment has both a management and provider networks, here are the IPs of my single Controller and Compute nodes:

controller Management Network 10.0.0.10 Provider Network 192.168.0.2

compute1 Management Network 10.0.0.11 Provider Network 192.168.0.3

I am able to create an instance but get the "Failed to connect to server (code: 1006) when try to connect to the console of my Cirros based instance.

"controller" resolves to 10.0.0.10 and is in the host file of all servers in the test OpenStack environment. Here are the relevant portions of the /etc/nova/nova.conf file from the compute node:

 [DEFAULT]
...
my_ip = 10.0.0.11

[vnc]
...
vncserver_listen = $my_ip
vncserver_proxyclient_address = $my_ip

[glance]
...
api_servers = http://controller:9292
2016-07-25 14:37:43 -0600 commented answer Internal Server Error (HTTP 500) error during Service Create

Barry, this was a password issue with the Keystone database. It is working for me now.

Thanks for your help!

2016-07-24 07:53:44 -0600 received badge  Famous Question (source)
2016-07-20 09:32:46 -0600 commented answer Internal Server Error (HTTP 500) error during Service Create

At this point, should I be able to start openstack-keystone service using systemctl start openstack-keystore.service I get the following error when I attempt "Job for openstack-keystone.service failed because the control process exited with error code.

2016-07-20 09:30:38 -0600 commented answer Internal Server Error (HTTP 500) error during Service Create

Thanks Barry for your patience. Openstack-Linux was installed as a pre-req. There are no error messages in keystone.log every line is "INFO" migrate.versioning.api" I temp disabled SE Linux using command setenforce 0 this did not resolve the issue.

2016-07-20 07:00:34 -0600 received badge  Notable Question (source)
2016-07-19 23:44:03 -0600 received badge  Student (source)
2016-07-19 21:32:17 -0600 commented answer Internal Server Error (HTTP 500) error during Service Create

/var/log/keystone/keystone.log exists on my controller server. I can examine the contents using VIM. I do not get any permission errors when I type in vim /var/log/keystone/keystone.log as mentioned, I am logged in as root.

2016-07-19 20:40:25 -0600 commented answer Internal Server Error (HTTP 500) error during Service Create

/var/log/keystone/keystone.log does exist on my controller server.

2016-07-19 20:38:11 -0600 received badge  Popular Question (source)
2016-07-19 20:31:35 -0600 commented answer Internal Server Error (HTTP 500) error during Service Create

Thanks Barry, I did as you suggested but have the same issue. The only strange thing is when I ran su -s /bin/sh -c "keystone-manage db_sync" keystone I get the following error on the last line: IOError: [Errno 13] permission denied: '/var/log/keystone/keystone.log' I am logged in as root.

2016-07-19 14:38:19 -0600 asked a question Internal Server Error (HTTP 500) error during Service Create

I am following the OpenStack procedure (below) and am at the service create step.

http://docs.openstack.org/mitaka/install-guide-rdo/keystone-services.html (http://docs.openstack.org/mitaka/inst...)

When I run as root:

openstack service create --name keystone --description "OpenStack Identity" identity

I get the following error:

Internal Server Error (HTTP 500)

When I run ps -aux | grep keystone I see 10 processes.

Thanks,

John