January 2016 - openstack-ko - lists.openstack.org

[Help-Ask] cinder 볼륨생성 후 볼륨상태 status 에 멈춰있는 문제... 잠깐 한번만 봐주시면 감사하겠습니다
by 디케이 21 Jan '16

21 Jan '16

안녕하세요 오픈스택관련 해서 문의 드립니다. 잠깐 한번만 봐주시면 감사하겠습니다.^^ cinder create 명령으로 생성한 새로운 볼륨의 상태가 creating 에서 계속 멈춰있습니다. 예상되는 문제 포인트 지점이 어디일까요? 해결을 못하겠네요...ㅠ 해결방법이나 접근방법을 아시면 답변 주시면 감사하겠습니다. 서버에서 확인한 로그와 구성정보 및 상태 함께 공유합니다. ● [오픈스택 구성] : 3-node configuration (Controller-node, Network-node, Compute-node(스토리지노드이기도함)) : ubuntu14.04, icehouse 버젼이 각 노드마다 설치되어 있으며, virtualbox에서 실행되고 있음 ● (On Controller node) # cinder create --display-name myVolume 1 # cinder list +--------------------------------------+----------+--------------+------+-------------+----------+-------------+ | ID | Status | Display Name | Size | Volume Type | Bootable | Attached to | +--------------------------------------+----------+--------------+------+-------------+----------+-------------+ | 4891a2e7-0cb2-4caf-9528-6612d8cf5f5a | creating | myVolume | 1 | None | false | | +--------------------------------------+----------+--------------+------+-------------+----------+-------------+ mysql> select status from volumes; +----------+ | status | +----------+ | creating | +----------+ mysql> select id from volumes; +--------------------------------------+ | id | +--------------------------------------+ | 4891a2e7-0cb2-4caf-9528-6612d8cf5f5a | +--------------------------------------+ # netstat -an | grep 8776 tcp 0 0 0.0.0.0:8776 0.0.0.0:* LISTEN # netstat -an | grep 5672 ..... tcp6 0 0 :::5672 :::* LISTEN tcp6 0 0 10.10.15.11:567210.10.15.31:33271 ESTABLISHED ..... # service cinder-api status cinder-api start/running, process 3733 # service cinder-scheduler status cinder-scheduler start/running, process 3755 *<Logs>* 명령어 실행할때 생성된 로그 *<cinder-api.log>* 2016-01-20 15:24:29.584 3739 INFO eventlet.wsgi.server [-] (3739) accepted ('10.10.15.11', 51845) 2016-01-20 15:24:29.588 3739 INFO urllib3.connectionpool [-] Starting new HTTP connection (1): 10.10.15.11 2016-01-20 15:24:29.874 3739 INFO urllib3.connectionpool [-] Starting new HTTP connection (1): 10.10.15.11 2016-01-20 15:24:30.029 3739 INFO cinder.api.openstack.wsgi [req-c7c065b5-3e4c-40c8-b011-24a1afbf6e50 5f8b76cf5986402fa6affdb4c9e2fc44 56ee36bd79724517bf115df7f3202f1d - - -] POST http://10.10.15.11:8776/v1/56ee36bd79724517bf115df7f3202f1d/volumes 2016-01-20 15:24:30.032 3739 AUDIT cinder.api.v1.volumes [req-c7c065b5-3e4c-40c8-b011-24a1afbf6e50 5f8b76cf5986402fa6affdb4c9e2fc44 56ee36bd79724517bf115df7f3202f1d - - -] Create volume of 1 GB 2016-01-20 15:24:30.212 3739 AUDIT cinder.api.v1.volumes [req-c7c065b5-3e4c-40c8-b011-24a1afbf6e50 5f8b76cf5986402fa6affdb4c9e2fc44 56ee36bd79724517bf115df7f3202f1d - - -] vol={'migration_status': None, 'availability_zone': 'nova', 'terminated_at': None, 'reservations': ['8339d8b8-70a5-4226-94a5-ad7c4f16d3f6', '6795bec3-0875-49cb-b538-c1e0f3b097c1'], 'updated_at': None, 'provider_geometry': None, 'snapshot_id': None, 'ec2_id': None, 'mountpoint': None, 'deleted_at': None, 'id': '4891a2e7-0cb2-4caf-9528-6612d8cf5f5a', 'size': 1, 'user_id': u'5f8b76cf5986402fa6affdb4c9e2fc44', 'attach_time': None, 'attached_host': None, 'display_description': None, 'volume_admin_metadata': [], 'encryption_key_id': None, 'project_id': u'56ee36bd79724517bf115df7f3202f1d', 'launched_at': None, 'scheduled_at': None, 'status': 'creating', 'volume_type_id': None, 'deleted': False, 'provider_location': None, 'host': None, 'source_volid': None, 'provider_auth': None, 'display_name': u'myVolume', 'instance_uuid': None, 'bootable': False, 'created_at': datetime.datetime(2016, 1, 20, 6, 24, 30, 108934), 'attach_status': 'detached', 'volume_type': None, '_name_id': None, 'volume_metadata': [], 'metadata': {}} 2016-01-20 15:24:30.217 3739 INFO cinder.api.openstack.wsgi [req-c7c065b5-3e4c-40c8-b011-24a1afbf6e50 5f8b76cf5986402fa6affdb4c9e2fc44 56ee36bd79724517bf115df7f3202f1d - - -] http://10.10.15.11:8776/v1/56ee36bd79724517bf115df7f3202f1d/volumes returned with HTTP 200 2016-01-20 15:24:30.226 3739 INFO eventlet.wsgi.server [req-c7c065b5-3e4c-40c8-b011-24a1afbf6e50 5f8b76cf5986402fa6affdb4c9e2fc44 56ee36bd79724517bf115df7f3202f1d - - -] 10.10.15.11 - - [20/Jan/2016 15:24:30] "POST /v1/56ee36bd79724517bf115df7f3202f1d/volumes HTTP/1.1" 200 602 0.639812 *<cinder-scheduler.log>* 계속 같은 로그가 반복되며 실행될때는 "2016-01-20 15:24:30.205" 로그가 한번가 찍혔음 2016-01-20 15:23:12.097 3755 WARNING cinder.context [-] Arguments dropped when creating context: {'user': None, 'tenant': None, 'user_identity': u'- - - - -'} 2016-01-20 15:24:12.105 3755 WARNING cinder.context [-] Arguments dropped when creating context: {'user': None, 'tenant': None, 'user_identity': u'- - - - -'} *2016-01-20 15:24:30.205 3755 WARNING cinder.context [-] Arguments dropped when creating context: {'user': u'5f8b76cf5986402fa6affdb4c9e2fc44', 'tenant': u'56ee36bd79724517bf115df7f3202f1d', 'user_identity': u'5f8b76cf5986402fa6affdb4c9e2fc44 56ee36bd79724517bf115df7f3202f1d - - -'}*2016-01-20 15:25:12.133 3755 WARNING cinder.context [-] Arguments dropped when creating context: {'user': None, 'tenant': None, 'user_identity': u'- - - - -'} *# cinder.conf* <controller node> [DEFAULT] rootwrap_config = /etc/cinder/rootwrap.conf api_paste_confg = /etc/cinder/api-paste.ini iscsi_helper = tgtadm volume_name_template = volume-%s volume_group = cinder-volumes verbose = True auth_strategy = keystone state_path = /var/lib/cinder lock_path = /var/lock/cinder volumes_dir = /var/lib/cinder/volumes rpc_backend = cinder.openstack.common.rpc.impl_kombu rabbit_host = 10.10.15.11 rabbit_port = 5672 rabbit_userid = guest rabbit_password = rabbitpass control_exchange = cinder notification_driver = cinder.openstack.common.notifier.rpc_notifier [database] connection = mysql://cinder:cinderdbpass@10.10.15.11/cinder [keystone_authtoken] auth_uri = http://10.10.15.11:5000 auth_host = 10.10.15.11 auth_port = 35357 auth_protocol = http admin_tenant_name = service admin_user = cinder admin_password = cinderpass --------------------------------------------------------------------------------------------------------------- ● (On Compute node) 스토리지노드 # vgs VG #PV #LV #SN Attr VSize VFree cinder-volumes 2 0 0 wz--n- 1.99g 1.99g # pvs PV VG Fmt Attr PSize PFree /dev/sdc cinder-volumes lvm2 a-- 1020.00m 1020.00m /dev/sdd cinder-volumes lvm2 a-- 1020.00m 1020.00m # service cinder-volume status cinder-volume start/running, process 1755 # service tgt status tgt start/running, process 1783 # /etc/lvm/lvm.conf ... filter = [ "a/sda1/", "a/sdc/", "a/sdd/", "r/.*/"] .... # netstat -an | grep 5672 tcp 0 0 10.10.15.31:33263 10.10.15.11:5672 ESTABLISHED *# cinder-volume.log * (명령수행과 관계없이 아래 로그만 반복됨.) 2016-01-20 15:12:12.112 2422 INFO cinder.volume.manager [-] Updating volume status 2016-01-20 15:13:12.139 2422 INFO cinder.volume.manager [-] Updating volume status 2016-01-20 15:14:12.107 2422 INFO cinder.volume.manager [-] Updating volume status 2016-01-20 15:15:12.147 2422 INFO cinder.volume.manager [-] Updating volume status 2016-01-20 15:16:12.121 2422 INFO cinder.volume.manager [-] Updating volume status *# cinder.conf* <compute node> [DEFAULT] rootwrap_config = /etc/cinder/rootwrap.conf api_paste_confg = /etc/cinder/api-paste.ini iscsi_helper = tgtadm volume_name_template = volume-%s volume_group = cinder-volumes verbose = True auth_strategy = keystone state_path = /var/lib/cinder lock_path = /var/lock/cinder volumes_dir = /var/lib/cinder/volumes # rpc_backend = cinder.openstack.common.rpc.impl_kombu rabbit_host = 10.10.15.11 rabbit_port = 5672 rabbit_userid = guest rabbit_password = rabbitpass # my_ip = 10.10.15.31 glance_host = 10.10.15.11 # [keystone_authtoken] auth_uri = http://10.10.15.11:5000 auth_host = 10.10.15.11 auth_port = 35357 auth_protocol = http admin_tenant_name = service admin_user = cinder admin_password = cinderpass # [database] connection = mysql://cinder:cinderdbpass@10.10.15.11/cinder # ls -al /var/lib/cinder/volumes total 8 drwxr-xr-x 2 cinder cinder 4096 9월 5 05:43 . drwxr-xr-x 3 cinder cinder 4096 1월 19 21:13 .. # ls -al /var/lock/cinder total 0 drwxr-xr-x 2 cinder root 40 1월 19 21:52 . drwxrwxrwt 7 root root 140 1월 19 21:53 .. # cat /admin-openrc.sh export OS_USERNAME=admin export OS_PASSWORD=adminpass export OS_TENANT_NAME=admin export OS_AUTH_URL=http://10.10.15.11:35357/v2.0

