Ask Your Question

soheil08's profile - activity

2019-08-23 02:51:19 -0600 received badge  Notable Question (source)
2019-08-23 02:51:19 -0600 received badge  Famous Question (source)
2019-08-06 02:43:46 -0600 received badge  Famous Question (source)
2019-05-07 04:11:52 -0600 received badge  Famous Question (source)
2019-02-20 10:17:44 -0600 received badge  Notable Question (source)
2019-02-20 10:00:45 -0600 received badge  Notable Question (source)
2019-02-03 06:04:48 -0600 received badge  Famous Question (source)
2019-01-30 02:29:02 -0600 received badge  Popular Question (source)
2019-01-30 02:29:02 -0600 received badge  Famous Question (source)
2019-01-30 02:29:02 -0600 received badge  Notable Question (source)
2019-01-19 22:30:59 -0600 received badge  Famous Question (source)
2019-01-08 03:08:44 -0600 received badge  Famous Question (source)
2019-01-03 14:19:21 -0600 received badge  Notable Question (source)
2019-01-01 00:15:47 -0600 commented question Setting Firewall on OpenStack nodes

Adding the rules firewall-cmd --permanent --direct --passthrough ipv4 -I FORWARD -i bridge0 -j ACCEPT and firewall-cmd --permanent --direct --passthrough ipv4 -I FORWARD -o bridge0 -j ACCEPT I can ssh to instances using static IP address but the controller became unreachable sometimes.

2018-12-30 09:54:03 -0600 received badge  Popular Question (source)
2018-12-30 07:48:38 -0600 commented question Setting Firewall on OpenStack nodes

I created ports for instances and run them using static IP.

2018-12-29 23:53:17 -0600 commented question Setting Firewall on OpenStack nodes

I mean when firewall of the controller node is off, I can connect to the VMs remotely using SSH (so the security groups work fine), but when I turn the firewall on, I just can ping the VMs and SSH errors No route to host. I guess it's because of the VMs use bridge connection.

2018-12-29 01:36:29 -0600 asked a question Setting Firewall on OpenStack nodes

I tried to configure the firewall for OpenStack Controller and Compute node and here are the rules I added to the firewall:

myZone (active)
  target: default
  icmp-block-inversion: no
  interfaces: enp2s0 enp7s4
  sources: 
  services: ssh dhcpv6-client
  ports: 80/tcp 6080/tcp 11211/tcp 9696/tcp
  protocols: 
  masquerade: no
  forward-ports: 
  source-ports: 
  icmp-blocks: 
  rich rules: 
    rule family="ipv4" source address="192.168.0.32" accept
    rule family="ipv4" source address="192.168.0.31" accept

The address of the Controller and the Compute nodes are 192.168.0.31 and 192.168.0.32, respectively. Using these rules I can use Horizon on the browser and the Compute node services can connect to the Controller nodes ports.

The problem is when the firewall is enabled on the Controller node, instances that are running on the Controller node (I configure the Controller node as the Compute node, too) just can be pinged and all other VMs and nodes (including the Controller node) cannot connect to it (using SSH or any other connection to a specific port). There is no firewall running on instances. I configured an external network to connect VMs to each other CentOS7 is running on all nodes Here are ports listening on the Controller node:

Proto Recv-Q Send-Q Local Address           Foreign Address         State       PID/Program name    
tcp        0      0 0.0.0.0:8775            0.0.0.0:*               LISTEN      4478/python2        
tcp        0      0 0.0.0.0:9191            0.0.0.0:*               LISTEN      4461/python2        
tcp        0      0 0.0.0.0:5000            0.0.0.0:*               LISTEN      10189/httpd         
tcp        0      0 0.0.0.0:8776            0.0.0.0:*               LISTEN      4487/python2        
tcp        0      0 0.0.0.0:25672           0.0.0.0:*               LISTEN      4466/beam.smp       
tcp        0      0 0.0.0.0:8778            0.0.0.0:*               LISTEN      10189/httpd         
tcp        0      0 192.168.0.31:3306       0.0.0.0:*               LISTEN      4860/mysqld         
tcp        0      0 192.168.0.31:2379       0.0.0.0:*               LISTEN      4464/etcd           
tcp        0      0 192.168.0.31:11211      0.0.0.0:*               LISTEN      4457/memcached      
tcp        0      0 127.0.0.1:11211         0.0.0.0:*               LISTEN      4457/memcached      
tcp        0      0 192.168.0.31:5900       0.0.0.0:*               LISTEN      16844/qemu-kvm      
tcp        0      0 0.0.0.0:9292            0.0.0.0:*               LISTEN      4500/python2        
tcp        0      0 192.168.0.31:2380       0.0.0.0:*               LISTEN      4464/etcd           
tcp        0      0 192.168.0.31:5901       0.0.0.0:*               LISTEN      16982/qemu-kvm      
tcp        0      0 192.168.0.31:5902       0.0.0.0:*               LISTEN      17339/qemu-kvm      
tcp        0      0 192.168.0.31:5903       0.0.0.0:*               LISTEN      17621/qemu-kvm      
tcp        0      0 192.168.0.31:5904       0.0.0.0:*               LISTEN      17840/qemu-kvm      
tcp        0      0 0.0.0.0:80              0.0.0.0:*               LISTEN      10189/httpd         
tcp        0      0 0.0.0.0:4369            0.0.0.0:*               LISTEN      1 ...
(more)
2018-12-29 01:33:24 -0600 received badge  Notable Question (source)
2018-12-29 01:33:24 -0600 received badge  Popular Question (source)
2018-12-15 05:17:06 -0600 asked a question OpenStack doesn't apply default configurations anymore

Hi, I have configured an OpenStack 2 nodes cluster. One node acts as the controller and compute node and the other as just compute node. The cluster was working fine until I activated a new NIC interface and add it to the property physical_interface_mappings: physical_interface_mappings = provider:enp2s0,provider1:enp7s4 Since then some services only on the controller node like glance and controller nova services stop to working properly.

It seems the services cannot detect default configuration anymore. For example, the glance error was about Unable to locate paste config file for glance-api and when I set the config_file=/usr/share/glance/glance-api-dist-paste.ini in the file glance-api.conf, it disappeared. This is while before activating the new NIC interface, it worked without any needs to config_file property! On the other hand, the nova-compute service errors about cannot find instances directory and set the property state_path=/var/lib/nova. This is while before activating new NIC interface it used the path /var/lib/nova as state path and it had created directories like instances there! The compute service on the controller node didn't detect the driver and error. I set the property compute_driver=libvirt.LibvirtDriver and it solved.

In addition, most of the services don't write logs on the log file anymore! For example, nova-compute didn't write any log into its log file since I rebooted the controller node! this is while the compute service is up and running on the controller node!

What can be the cause of all new errors and behavior?

2018-12-05 08:10:55 -0600 commented answer neutron warning No controller found for: floatingips

I set web_framework = legacy, but it causes no change and neutron still logs!

2018-12-05 08:00:45 -0600 commented answer neutron warning No controller found for: floatingips

Hi, I checked the neutron.conf and there was no pecan or web_framework on the file. I applied all settings according to the document.

2018-12-05 08:00:45 -0600 received badge  Commentator
2018-12-05 02:04:16 -0600 commented answer nova-compute service start stucks in a loop

See the answer.

2018-12-05 02:03:40 -0600 answered a question nova-compute service start stucks in a loop

In my case, it was because of faulty Rabbitmq. Check the Rabbitmq logs and ensure it works properly.

2018-12-05 02:00:14 -0600 asked a question neutron warning No controller found for: floatingips

Hi,

I configured the OpenStack on two nodes,

  1. controller + network + storage + compute
  2. compute + storage

I started so many VMs on each and the overall working is fine.

The problem is in Neutron server.log it repeatedly writes the following lines:

