Difference between revisions of "Translations:ReleaseNotes/Juno/118/ko"

Latest revision as of 01:55, 23 October 2014

Information about message (contribute)

This message has no documentation. If you know where or how this message is used, you can help other translators by adding documentation to this message.

Message definition (ReleaseNotes/Juno)

* A list of all updated, deprecated or removed options in Glance can be found at: http://docs.openstack.org/trunk/config-reference/content/glance-conf-changes-master.html
* The ability to upload a public image is now admin-only by default. To continue to use the previous behaviour, edit the publicize_image flag in etc/policy.json to remove the role restriction.
* The requirement and check on UTF-8 charset for DB tables is enforced, operator need to migration tables and existing data to UTF-8 manually if glance-manage complains it during the sync.
* glance workers will now be equal to the number of CPUs available by default if not explicitly specified in glance-api.conf and/or glance-registry.conf
** There is no upgrade impact to glance-api workers since glance-api.conf previously hard-coded the workers value to 1 so anyone upgrading to tihs will still get whatever value was set in glance-api.conf prior to this change. There is an upgrade impact to the glance-registry workers since glance-registry.conf did not hard-code the workers value to 1 before this change. So anyone upgrading to this change that does not have workers specified in glance-registry.conf will now be running multiple workers by default when they restart the glance registry service.

*  A list of all updated, deprecated or removed options in Glance can be found at: http://docs.openstack.org/trunk/config-reference/content/glance-conf-changes-master.html
* The ability to upload a public image is now admin-only by default. To continue to use the previous behaviour, edit the publicize_image flag in etc/policy.json to remove the role restriction.
* The requirement and check on UTF-8 charset for DB tables is enforced, operator need to migration tables and existing data to UTF-8 manually if glance-manage complains it during the sync.
* glance workers will now be equal to the number of CPUs available by default if not explicitly specified in glance-api.conf and/or glance-registry.conf
** There is no upgrade impact to glance-api workers since glance-api.conf previously hard-coded the workers value to 1 so anyone upgrading to tihs will still get whatever value was set in glance-api.conf prior to this change. There is an upgrade impact to the glance-registry workers since glance-registry.conf did not hard-code the workers value to 1 before this change. So anyone upgrading to this change that does not have workers specified in glance-registry.conf will now be running multiple workers by default when they restart the glance registry service.

Translation* Glance에서 업데이트, deprecated,제거된 옵션 목록은 여기서 확인 가능합니다: http://docs.openstack.org/trunk/config-reference/content/glance-conf-changes-master.html
* 공용 이미지를 업로드는 이제 디폴트로 admin 만 가능합니다. 이전과 동일하게 동작하기를 원하는 경우 etc/policy.json 에 있는 publicize_image 플래그를 수정하여 역할 제한을 제거하십시오.
* DB 테이블의 UTF-8 문자셋 요구 사항 및 확인이 강화되어, DB sync 중에 glance-manage 명령에서 에러를 출력하는 경우, 운영자는 테이블 및 기존 데이터를 UTF-8로 수동 마이그레이션을 할 필요가 있습니다.

Glance에서 업데이트, deprecated,제거된 옵션 목록은 여기서 확인 가능합니다: http://docs.openstack.org/trunk/config-reference/content/glance-conf-changes-master.html
공용 이미지를 업로드는 이제 디폴트로 admin 만 가능합니다. 이전과 동일하게 동작하기를 원하는 경우 etc/policy.json 에 있는 publicize_image 플래그를 수정하여 역할 제한을 제거하십시오.
DB 테이블의 UTF-8 문자셋 요구 사항 및 확인이 강화되어, DB sync 중에 glance-manage 명령에서 에러를 출력하는 경우, 운영자는 테이블 및 기존 데이터를 UTF-8로 수동 마이그레이션을 할 필요가 있습니다.