2 1

오픈스택 커뮤니티 회원님들의 도움의 손길을 기다립니다.^^
by 이상하 21 Jan '16

21 Jan '16

안녕하세요. 전 이상하라고 합니다. 다름이 아니옵고 오픈스택 환경 구성을 하다보니 잘 안되는 부분이 있어 도움을 받고자 메일을 드립니다. 제가 궁금한 사항은 오픈스택 구성시에 기존에 네트워크 환경을 반영해 Flat 네트워크 환경을 구성하고자 합니다. 오픈스택 서버에 네트워크 인터페이스가 브릿지 네트워크만을 사용하는 방법을 알고 싶습니다. 네트워크 인터페이스가 서로 브릿지 되지 않아 오픈스택 서버와 인스턴스간 통신이 안되는 상황인 것으로 생각되어집니다. 그리고 인스턴스를 프로비저닝하게 되면 virt-manager에서 새로운 브릿지가 생성되는지 모르겠습니다. 혹시 브리지로만 사용하는분이 있으시면 도움좀 주세요~~~ 카카오가 그렇게 구성한걸로 알고 있는데 궁금합니다요... 감사합니다.

2 1

[or_kr] Mitaka Design Series
by potopro＠gmail.com 17 Jan '16

17 Jan '16

매번 서밋이 끝나고 난뒤 PTL들이 나와서 발표하는 내용들이 올라오죠. 이번에 나오는 Mitaka에서 추가되는 것들에 대한 이야기입니다. OpenStack Superuser 사이트에 올라온 글들입니다. 그냥 발표자료에 나온것들만 정리했습니다. 더 자세한 내용은 들어가서 동영상과 함께 작성해놓은 글을 보시면 됩니다. Swift, Ironic OpenStack Mitaka release: what’s next for swift and Ironic Swift Burning issues Data at Rest Encryption Continuing the work on erasure coding Request for resource usage data (disk utilisation, etc.) Improving docs and auth for Swift SDK and CLI Tools What’s next Encryption Improving the overall experience for end users and operators in various ways Lowering and smoothing latency What matters in Mitaka Continued focus on scalability and performance Interoperability: adding Keystone policy support for role-based access control Ironic Burning issues General stability: testing, Nova integration Improving HA for Nova integration What’s next Better testing Nova integration: supporting multiple compute nodes Networking support with Neutron RAID Support What matters in Mitaka Scalability Resiliency Third-party testing for all drivers Ansible, Oslo, Designate OpenStack Mitaka release: what’s next for Ansible, Oslo and Designate Ansible Burning issues Upgrading OpenStack Image-based deployment of OpenStack Focusing on providing a toolset for operators What’s next Breaking out repository into composable parts Increased focus on quality of testing Provide examples for use cases that are important to deployers Production-ready upgrade framework for OpenStack What matters in Mitaka Reducing complexity Improve modularity by implementing everything Oslo Burning issues Both old and new Oslo projects were discussed at Summit Focused on operator feedback and ongoing feedback through bug reports Discussed how to work closely with logging and security working groups What’s next Promoting existing projects built over last few cycles (e.g. TaskFlow) Oslo-privsep: New privilege mechanism based on python functions Oslo-tooz: distributed lock management, leader elections, etc. What matters in Mitaka Hardening the messaging infrastructure New Oslo messaging driver using Pika New driver for ZeroMQ and adding driver for Kafka Designate Burning issues Gaps remaining from the refactoring that occurred between Kilo and Liberty DNSSEC (DNS Security Extensions) Verification that returned records have not been tampered Integration with Nova and neutron for automatic record creation What’s next Incremental zone transfers (IXFR) Enabling pool scheduler What matters in Mitaka Increasing number of DNS server types, breaking down services into smaller services enhances: Modularity (모듈성) Resiliency (탄력성) Scalability (확장성) OpenStackClient, Documentation OpenStack Mitaka release: what’s next for OpenStackClient and Documentation OpenStackClient Burning issues Help output from tool (feel and heavier) Name spacing of commands Only includes 5 services in repo; others are plugins Some plugins want to use the same resource name Making command set consistent What’s next Adding more sets of commands Neutron networking is missing currently switch to using the OpenStack SDK What matters in Mitaka Performance improvements Documentation Burning issues Information architecture and data typing Moving towards a task-based approach rather than role-based to make approach rather Impact Big Tent on docs approach Rethinking approach to API documentation A lot of feedback on release notes What’s planned for Mitaka Data typing Role to task centric approach: stating with user guides Re-order index pages Ongoing conversion to RST (Restructured Text) Modifying DocImpact tool Nova, Kuryr OpenStack Mitaka release: what’s next for Nova, Kuryr Nova Burning issues Focused on resource model for Nova and scheduler interactions Held several unconference sessions to drill into specific items raised by community members Plan to reduce the number of configuration options available for Nova What’s next Improved live migrate API docs and functionality with service catalog OS VIF: interface between Nova and Neutron for VIF plugins (in support of Neutron Stadium) Continue evolution of scheduler interface What matters in Mitaka Cells V2 impacts scalability and manageability Live migrate work will improve resiliency OS VIF will help with modularity Nova has work planned in all themes (scalability, resiliency, manageability, modularity, interoperability) Kuryr Burning issues Focused on identifying pain-points around user deployments with container networking Investigating how the flexibility of Neutron could help with the container networking experience Integration work with Magnum and Kolla What’s next Stabilisation through functional tests, CI, gate testing Nested containers use case with Magnum Deployment and packaging Stretch goal: multi-node environments; Docker Swarm, Mesos, Kubernetes support Neutron, Cinder, Ceilometer OpenStack Mitaka release: what’s next for Neutron, Cinder and Ceilometer Neutron Burning issues Network Function Virtualisation Container networking support Advanced services (LBaaS, FWaaS, etc.) Discussions on overall performance, reliability and operability What’s next Better protocol support for L3 (IPv6, BGP, etc.) Continue NFV and container networking work through Neutron Stadium What matters in Mitaka Scalability: continuing the work on distributed virtual routing (DVR) Resiliency Manageability: continuing work towards minimally disruptive upgrades Modularity: continue to build software modules that are loosely coupled (Neutron Stadium) Ceilometer Burning issues Collaborating with other project (Vitrage and CloudKitty) Requirement for real-time alarms: creating more flexible alarm rules and support for horizontal scaling User Interface (UI) discussions and prototypes Sample configuration files What’s next Aodh: add multiple worker support Ceilometer: add caching and batch support for write performance improvement Gnocchi: metric archive sharing to improve scalability for large data-sets What matters in Mitaka Scalability: alarming and storage Modularity: continue to break down services further to allow for better integration from external projects Cinder Burning issues how to balance being a general-purpose block storage service and taking advantage of features found in SAN arrays Object inheritance for drivers Expanded functional testing and third-party CI What’s next Replication V2 API API micro-versioning Continued focus on Third-Party CI and functional testing What matters in Mitaka Interoperability: API micro-versioning Resiliency: Investigating Active/Active Cinder from OpenStack 한국 커뮤니티 http://ift.tt/1naU47s