2018-12-05 11:21:39.060 2214 INFO neutron.wsgi [req-f5aeb723-5653-4edd-9dce-2ddd54b5bf26 539929ca1549436cb4c4171e037e8df7 0a26c316d0d143229f7420cf7fa35bdc - default default] 192.168.0.32 "GET /v2.0/networks?id=a90d7d71-1ff4-4a98-b2b9-68adaea7d1c4 HTTP/1.1" status: 200  len: 877 time: 0.1932352
2018-12-05 11:21:39.067 2214 WARNING neutron.pecan_wsgi.controllers.root [req-21e4a83d-26c7-4eac-86c4-163a7cc2e224 539929ca1549436cb4c4171e037e8df7 0a26c316d0d143229f7420cf7fa35bdc - default default] No controller found for: floatingips - returning response code 404: PecanNotFound
2018-12-05 11:21:39.068 2214 INFO neutron.pecan_wsgi.hooks.translation [req-21e4a83d-26c7-4eac-86c4-163a7cc2e224 539929ca1549436cb4c4171e037e8df7 0a26c316d0d143229f7420cf7fa35bdc - default default] GET failed (client error): The resource could not be found.
2018-12-05 11:21:39.070 2214 INFO neutron.wsgi [req-21e4a83d-26c7-4eac-86c4-163a7cc2e224 539929ca1549436cb4c4171e037e8df7 0a26c316d0d143229f7420cf7fa35bdc - default default] 192.168.0.32 "GET /v2.0/floatingips?fixed_ip_address=192.168.0.210&port_id=69db0b54-c3f1-41a8-bd78-be64333d4444 HTTP/1.1" status: 404  len: 309 time: 0.0071781
2018-12-05 11:21:39.164 2214 INFO neutron.wsgi [req-645f2c12-9e58-4b6e-b0b5-3b682580bbc6 539929ca1549436cb4c4171e037e8df7 0a26c316d0d143229f7420cf7fa35bdc - default default] 192.168.0.32 "GET /v2.0/subnets?id=9771f7f2-12f8-46bd-aca3-f1d26e0b9768 HTTP/1.1" status: 200  len: 835 time: 0.0917201
2018-12-05 11:21:39.259 2214 INFO neutron.wsgi [req-7fcd4b7e-9f52-44af-915c-3cc0618609ee 539929ca1549436cb4c4171e037e8df7 0a26c316d0d143229f7420cf7fa35bdc - default default] 192.168.0.32 "GET /v2.0/ports?network_id=a90d7d71-1ff4-4a98-b2b9-68adaea7d1c4&device_owner=network%3Adhcp HTTP/1.1" status: 200  len: 1085 time: 0.0926280
2018-12-05 11:21:39.456 2214 INFO neutron.wsgi [req-6ec90519-59f9-4a63-ba95-462c19f2442d 539929ca1549436cb4c4171e037e8df7 0a26c316d0d143229f7420cf7fa35bdc - default default] 192.168.0.32 "GET /v2.0/networks/a90d7d71-1ff4-4a98-b2b9-68adaea7d1c4?fields=segments HTTP/1.1" status: 200  len: 212 time: 0.1940138
2018-12-05 11:21:39.654 2214 INFO neutron.wsgi [req-2f085296-16ce-4f5f-8d2c-d40ebfe631f6 539929ca1549436cb4c4171e037e8df7 0a26c316d0d143229f7420cf7fa35bdc - default default] 192.168.0.32 "GET /v2.0/networks/a90d7d71-1ff4-4a98-b2b9-68adaea7d1c4?fields=provider%3Aphysical_network&fields=provider%3Anetwork_type HTTP/1.1" status: 200  len: 281 time: 0.1963122

Actually I created an external Network (according to the documents) and VMs are run using that. The other detail is that I created a port (fixed IP) for each Instance (VMs) and assign it to the instance at initialization.

The main problem is the warning:

2018-12-05 11:21:39.067 2214 WARNING neutron.pecan_wsgi.controllers.root [req-21e4a83d-26c7-4eac-86c4-163a7cc2e224 539929ca1549436cb4c4171e037e8df7 0a26c316d0d143229f7420cf7fa35bdc - default default] No controller found for: floatingips - returning response code 404: PecanNotFound

