Ask Your Question

NileshB's profile - activity

2017-03-08 11:03:15 -0500 received badge  Famous Question (source)
2016-03-24 02:34:10 -0500 received badge  Famous Question (source)
2016-03-21 01:14:15 -0500 received badge  Notable Question (source)
2016-03-21 01:14:15 -0500 received badge  Popular Question (source)
2016-03-21 01:10:34 -0500 received badge  Popular Question (source)
2016-03-21 01:10:34 -0500 received badge  Notable Question (source)
2016-03-03 03:16:16 -0500 asked a question Fuel master UI is not accesible with Mirantis 8.0

Anyone tried with Mirantis 8.0 integration with vmware? I have installed Mirantis-OpenStack-8.0.iso on virtual machine and then configure static ips, ntp, DNS, gateway and other options with "fuelmenu" command.

But when I tried to access fuel master UI with ip address it always gives error "Error:Sript error for: main http://requirejs.org/docs/errors.html#scripterror (http://requirejs.org/docs/errors.html...) "

or page can not displayed.

I have configured two ip addresses on fuel-master one for PXE boot and another for public network.

I have tried following combinations to access fuel-master UI.

https://x.x.x.x:8443 (secure PXE ip address)

http://x.x.x.x:8000 (Normal PXE ip address)

or

https://y.y.y.y:8443 (secure public ip address)

http://y.y.y.y:8000 (Normal public ip address)

Any help would be appreciated.

2016-02-18 14:22:32 -0500 received badge  Famous Question (source)
2016-02-16 22:39:50 -0500 asked a question vmware: How to create vlan id and vlan tag

Hi

