Ask Your Question

amotoki's profile - activity

2017-08-31 10:01:44 -0600 commented answer Error: No available formula with the name "openstacksdk"

formula is a terminology used in brew. Did you really run "pip install openstacksdk"? It looks better to check your command line again.

2017-08-31 09:58:58 -0600 commented answer Error: No available formula with the name "openstacksdk"

https://stackoverflow.com/questions/3... might help you, but I would suggest to check what happens carefully when doing it (especially if use pip install --ignore-installed six).

2017-08-31 09:57:13 -0600 answered a question Error: No available formula with the name "openstacksdk"

This is not a problem specific to openstacksdk. This is caused due to MacOSX file permission. The easiest solution would be to use virtualenv. If you really want to install it to your MacOSX environment globally, it is better to search information around 'six' and MacOSX.

2017-08-20 07:32:25 -0600 answered a question Unable to login to horizon

I am not sure what "ubuntu 16.04 guide for openstack newton" suggests, but it seems you try to run keystone and horizon on a single apache httpd server. If so, horizon and keystone access needs to be distinguishable.

Looking at /etc/openstack-dashboard/local_settings.py.bak, "WEBROOT" is "/". I think you need to locate the horizon URL under /dashboard (for example). To do this, "WEBROOT" needs to be "/dashboard/" and you also need to set WSGIScriptAlias appropriately like "WSGIScriptAlias /dashboard /opt/stack/horizon/openstack_dashboard/wsgi/django.wsgi" (this is quoted from devstack, so the patch will be different)

2017-08-20 07:09:59 -0600 answered a question Adding rule to a security group using Horizon fails

See https://ask.openstack.org/en/question... for the current progress.

2017-08-20 07:05:02 -0600 answered a question unable to add rules to security group from horizon dashboard

Are you using Pike version of horizon? If so, this is being tracked in the following bugs. It will be fixed soon in Pike RC2 horizon. https://bugs.launchpad.net/horizon/+b... https://bugs.launchpad.net/horizon/+b...

2016-11-24 02:24:12 -0600 received badge  Enlightened (source)
2016-11-24 02:24:12 -0600 received badge  Good Answer (source)
2016-07-05 09:43:05 -0600 answered a question horizon dashboard issue downloading large files from swift

Horizon bug on this is https://bugs.launchpad.net/horizon/+b.... It is not a design. It is a bug. Django StreamingHttpRequest should be used for such a large request instead of HttpRequest. It was fixed in Kilo or later in Horizon.

2014-07-12 10:19:49 -0600 received badge  Nice Answer (source)
2014-04-05 12:07:28 -0600 received badge  Teacher (source)
2014-04-04 14:42:58 -0600 received badge  Editor (source)
2014-04-04 14:41:10 -0600 answered a question ODL: unable to launch VM in devstack

After merging the patch, there was a change in an interaction between nova and neutron: "event notification", and I think it affects VM launching with ODL mechanism driver. The bug is reported in https://bugs.launchpad.net/neutron/+bug/1301449 and we have a fix for this in https://review.openstack.org/#/c/85176/ . Could you try it? The fix will be released in Neutron RC2.

2013-11-02 09:32:54 -0600 answered a question failed to create network by dashboard

OpenStack Dashboard is expected to use keystone-enabled OpenStack. When creating a network, Dashboard passes keystone token to Neutron and Neutron retrieves tenant_id or other information such as roles from Keystone based on the passed token.

I believe yong's suggestion will address your problem. It seems you already enable keystone because you succeed to login Dashboard, but it seems neutron is not configured to use keystone.

2013-07-29 11:18:18 -0600 answered a question Instance is not getting a static IP

The reason that eth1 is not getting an IP is because DHCP is disable for subnet2.

"port-create" assigned an IP address for the quantum port at the database level. This means the port has a right to use the assigned IP address.

The same thing applied to Dashboard. Dashboard show what IP addresses are assigned at the database on Quantum (or Nova). It does not check if the IP address is configured inside VMs.

2013-03-25 08:44:01 -0600 answered a question dhcp-agent and create_port question.

I agree that it would be better that device_id of DHCP server port should be more meaningful (i.e., use agent id as uuidX in dhcp<uuidx>-<network_id>). We need to take care of dhcp-agent or l3-agent without state report.

For your purpose, if you know the host name where dhcp-agent is running, you can identify a network node by combining results of the following commands: (a) quantum agent-list -- and quantum dhcp-agent-list-hosting-net <network-id>. (though it is not a smart way i think).

2013-01-28 07:34:31 -0600 answered a question Why does OVS agent creates three "qbr..." interfaces every time that a VM is created?

Nova's LibvirtHybridOVSBridgeDriver (which is recommended to use by default) creates an additional bridge and related interfacces per tap interface.

The reason to create the bridge is to make Nova'security group work. Security group implementation is based on iptables, but iptables rules are not applied when packets are forwarded on OVS bridges. Thus we prepare an extra bridge per VIF to apply iptables rules and ensure security group works.

2012-11-07 18:16:42 -0600 answered a question Can't access Quantum services via REST requests

"id" returned by token-get should be passed as X-Auth-Token in REST call.

In my last command line, "X-Auth-Token: dcf3d36161154f9faedcec7d16cc01ff" should be "X-Auth-Token: f21fb6ffde104696ad5a3c854391ce75".

I did a mistake when I prepared the command lines to paste them. I reused the previous command line without updating the token. The previous token "dcf3d36161154f9faedcec7d16cc01ff" is also valid in this case.

2012-11-07 07:29:18 -0600 answered a question Can't access Quantum services via REST requests

If your quantum server is configured to use keystone auth (it is default in Folsom), you need to fetch a valid token from keystone before accesing quantum server.

Command lines are here when I tested: http://paste.openstack.org/show/24745/

I hope it will help you.

2012-11-07 06:42:41 -0600 answered a question quantum admin plugin for horizon

In Folsom Quantum, VIF attach/detach is repsented by updating device_id attribute of a port.

In Horizon, to attach VIF, go to network detail panel, select edit port. After Port update panel is displayed, input an appropriate device_id (usually VM instance UUID) to "device_id" text box. To detach device_id (ie VIF), clear "device_id" text box in "Port Update" panel.

I understand this UI is not user-friendly and it is one of improvement points in future.

2012-08-14 00:57:08 -0600 answered a question quantum admin plugin for horizon

Network operations are supported in Horizon in Folsom release. It is merged to the mainline yesterday. The latest codebase is available from https://github.com/openstack/horizon

For Essex, I remember there are an official version of Quantum support, but I do not know the status.