How can I stop the warning?

2018-11-29 00:19:27 -0600 received badge  Popular Question (source)
2018-11-28 07:18:27 -0600 received badge  Notable Question (source)
2018-11-26 01:47:14 -0600 received badge  Popular Question (source)
2018-11-25 06:43:03 -0600 asked a question nova-compute service start stucks in a loop

Hi,

I'm installing OpenStack on two nodes. One as controller, network and compute, the other just as compute node. According to the document of Rocky, I installed all modules on the controller node and all became verified. At the next step, I configure the compute node and set the configurations according to the document, but when I start the service openstack-nova-compute it just logs:

compute.pps.wams systemd[1]: Starting OpenStack Nova Compute Server...

and it never start!

In the logs of nova-compute it just writes one line:

2018-11-25 15:53:56.730 1246 INFO os_vif [-] Loaded VIF plugins: ovs, linux_bridge, noop

I should tell that I don't config and install Neutron, yet because the documentation suggested installing components according to the list order. What could be the problem?

2018-11-14 09:01:49 -0600 received badge  Notable Question (source)
2018-11-13 04:07:18 -0600 commented answer How to increase the storage of volumes in PackStack

Thanks, I installed the PackStack using the default value. Is it possible to increase the volume's space after installing PackStack?

2018-11-12 10:52:22 -0600 received badge  Popular Question (source)
2018-11-12 05:36:15 -0600 asked a question How to increase the storage of volumes in PackStack

Hi, I installed OpenStack RDO on one node. The size of the root OS was 460GB (as shown in the horizon dashboard). I launched 18 instances with a volume size of 20GB. In the overview part of the dashboard, it shows I used 360GB of volume storage. There is no data in instances (just OS files). But when I try to launch a new instance with the size of 20GB it errors on creating volume. I checked the nova and cinder logs but they didn't contain something special about the error.

Just for a test, I tried to create volumes with the size of 15GB and 10GB and no error happened, so I guess we have a capacity problem. I checked the compute OS storage status, but it has so much capacity! I guess OpenStack configure just a part of the compute disk for volumes and I don't know where OpenStack store them. I only found a path in the /dev/cinder-volumes that contains volume ids but it's just a link!

Note: I found this error on cinder scheduler :

Failed to run task cinder.scheduler.flows.create_volume.ScheduleCreateVolumeTask;volume:create: No valid backend was found

Here is the result of the command vgs:

VG                        #PV #LV #SN Attr   VSize    VFree   
  centos                      1   3   0 wz--n- <464.76g    4.00m
  centos_host-192-168-0-199   1   4   0 wz--n-  <19.00g       0 
  cinder-volumes              1  20   0 wz--n-  <20.60g 1012.00m

How can I increase the storage of cinder volumes?

2018-11-10 07:47:18 -0600 received badge  Popular Question (source)
2018-11-03 06:48:44 -0600 marked best answer Instance volume is not accessible

Hi,

I created a new project with a new use in OpenStack-PackStack. Using dashboard In the new project, I lunch an instance with a source of CentOS ISO file and during lunching instance, I set it to create a new volume for that instance. After creating a new instance, an attached volume for it is visible in the volume tabs of the dashboard. The problem is running the new instance, in the CentOS installation wizard, the is no disk to choose. It means the operation of attaching the volume to instance was not done correctly. But surprisingly in the dashboard, the volume is created and attached to the new instance. I try the command "openstack volume list" and there isn't any volume listed there.

I created a volume using the command line, "openstack volume create --size 10 --availability-zone nova CentOS-Disk" and attached it to the CentOS instance, So then I can choose the disk in CentOS installation. Using this approach the problem is the command-line-created volume is for user "admin" and in the dashboard of the instance's user, I can't see the volume! How can I solve such problem?

2018-11-03 06:12:35 -0600 received badge  Famous Question (source)