1 0

OpenStack Day in Korea 2016 자봉 신청 받습니다.
by Sungjin Kang 11 Jan '16

11 Jan '16

안녕하세요. 강성진입니다. 2016년 OpenStack Day in Korea 2016 자봉 신청받습니다. 아래의 문서를 작성해주시면 따로 연락드리겠습니다. http://goo.gl/forms/nUrrJlZhyg ps. 발표자도 받습니다! http://about.me/gangsungjin 마음의 변덕에 따라 이리저리 흔들리지 말라. 항상 마음을 잘 다스려서 부드럽고 순하고 고요함을 지니도록 하라. 마음이 하늘도 만들고 사람도 만들고, 지옥도 만들고 친구도 만든다. 그러니 마음에 쫓아가지 말고, 항상 마음의 주인이 되도록 노력하라.

1 0

Fwd: [openstack-community] OpenStack Day in Korea 2016 - call for everything
by Ian Y. Choi 11 Jan '16

11 Jan '16

안녕하세요! OpenStack Day in Korea 2016이 2월 18일 (목)에 서울 롯데 잠실 호텔에서 개 최 예정입니다. 현재 발표자 및 스폰서쉽 모집 중이고, 행사 등록 등은 곧 http://event.openstack.or.kr 홈페이지를 통해 공개 예정입니다. 해당 날짜 미리 참고해 주시고, 조만간 자원봉사 신청 등 또한 공유하고자 합 니다 ^^ 감사드립니다. 최영락 드림. -------- Original Message -------- Subject: [openstack-community] OpenStack Day in Korea 2016 - call for everything Date: Mon, 11 Jan 2016 10:38:28 -0500 From: bluejay@gmail <bluejay.ahn(a)gmail.com> To: community(a)lists.openstack.org, openstack(a)lists.openstack.org Hi everyone. OpenStack Korea User Group is having OpenStack Day in Korea event. Date: Feb. 18th 2016 Location: Seoul, Korea We had so much fun last year with lots of folks participated at the event. I hope we can make much better one thus year together with everyone in the community. Call for Sponsorship and Call for Speaker is still open. Please let me know if you are intetested in participating this event. Visit http://event.openstack.or.kr/2016/index.html now to get notified when registration opens. cheers!! ------ Jaesuk Ahn

1 0