Ask Your Question

MustafaArif's profile - activity

2017-10-24 01:14:37 -0500 received badge  Enthusiast
2017-10-17 07:15:01 -0500 answered a question OpenStack inside VM

We have successfully done this kind of setup. It is to be used for POC purpose only

We took help from https://keithtenzer.com/2017/04/20/red-hat-openstack-platform-10-newton-installation-and-configuration-guide/ (link text)

2017-10-17 06:55:15 -0500 answered a question TripleO installation completed, Dashboard is accessible on the same host machine, but not accessible from other computer

In your network-environment.yaml please check what is the IP address you have mentioned for "ControlPlaneDefaultRoute" tag. If it is Director node IP address you will have director node as a gateway and you will not be able to access horizon from outside network. Change it to your network gateway.

2017-10-17 06:53:13 -0500 answered a question Tripleo - Controller : Horizon Web URL is not accessible from outside the provision network

In your network-environment.yaml please check what is the IP address you have mentioned for "ControlPlaneDefaultRoute" tag. If it is Director node IP address you will have director node as a gateway and you will not be able to access horizon from outside network. Change it to your network gateway.

2017-10-17 06:48:14 -0500 received badge  Editor (source)
2017-10-17 06:47:47 -0500 answered a question TripleO introspection failed with timeout.

Possible flow of troubleshooting this problem is

  • Look to the sever console if it is able to get the DHCP IP address from director node if it is not getting please check following things

a. The VLAN which you are using for introspection is native untagged VLAN

b. tcpdump on director node will give you insight if you are getting DHCP request from the node, if yes then director should send the DHCP response

  • It may also happen that your node is able to download the image but is not able to end the introspection data collection, it can get to hang state. This will result in your node not sending introspected data back to director and post default timeout the introspection will fail with timeout error.
2017-10-17 06:39:32 -0500 answered a question PackStack suggest for Production ?

Red Hat OpenStack Platform is the recommended way of doing a production setup if you want to go with Red Hat enterprise subscription.

Packstack is no more supported by Red Hat

2017-10-17 06:33:23 -0500 answered a question cinder unable to attach volume to instances when used nfs driver

Please check if your compute nodes are able to access the nfs share by using showmount -e NFSIP This happens when your compute nodes are not able reach to your nfs share. Possible cause of this issue can be

  1. Firewall preventing the connection
  2. NFS server is not configured correctly
2017-10-17 06:20:56 -0500 commented question error:couldn't find suitable memory target

We faced similar issue in one of our setup and found that the flavor which we were using had only 8MB of RAM allocated to it, which was a typo while creating the flavor.

Post increasing the memory size we were able to launch the VM

2016-08-18 14:01:18 -0500 received badge  Famous Question (source)
2016-04-08 17:52:27 -0500 received badge  Popular Question (source)
2016-04-08 17:52:27 -0500 received badge  Notable Question (source)
2016-03-19 12:34:39 -0500 received badge  Supporter (source)
2016-02-29 10:21:37 -0500 asked a question Openstack installation fails using packstack, failure is in installation of openstack-nova-compute. Error: Dependency Package[nova-compute] has failures
 The solution to this is:

device-mapper *alone* is updated and not together with lvm2.

So first update lvm2
"yum update lvm2"

Then start installation with packstack again

Log msg:

**Error Summary
-------------^[[0m
^[[mNotice: /Stage[main]/Nova/Package[python-greenlet]/ensure: created^[[0m
^[[mNotice: /Stage[main]/Main/File[/etc/nova/ssh/nova_migration_key]/content: content changed '{md5}318eec29b2d8a1eb9c12dd9e3d873622' to '{md5}d35640b68bbe8$
^[[mNotice: /Stage[main]/Nova::Compute/Nova::Generic_service[compute]/Service[nova-compute]: Dependency Package[nova-compute] has failures: true^[[0m
^[[1;31mWarning: /Stage[main]/Nova::Compute/Nova::Generic_service[compute]/Service[nova-compute]: Skipping because of failed dependencies^[[0m
^[[mNotice: /Stage[main]/Nova/Exec[networking-refresh]: Dependency Package[nova-compute] has failures: true^[[0m
^[[1;31mWarning: /Stage[main]/Nova/Exec[networking-refresh]: Skipping because of failed dependencies^[[0m
^[[mNotice: /Stage[main]/Main/Exec[load_kvm]: Dependency Package[nova-compute] has failures: true^[[0m
^[[1;31mWarning: /Stage[main]/Main/Exec[load_kvm]: Skipping because of failed dependencies^[[0m
^[[mNotice: Finished catalog run in 100.63 seconds^[[0m**