I am in process of installing Mirantis Openstack fuel on vSphere. In one Mirantis blog I found below configuration to be done before installation. Mirantis blog link (http://samuraiincloud.com/2014/08/23/openstack-and-vmware-vsphere-integration-with-mirantis-fuel/)

vSphere configuration-

PXE/Storage/Mgmt – VLAN ID: All (4095) / Promiscuous mode: accept

  • Fuel Admin (PXE) network (untagged) – 10.20.0.0/24
  • OpenStack Management network (tagged as VLAN101) – 192.168.100.0/24
  • OpenStack Storage network for Cinder (tagged as VLAN102) – 192.168.110.0/24

I am not good at vSphere networking. I have created port group named 'PXE/Storage/Mgmt' and vlan id as 'All(4095)' (Esxi host -> Configuration -> Networking -> add networking -> create)

I want to know after this configuration how can I create

  • Fuel Admin (PXE) network (untagged)

  • Openstack management network (tagged as VLAN101)

  • Openstack storage network (tagged as VLAN102)

For port group I have already gave tag as 'All(4095)'. How can I assign tag like 'VLAN101' and subnet to same portgroup?

thanks in advance

2016-02-11 00:16:01 -0500 received badge  Famous Question (source)
2016-02-10 03:30:08 -0500 received badge  Notable Question (source)
2016-02-08 13:53:57 -0500 received badge  Popular Question (source)
2016-02-07 08:20:40 -0500 asked a question Unable to install Mirantis Openstack on oracle virtualbox 5.0.14 or 4.3

Hi, I have started using OpenStack and studying Mirantis Openstack. I am using Mirantis quick start to install it on oracle virtual box.

Configuration: 1. Oracle virtual box 5.0.14 and latest extension pack

  1. Ubuntu 14.04

  2. Enabled intel VT from BIOS

  3. Virtual box setting: "Settings -> System -> Acceleration" and enabled "Enable VT-x/AMD-V".

  4. Virtual box setting: Enabled I/O Apic

  5. Follow instruction from Mirantis quick start. Copied Mirantis-Openstack-7.0.iso to "iso" directory

  6. Execute script "launch.sh" as root user.

  7. Every time script execution failed with error "VT-x/AMD-V hardware acceleration is not available on your system. Your 64-bit guest will fail to detect a 64-bit CPU and will not be able to boot."

I have tried same steps on virtual box 4.3 and gets same error. Please let me know if more information to be needed. I'm unable to progress further.

2016-02-07 08:20:40 -0500 received badge  Taxonomist
2016-01-21 22:45:28 -0500 received badge  Famous Question (source)
2016-01-20 00:10:20 -0500 received badge  Popular Question (source)
2016-01-20 00:10:20 -0500 received badge  Notable Question (source)
2016-01-19 05:24:01 -0500 received badge  Student (source)
2016-01-19 02:54:48 -0500 asked a question openstack and vmware integration

Hi

Similar question have been asked on this community but didn't found satisfy answer.

I am currently trying to figure out how to integrate OpenStack with vmware. I am using Openstack Libery and vCenter server 6.0

I don't want to use Vmware Integrated Openstack (VIO) because it comes with vSphere enterprise plus edition.

I have read couple of links but didn't get satisfactory steps to install. I found OpenStack documentation to use KVM/QEMU is best guide but when it comes to use ESXi as hypervisor documented steps are confusing.

For example:

In OpenStack config reference section named "Networking with VMware vSphere" has following contents:

"If you are using the OpenStack Networking Service: Before provisioning VMs, create a port group with the same name as the vmware.integration_bridge value in nova.conf (default is br-int). All VM NICs are attached to this port group for management by the OpenStack Networking plug-in."

Here it is unclear that how to create port-group or how all VM NICs are attached to port-group.

I went through following links for reference:

http://docs.openstack.org/liberty/config-reference/content/vmware.html

http://www.hellovinoth.com/?p=59

Do we have any well structured documentation for integrartion of OpenStack(Liberty) with vmware.

2016-01-19 00:32:33 -0500 received badge  Notable Question (source)
2016-01-18 23:40:45 -0500 received badge  Famous Question (source)
2016-01-18 23:38:54 -0500 answered a question Newly created instance always have status=error and powerstate=nostate because of authentication on compute node

In my case, it was a same problem mentioned in link https://ask.openstack.org/en/question/54526/amqp-server-on-1000115672-is-unreachable/

Add firewall rule to allow keystone and glance ports.

Execute following command on controller node:

-----------------Allow keystone ports on controller node

sudo iptables -A IN_public_allow -p tcp -m tcp --dport 5000 -m conntrack --ctstate NEW -j ACCEPT

sudo iptables -A IN_public_allow -p tcp -m tcp --dport 35357 -m conntrack --ctstate NEW -j ACCEPT

-----------------Allow glance port on controller node

sudo iptables -A IN_public_allow -p tcp -m tcp --dport 9292 -m conntrack --ctstate NEW -j ACCEPT

2016-01-18 06:34:19 -0500 received badge  Popular Question (source)
2016-01-15 04:28:51 -0500 asked a question Newly created instance always have status=error and powerstate=nostate because of authentication on compute node

Hi, I have started OpenStack liberty installation on CentOS7. I have followed each step on installation guide till last step. At each step verified operation successfully. I have two node Controller (with two network interfaces) and Compute (again with two network interfaces) as mentioned in guide.

I have installed Keystone, Nova-compute, Neutron successfully.

When I am creating instance it always created with status=error and powerstate=nostate.

Keystone is issuing token successfully on Controller node. All logs files on Controller don't have any error. Following are error logs on Compute node in "/etc/nova/nova.conf" file.

----------------------------------Error messages

2016-01-14 20:59:47.602 16974 INFO nova.compute.claims [req-7585288c-39a1-4920-913b-23fb4658d1f6 caa811f6476e402aa27bc0c82b738d4b 10a350f60ed7436882b1180aba3237bf - - -] [instance: ed962f0b-2d62-408f-811f-1ffa3195f049] Claim successful

2016-01-14 20:59:47.961 16974 WARNING keystoneclient.auth.identity.generic.base [-] Discovering versions from the identity service failed when creating the password plugin. Attempting to determine version from URL.

2016-01-14 20:59:47.962 16974 ERROR nova.compute.manager [-] Instance failed network setup after 1 attempt(s)

2016-01-14 20:59:47.962 16974 ERROR nova.compute.manager Traceback (most recent call last):

2016-01-14 20:59:47.962 16974 ERROR nova.compute.manager   File "/usr/lib/python2.7/site-packages/nova/compute/manager.py", line 1564, in _allocate_network_async

2016-01-14 20:59:47.962 16974 ERROR nova.compute.manager     dhcp_options=dhcp_options)

2016-01-14 20:59:47.962 16974 ERROR nova.compute.manager   File "/usr/lib/python2.7/site-packages/nova/network/neutronv2/api.py", line 620, in allocate_for_instance

2016-01-14 20:59:47.962 16974 ERROR nova.compute.manager     get_client(context, admin=True))

2016-01-14 20:59:47.962 16974 ERROR nova.compute.manager   File "/usr/lib/python2.7/site-packages/nova/network/neutronv2/api.py", line 237, in get_client

2016-01-14 20:59:47.962 16974 ERROR nova.compute.manager     auth_token = _ADMIN_AUTH.get_token(_SESSION)

2016-01-14 20:59:47.962 16974 ERROR nova.compute.manager   File "/usr/lib/python2.7/site-packages/keystoneclient/auth/identity/base.py", line 200, in get_token

2016-01-14 20:59:47.962 16974 ERROR nova.compute.manager     return self.get_access(session).auth_token

