OpenStack - User contributions [en]

Manila/issue-neutron-on-localhost-ipv6

2014-07-25T12:58:46Z

Bogun Dmitriy:

I got an issue, on fresh devstack installation (ubuntu-server-14.04). Here is symptom:

2014-07-24 07:26:21.852 INFO urllib3.connectionpool [req-17b5ef32-2198-4d6f-9baf-d24c803010ba None None] Starting new HTTP connection (1): localhost
2014-07-24 07:26:21.852 DEBUG neutronclient.client [req-17b5ef32-2198-4d6f-9baf-d24c803010ba None None] throwing ConnectionFailed : HTTPConnectionPool(host='localhost', port=5000): Max retries exceeded with url: /v2.0/tokens (Caused by <class 'socket.error'>: [Errno -9] Address family for hostname not supported) from (pid=22246) _cs_request /opt/devel/openstack/python-neutronclient/neutronclient/client.py:112
2014-07-24 07:26:21.853 DEBUG manila.share.drivers.service_instance [req-17b5ef32-2198-4d6f-9baf-d24c803010ba None None] Connection to neutron failed. from (pid=22246) init /opt/devel/openstack/manila/manila/share/drivers/service_instance.py:145
2014-07-24 07:26:24.857 ERROR manila.service [req-17b5ef32-2198-4d6f-9baf-d24c803010ba None None] Unhandled exception
2014-07-24 07:26:24.857 TRACE manila.service Traceback (most recent call last):
2014-07-24 07:26:24.857 TRACE manila.service File "/opt/devel/openstack/manila/manila/service.py", line 225, in _start_child
2014-07-24 07:26:24.857 TRACE manila.service self._child_process(wrap.server)
2014-07-24 07:26:24.857 TRACE manila.service File "/opt/devel/openstack/manila/manila/service.py", line 202, in _child_process
2014-07-24 07:26:24.857 TRACE manila.service launcher.run_server(server)
2014-07-24 07:26:24.857 TRACE manila.service File "/opt/devel/openstack/manila/manila/service.py", line 93, in run_server
2014-07-24 07:26:24.857 TRACE manila.service server.start()
2014-07-24 07:26:24.857 TRACE manila.service File "/opt/devel/openstack/manila/manila/service.py", line 374, in start
2014-07-24 07:26:24.857 TRACE manila.service self.manager.init_host()
2014-07-24 07:26:24.857 TRACE manila.service File "/opt/devel/openstack/manila/manila/share/manager.py", line 76, in init_host
2014-07-24 07:26:24.857 TRACE manila.service self.driver.do_setup(ctxt)
2014-07-24 07:26:24.857 TRACE manila.service File "/opt/devel/openstack/manila/manila/share/drivers/generic.py", line 143, in do_setup
2014-07-24 07:26:24.857 TRACE manila.service driver_config=self.configuration)
2014-07-24 07:26:24.857 TRACE manila.service File "/opt/devel/openstack/manila/manila/share/drivers/service_instance.py", line 149, in init
2014-07-24 07:26:24.857 TRACE manila.service raise exception.ServiceInstanceException(_('Can not receive '
2014-07-24 07:26:24.857 TRACE manila.service ServiceInstanceException: Can not receive service tenant id.
2014-07-24 07:26:24.857 TRACE manila.service

After some digging, I have found out the source of this error. There is a python-dnspython package installed. The eventlet package check is dns module (dnspython) present and if present in replace socket's function getaddrinfo. But function getaddrinfo from eventlet packages incorrectly handle ipv6 addresses. In our case it resolve domain "localhost" into ::1 (using /etc/hosts) and we got this error.

[[https://bitbucket.org/eventlet/eventlet/issue/105/name-resolution-needs-to-support-ipv6 eventlet issue]]

== workaround ==
Set environment variable EVENTLET_NO_GREENDNS to any value. Or remove line

::1 localhost

from /etc/hosts

Manila/issue-neutron-on-localhost-ipv6

2014-07-24T14:31:35Z

Bogun Dmitriy:

Manila

2014-07-24T14:16:31Z

Bogun Dmitriy: /* Known issues */ fix typo

== Introduction ==
This page documents the concept and vision for establishing a shared file system service for OpenStack. The development name for this project is Manila. We propose and are in the process of implementing a new OpenStack service (originally based on Cinder). Cinder presently functions as the canonical storage provisioning control plane in [[OpenStack]] for block storage as well as delivering a persistence model for instance storage. The File Share Service prototype, in a similar manner, provides coordinated access to shared or distributed file systems. While the primary consumption of file shares would be across OpenStack Compute instances, the service is also intended to be accessible as an independent capability in line with the modular design established by other OpenStack services. The design and prototype implementation provide extensibility for multiple backends (to support vendor or file system specific nuances / capabilities) but is intended to be sufficiently abstract to accommodate any of a variety of shared or distributed file system types. The team's intention is to introduce the capability as an OpenStack incubated project in the Juno timeframe, graduate it and submit for consideration as a core service as early as the as of yet unnamed "K" release.

[[File:Shares_Service.png]]

According to IDC in its “[http://www.idc.com/getdoc.jsp?containerId=235910 Worldwide File-Based Storage 2012-2016 Forecast]", file-based storage continues to be a thriving market, with spending on File-based storage solutions to reach north of $34.6 billion in 2016. Of the 27 Exabyte’s (EB) of total disk capacity estimated to have shipped in 2012, IDC projected that nearly 18 EB were file-based capacity, accounting for over 65% of all disk shipped by capacity. A diversity of applications, from server virtualization to relational or distributed databases to collaborative content creation, often depend on the performance, scalability and simplicity of management associated with file-based systems, and the large ecosystem of supporting software products. OpenStack, as the leading open IaaS capability, is increasingly contemplated as an option for deploying classic infrastructure in an "as a Service" model, but without specific accommodation for shared file systems represents an incomplete solution.

== Projects==

=== Manila ===

{| border="1" cellpadding="2"
| Source code
| https://github.com/stackforge/manila
|-
| Bug tracker
| https://bugs.launchpad.net/manila
|-
| Feature tracker
| https://blueprints.launchpad.net/manila
|}

=== Python Manila Client ===
{| border="1" cellpadding="2"
| Source code
| https://github.com/stackforge/python-manilaclient
|-
| Bug tracker
| https://bugs.launchpad.net/python-manilaclient
|-
| Feature tracker
| https://blueprints.launchpad.net/python-manilaclient
|}

=== Meetings ===

[[Manila/Meetings|Project Agenda & Meetings]]

[[Manila/JunoSummitPresentation|Overview Presentation from Juno (Atlanta) Summit]]

=== Getting Started with Manila ===

Instructions for getting started with Manila using Devstack are available at: [[Manila/IcehouseDevstack|Manila on Devstack]]

Developer documentation is still in progress, but is available in a draft state: [[Manila/docs|Manila Documentation]]

=== Project Plan & Progress ===

[[Manila/ProjectPlan|Manila Project Plan]]<br />
Track progress towards [[Manila/Graduation|Manila Incubation & Graduation]].

== Design & Use Cases ==

[[Manila/design|Manila Component Design]]<br />
[[Manila/usecases|Manila Use Cases]]

== Known issues ==

[[Manila/issue-neutron-on-localhost-ipv6|Connection to neutron failed.]]

== Subpages ==

{{Special:PrefixIndex/:Manila/}}

[[Category:Manila]]

Manila/issue-neutron-on-localhost-ipv6

2014-07-24T14:15:45Z

Bogun Dmitriy: Bogun Dmitriy moved page Manila/iddue-neutron-on-localhost-ipv6 to Manila/issue-neutron-on-localhost-ipv6: typo in name

I got an issue, on fresh devstack installation (ubuntu-server-14.04). Here is symptom:

2014-07-24 07:26:21.852 INFO urllib3.connectionpool [req-17b5ef32-2198-4d6f-9baf-d24c803010ba None None] Starting new HTTP connection (1): localhost
2014-07-24 07:26:21.852 DEBUG neutronclient.client [req-17b5ef32-2198-4d6f-9baf-d24c803010ba None None] throwing ConnectionFailed : HTTPConnectionPool(host='localhost', port=5000): Max retries exceeded with url: /v2.0/tokens (Caused by <class 'socket.error'>: [Errno -9] Address family for hostname not supported) from (pid=22246) _cs_request /opt/devel/openstack/python-neutronclient/neutronclient/client.py:112
2014-07-24 07:26:21.853 DEBUG manila.share.drivers.service_instance [req-17b5ef32-2198-4d6f-9baf-d24c803010ba None None] Connection to neutron failed. from (pid=22246) init /opt/devel/openstack/manila/manila/share/drivers/service_instance.py:145
2014-07-24 07:26:24.857 ERROR manila.service [req-17b5ef32-2198-4d6f-9baf-d24c803010ba None None] Unhandled exception
2014-07-24 07:26:24.857 TRACE manila.service Traceback (most recent call last):
2014-07-24 07:26:24.857 TRACE manila.service File "/opt/devel/openstack/manila/manila/service.py", line 225, in _start_child
2014-07-24 07:26:24.857 TRACE manila.service self._child_process(wrap.server)
2014-07-24 07:26:24.857 TRACE manila.service File "/opt/devel/openstack/manila/manila/service.py", line 202, in _child_process
2014-07-24 07:26:24.857 TRACE manila.service launcher.run_server(server)
2014-07-24 07:26:24.857 TRACE manila.service File "/opt/devel/openstack/manila/manila/service.py", line 93, in run_server
2014-07-24 07:26:24.857 TRACE manila.service server.start()
2014-07-24 07:26:24.857 TRACE manila.service File "/opt/devel/openstack/manila/manila/service.py", line 374, in start
2014-07-24 07:26:24.857 TRACE manila.service self.manager.init_host()
2014-07-24 07:26:24.857 TRACE manila.service File "/opt/devel/openstack/manila/manila/share/manager.py", line 76, in init_host
2014-07-24 07:26:24.857 TRACE manila.service self.driver.do_setup(ctxt)
2014-07-24 07:26:24.857 TRACE manila.service File "/opt/devel/openstack/manila/manila/share/drivers/generic.py", line 143, in do_setup
2014-07-24 07:26:24.857 TRACE manila.service driver_config=self.configuration)
2014-07-24 07:26:24.857 TRACE manila.service File "/opt/devel/openstack/manila/manila/share/drivers/service_instance.py", line 149, in init
2014-07-24 07:26:24.857 TRACE manila.service raise exception.ServiceInstanceException(_('Can not receive '
2014-07-24 07:26:24.857 TRACE manila.service ServiceInstanceException: Can not receive service tenant id.
2014-07-24 07:26:24.857 TRACE manila.service

After some digging, I have found out the source of this error. There is a python-dnspython package installed. The eventlet package check is dns module (dnspython) present and if present in replace socket's function getaddrinfo. But function getaddrinfo from eventlet packages incorrectly handle ipv6 addresses. In our case it resolve domain "localhost" into ::1 (using /etc/hosts) and we got this error.

[[https://bitbucket.org/eventlet/eventlet/issue/105/name-resolution-needs-to-support-ipv6]]

== workaround ==
remove line

::1 localhost

from /etc/hosts

Manila/iddue-neutron-on-localhost-ipv6

2014-07-24T14:15:45Z

Bogun Dmitriy: Bogun Dmitriy moved page Manila/iddue-neutron-on-localhost-ipv6 to Manila/issue-neutron-on-localhost-ipv6: typo in name

#REDIRECT [[Manila/issue-neutron-on-localhost-ipv6]]

Manila/issue-neutron-on-localhost-ipv6

2014-07-24T13:00:29Z

Bogun Dmitriy: Created page with "I got an issue, on fresh devstack installation (ubuntu-server-14.04). Here is symptom: 2014-07-24 07:26:21.852 INFO urllib3.connectionpool [req-17b5ef32-2198-4d6f-9baf-d24c..."

I got an issue, on fresh devstack installation (ubuntu-server-14.04). Here is symptom:

2014-07-24 07:26:21.852 INFO urllib3.connectionpool [req-17b5ef32-2198-4d6f-9baf-d24c803010ba None None] Starting new HTTP connection (1): localhost
2014-07-24 07:26:21.852 DEBUG neutronclient.client [req-17b5ef32-2198-4d6f-9baf-d24c803010ba None None] throwing ConnectionFailed : HTTPConnectionPool(host='localhost', port=5000): Max retries exceeded with url: /v2.0/tokens (Caused by <class 'socket.error'>: [Errno -9] Address family for hostname not supported) from (pid=22246) _cs_request /opt/devel/openstack/python-neutronclient/neutronclient/client.py:112
2014-07-24 07:26:21.853 DEBUG manila.share.drivers.service_instance [req-17b5ef32-2198-4d6f-9baf-d24c803010ba None None] Connection to neutron failed. from (pid=22246) init /opt/devel/openstack/manila/manila/share/drivers/service_instance.py:145
2014-07-24 07:26:24.857 ERROR manila.service [req-17b5ef32-2198-4d6f-9baf-d24c803010ba None None] Unhandled exception
2014-07-24 07:26:24.857 TRACE manila.service Traceback (most recent call last):
2014-07-24 07:26:24.857 TRACE manila.service File "/opt/devel/openstack/manila/manila/service.py", line 225, in _start_child
2014-07-24 07:26:24.857 TRACE manila.service self._child_process(wrap.server)
2014-07-24 07:26:24.857 TRACE manila.service File "/opt/devel/openstack/manila/manila/service.py", line 202, in _child_process
2014-07-24 07:26:24.857 TRACE manila.service launcher.run_server(server)
2014-07-24 07:26:24.857 TRACE manila.service File "/opt/devel/openstack/manila/manila/service.py", line 93, in run_server
2014-07-24 07:26:24.857 TRACE manila.service server.start()
2014-07-24 07:26:24.857 TRACE manila.service File "/opt/devel/openstack/manila/manila/service.py", line 374, in start
2014-07-24 07:26:24.857 TRACE manila.service self.manager.init_host()
2014-07-24 07:26:24.857 TRACE manila.service File "/opt/devel/openstack/manila/manila/share/manager.py", line 76, in init_host
2014-07-24 07:26:24.857 TRACE manila.service self.driver.do_setup(ctxt)
2014-07-24 07:26:24.857 TRACE manila.service File "/opt/devel/openstack/manila/manila/share/drivers/generic.py", line 143, in do_setup
2014-07-24 07:26:24.857 TRACE manila.service driver_config=self.configuration)
2014-07-24 07:26:24.857 TRACE manila.service File "/opt/devel/openstack/manila/manila/share/drivers/service_instance.py", line 149, in init
2014-07-24 07:26:24.857 TRACE manila.service raise exception.ServiceInstanceException(_('Can not receive '
2014-07-24 07:26:24.857 TRACE manila.service ServiceInstanceException: Can not receive service tenant id.
2014-07-24 07:26:24.857 TRACE manila.service

After some digging, I have found out the source of this error. There is a python-dnspython package installed. The eventlet package check is dns module (dnspython) present and if present in replace socket's function getaddrinfo. But function getaddrinfo from eventlet packages incorrectly handle ipv6 addresses. In our case it resolve domain "localhost" into ::1 (using /etc/hosts) and we got this error.

[[https://bitbucket.org/eventlet/eventlet/issue/105/name-resolution-needs-to-support-ipv6]]

== workaround ==
remove line

::1 localhost

from /etc/hosts

Manila

2014-07-24T12:39:56Z

Bogun Dmitriy: /* Design & Use Cases */

== Introduction ==
This page documents the concept and vision for establishing a shared file system service for OpenStack. The development name for this project is Manila. We propose and are in the process of implementing a new OpenStack service (originally based on Cinder). Cinder presently functions as the canonical storage provisioning control plane in [[OpenStack]] for block storage as well as delivering a persistence model for instance storage. The File Share Service prototype, in a similar manner, provides coordinated access to shared or distributed file systems. While the primary consumption of file shares would be across OpenStack Compute instances, the service is also intended to be accessible as an independent capability in line with the modular design established by other OpenStack services. The design and prototype implementation provide extensibility for multiple backends (to support vendor or file system specific nuances / capabilities) but is intended to be sufficiently abstract to accommodate any of a variety of shared or distributed file system types. The team's intention is to introduce the capability as an OpenStack incubated project in the Juno timeframe, graduate it and submit for consideration as a core service as early as the as of yet unnamed "K" release.

[[File:Shares_Service.png]]

According to IDC in its “[http://www.idc.com/getdoc.jsp?containerId=235910 Worldwide File-Based Storage 2012-2016 Forecast]", file-based storage continues to be a thriving market, with spending on File-based storage solutions to reach north of $34.6 billion in 2016. Of the 27 Exabyte’s (EB) of total disk capacity estimated to have shipped in 2012, IDC projected that nearly 18 EB were file-based capacity, accounting for over 65% of all disk shipped by capacity. A diversity of applications, from server virtualization to relational or distributed databases to collaborative content creation, often depend on the performance, scalability and simplicity of management associated with file-based systems, and the large ecosystem of supporting software products. OpenStack, as the leading open IaaS capability, is increasingly contemplated as an option for deploying classic infrastructure in an "as a Service" model, but without specific accommodation for shared file systems represents an incomplete solution.

== Projects==

=== Manila ===

{| border="1" cellpadding="2"
| Source code
| https://github.com/stackforge/manila
|-
| Bug tracker
| https://bugs.launchpad.net/manila
|-
| Feature tracker
| https://blueprints.launchpad.net/manila
|}

=== Python Manila Client ===
{| border="1" cellpadding="2"
| Source code
| https://github.com/stackforge/python-manilaclient
|-
| Bug tracker
| https://bugs.launchpad.net/python-manilaclient
|-
| Feature tracker
| https://blueprints.launchpad.net/python-manilaclient
|}

=== Meetings ===

[[Manila/Meetings|Project Agenda & Meetings]]

[[Manila/JunoSummitPresentation|Overview Presentation from Juno (Atlanta) Summit]]

=== Getting Started with Manila ===

Instructions for getting started with Manila using Devstack are available at: [[Manila/IcehouseDevstack|Manila on Devstack]]

Developer documentation is still in progress, but is available in a draft state: [[Manila/docs|Manila Documentation]]

=== Project Plan & Progress ===

[[Manila/ProjectPlan|Manila Project Plan]]<br />
Track progress towards [[Manila/Graduation|Manila Incubation & Graduation]].

== Design & Use Cases ==

[[Manila/design|Manila Component Design]]<br />
[[Manila/usecases|Manila Use Cases]]

== Known issues ==

[[Manila/iddue-neutron-on-localhost-ipv6|Connection to neutron failed.]]

== Subpages ==

{{Special:PrefixIndex/:Manila/}}

[[Category:Manila]]