2016-01-14 20:59:47.962 16974 ERROR nova.compute.manager   File "/usr/lib/python2.7/site-packages/keystoneclient/auth/identity/base.py", line 240, in get_access

2016-01-14 20:59:47.962 16974 ERROR nova.compute.manager     self.auth_ref = self.get_auth_ref(session)

2016-01-14 20:59:47.962 16974 ERROR nova.compute.manager   File "/usr/lib/python2.7/site-packages/keystoneclient/auth/identity/generic/base.py", line 184, in get_auth_ref

2016-01-14 20:59:47.962 16974 ERROR nova.compute.manager     self._plugin = self._do_create_plugin(session)

2016-01-14 20:59:47.962 16974 ERROR nova.compute.manager   File "/usr/lib/python2.7/site-packages/keystoneclient/auth/identity/generic/base.py", line 180, in _do_create_plugin

2016-01-14 20:59:47.962 16974 ERROR nova.compute.manager     raise exceptions.DiscoveryFailure(msg)

2016-01-14 20:59:47.962 16974 ERROR nova.compute.manager DiscoveryFailure: Could not determine a suitable URL for the plugin

2016-01-14 20:59:47.962 16974 ERROR nova.compute.manager 

2016-01-14 20:59:48.238 16974 INFO nova.virt.libvirt.driver [req-7585288c-39a1-4920-913b-23fb4658d1f6 caa811f6476e402aa27bc0c82b738d4b 10a350f60ed7436882b1180aba3237bf - - -] [instance ...
(more)
2016-01-08 00:46:48 -0500 received badge  Notable Question (source)
2016-01-08 00:46:48 -0500 received badge  Popular Question (source)
2015-12-30 23:33:29 -0500 received badge  Famous Question (source)
2015-12-29 00:07:12 -0500 received badge  Enthusiast
2015-12-28 11:42:09 -0500 received badge  Notable Question (source)
2015-12-26 17:10:51 -0500 received badge  Popular Question (source)
2015-12-22 03:01:02 -0500 received badge  Supporter (source)
2015-12-22 02:58:15 -0500 received badge  Editor (source)
2015-12-22 02:56:32 -0500 answered a question keystone error on liberty: InternalServerError: An unexpected error prevented the server from fulfilling your request. (HTTP 500)

Hi Prateek thanks for your suggestion.

My problem go solved. Problem is with Openstack documentation.

In steps "Create the service entity and API endpoints" document has commands as follow:

Command-------------------------------

$ openstack endpoint create --region RegionOne identity public http://controller:5000/v2.0

We have configured API version as 3.0 by exporting variable $ export OS_IDENTITY_API_VERSION=3

So I modified command like below:

Modified Command--------------------------------------------

$ openstack endpoint create --region RegionOne identity public http://controller:5000/v3

(I have used IP address instead of controller in my setup as mentioned in original question)

and problem got solved.

Bottom line is modify version as v2.0 -> v3 while creating Identity service API endpoints.

2015-12-21 12:15:12 -0500 asked a question keystone error on liberty: InternalServerError: An unexpected error prevented the server from fulfilling your request. (HTTP 500)

I am installing Openstack Liberty on Ubuntu 14.04 LTS

I followed all steps and stuck at stage "Verify operation"

  1. As per instruction on page I removed "admin_token_auth" token from file "/etc/keystone/keystone-paste.ini" from all three sections.
  2. Then unset environment variable by executing command "unset OS_TOKEN OS_URL"
  3. Database and keystone service is running as I was able to create tenant, users
  4. When I execute following command I am getting "unexpected error HTTP 500 error"

    #openstack --os-auth-url http://controller:35357/v3 --os-project-domain-id default --os-user-domain-id default --os-project-name admin --os-username admin --os-auth-type password token issue

Below is debug output of command:

Command--------------------------

private@private-VirtualBox:~$ openstack --debug --os-auth-url http://10.6.70.26:35357/v3 --os-project-domain-id default --os-user-domain-id default --os-project-name admin --os-username admin --os-auth-type password token issue

Debug output-----------------------

START with options: ['--debug', '--os-auth-url', 'http://10.6.70.26:35357/v3', '--os-project-domain-id', 'default', '--os-user-domain-id', 'default', '--os-project-name', 'admin', '--os-username', 'admin', '--os-auth-type', 'password', 'token', 'issue'] options: Namespace(access_token_endpoint='', auth_type='password', auth_url='http://10.6.70.26:35357/v3', cacert='', client_id='', client_secret='', cloud='', debug=True, default_domain='default', deferred_help=False, domain_id='', domain_name='', endpoint='', identity_provider='', identity_provider_url='', insecure=None, interface='', log_file=None, os_compute_api_version='', os_identity_api_version='3', os_image_api_version='', os_network_api_version='', os_object_api_version='', os_project_id=None, os_project_name=None, os_volume_api_version='', password='Passwd1', project_domain_id='default', project_domain_name='', project_id='', project_name='admin', protocol='', region_name='', scope='', service_provider_endpoint='', timing=False, token='', trust_id='', url='', user_domain_id='default', user_domain_name='', user_id='', username='admin', verbose_level=3, verify=None) defaults: {'auth_type': 'password', 'compute_api_version': '2', 'database_api_version': '1.0', 'api_timeout': None, 'baremetal_api_version': '1', 'cacert': None, 'image_api_use_tasks': False, 'floating_ip_source': 'neutron', 'key': None, 'interface': None, 'network_api_version': '2', 'image_format': 'qcow2', 'object_api_version': '1', 'image_api_version': '1', 'verify': True, 'identity_api_version': '2', 'volume_api_version': '1', 'cert': None, 'secgroup_source': 'neutron', 'dns_api_version': '2', 'disable_vendor_agent': {}} cloud cfg: {'auth_type': 'password', 'compute_api_version': '2', 'database_api_version': '1.0', 'interface': None, 'network_api_version': '2', 'image_format': 'qcow2', 'object_api_version': '1', 'image_api_version': '1', 'verify': True, 'timing': False, 'dns_api_version': '2', 'verbose_level': 3, 'region_name': '', 'api_timeout': None, 'baremetal_api_version': '1', 'auth': {'username': 'admin', 'project_name': 'admin', 'user_domain_id': 'default', 'tenant_name': 'admin', 'auth_url': 'http://10.6.70.26:35357/v3', 'password': 'Passwd1', 'project_domain_id': 'default'}, 'default_domain': 'default', 'image_api_use_tasks': False, 'floating_ip_source': 'neutron', 'key': None, 'cacert': None, 'deferred_help': False, 'identity_api_version': '3', 'volume_api_version': '1', 'cert': None, 'secgroup_source': 'neutron', 'debug': True, 'disable_vendor_agent': {}} compute API version 2, cmd group openstack.compute.v2 network API version 2, cmd group openstack.network.v2 image API version 1, cmd group openstack.image.v1 volume API version 1, cmd group openstack.volume.v1 identity API version 3, cmd group openstack.identity.v3 object_store API version 1, cmd group openstack.object_store.v1 command: token issue -> openstackclient.identity.v3.token.IssueToken Auth plugin password selected auth_type: password Using auth plugin: password Using parameters {'username': 'admin', 'project_name': 'admin', 'auth_url': 'http://10.6.70.26:35357/v3', 'user_domain_id': 'default', 'tenant_name': 'admin', 'password': 'Passwd1', 'project_domain_id': 'default'} Get auth_ref REQ: curl -g -i -X GET http://10.6.70.26:35357/v3 -H "Accept: application/json" -H "User-Agent: python-openstackclient" Starting new HTTP connection (1): 10.6.70.26 "GET /v3 HTTP/1.1" 200 249 RESP: [200] Content-Length: 249 Vary: X-Auth-Token Keep-Alive: timeout=5, max=100 Server: Apache/2.4.7 (Ubuntu) Connection: Keep-Alive Date: Mon, 21 Dec 2015 12:24:41 ... (more)

2015-12-21 12:15:09 -0500 asked a question No handlers could be found for logger "oslo_config.cfg"

I am installing Openstack Liberty by following Openstack guide on Ubuntu 14.04 LTS. I followed all steps, then issue following command for populating identity database.

#su -s /bin/sh -c "keystone-manage db_sync" keystone

      Password: 
      su: Authentication failure

It gives error of authentication failure as there is no 'su' user in ubuntu. Then I tried command with sudo.

#sudo -s /bin/sh -c "keystone-manage db_sync" keystone

     No handlers could be found for logger "oslo_config.cfg"

It gives error like above. I am at beginning of installation so there is no nova or anything else. I have searched through forums most people facing same issue but no answer is there.

If I ignore error and go ahead to create endpoints it gives error like "error 500 when creating identity endpoint"

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

Internal Server Error (HTTP 500)

Followed all the steps, then I got stucked at Add the Identity Service - Install and configure section. Inside Install and configure components section I sent the following command:

 ln -s /etc/apache2/sites-available/wsgi-keystone.conf /etc/apache2/sites-enabled

But then the system says

No handlers could be found for logger "oslo_config.cfg"

What he's talking about ? I am at the beginning of the installation so till now there's no nova, nor anything else, just setting up keystone.

2015-12-21 00:51:21 -0500 received badge  Organizer (source)