Jump to: navigation, search

Difference between revisions of "ReleaseNotes/Liberty/zh-tw"

(Created page with "=== 新功能 ===")
 
(273 intermediate revisions by 5 users not shown)
Line 1: Line 1:
 
<languages />
 
<languages />
  
−
[[Category:Liberty|Release Note]]
+
[[Category: Liberty |更新日誌]]
−
[[Category:Release Note|Liberty]]
+
[[Category:更新日誌| Liberty]]
  
−
= OpenStack Liberty Release Notes =
+
= OpenStack Liberty更新說明 =
  
 
<div style="column-count:3;-moz-column-count:3;-webkit-column-count:3">
 
<div style="column-count:3;-moz-column-count:3;-webkit-column-count:3">
Line 12: Line 12:
 
== OpenStack 物件儲存 (Swift) ==
 
== OpenStack 物件儲存 (Swift) ==
  
−
Please see full release notes at https://github.com/openstack/swift/blob/master/CHANGELOG
+
完整的版本更新說明請參閱 https://github.com/openstack/swift/blob/master/CHANGELOG
  
−
=== New Features ===
+
=== 新功能 ===
  
−
* Allow 1+ object-servers-per-disk deployment enabled by a new > 0 integer config value, "servers_per_port" in the [DEFAULT] config section for object-server and/or replication server configurations. The setting's integer value determines how many different object-server workers handle requests for any single unique local port in the ring. In this mode, the parent swift-object-server process continues to run as the original user (i.e. root if low-port binding is required). It binds to all ports as defined in the ring. It then forks off the specified number of workers per listen socket. The child, per-port servers, drops privileges and behaves pretty much how object-server workers always have with one exception: the ring has unique ports per disk, the object-servers will only handle requests for a single disk. The parent process detects dead servers and restarts them (with the correct listen socket). It starts missing servers when an updated ring file is found with a device on the server with a new port, and kills extraneous servers when their port is no longer found in the ring. The ring files are started at most on the schedule configured in the object-server configuration by every the "ring_check_interval" parameter (same default of 15s). In testing, this deployment configuration (with a value of 3) lowers request latency, improves requests per second, and isolates slow disk IO as compared to the existing "workers" setting. To use this, each device must be added to the ring using a different port.
+
* 透過設定一個大於0的整數，允許一個以上的object-servers-per-disk，在[DEFAULT]中的"servers_per_port"設定，設定object-server或是replication server的設定。這個設定值決定了許多不同的object-server workers處理一個唯一local port 在ring。在這個模式下，父類別swift-object-server處理繼續使用原本使用者去執行(例如:如果需要low-port綁定須使用root帳號)。他綁定所有在ring定義的ports。然後為每一個監聽socket分離出一個指定數量的workers。子類別，每一個port的服務，降低權限並且表現出object-server workers狀態，但有一個例外:ring在每個disk擁有唯一的port， object-server只單獨處理每一個disk請求。父類別偵測到已經掛掉的服務並且重新啟動他們(用正確的監聽socket)。當發現一個更新的ring檔案，新啟動停止的服務，並在服務中仔入一個新的port，並且當在ring找不到的時候，後停用多餘的服務。ring檔案啟動是在每個object-server設定中由"ring_check_interval"參數進行設定(預設為15秒)。在測試的時候，這種部屬配置(預設3秒)降低了請求延遲，改善了每秒的請求，與存在在"workers" 設定比較的話，隔離速度比較慢的disk IO請求。若要使用這個設定，每個device必須要增加到ring並使用不同的port。
  
−
* The object server includes a "container_update_timeout" setting (with a default of 1 second). This value is the number of seconds that the object server will wait for the container server to update the listing before returning the status of the object PUT operation. Previously, the object server would wait up to 3 seconds for the container server response. The new behavior dramatically lowers object PUT latency when container servers in the cluster are busy (e.g. when the container is very large). Setting the value too low may result in a client PUT'ing an object and not being able to immediately find it in listings. Setting it too high will increase latency for clients when container servers are busy.
+
* object server 包括一個 "container_update_timeout" 設定 (預設設定為1秒)。這個值包含object server服務等待container返回object PUT操作之前更新列表秒數。以前，object server將會等待container server 3秒回應。當叢集container繁忙時新的行為大幅降低了object PUT的延遲(例如:當container非常大的時候)。如果將這個值設定太底可能導致 client PUT'ing一個objcet中無法馬上找到對象。如果設定值太高會增加client延遲當container servers繁忙。
  
−
* Added the ability to specify ranges for Static Large Object (SLO) segments.
+
* 可以對靜態大型物件(Static Large Object, SLO)分段指定範圍。
  
−
* Allow SLO PUTs to forgo per-segment integrity checks. Previously, each segment referenced in the manifest also needed the correct etag and bytes setting. These fields now allow the "null" value to skip those particular checks on the given segment.
+
* 允許 SLO PUT 操作放棄預先分段完整性的檢查。之前方式是在 manifest 的每個分段引用,且也需要設定一個正確的 etag 與 bytes。這些欄位現在允許  設定 "null" 直來跳過這些特定的檢查。
  
−
* Replicator configurations now support an "rsync_module" value to allow for per-device rsync modules. This setting gives operators the ability to fine-tune replication traffic in a Swift cluster and isolate replication disk IO to a particular device. Please see the docs and sample config files for more information and examples.
+
* Replicator設定現在支援"rsync_module" 來允許每個設備rsync模組。此設定可以讓操作人員能夠控制並調整Swift叢集流量並且隔離複製硬碟的IO到指定的設備。情參閱文件檔和設定範例文件的詳細訊息。
  
−
* Ring changes
+
* Ring 的改變
−
** Partition placement no longer uses the port number to place partitions. This improves dispersion in small clusters running one object server per drive, and it does not affect dispersion in clusters running one object server per server.
+
** Partition 的配置不再使用port號來配置分區。在一個小型叢集運行一個object server提高分散性，並且他不會影響正在執行的object server。
−
** Added ring-builder-analyzer tool to more easily test and analyze a series of ring management operations.
+
** 新增 ring-builder-analyzer 工具來簡化測試與分析 ring 管理維護
−
** Ring validation now warns if a placement partition gets assigned to the same device multiple times. This happens when devices in the ring are unbalanced (e.g. two servers where one server has significantly more available capacity).
+
** Ring 驗證時如果一個設備被分配到同一區很多次就會跳出警告。這個情況發生在ring不平衡的時候(例如:兩個server其中一個server有多餘的空間大於另外一個)
  
−
* TempURL fixes (closes CVE-2015-5223)<p>Do not allow PUT tempurls to create pointers to other data. Specifically, disallow the creation of DLO object manifests via a PUT tempurl. This prevents discoverability attacks which can use any PUT tempurl to probe for private data by creating a DLO object manifest and then using the PUT tempurl to head the object.</p>
+
* TempURL被修復了(關閉 CVE-2015-5223)<p>不要允許 PUT tempurls 建立指向其他資料。具體來說,不允許透過 PUT tempurl 建立 DLO 物件 manifests。這防止發現性攻擊,這種攻擊能夠利用任何的 PUT tempurl 偵測到被 DLO 物件 manifest 建立的私有資料,並且使用 PUT tempurl 指向物件</p>
−
* Swift now emits StatsD metrics on a per-policy basis.
+
* Swift 現在會再每一個策略基礎上發送 StatsD metrics。
−
* Fixed an issue with Keystone integration where a COPY request to a service account may have succeeded even if a service token was not included in the request.
+
* 修復了一個 Keystone 整合問題,這問題會導致服務帳戶的 COPY 請求能成功，即使這個服務沒有 token 包含在這個請求中。.
−
* Bulk upload now treats user xattrs on files in the given archive as object metadata on the resulting created objects.
+
* 批量上傳現在在檔案上處理使用者 xattrs,在處理建立物件時,使用給定的存檔作為物件 metadata。
−
* Emit warning log in object replicator if "handoffs_first" or "handoff_delete" is set.
+
* 在物件複製中提交警告 Log，如果 "handoffs_first" 和 "handoff_delete" 有設定
−
* Enable object replicator's failure count in swift-recon.
+
* 允許在 Swift-recon 開啟物件複製失敗的次數
−
* Added storage policy support to dispersion tools.
+
* 在分散工具中新增支援儲存策略
−
* Support keystone v3 domains in swift-dispersion.
+
* 在 swift-dispersion 支援了 keystone v3 domains
−
* Added domain_remap information to the /info endpoint.
+
* 在 /info endpoint 新增了 domain_remap 資訊
−
* Added support for a "default_reseller_prefix" in domain_remap middleware config.
+
* 在 domain_remap 中介軟體配置中支援 “default_reseller_prefix”
−
* Allow rsync to use compression via a "rsync_compress" config. If set to true, compression is only enabled for an rsync to a device in a different region. In some cases, this can speed up cross-region replication data transfer.
+
* 透過設定 "rsync_compress" 配置,允許 rsync 使用壓縮。如果設定為 true，壓縮僅在不同區域 rsync 時生效。在一些情況下，這能加速跨領域複製時的資料傳輸。
−
* Added time synchronization check in swift-recon (the --time option).
+
* 在 swift-recon 中新增時間同步檢查(--time 參數)
−
* The account reaper now runs faster on large accounts.
+
* 一個大型的 accounts 上 account 收割機執行速度加快。
−
* Various other minor bug fixes and improvements.
+
* 各式各樣的其他小 Bug 修復與優化。
  
 
=== 升級提示 ===
 
=== 升級提示 ===
  
−
* Dependency changes
+
* 相依性改變
−
** Added six requirement. This is part of an ongoing effort to add support for Python 3.
+
** 新增 six 相依。這部分作為支援 Python 3 的一部分。
−
** Dropped support for Python 2.6.
+
** 捨棄對 Python 2.6 的支援。
−
* Config changes
+
* 配置改變
−
** Recent versions of Python restrict the number of headers allowed in a request to 100. This number may be too low for custom middleware. The new "extra_header_count" config value in swift.conf can be used to increase the number of headers allowed.
+
** 最近 Python 版本將請求 Headers 的數量限制為 100。對於客制化的中介軟體來說大低了。swift.conf 新的 "extra_header_count" 配置值能夠用來增加 Headers 的數量。
−
** Renamed "run_pause" setting to "interval" (current configs with run_pause still work). Future versions of Swift may remove the run_pause setting.
+
** 將 "run_pause" 設定為 "interval" (目前配置採用 run_pause 仍可以運作)。未來的版本將移除 run_pause。
−
* The versioned writes feature has been refactored and reimplemented as middleware. You should explicitly add the versioned_writes middleware to your proxy pipeline, but do not remove or disable the existing container server config setting ("allow_versions"), if it is currently enabled. The existing container server config setting enables existing containers to continue being versioned. Please see http://swift.openstack.org/middleware.html#how-to-enable-object-versioning-in-a-swift-cluster for further upgrade notes.
+
* 版本化的寫入功能已被重構，並且在中介軟體重新實現。需要明確的在 versioned_writes 中介軟體新增你的 proxy pipeline,但是不要去掉或者停用已經存在的Container 服務配置("allow_versions")。這個已經存在的 Container 服務配置開啟保證已經存在的 Container 繼續被版本化。更多詳細的升級資訊請參考：http://swift.openstack.org/middleware.html#how-to-enable-object-versioning-in-a-swift-cluster
  
−
== OpenStack Networking (Neutron) ==
+
== OpenStack 網路服務 (Neutron) ==
  
−
=== New Features ===
+
=== 新功能 ===
−
* Neutron now supports IPv6 Prefix Delegation for the automatic assignment of CIDRs to IPv6 subnets. For more information on the usage and configuration of this feature, see the [http://docs.openstack.org/networking-guide/adv_config_ipv6.html#prefix-delegation OpenStack Networking Guide].
+
* Neutron現在支援IPv6 Prefix Delegation，來自動分配IPv6子網路的CIDRs，此功能的詳細資訊與使用配置請參考 [http://docs.openstack.org/networking-guide/adv_config_ipv6.html#prefix-delegation OpenStack Networking Guide].
−
* Neutron now exposes a QoS API, initially offering bandwidth limitation on the port level. The API, CLI, configuration and additional information may be found here [http://docs.openstack.org/developer/neutron/devref/quality_of_service.html].
+
* Neutron現在公開了QoS API，而初步提供的頻寬為port level，API, CLI, 配置和其他訊息請參閱： [http://docs.openstack.org/developer/neutron/devref/quality_of_service.html].
−
* Router high availability (L3 HA / VRRP) now works when layer 2 population (l2pop) is enabled [https://bugs.launchpad.net/neutron/+bug/1365476].
+
* 路由的高可靠(L3 HA/VRRP)現在在第二層population(l2pop)被啟動時工作。 [https://bugs.launchpad.net/neutron/+bug/1365476].
−
* VPNaaS reference drivers now work with HA routers.
+
* VPNaaS相關驅動現在和HA路由器相容。
−
* Networks used for VRRP traffic for HA routers may now be configured to use a specific segmentation type or physical network tag [https://bugs.launchpad.net/neutron/+bug/1481443].
+
* Networks的HA路由器使用VRRP traffic 現在需要配置使用特定區段類型或實體網路標籤。 [https://bugs.launchpad.net/neutron/+bug/1481443].
−
* The OVS agent may now be restarted without affecting data plane connectivity.
+
* OVS agent重新啟動不會影響資料層連接。
−
* Neutron now offers role base access control (RBAC) for networks [http://specs.openstack.org/openstack/neutron-specs/specs/liberty/rbac-networks.html].
+
* Neutron網路現在支援role base access control。 [http://specs.openstack.org/openstack/neutron-specs/specs/liberty/rbac-networks.html].
 
** https://bugs.launchpad.net/neutron/+bug/1498790
 
** https://bugs.launchpad.net/neutron/+bug/1498790
−
* LBaaS V2 reference driver is now based on Octavia, an operator grade scalable, reliable Load Balancer platform.
+
* LBaaS V2 相關驅動現在是基於Octavia，一個operator級別的擴展、可靠的負載平衡平台。
−
* LBaaS V2 API is no longer experimental. It is now stable.
+
* LBaaS V2 API 目前已經穩定，不再是試驗版本。
−
* Neutron now provides a way for admins to manually schedule agents, allowing host resources to be tested before they are enabled for tenant use [https://github.com/openstack/neutron-specs/blob/master/specs/liberty/enable-new-agents.rst#user-documentation].
+
* Neutron現在提供admin手動調度agents，讓tenant使用之前使主機資源被測試。 [https://github.com/openstack/neutron-specs/blob/master/specs/liberty/enable-new-agents.rst#user-documentation].
−
* Neutron now has a pluggable IP address management framework, enabling the use of alternate or third-party IPAM. The original, non-pluggable version of IPAM is enabled by default.
+
* Neutron現在有一套pluggable IP的管理工具，可以選擇是否使用或第三方IPAM。當初，預設使用IPAM non-pluggable版本。
  
−
=== Deprecated and Removed Plugins and Drivers ===
+
=== 已棄用和移除的Plugin和Driver ===
−
* The metaplugin is removed in the Liberty release.
+
* metaplugin在Liberty版本中被刪除。
−
* The IBM SDN-VE monolithic plugin is removed in the Liberty release.
+
* IBM SDN-VE monolithic plugin在Liberty版本中被刪除。
−
* The Cisco N1kV monolithic plugin is removed in the Liberty release (replaced by the ML2 mechanism driver).
+
* Cisco N1kV monolithic plugin在Liberty版本中被刪除 (由ML2 mechanism driver取而代之)。
−
* The Embrane plugin is deprecated and will be removed in the Mitaka release.
+
* Embrane plugin被棄用，將在下一個版本Mitaka中刪除。
  
−
=== Deprecated Features ===
+
=== 已棄用的功能 ===
−
* The FWaaS API is marked as experimental for Liberty. Further, the current API will be removed in Mitaka and replaced with a new FWaaS API, which the team is in the process of developing.
+
* Liberty中FWaaS API被標記為試驗版本，此外，目前的API將會在下一個版本Mitaka被移除，且相關團隊已經在開發新的FWaaS API來取代。
−
* The LBaaS V1 API is marked as deprecated and is planned to be removed in a future release. Going forward, the LBaaS V2 API should be used.
+
* LBaaS V1 API已被標記為捨棄，並計畫在將來的版本中刪除。往後則應使用LBaaS V2 API。
−
* The 'external_network_bridge' option for the L3 agent has been deprecated in favor of a bridge_mapping with a physnet. For more information, see the "Network Node" section of this scenario in the networking guide: http://docs.openstack.org/networking-guide/scenario_legacy_ovs.html
+
* L3 agent 中的'external_network_bridge'選項已被棄用，支援pyhsnet的bridge_mapping。更多訊息請參考network guide中"Network Node"小節的場景 : http://docs.openstack.org/networking-guide/scenario_legacy_ovs.html
  
−
=== Performance Considerations ===
+
=== 影響效能的因素 ===
−
* The stock Trusty Tahr kernel (3.13) shows linear performance degradation when running "ip netns exec" as the number of namespaces increases.  In cases where scale is important, a later version kernel (e.g. 3.19) should be used. [WHICH VERSION OF 3.13 EXHIBITED THIS. MOST VERSIONS WILL HAVE THIS FIX ALREADY.]
+
* 舊版本的Trusty Tahr kernel (3.13) 在命名空間增加執行"ip netns exec"效能會出現的線性下樣。 在這樣的情況下可擴展性是很重要的，應該使用之後的kernel版本 (例如 3.19) 。 [在版本 3.13 出現的問題，大多數版本已經被修復了。]
 
<br />
 
<br />
−
  '''Note:''' This regression should be fixed in Trusty Thar since 3.13.0-36.63 and later kernel versions. For further references see: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1328088
+
  '''注意：''' 這個問題應該在Trusty Thar 3.13.0-36.63以及之後的版本被修復。更多訊息請參閱： https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1328088
  
−
* Creating Neutron-LBaaS load balancers in environments without hardware virtualization may be slow when using the Octavia driver.  This is due to QEMU using the TCG accelerator instead of the KVM accelerator in environments without hardware virtualization available.  We recommend enabling hardware virtualization on your compute nodes, or enabling nested virtualization when using the Octavia driver inside a virtual environment.  See the following link for details on setting up nested virtualization for DevStack running inside KVM: http://docs.openstack.org/developer/devstack/guides/devstack-with-nested-kvm.html.
+
使用Octavia驅動程式，建立Neutron-LBaaS負載平衡時，不使用硬體虛擬化將會導致效能低下，這是因為環境中QEMU使用TCG加速套件替代KVM加速套件而沒有使用KVM可用的硬體虛擬化。我們建議開啟運算節點的硬體虛擬化，或在使用Octavia驅動程式時使用巢狀虛擬化來代替虛擬環境。
 +
以下連結查看在DevStack中如何設定巢狀虛擬化來代替KVM：http://docs.openstack.org/developer/devstack/guides/devstack-with-nested-kvm.html
  
−
== OpenStack Compute (Nova) ==
+
== OpenStack 運算服務 (Nova) ==
  
 
=== 新功能 ===
 
=== 新功能 ===
Line 96: Line 97:
 
==== API ====
 
==== API ====
  
−
* Turned on v2.1 by default for all endpoints, v2.0 and v1.1 using a new compatibility mode, to make the transition transparent to existing API users (https://blueprints.launchpad.net/nova/+spec/api-relax-validation)
+
*在所有endpoints預設狀況下將開啟v2.1，v2.0和v1.1採用了全新的相容模式，已存在的API使用者使過度透明 (https://blueprints.launchpad.net/nova/+spec/api-relax-validation)
−
* Evacuate made more robust (partial) (https://blueprints.launchpad.net/nova/+spec/robustify-evacuate)
+
*撤下變得更穩健 (部分) (https://blueprints.launchpad.net/nova/+spec/robustify-evacuate)
−
* New "mark host down"/"force down" API for external high availability tools to notify Nova in the event of a host failure (http://specs.openstack.org/openstack/nova-specs/specs/liberty/approved/mark-host-down.html).
+
* 新的 "mark host down"/"force down" API外部高可用性工具在主機故障時通知Nova (http://specs.openstack.org/openstack/nova-specs/specs/liberty/approved/mark-host-down.html)
−
* Consolidate the APIs for getting consoles https://blueprints.launchpad.net/nova/+spec/consolidate-console-api
+
* 鞏固APIs獲取consolese https://blueprints.launchpad.net/nova/+spec/consolidate-console-api
−
* Show 'reserved' status in os-fixed-ips API  (https://blueprints.launchpad.net/nova/+spec/show-reserved-status-in-os-fixed-ips-api)
+
* 在os-fixed-ips API顯示 'reserved' 狀態 (https://blueprints.launchpad.net/nova/+spec/show-reserved-status-in-os-fixed-ips-api)
−
* Allow ip6 server search for non-admin (https://blueprints.launchpad.net/nova/+spec/allow-ip6-search-for-non-admin)
+
* 允許 ip6 server 尋找 non-admin (https://blueprints.launchpad.net/nova/+spec/allow-ip6-search-for-non-admin)
−
* Check flavor type before add tenant access (https://blueprints.launchpad.net/nova/+spec/check-flavor-type-before-add-tenant)
+
* 檢查 flavor 類型之前增加tenant access (https://blueprints.launchpad.net/nova/+spec/check-flavor-type-before-add-tenant)
−
* Make on_shared_storage flag optional in rebuild_instance  (https://blueprints.launchpad.net/nova/+spec/optional-on-shared-storage-flag-in-rebuild-instance)
+
* 使 on_shared_storage 標誌可選在 rebuild_instance  (https://blueprints.launchpad.net/nova/+spec/optional-on-shared-storage-flag-in-rebuild-instance)
−
* Policy checks have been removed from the database layer, so are now only at the API layer (https://blueprints.launchpad.net/nova/+spec/nova-api-policy-final-part)
+
* 策略檢查已從database層中移除，所以現在只在 API 層 (https://blueprints.launchpad.net/nova/+spec/nova-api-policy-final-part)
−
* Add VIF net-id in virtual interfaces list API Response (https://blueprints.launchpad.net/nova/+spec/add-vif-net-id-in-vif-list)
+
* 增加 VIF 網路識別碼在虛擬介面列表 API 回覆 (https://blueprints.launchpad.net/nova/+spec/add-vif-net-id-in-vif-list)
−
* Convert glance image meta properties into NovaObject (partial) (https://blueprints.launchpad.net/nova/+spec/convert-image-meta-into-nova-object)
+
* 允許最高管理權限使用者瀏覽任何 keypair (https://blueprints.launchpad.net/nova/+spec/admin-query-any-keypair)
−
* Adding locking information in server get response (https://blueprints.launchpad.net/nova/+spec/add-locking-information-in-server-get-response)
+
* Metadata: 增加 project_id 到 liberty版本的metadata (https://blueprints.launchpad.net/nova/+spec/project-id-in-metadata)
−
* Allow admin users to view any keypair (https://blueprints.launchpad.net/nova/+spec/admin-query-any-keypair)
+
* Metadata: 加入路由器到網路樣板引擎 (https://blueprints.launchpad.net/nova/+spec/network-template-routes-injection)
−
* Metadata: Add project_id to liberty-versioned metadata (https://blueprints.launchpad.net/nova/+spec/project-id-in-metadata)
+
* Metadata: API: 代理neutron的設定配置guest instance (部分) (https://blueprints.launchpad.net/nova/+spec/metadata-service-network-info)
−
* Metadata: inject routes into network template engine (https://blueprints.launchpad.net/nova/+spec/network-template-routes-injection)
 
−
* Metadata: API: Proxy neutron configuration to guest instance (partial) (https://blueprints.launchpad.net/nova/+spec/metadata-service-network-info)
 
  
 
==== Scheduler ====
 
==== Scheduler ====
  
−
Architectural evolution on the scheduler has continued, along with key bug fixes:
+
在Scheduler架構演變扔在持續中，以及關鍵的bug修復:
−
* Adds object model for a launch request spec (partially complete) (https://blueprints.launchpad.net/nova/+spec/request-spec-object)
+
* 增加物件模組給一個啟動規範 (部分完成) (https://blueprints.launchpad.net/nova/+spec/request-spec-object)
−
* Move resource allocation ratios from scheduler to resource tracker (https://blueprints.launchpad.net/nova/+spec/allocation-ratio-to-resource-tracker)
+
* 將資源分配比率從scheduler到資源追蹤 (https://blueprints.launchpad.net/nova/+spec/allocation-ratio-to-resource-tracker)
−
* Fix resource tracking for operations that move instances between hosts  (https://blueprints.launchpad.net/nova/+spec/migration-fix-resource-tracking)
+
* 解決資源追蹤對於移動主機之間的instances操作 (https://blueprints.launchpad.net/nova/+spec/migration-fix-resource-tracking)
−
* Improved user feedback when returning ''NoValidHost'' from the scheduler (http://specs.openstack.org/openstack/nova-specs/specs/liberty/approved/add_exceeded_max_retries_exception.html).
+
* 改善了使用者回饋當從scheduler回傳''NoValidHost'' (http://specs.openstack.org/openstack/nova-specs/specs/liberty/approved/add_exceeded_max_retries_exception.html).
  
 
==== Cells v2 ====
 
==== Cells v2 ====
  
−
Cells v2 is not currently in a usable state, but we have added some more supporting infrastructure:
+
Cells v2 目前還是處於不能用的狀態, 但我們增加了一些配套基礎設施:
  
−
* Cells host mapping (https://blueprints.launchpad.net/nova/+spec/cells-host-mapping)
+
* Cells 主機對應(https://blueprints.launchpad.net/nova/+spec/cells-host-mapping)
−
* Cells instance migration (https://blueprints.launchpad.net/nova/+spec/cells-instance-migration)
+
* Cells instance 遷移 (https://blueprints.launchpad.net/nova/+spec/cells-instance-migration)
  
−
==== Compute Driver Features ====
+
==== Compute Driver 功能 ====
  
 
===== Libvirt =====
 
===== Libvirt =====
  
−
* Moved to using ''os-brick'' library for Libvirt volume drivers allowing sharing of logic for volume discovery and removal between Nova and Cinder (http://specs.openstack.org/openstack/nova-specs/specs/liberty/implemented/use-os-brick-library.html).
+
* 使用''os-brick'' 函式庫給Libvirt volume drivers 使得共享邏輯Nova 與 Cinder之間對於volume發現和去除 (http://specs.openstack.org/openstack/nova-specs/specs/liberty/implemented/use-os-brick-library.html).
−
* Added ''live_migration_completion_timeout'' and ''live_migration_progress_timeout'' configuration keys to assist with capping the maximum time a live migration should be allowed to run, particularly when progress has halted (https://launchpad.net/bugs/1429220).
+
* 增加 ''live_migration_completion_timeout'' 和 ''live_migration_progress_timeout'' 配置 keys 以協助最大時間的動態遷移應被允許運行，尤其是當進度已停止  (https://launchpad.net/bugs/1429220).
−
* Added logic to manage and scale the maximum downtime setting during live migration to provide larger guest sizes with a better chance of completing migration successfully (https://launchpad.net/bugs/1429220).
+
* 增加邏輯管理並在即時遷移時擴大停機時間的設置，以提供更大的guest sizes有更好的機會成功完成遷移(https://launchpad.net/bugs/1429220).
−
* Limit parallel live migrations in progress (https://launchpad.net/bugs/1478108).
+
* 限制執行並行即時遷移 (https://launchpad.net/bugs/1478108).
 
* Optionally enable the scaling of VirtIO queues in relation to guest vCPUs if the ''hw_vif_multiqueue_enabled'' image property is set to 'true' (default: 'false') providing enhanced network performance for guests with more than one vCPU, many concurrent connections, and/or relatively large packet sizes (http://specs.openstack.org/openstack/nova-specs/specs/liberty/implemented/libvirt-virtiomq.html).
 
* Optionally enable the scaling of VirtIO queues in relation to guest vCPUs if the ''hw_vif_multiqueue_enabled'' image property is set to 'true' (default: 'false') providing enhanced network performance for guests with more than one vCPU, many concurrent connections, and/or relatively large packet sizes (http://specs.openstack.org/openstack/nova-specs/specs/liberty/implemented/libvirt-virtiomq.html).
−
* Allow admin to set guest ''Administrator''/''root'' password if QEMU guest agent is installed and enabled via the ''hw_qemu_guest_agent'' image property (http://specs.openstack.org/openstack/nova-specs/specs/liberty/approved/libvirt-set-admin-password.html).
+
* 允許管理者設定guest'Administrator''/''root''密碼當 QEMU guest 安裝與啟用通過 ''hw_qemu_guest_agent'' image屬性(http://specs.openstack.org/openstack/nova-specs/specs/liberty/approved/libvirt-set-admin-password.html).
−
* New VIF type to allow routing VM data instead of bridging it (https://blueprints.launchpad.net/nova/+spec/vif-type-tap)
+
* 新VIF 類型允許路由虛擬機資料而不是橋接 (https://blueprints.launchpad.net/nova/+spec/vif-type-tap)
−
* Add support for InfiniBand SR-IOV for libvirt virtualization (https://blueprints.launchpad.net/nova/+spec/vif-driver-ib-passthrough)
+
* 增加支援 InfiniBand SR-IOV 的libvirt虛擬化 (https://blueprints.launchpad.net/nova/+spec/vif-driver-ib-passthrough)
−
* Add MacVTap as new virtual interface type for libvirt virtualization (https://blueprints.launchpad.net/nova/+spec/libvirt-macvtap-vif)
+
* 增加MacVTap作為libvirt的虛擬化新的虛擬接口類型 (https://blueprints.launchpad.net/nova/+spec/libvirt-macvtap-vif)
−
* Consolidate FS-style libvirt drivers (https://blueprints.launchpad.net/nova/+spec/consolidate-libvirt-fs-volume-drivers)
+
* 整合 FS-style libvirt drivers (https://blueprints.launchpad.net/nova/+spec/consolidate-libvirt-fs-volume-drivers)
 
* EMC ScaleIO Data Client (SDC) Libvirt Volume Driver (https://blueprints.launchpad.net/nova/+spec/emc-sdc-libvirt-volume-driver)
 
* EMC ScaleIO Data Client (SDC) Libvirt Volume Driver (https://blueprints.launchpad.net/nova/+spec/emc-sdc-libvirt-volume-driver)
−
* Implementation of remote FS driver based on `rsync` for libvirt (https://blueprints.launchpad.net/nova/+spec/remote-fs-driver)
+
* 實現遠端 FS driver 基於 `rsync` libvirt 上 (https://blueprints.launchpad.net/nova/+spec/remote-fs-driver)
−
* Virtuozzo containers boot from volume (https://blueprints.launchpad.net/nova/+spec/virtuozzo-container-boot-from-volume)
+
* Virtuozzo containers 從volume啟動 (https://blueprints.launchpad.net/nova/+spec/virtuozzo-container-boot-from-volume)
−
* Add HGST volume type support w/os-brick (https://blueprints.launchpad.net/nova/+spec/add-os-brick-volume-driver-hgst-solutions)
+
* 增加 HGST volume 類型支援 w/os-brick (https://blueprints.launchpad.net/nova/+spec/add-os-brick-volume-driver-hgst-solutions)
−
* virtio-net multiqueue (partial) (https://blueprints.launchpad.net/nova/+spec/libvirt-virtio-net-multiqueue)
+
* virtio-net multiqueue (部分) (https://blueprints.launchpad.net/nova/+spec/libvirt-virtio-net-multiqueue)
  
 
===== VMware =====
 
===== VMware =====
  
 
* VMware driver domain metadata (https://blueprints.launchpad.net/nova/+spec/vmware-driver-domain-metadata)
 
* VMware driver domain metadata (https://blueprints.launchpad.net/nova/+spec/vmware-driver-domain-metadata)
−
* Enable setting memory, disk and vnic limits (partial) (https://blueprints.launchpad.net/nova/+spec/vmware-limits)
+
* 啟動設定記憶體、硬碟和虛擬網卡的限制 (partial) (https://blueprints.launchpad.net/nova/+spec/vmware-limits)
−
* Native HTML5 consoles for VMware (https://blueprints.launchpad.net/nova/+spec/vmware-webmks-console)
+
* 原生VMware的HTML5 管理介面 (https://blueprints.launchpad.net/nova/+spec/vmware-webmks-console)
−
* Support swap disk in VMware driver (https://blueprints.launchpad.net/nova/+spec/vmware-swap-support)
+
* 支援 swap 磁區在VMware driver (https://blueprints.launchpad.net/nova/+spec/vmware-swap-support)
−
* VMware NSXv Support (https://blueprints.launchpad.net/nova/+spec/vmware-nsxv-support)
+
* 支援VMware NSXv (https://blueprints.launchpad.net/nova/+spec/vmware-nsxv-support)
−
* VMware: Support for console log in the VMware driver (partial) (https://blueprints.launchpad.net/nova/+spec/vmware-console-log)
+
* VMware: 支援管理介面日誌在VMware driver (部分) (https://blueprints.launchpad.net/nova/+spec/vmware-console-log)
  
 
===== Hyper-V =====
 
===== Hyper-V =====
  
−
* Hyper-V unit tests refactoring (continued + partial) (https://blueprints.launchpad.net/nova/+spec/hyper-v-test-refactoring-liberty)
+
* Hyper-V 單元測試重構 (持續 + 部分) (https://blueprints.launchpad.net/nova/+spec/hyper-v-test-refactoring-liberty)
  
 
===== Ironic =====
 
===== Ironic =====
  
−
* Pass down the instance name to Ironic driver (https://blueprints.launchpad.net/nova/+spec/pass-down-instance-name-to-ironic-driver)
+
* 傳遞instance名稱到Ironic driver (https://blueprints.launchpad.net/nova/+spec/pass-down-instance-name-to-ironic-driver)
  
−
==== Other Features ====
+
==== 其他功能 ====
  
−
* Added support for specifying multiple ''instance_type'' names to the ''AggregateTypeAffinityFilter'' (https://blueprints.launchpad.net/nova/+spec/aggregatetypeaffinityfilter-multi-value-support).
+
* 增加了指定多個對''instance_type'' 名稱於 ''AggregateTypeAffinityFilter''的支援 (https://blueprints.launchpad.net/nova/+spec/aggregatetypeaffinityfilter-multi-value-support).
−
* Added experimental online DB schema change option (https://blueprints.launchpad.net/nova/+spec/online-schema-changes)
+
* 增加了實驗線上 DB模式更改選項 (https://blueprints.launchpad.net/nova/+spec/online-schema-changes)
−
* Improved example config file generation (https://blueprints.launchpad.net/nova/+spec/oslo-config-generator)
+
* 改善了範例配置文件產生 (https://blueprints.launchpad.net/nova/+spec/oslo-config-generator)
−
* Add DB2 as an option for backend database (https://blueprints.launchpad.net/nova/+spec/db2-database)
+
* 增加 DB2 做為後端database的選項 (https://blueprints.launchpad.net/nova/+spec/db2-database)
−
* Cells: different_cells scheduler filter (https://blueprints.launchpad.net/nova/+spec/cells-scheduler-anti-affinity-filter)
+
* Cells: different_cells scheduler 過濾器 (https://blueprints.launchpad.net/nova/+spec/cells-scheduler-anti-affinity-filter)
−
* Started on the road towards Python 3.4 support (https://blueprints.launchpad.net/nova/+spec/nova-python3)
+
* 開始邁向對 Python 3.4 的支援 (https://blueprints.launchpad.net/nova/+spec/nova-python3)
−
* Ability to run some Nova services under Apache2 (https://blueprints.launchpad.net/nova/+spec/run-nova-services-under-apache2)
+
* 能夠在Apache2上運行一些Nova服務 (https://blueprints.launchpad.net/nova/+spec/run-nova-services-under-apache2)
−
* Upgrade infrastructure: Add a universal service version number (https://blueprints.launchpad.net/nova/+spec/service-version-number)
+
* 升級基礎設施: 增加一個全面服務的版本號 (https://blueprints.launchpad.net/nova/+spec/service-version-number)
−
* Running Nova with rootwrap as a daemon (https://blueprints.launchpad.net/nova/+spec/nova-rootwrap-daemon-mode)
+
* 運行 Nova 後台程序在rootwrap (https://blueprints.launchpad.net/nova/+spec/nova-rootwrap-daemon-mode)
−
* Remove 'scheduled_at' column in nova instances table (https://blueprints.launchpad.net/nova/+spec/cleanup-scheduled-at)
+
* 移除 'scheduled_at' 在nova instances列表 (https://blueprints.launchpad.net/nova/+spec/cleanup-scheduled-at)
−
* A new config option "handle_virt_lifecycle_events" in the DEFAULT group was added to allow disabling the event callback handling for instance lifecycle events from the virt driver (which is only implemented by the libvirt and hyper-v drivers in Liberty). This mostly serves as a workaround in case the callbacks are racing under heavy load and causing problems like shutting down running instances. See https://review.openstack.org/#/c/159275/ for details.
+
* 在一個預設群組增加一個新的配置選項"handle_virt_lifecycle_events"去允許禁用事件帶回處理從virt driver對於instance生命週期事件(這是由僅在Liberty的libvirt和hyper-v drivers中實現 )。這主要是作為一種代替方法以防回調都在競相重負載下造成類似關閉正常運作的instance問題 請參閱https://review.openstack.org/#/c/159275/ 了解詳細情形.
  
−
=== Upgrade Notes ===
+
=== 升級提示 ===
  
−
* If you are coming from Kilo stable, please make sure you have fully upgraded to the latest release of that lineage before deploying Liberty. Due to bug https://bugs.launchpad.net/nova/+bug/1474074 versions of Kilo from before the fix will be problematic when talking to Liberty nodes.
+
* 如果你是從Kilo版本來的，再升級到Liberty之前請先升級到最新版本。由於bug https://bugs.launchpad.net/nova/+bug/1474074 修正從Kilo版本訪問Liberty節版本節點問題
−
* Allocation ratios for RAM and CPU are now defined within the nova-compute service (so per compute node). Ratios also need to be provided for the scheduler service. Depending on whether a compute node is running Kilo or Liberty, the allocation ratios will behave differently : ''if the compute node is running Kilo'' then the CPU and RAM allocation ratios for that compute node will be the ones defaulted in the controller's nova.conf file.''Or, if the compute node is Liberty'' then you'll be able to set a per-compute allocation ratio for both CPU and RAM. In order to leave the operator providing the allocation ratios to all the compute nodes, the default allocation ratio will be set in nova.conf to 0.0 (even for the controller). That doesn't mean that allocation ratios will actually be 0.0, just that the operator needs to provide those '''before the next release (ie. Mitaka)'''. To be clear, the default allocation ratios are still 16.0 for cpu_allocation_ratio and 1.5 for ram_allocation_ratio.
+
* RAM 和 CPU分配比率現在是由nova-compute所定義的(所以每個compute節點)。分配率也需要提供scheduler服務。取決於compute節點是否運行 Kilo 或是 Liberty，分配比率表現不同 : ''如果compute節點運行Kilo''該compute的節點CPU and RAM預設設定將會是在controller的nova.conf上，''或是compute節點是Liberty''那麼你就可以配置compute分配率為CPU and RAM。為了給操作者提供的分配率所有compute節點，預設分配比勒將是在nova.conf設定為0.0(即使對於controller)。這並不代表分配率實際上是0.0，指示操作者提供那些'''在下一個版本之前 (例如 Mitaka)'''。需要了解的是，預設配置扔然是16.0為cpu_allocation_ratio 和 1.5為ram_allocation_ratio。
−
* nova-compute should be upgraded to Liberty code before upgrading Neutron services per the new "network-vif-deleted" event: https://review.openstack.org/#/c/187871/
+
* 升級Neutron服務"network-vif-deleted"之前nova-compute應該升級到Liberty版本事件event: https://review.openstack.org/#/c/187871/
−
* Rootwrap filters must be updated after release to add the 'touch' command.
+
* Rootwrap過濾必須升級之後版本加入 'touch'指令。
−
** There is a race condition between imagebackend and imagecache mentioned in the Launchpad Bug [https://bugs.launchpad.net/nova/+bug/1256838 1256838].  
+
** 在Launchpad中bug提到 imagebackend 和 imagecache之間的條件競爭 [https://bugs.launchpad.net/nova/+bug/1256838 1256838].  
−
** In this case if base image is deleted by ImageCacheManager while imagebackend is copying the image to instance path, then the instance goes in to error state.
+
** 在這情況下如果base image被 ImageCacheManager刪除當 imagebackend的image複製到instance路徑，那麼instance會出現錯誤狀態
−
** In order to resolve this issue, there is a need to add 'touch' command in compute.filters along with the change https://review.openstack.org/#/c/217579/.
+
** 為了解決這個問題，有必要改變並增加在compute.filters 'touch'指令 https://review.openstack.org/#/c/217579/.
−
** In case of a race condition, when libvirt has changed the base file ownership to libvirt-qemu while imagebackend is copying the image, then we get permission denied error on updating the file access time using os.utime. To resolve this error we need to update the base file access time with root user privileges using 'touch' command.
+
** 在案例競爭條件，當libvirt已經改變基本文件所有權 libvirt-qemu同時imagebackend被複製image，然後我們使用os.utime更新檔案時發生拒絕錯誤。要解決這個錯誤我們需要使用root使用者權限去更新存取'touch'指令。
−
* The ''DiskFilter'' is now part of the ''scheduler_default_filters'' in Liberty per https://review.openstack.org/#/c/207942/ .
+
* ''DiskFilter''現在是由部分 ''scheduler_default_filters'' 在Liberty https://review.openstack.org/#/c/207942/
−
* Per https://review.openstack.org/#/c/103916/ you can now only map one vCenter cluster to a single nova-compute node.
+
* 現在只能對應一個vCenter 叢集到一個nova-compute節點 https://review.openstack.org/#/c/103916/
−
* The Libvirt driver ''parallels'' has been renamed to ''virtuozzo''
+
* Libvirt driver ''parallels'' 已經更名為 ''virtuozzo''
−
* Orphaned tables - ''iscsi_targets'', ''volumes'' - have been removed.
+
* Orphaned tables - ''iscsi_targets'', ''volumes'' - 已經被刪除
−
* The default paste.ini has been updated to use the new v2.1 API for all endpoints, and the v3 endpoint has been removed. A compatibility mode middlewear is used to relax the v2.1 validation for the /v2 and /v1.1 endpoints.
+
* 預設paste.ini已經被所有節點更新使用v2.1 API，而v3 節點已經被移除。相容模式middlewear是用來放寬v2.1對/v2 和 /v1.1驗證
−
* The code for DB schema downgrades has now been removed: https://blueprints.launchpad.net/nova/+spec/nova-no-downward-sql-migration
+
* 對於DB模式降階代碼已經被刪除 : https://blueprints.launchpad.net/nova/+spec/nova-no-downward-sql-migration
−
* The default DB driver we test against is now pymysql rather than Python-MySQL
+
* 預設DB driver我們目前測試是在pymysql 而不是Python-MySQL
−
* The "powervm" hv_type shim has been removed. This only affects users of the [https://github.com/stackforge/powervc-driver PowerVC driver on stackforge] which are using older images with hv_type=powervm in the image metadata.
+
* "powervm" hv_type shim 已經被移除。這只會影響[https://github.com/stackforge/powervc-driver PowerVC driver on stackforge]哪個使用舊的images與with hv_type=powervm在image metadata
−
* The minimum required version of libvirt in the Mitaka release will be 0.10.2. Support for libvirt < 0.10.2 is deprecated in Liberty: https://review.openstack.org/#/c/183220/
+
* libvirt在Mitaka最低需求版本將會是0.10.2。libvirt本本 < 0.10.2將不再 Liberty使用: https://review.openstack.org/#/c/183220/
−
* The libvirt.remove_unused_kernels config option is deprecated for removal and now defaults to True: https://review.openstack.org/#/c/182315/
+
* libvirt.remove_unused_kernels設定選項已經廢除，現在預設為True: https://review.openstack.org/#/c/182315/
  
−
=== Deprecated Features ===
+
=== 已棄用的功能 ===
  
−
* The ability to disable in tree API extensions has been deprecated (https://blueprints.launchpad.net/nova/+spec/nova-api-deprecate-extensions)
+
* 在禁用tree API擴展的能力已經被棄用 (https://blueprints.launchpad.net/nova/+spec/nova-api-deprecate-extensions)
−
* The novaclient.v1_1 module has been deprecated [[https://git.openstack.org/cgit/openstack/python-novaclient/commit/?id=61ef35fe79e2a3a76987a92f9ee2db0bf1f6e651]][[https://git.openstack.org/cgit/openstack/python-novaclient/commit/?id=0a60aae852d2688861d0b4ba097a1a00529f0611]] since 2.21.0 and we are going to remove it in the first python-novaclient release in Mitaka.
+
*從 2.21.0開始novaclient.v1_1 模組已經被棄用 [[https://git.openstack.org/cgit/openstack/python-novaclient/commit/?id=61ef35fe79e2a3a76987a92f9ee2db0bf1f6e651]][[https://git.openstack.org/cgit/openstack/python-novaclient/commit/?id=0a60aae852d2688861d0b4ba097a1a00529f0611]] 我們將會在第一個Mitaka版本釋出移除python-novaclient Mitaka.
−
* Method `novaclient.client.get_client_class` is deprecated [[https://git.openstack.org/cgit/openstack/python-novaclient/commit/?id=147a1a6ee421f9a45a562f013e233d29d43258e4]] since 2.29.0.  The method will be removed in Mitaka.
+
*從2.29.0開始方法`novaclient.client.get_client_class` 已經過時 [[https://git.openstack.org/cgit/openstack/python-novaclient/commit/?id=147a1a6ee421f9a45a562f013e233d29d43258e4]] 該方法將在Mitaka版本刪除。
−
* The ''mute_weight_value'' option on weighers has been deprecated, including for use with Cells.
+
* weighers上使用''mute_weight_value''已經被否決， 包括使用Cells。
−
* The ''remove_unused_kernels'' configuration option for the Libvirt driver is now deprecated.
+
* '在Libvirt driver上使用''remove_unused_kernels'' 已經不被使用.
−
* The minimum recommended version of vCenter for use with the ''vcenter'' driver is now 5.1.0. In Liberty this is logged as a warning, in Mitaka support for versions lower than 5.1.0 will be removed.
+
* 目前使用的''vcenter'' driver最小版本為5.1.0，在 Liberty版本會跳出警告訊息，在Mitaka版本低於5.1.0將會被刪除不使用
−
* API v3 specific components have all been deprecated and removed from the default paste.ini
+
* API v3 將會不再使用，並在paste.ini中刪除
  
−
== OpenStack Telemetry (Ceilometer) ==
+
== OpenStack 計量服務 (Ceilometer) ==
  
−
=== Key New Features ===
+
=== 關鍵的新功能 ===
−
* Creation of Aodh to handle alarming service.
+
* 創建Aodh來處理警報功能。
−
* Metadata caching - reduced load of nova API polling.
+
* Metadata caching - 減少nova API輪詢(polling)的負載。
−
* Declarative meters
+
* meters的聲明
−
** Ability to generate meters by defining meter definition template.
+
** 能夠根據定義meter樣板來產生meters。
−
** Ability to define specific SNMP meters to poll.
+
** 能夠輪詢(poll)特別定義的SNMP。
−
* Support for data publishing from Ceilometer to Gnocchi.
+
* 支援資料從Ceilometer發佈至Gnocchi。
−
* Mandatory limit - limit restricted querying is enforced. The limit must be explicitly provided on queries, otherwise the result set is restricted to a default limit.
+
* 強制limit - limit強制查詢執行。limit必須明確地提供給查詢，否則結果強制設為默認limit。
−
* Distributed, coordinated notification agents - support for workload partitioning across multiple notification agents.
+
* 分散, 協調notification agents - 支援工作負載分割跨多個notification agents。
−
* Events RBAC support.
+
* Events RBAC 支援。
−
* PowerVM hypervisor support.
+
* PowerVM hypervisor 支援。
−
* Improved MongoDB query support - performance improvement to statistic calculations.
+
* 改善MongoDB查詢支援 - 改善statistic calculations.。
−
* Additional meter support:
+
* 其他meter支援 :
 
** Magnum meters
 
** Magnum meters
 
** DBaaS meters
 
** DBaaS meters
 
** DNSaaS meters
 
** DNSaaS meters
  
−
==== Gnocchi Features ====
+
==== Gnocchi功能 ====
−
* Initial influxdb driver implemented.
+
* 實現第一個版本的influxdb driver。
  
−
==== Aodh Features ====
+
==== Aodh功能 ====
−
* Event alarms - ability to trigger an action when an event is received.
+
* 事件警報 - 當接收到事件能夠觸發一個動作。
−
* Trust support in alarms [https://blueprints.launchpad.net/ceilometer/+spec/trust-alarm-notifier link].
+
* 警報的信任支持 [https://blueprints.launchpad.net/ceilometer/+spec/trust-alarm-notifier link].
  
−
=== Upgrade Notes ===
+
=== 升級提示 ===
−
* The name of some middleware used by ceilometer changed in a backward incompatible way. Before upgrading, edit the <code>paste.ini</code> file for ceilometer to change <code>oslo.middleware</code> to <code>oslo_middleware</code>. For example, using <nowiki>sed -ri 's/oslo\.middleware/oslo_middleware/' api_paste.ini</nowiki>
+
* ceilometer使用的一些middleware名字改變採用向後不相容的方式。 再升級之前， 編輯 <code>paste.ini</code> 檔案，修改 <code>oslo.middleware</code> 為 <code>oslo_middleware</code>. 例如：使用 <nowiki>sed -ri 's/oslo\.middleware/oslo_middleware/' api_paste.ini</nowiki>
−
* The notification agent is a core service to collecting data in Ceilometer. It now handles all transformations and publishing. Polling agents now defer all processing to notification agents, and must be deployed in tandem.
+
* Ceilometer中notification agent是收集資料的核心服務，它處理所有的transformations和publishing。 Polling agents現在延緩所有processing到notification agents，且必須部署為tandem。
−
* A mandatory limit is applied to each request. If no limit is given, it will be restricted to a default limit.
+
* 強制limit添加到每個請求中，如果沒有limit，將會被強制視為預設limit。
  
−
=== Deprecated Features ===
+
=== 已棄用的功能 ===
−
* Ceilometer Alarms is deprecated in favour or Aodh.
+
* 不推薦使用Ceilometer Alarms，支持使用Aodh。
−
* RPC publisher and collector is deprecated in favour of a topic based notifier publisher.
+
* 不推薦使用RPC publisher和collector，支持使用topic based notifier publisher。
−
* Non-metric meters are still deprecated, and are to be removed in a future release.
+
* 依然不推薦使用Non-metric meters，且在未來版本將被移除。
  
−
== OpenStack Identity (Keystone) ==
+
== OpenStack 身份驗證服務 (Keystone) ==
  
−
=== Key New Features ===
+
=== 新功能 ===
  
−
* '''''Experimental''''': Domain specific configuration options can be stored in SQL instead of configuration files, using the new REST APIs.
+
* '''''實驗性''''': Domain 特定設定選項可以儲存在SQL代替設定文件, 使用新的REST APIs.
−
* '''''Experimental''''': Keystone now supports tokenless authorization with X.509 SSL client certificate.
+
* '''''實驗性''''': Keystone 現在支援不用 token授權， 使用 X.509 SSL 使用者驗證.
−
* Configuring per-Identity Provider WebSSO is now supported.
+
* 現在支援per-Identity配置WebSSO.
−
* <code>openstack_user_domain</code> and <code>openstack_project_domain</code> attributes were added to SAML assertion in order to map user and project domains, respectively.
+
* <code>openstack_user_domain</code> 和 <code>openstack_project_domain</code> 屬性增加到SAML判定，用來分別對應用戶與project domains
−
* The credentials list call can now have its results filtered by credential type.
+
* credentials 列表的調用現在能夠使用credential 類型進行過濾.
−
* Support was improved for out-of-tree drivers by defining stable Driver Interfaces.
+
* 支持優化out-of-tree drivers 定義穩定Driver Interfaces.
−
* Several features were hardened, including Fernet tokens, Federation, domain specific configurations from database and role assignments.
+
* 一些功能進行了加強，包括Fernet tokens, Federation, 從資料庫指定domain和角色分配
−
* Certain variables in keystone.conf now have options, which determine if the user's setting is valid.
+
* keystone.conf現在有了新的選項，用來判定使用者設定是不是有效的
  
−
=== Upgrade Notes ===
+
=== 升級提示 ===
  
−
* The EC2 token middleware, deprecated in Juno, is no longer available in keystone. It has been moved to the keystonemiddleware package.
+
* EC2 token middleware, 在Juno版本已經捨棄, keystone已經不存在. 已經完全被移到keystonemiddleware package中.
−
* The <code>compute_port configuration</code> option, deprecated in Juno, is no longer available.
+
* <code>compute_port configuration</code> 選項, 在Juno版本中已經不使用,已經不存在.
−
* The XML middleware stub has been removed, so references to it must be removed from the <code>keystone-paste.ini</code> configuration file.
+
* XML middleware 已經完全被刪除, 所以相關配置也從 <code>keystone-paste.ini</code> 設定檔中刪除.
−
* stats_monitoring and stats_reporting paste filters have been removed, so references to it must be removed from the <code>keystone-paste.ini</code> configuration file.
+
* stats_monitoring 和 stats_reporting 中的篩選器已經被刪除,所以相關配置檔案也從 <code>keystone-paste.ini</code> 移除.
−
* The external authentication plugins ExternalDefault, ExternalDomain, LegacyDefaultDomain, and LegacyDomain, deprecated in Icehouse, are no longer available.
+
* 而外認證的plugin ExternalDefault, ExternalDomain, LegacyDefaultDomain, 與 LegacyDomain, 在Icehouse版本中已經不再使用.
−
* <code>keystone.conf</code> now references entrypoint names for drivers. For example, the drivers are now specified as "sql", "ldap", "uuid", rather than the full module path. See the sample configuration file for other examples.
+
* <code>keystone.conf</code> 現在為drivers關係入口.例如, drivers現在被定義成 "sql", "ldap", "uuid", 而不是一個完整的路徑.查看設定檔案中的範例
−
* We now expose entrypoints for the <code>keystone-manage</code> command instead of a file.
+
* 我們現在為<code>keystone-manage</code> 公開entrypoints指令取代文件.
−
* Schema downgrades via <code>keystone-manage db_sync</code> are no longer supported. Only upgrades are supported.
+
* 聽過架構<code>keystone-manage db_sync</code> 降級已經不再支援. 僅支援升級.
−
* Features that were "extensions" in previous releases (OAuth delegation, Federated Identity support, Endpoint Policy, etc) are now enabled by default.
+
* 之前版本增加的"extensions"功能 (OAuth delegation, Federated Identity support, Endpoint Policy, etc) 目前預設都是開啟.
−
* A new <code>secure_proxy_ssl_header</code> configuration option is available when running keystone behind a proxy.
+
* 一個新的<code>secure_proxy_ssl_header</code> 設定選項，用於keystone運行在proxy之後的情形.
−
* Several configuration options have been deprecated, renamed, or moved to new sections in the <code>keystone.conf</code> file.
+
* 一些設定選項已經不再使用，重新命名或是移動到新的地方在<code>keystone.conf</code>文件.
−
* Domain name information can now be used in policy rules with the attribute <code>domain_name</code>.
+
* Domain name 資訊現在可以在策略規則與屬性<code>domain_name</code>.
  
−
=== Deprecated Features ===
+
=== 已棄用的功能 ===
  
−
* Running Keystone in Eventlet remains deprecated and will be removed in the Mitaka release.
+
* 在Eventlet運行Keystone 依然不建議使用，將Mitaka版本中刪除.
−
* Using LDAP as the resource backend, i.e for projects and domains, is now deprecated and will be removed in the Mitaka release.
+
* 使用LDAP 做為後端的資源, 例如projects 和 domains, 目前已經不再使用，在Mitaka版本將刪除.
−
* Using the full path to the driver class is deprecated in favor of using the entrypoint. In the Mitaka release, the entrypoint must be used.
+
* 使用完整路徑driver已經不建議使用，使用entrypoint的方式。在Mitaka版本，entrypoint 必須被使用.  
−
* In the [resource] and [role] sections of the <code>keystone.conf</code> file, not specifying the driver and using the assignment driver is deprecated. In the Mitaka release, the resource and role drivers will default to the SQL driver.
+
* 在<code>keystone.conf</code>中[resource] 和 [role]不建議使用指定driver或是不指定driver.在Mitaka版本釋出 resource 和 role drivers預設會使用SQL driver.
−
* In <code>keystone-paste.ini</code>, using <code>paste.filter_factory</code> is deprecated in favor of the "use" directive, specifying an entrypoint.
+
* 在<code>keystone-paste.ini</code>, 使用<code>paste.filter_factory</code> 不建議使用，因為"use" 指令，指定entrypoint.
−
* Not specifying a domain during a create user, group or project call, which relied on falling back to the default domain, is now deprecated and will be removed in the N release.
+
* 不指定domain新增user、group和project，在有問題的情況下他會回到預設的domain，目前不建議使用，並且在N版本終將會刪除.
−
* Certain deprecated methods from the assignment manager were removed in favor of the same methods in the [resource] and [role] manager.
+
* 分配管理不建議使用的方式已經刪除，使用 [resource] 和 [role]相同的方式管理
  
−
== OpenStack Block Storage (Cinder) ==
+
== OpenStack 區塊儲存 (Cinder) ==
  
−
=== Key New Features ===
+
=== 新功能 ===
−
* A generic image caching solution, so popular VM images can be cached and copied-on-write to a new volume. [http://docs.openstack.org/admin-guide-cloud/blockstorage_image_volume_cache.html Read docs for more info]
+
* 通用的映像檔快取解決方案,常用的 VM 映像檔都能被快取起來,且以 copy-on-write 方式到一個新的 Volume [http://docs.openstack.org/admin-guide-cloud/blockstorage_image_volume_cache.html 獲取更多的資訊]
−
* Non-disruptive backups [http://docs.openstack.org/admin-guide-cloud/blockstorage_volume_backups.html Read docs for more info].
+
* 無中斷的備份 [http://docs.openstack.org/admin-guide-cloud/blockstorage_volume_backups.html 獲取更多的資訊].
−
* Ability to clone consistency groups of volumes [http://docs.openstack.org/admin-guide-cloud/blockstorage-consistency-groups.html Read docs for more info].
+
* 能夠對一致性 Volume的群組進行 clone [http://docs.openstack.org/admin-guide-cloud/blockstorage-consistency-groups.html 獲取更多的資訊]
−
* List capabilities of a volume backend (fetch extra-specs).
+
* 獲取 Volume 儲存後端的列表 (取得 extra-specs).
−
* Nested quotas.
+
* 嵌套的配額
−
* Default LVM backends to be thin provisioned if available.
+
* 預設的 LVM 後端採用 thin-provisioned
−
* Corrected cinder service-list to show as Down when a driver fails to initialize.
+
* 修復 cinder service-list,當驅動程式載入失敗時會顯示為 Down
−
* Improved volume migration management:
+
* 優化 volume 移轉管理:
−
** Able to see if previous migration attempt was successful
+
** 能夠查看之前嘗試的移轉是否成功
−
** Admins able to monitor migrations via cinder list
+
** 管理人員可以透過 cinder list 查看移轉狀態
−
** New volume status of 'maintenance' to prevent operations being attempted while migration is occurring
+
** 新的 Volume 狀態"維護狀態",保證當移轉進行時,會阻止任何操作行為
−
** Improve backend volume name/id consistency after migration completes
+
** 優化 Volumes 的 name/id,在移轉完成後的一致性
  
−
=== Upgrade Notes ===
+
=== 升級提示 ===
−
* A change in parameters to RPC APIs and work on object conversion prevent running Liberty c-vol or c-api services with Kilo or earlier versions of either service.
+
* 對於 RPC API 的參數變化和在物件化轉化導致無法使用 Liberty c-vol 和 c-api 服務相容 Kilo 或者更早的版本的相關服務
  
−
=== Deprecated Features ===
+
=== 已棄用的功能 ===
−
* Removed Simple and Chance Schedulers.
+
* 已移除 Simple 和 Chance 兩種 Schedulers
−
* Removed deprecated HDS HUS iSCSI driver.
+
* 已移除棄用的 HDS HUS iSCSI 驅動程式
−
* Removed Coraid driver.
+
* 已移除 Coraid 驅動程式
−
* Remove Solaris iSCSI driver.
+
* 已移除 Solaris iSCSI 驅動程式
−
* Removed --force option for allowing upload of image to attached volume.
+
* 已移除 --force 選項,該選項用於允許上傳映像檔到已經附加的 Volume
−
* Marked the v1 API as deprecated.
+
* 將 v1 API 標示為已棄用
  
−
== OpenStack Orchestration (Heat) ==
+
== OpenStack 編配服務 (Heat) ==
  
 
=== 新功能 ===
 
=== 新功能 ===
  
 
==== Convergence ====
 
==== Convergence ====
−
Convergence is a new orchestration engine maturing in the heat tree. In Liberty, the benefits of using the convergence engine are:
+
Convergence是一個新的編配引擎，在Heat中日趨成熟。在Liberty中，使用Convergence的好處為：
−
* Greater parallelization of resource actions (for better scaling of large templates)
+
* 更好的資源平行處理 (為了更好的大型templates擴展)
−
* The ability to do a stack-update while there is already an update in-progress
+
* 能夠在已經執行更新操作過程中執行stack-update。
−
* Better handling of heat-engine failures (still WIP)
+
* 更好的處理heat-engine的錯誤 (仍然WIP)
  
−
The convergence engine can be enabled by setting /etc/heat/heat/conf [DEFAULT] convergence_engine=true, then restarting heat-engine. Once this has been done, any subsequent created stack will use the convergence engine, while operations on existing stacks will continue to use the traditional engine.
+
convergence engine可以透過設置 /etc/heat/heat/conf [DEFAULT]中的 convergence_engine=true，設定完成需重新啟動heat-engine。 完成之後，之後創建的stack將會使用convergence engine，而操作之前已存在的stack仍然會使用傳統引擎。
  
−
Convergence has '''not''' been production tested and thus should be considered '''beta''' quality - use with caution. For the Liberty release, we recommend enabling convergence for the purposes of evaluation and scale testing. We will be considering making convergence the default engine in the Mitaka cycle. Convergence specific bugs are tracked in launchpad with the [https://bugs.launchpad.net/heat/+bugs?field.tag=convergence-bugs convergence-bugs tag].
+
Convergence並'''未'''經過產品的測試，因此應該視為'''beta'''版本，小心使用。 在Liberty版本中，如果你的目的是評估或擴展測試，我們建議可以啟用convergence。我們考慮在下一個版本Mitaka中將convergence設為預設引擎。 Convergence相關的bugs追蹤在以下launchpad[https://bugs.launchpad.net/heat/+bugs?field.tag=convergence-bugs convergence-bugs tag].
  
−
==== Conditional resource exposure ====
+
==== 有條件的資源公開 ====
−
Only resources actually installed in the cloud services are made available to users. Operators can further control resources available to users with standard policy rules in [https://github.com/openstack/heat/blob/master/etc/heat/policy.json#L80 policy.json on per-resource type basis].
+
只有在雲端服務中安裝使用者才能使用。 維運人員可以透過標準的政策(policy)規則進一步來控制使用者的使用，請參考 [https://github.com/openstack/heat/blob/master/etc/heat/policy.json#L80 policy.json on per-resource type basis].
  
 
==== heat_template_version: 2015-10-15 ====
 
==== heat_template_version: 2015-10-15 ====
  
−
2015-10-15 indicates that the YAML document is a HOT template and it may contain features added and/or removed up until the Liberty release.
+
2015-10-15 表示YAML文件是HOT template並且包含了到Liberty之前新增或刪除的功能。
−
* Removes the Fn::Select function (path based [http://docs.openstack.org/developer/heat/template_guide/hot_spec.html#get-attr get_attr]/[http://docs.openstack.org/developer/heat/template_guide/hot_spec.html#get-param get_param] references should be used instead).  
+
* 移除Fn::Select 功能 (path based [http://docs.openstack.org/developer/heat/template_guide/hot_spec.html#get-attr get_attr]/[http://docs.openstack.org/developer/heat/template_guide/hot_spec.html#get-param get_param] references should be used instead).  
−
* If no <attribute name> is specified for calls to [http://docs.openstack.org/developer/heat/template_guide/hot_spec.html#get-attr get_attr], a dict of all attributes is returned, e.g. { get_attr: [<resource name>]}.
+
* 如果[http://docs.openstack.org/developer/heat/template_guide/hot_spec.html#get-attr get_attr]沒有指定<attribute name>， 所有屬性會以的字典格式回傳， 例如：{ get_attr: [<resource name>]}。
−
* Adds new [http://docs.openstack.org/developer/heat/template_guide/hot_spec.html#str-split str_split] intrinsic function
+
* 增加新的[http://docs.openstack.org/developer/heat/template_guide/hot_spec.html#str-split str_split]內部函式。
−
* Adds support for passing multiple lists to the existing [http://docs.openstack.org/developer/heat/template_guide/hot_spec.html#list-join list_join] function.
+
* 加入支援傳送多list到已存在的[http://docs.openstack.org/developer/heat/template_guide/hot_spec.html#list-join list_join]函式。
−
* Adds support for parsing map/list data to [http://docs.openstack.org/developer/heat/template_guide/hot_spec.html#str-replace str_replace] and [http://docs.openstack.org/developer/heat/template_guide/hot_spec.html#list-join list_join] (they will be json serialized automatically)
+
* 加入支援解析map/list資料到 [http://docs.openstack.org/developer/heat/template_guide/hot_spec.html#str-replace str_replace]和[http://docs.openstack.org/developer/heat/template_guide/hot_spec.html#list-join list_join] (它們會自動進行json serialized)
  
−
==== REST API/heatclient additions ====
+
==== REST API/heatclient 新增 ====
−
* Stacks can now be assigned with a set of tags, and stack-list can filter and sort through those tags
+
* Stacks現在可以分配一組tag，且stack-list可以透過這些tag來過濾與排序。
−
* "heat stack-preview ..." will return a preview of changes for a proposed stack-update
+
* "heat stack-preview ..."將會回傳已提出stack-update先前的改變。
−
* "heat template-validate --show-nested ..." will also validate all template resources and return nested data useful for building user interfaces
+
* "heat template-validate --show-nested ..." 將會驗證所有的template資源且回傳有用的nested data來建立使用者介面。
−
* "heat resource-type-template --template-type hot ..." generates a template in HOT format
+
* "heat resource-type-template --template-type hot ..."產生HOT format的樣板(template)。
−
* "heat resource-type-list" only shows types available to the user, and can filter results by name, version and support_status
+
* "heat resource-type-list"只顯示可用的類型給使用者，且可透過name、version、support_status來過濾結果。
−
* "heat template-version-list" lists available template versions
+
* "heat template-version-list"列出template版本。
−
* "heat template-function-list ..." lists available functions for a template version
+
* "heat template-function-list ..."列出template版本可用的功能。
  
−
==== Enhancements to existing resources ====
+
==== 加強現有資源 ====
−
* Software deployments can now use Zaqar for [http://docs.openstack.org/developer/heat/template_guide/openstack.html#OS::Nova::Server-prop-software_config_transport deploying software data] and [http://docs.openstack.org/developer/heat/template_guide/openstack.html#OS::Heat::SoftwareDeployment-prop-signal_transport signalling back to Heat]
+
* 軟體部署現在可以使用Zaqar來[http://docs.openstack.org/developer/heat/template_guide/openstack.html#OS::Nova::Server-prop-software_config_transport 部署軟體資料]和[http://docs.openstack.org/developer/heat/template_guide/openstack.html#OS::Heat::SoftwareDeployment-prop-signal_transport 信號回傳至Heat]
−
* Stack actions are now performed on remote [http://docs.openstack.org/developer/heat/template_guide/openstack.html#OS::Heat::Stack OS::Heat::Stack] resources
+
* Stack actions現在可以執行在遠端的[http://docs.openstack.org/developer/heat/template_guide/openstack.html#OS::Heat::Stack OS::Heat::Stack]資源上。
−
* [http://docs.openstack.org/developer/heat/template_guide/openstack.html#OS::Nova::Server OS::Nova::Server] now supports deletion_policy: Snapshot
+
* [http://docs.openstack.org/developer/heat/template_guide/openstack.html#OS::Nova::Server OS::Nova::Server]現在支援deletion_policy: 快照(snapshot )
−
* [http://docs.openstack.org/developer/heat/template_guide/openstack.html#OS::Heat::ResourceGroup-updpolicy OS::Heat::ResourceGroup update_policy] now supports specifying [http://docs.openstack.org/developer/heat/template_guide/openstack.html#OS::Heat::ResourceGroup-prop-batch_create batch_create] and [http://docs.openstack.org/developer/heat/template_guide/openstack.html#OS::Heat::ResourceGroup-prop-rolling_update rolling_update] options
+
* [http://docs.openstack.org/developer/heat/template_guide/openstack.html#OS::Heat::ResourceGroup-updpolicy OS::Heat::ResourceGroup update_policy]現在支援特定的[http://docs.openstack.org/developer/heat/template_guide/openstack.html#OS::Heat::ResourceGroup-prop-batch_create batch_create]和[http://docs.openstack.org/developer/heat/template_guide/openstack.html#OS::Heat::ResourceGroup-prop-rolling_update rolling_update]選項。
  
−
==== New resources ====
+
==== 新資源 ====
−
The following new resources are now distributed with the Heat release:
+
以下為Heat發佈的新資源:
 
* [http://docs.openstack.org/developer/heat/template_guide/openstack.html#OS::Barbican::Order OS::Barbican::Order] [1]
 
* [http://docs.openstack.org/developer/heat/template_guide/openstack.html#OS::Barbican::Order OS::Barbican::Order] [1]
 
* [http://docs.openstack.org/developer/heat/template_guide/openstack.html#OS::Barbican::Secret OS::Barbican::Secret] [1]
 
* [http://docs.openstack.org/developer/heat/template_guide/openstack.html#OS::Barbican::Secret OS::Barbican::Secret] [1]
Line 385: Line 384:
 
* [http://docs.openstack.org/developer/heat/template_guide/openstack.html#OS::Sahara::DataSource OS::Sahara::DataSource]
 
* [http://docs.openstack.org/developer/heat/template_guide/openstack.html#OS::Sahara::DataSource OS::Sahara::DataSource]
  
−
[1] These existed Kilo as contrib resources as they were for non-integrated projects. These resources are now distributed with Heat as Big Tent projects.
+
[1] 這些已存在Kilo的contrib資源因為它們不是非整合專案。這些資源為隨著Heat發佈，且為Big Tent專案。
  
−
[2] These existed Kilo as contrib resources as they require a user with an admin role. They are now distributed with Heat. Operators now have ability to hide them from under-privileged users by modifyig policy.json (for reference, OS::Nova::Flavor is hidden from non-admin users in default policy file supplied).
+
[2] 這些已存在Kilo的contrib資源因為這些使用者需要管理者。它們隨著Heat的發佈。 維運人員現在能夠透過修改policy.json來隱藏沒有權限的使用者(僅供參考：OS::Nova::Flavor對於非管理的使用者預設隱藏)。
  
−
[3] These existed in Kilo as contrib resources as they used an approach not endorsed by the Heat project. They are now distributed with heat and documented as UNSUPPORTED.
+
[3] 這些已存在Kilo的contrib資源它們使用的方法不被Heat專案認同。它們現在隨著Heat的發佈且標記不支援(UNSUPPORTED)。
  
−
[4] These resources are for projects which are not yet OpenStack Big Tent projects, so are documented as UNSUPPORTED
+
[4] 這些資源還不是OpenStack Big Tene專案，因此標記不支援(UNSUPPORTED)。
  
−
With the new OS::Keystone::* resources it is now be possible for cloud operators to use heat templates to manage Keystone service catalog entries and users.
+
使用新的OS::Keystone::*資源，現在能使雲端維運人員來使用Heat templates管理Keystone服務目錄和使用者。
  
−
==== Deprecated Resource Properties ====
+
==== 不推薦的資源屬性 ====
−
Many resource properties have previously been documented as DEPRECATED. 15 of these properties are now flagged as HIDDEN, which means they will no longer be documented, but existing stacks and templates will continue to work after a heat upgrade. The [ http://docs.openstack.org/developer/heat/template_guide/openstack.html Resource Type Reference] should be consulted to determine available resource properties and attributes.
+
許多資源屬性先前已被標記為DEPRECATED， 其中有15個屬性現在標記為隱藏(HIDDEN)， 這代表它們將不再被記錄， 但是已存在的stacks和templates在Heat升級之後繼續運做。 [http://docs.openstack.org/developer/heat/template_guide/openstack.html 資源類型參考] 應需要討論來決定可用資源特性和屬性。
  
−
=== Upgrade notes ===
+
=== 升級提示 ===
  
−
==== Configuration Changes ====
+
==== 配置檔案改變 ====
−
Notable changes to the /etc/heat/heat.conf [DEFAULT] section:
+
/etc/heat/heat.conf [DEFAULT] 中明顯的改變：
−
* hidden_stack_tags has been added, and stacks containing these tag names will be hidden from stack-list results (defaults to data-processing-cluster, which hides sahara-created stacks)
+
* hidden_stack_tags已經被新增，且stack包含這些標籤名字將會從stack-list結果中被隱藏(預設為data-processing-cluster，其中隱藏sahara-created stacks)
−
* instance_user was deprecated, and is now removed entirely. Nova servers created with OS::Nova::Server resource will now boot configured with the default user set up with the cloud image. AWS::EC2::Instance still creates "ec2-user"
+
* instance_user將被棄用，且已經完全移除。 Nova servers created with OS::Nova::Server resource will now boot configured with the default user set up with the cloud image. AWS::EC2::Instance仍然創建"ec2-user"。
−
* max_resources_per_stack can now be set to -1 to disable enforcement
+
* max_resources_per_stack現在可以設為-1來禁止執行。
−
* enable_cloud_watch_lite is now false by default as this REST API is deprecated
+
* enable_cloud_watch_lite預設為flase，因為這個REST API已被棄用。
−
* default_software_config_transport has gained the option ZAQAR_MESSAGE
+
* default_software_config_transport新增新選項ZAQAR_MESSAGE。
−
* default_deployment_signal_transport has gained the option ZAQAR_SIGNAL
+
* default_deployment_signal_transport新增新選項ZAQAR_SIGNAL。
−
* auth_encryption_key is now documented as requiring exactly 32 characters
+
* auth_encryption_key現在記錄要求精確地32個字。
−
* list_notifier_drivers was deprecated and is now removed
+
* list_notifier_drivers 已被棄用且現在已被移除。
−
* policy options have moved to the [oslo_policy] section
+
* policy options被移動至[oslo_policy]中。
−
* use_syslog_rfc_format is deprecated and now defaults to true
+
* use_syslog_rfc_format已被移除，現在預設為true。
  
−
Notable changes to other sections of heat.conf:
+
heat.conf中其他明顯的改變：
−
* [clients_keystone] auth_uri has been added to specify the unversioned keystone url
+
* [clients_keystone] auth_uri已經被新增到特定的unversioned keystone url。
−
* [heat_api] workers now defaults to 4 (was previously 0, which created a worker per host CPU)
+
* [heat_api] workers現在預設為4(之前為0，為每一個主機CPU創見一個worker)
  
−
The policy file /etc/heat/policy.json can now be configured with per-resource-type access policies, for example:
+
policy檔案 /etc/heat/policy.json 現在能夠為每一種資源類型單獨配置訪問策略(policy)，例如：
 
     "resource_types:OS::Nova::Flavor": "rule:context_is_admin"
 
     "resource_types:OS::Nova::Flavor": "rule:context_is_admin"
  
−
==== Upgrading from Kilo to Liberty ====
+
==== 從Kilo升級至Liberty ====
−
Progress has been made on supporting live sql migrations, however it is still recommended to bring down the heat service for the duration of the upgrade. Downward SQL schema migrations are no longer supported. A rollback to Kilo will require restoring a snapshot of the pre-upgrade database.
+
目前正在進行支援即時sql遷移， 但是仍然建議在升級的過程中暫停Heat服務。 向下SQL schema遷移不再支援。 rollback至Kilo需要恢復預升級資料庫的快照。
  
−
== OpenStack Data Processing (Sahara) ==
+
== OpenStack 資料處理服務 (Sahara) ==
  
 
=== 新功能 ===
 
=== 新功能 ===
  
−
* New plugins and versions:
+
* 新插件與版本:
−
** Ambari plugin with supports HDP  2.2 / 2.3
+
** Ambari 插件支援 HDP  2.2 / 2.3
−
** Apache Hadoop 2.7.1 was added, Apache Hadoop 2.6.0 was deprecated
+
** 新增 Apache Hadoop 2.7.1, Apache Hadoop 2.6.0 已棄用
−
** CDH 5.4.0 was added with HA support for NameNode and ResourceManager
+
** 新增 CDH 5.4.0, 並支援 NameNode 與 ResourceManager 的 HA
−
** MapR 5.0.0 was added
+
** 新增 MapR 5.0.0  
−
** Spark 1.3.1 was added, Spark 1.0.0 was deprecated
+
** 新增 Spark 1.3.1, Spark 1.0.0 已棄用
−
** HDP 1.3.2 and Apache Hadoop 1.2.1 was removed
+
** HDP 1.3.2 與 Apache Hadoop 1.2.1 被移除了
−
* Added support for using Swift with Spark EDP jobs
+
* 新增支援 Spark EDP jobs 結合 Swift 使用
−
* Added support for Spark EDP jobs in CDH and Ambari plugins
+
* CDH 與 Ambari 插件支援 Spark EDP jobs
−
* Added support for public and protected resources
+
* 支援 public 與 protected 資源
−
* Started integration with OpenStack client
+
* 已開始整合 OpenStack Client
−
* Added support for editing all Sahara resources
+
* 支援編輯所有的 Sahara 資源
−
* Added automatic Hadoop configuration for clusters
+
* 支援叢集的自動 Hadoop 配置
−
* Direct engine is deprecated and will be removed in Mitaka release
+
* 已棄用直接提供的引擎,並且在 Mitaka 版本將被移除
−
* Added OpenStack manila NFS shares as a storage backend option for job binaries and data sources
+
* 對 job binaries和資料來源新增 OpenStack Manila NFS 共享作為儲存後端選項
−
* Added support for definition and use of configuration interfaces for EDP job templates
+
* 支援對 EDP job 的板模定義和使用介面配置
  
−
=== Deprecated Features ===
+
=== 已棄用的功能 ===
  
−
* Direct provisioning engine
+
* 直接提供的引擎(Direct provisioning engine)
−
* Apache Hadoop 2.6.0
+
* Apache Hadoop 2.6.0  
−
* Spark 1.0.0
+
* Spark 1.0.0  
−
* All Hadoop 1.X removed
+
* 所有 Hadoop 1.X 版本已移除
  
 
== OpenStack Search (Searchlight) ==
 
== OpenStack Search (Searchlight) ==
  
−
This is the first release for Searchlight. Searchlight is intended to dramatically improving the search capabilities and performance of various OpenStack cloud services by offloading user search queries. It provides Keystone RBAC based searches across OpenStack services by indexing their data into ElasticSearch and providing a security layer on top of incoming search queries. ElasticSearch is a search server based on Lucene. It provides a distributed, scalable, near real-time, faceted, multitenant-capable, and full-text search engine with a RESTful web interface.
+
這是第一個Searchlight版本. Searchlight的目的是大幅提高通過請求使用者搜索查詢的功能和各種OpenStack 雲的服務性能. 它提供了跨OpenStack的服務Keystone RBAC 基於搜索通過檢驗自己的數據到ElasticSearch並提供一個安全層面對輸入搜索查詢.ElasticSearch是基於Lucene搜索服務.他提供了一個distributed, scalable, near real-time, faceted, multitenant-capable, and full-text 的一個RESTful web 引擎介面
  
−
* [https://wiki.openstack.org/wiki/Searchlight Project Wiki]
+
*[https://wiki.openstack.org/wiki/Searchlight Project Wiki]
  
−
=== Key New Features ===
+
=== 新功能 ===
−
* [http://docs.openstack.org/developer/searchlight/searchlightapi.html Searchlight Search API] OpenStack Resource Type based API providing native ElasticSearch query support
+
* [http://docs.openstack.org/developer/searchlight/searchlightapi.html Searchlight Search API] OpenStack 支援類型基於API 提供原生 ElasticSearch 支援查詢
−
* [http://docs.openstack.org/developer/searchlight/indexingservice.html#bulk-indexing Bulk Indexing CLI] searchlight-manage indexing command line interface
+
* [http://docs.openstack.org/developer/searchlight/indexingservice.html#bulk-indexing Bulk Indexing CLI] searchlight-manage 索引command line介面
 
* [http://docs.openstack.org/developer/searchlight/indexingservice.html#incremental-updates Incremental Notification based updates]
 
* [http://docs.openstack.org/developer/searchlight/indexingservice.html#incremental-updates Incremental Notification based updates]
−
* [http://docs.openstack.org/developer/searchlight/indexingservice.html#search-plugins Resource Type Plugin system] for adding and managing resource indexing and searches
+
* [http://docs.openstack.org/developer/searchlight/indexingservice.html#search-plugins Resource Type Plugin system] 對於增加和管理資源索引和搜索
 
* [https://github.com/openstack/searchlight/tree/master/devstack Devstack deployment]
 
* [https://github.com/openstack/searchlight/tree/master/devstack Devstack deployment]
  
−
==== New Resource Types Indexed ====
+
==== 新的資源類型索引 ====
 
* [http://docs.openstack.org/developer/searchlight/plugins/nova.html OS::Nova::Server] Nova server instances
 
* [http://docs.openstack.org/developer/searchlight/plugins/nova.html OS::Nova::Server] Nova server instances
−
* [http://docs.openstack.org/developer/searchlight/plugins/glance.html OS::Glance::Image & OS::Glance::Metadef] Glance Images and Metadata Definitions
+
* [http://docs.openstack.org/developer/searchlight/plugins/glance.html OS::Glance::Image & OS::Glance::Metadef] Glance Images和Metadata定義
−
* [http://docs.openstack.org/developer/searchlight/plugins/designate.html OS::Designate::Zone & OS::Designate::RecordSet] Designate Domain and Record Sets
+
* [http://docs.openstack.org/developer/searchlight/plugins/designate.html OS::Designate::Zone & OS::Designate::RecordSet] Designate Domain和Record Sets
  
−
=== Upgrade Notes ===
+
=== 升級提示 ===
  
 
N/A
 
N/A
  
−
=== Deprecated Features ===
+
=== 已棄用的功能 ===
  
 
N/A
 
N/A
  
−
== OpenStack DNS (Designate) ==
+
== OpenStack DNS管理服務 (Designate) ==
  
−
=== Key New Features ===
+
=== 新功能 ===
  
−
* '''''Experimental''''': Hook Point API
+
* '''''實驗的''''': Hook Point API
−
* Horizon Plugin moved out of tree
+
* Horizon Plugin 移除 tree
−
* Purging deleted domains
+
* Purging 刪除 domains
−
* Ceilometer "exists" periodic event per domain
+
* Ceilometer "exists" 每個周期事件 domain
 
* ASync actions
 
* ASync actions
 
** Import
 
** Import
 
** Export
 
** Export
−
* Active /passive failover for designate-pool-manager periodic tasks
+
* Active /passive 對於designate-pool-manager 週期性任務故障轉移
−
* OpenStack client integration
+
* OpenStack 用戶端集合
  
−
==== Addtional DNS Server Backends ====
+
==== 其他的 DNS 伺服器後端 ====
  
 
* InfoBlox
 
* InfoBlox
 
* Designate
 
* Designate
  
−
=== Upgrade Notes ===
+
=== 升級提示 ===
  
−
* New service <code>designate-zone-manager</code>
+
* 新的服務<code>designate-zone-manager</code>
−
** It is recommended to use a supported tooz backend.
+
** 建議使用 tooz 支援後台.
−
** ZooKeeper is recommended, or anything supported by tooz.
+
** 建議ZooKeeper ,或是任何tooz支援.
−
** If a tooz backend is not used, all zone-managers will assume ownership of all zones, and there will be ''''n'''' "exists" messages per hour, where ''''n'''' is the number of zone-manager processes.
+
** 如果tooz 後台不能使用, 所有zone-managers 將承擔所有區域的擁有權，而且在每個小時會有 ''''n'''' "exists" ，其中 ''''n'''' 是 zone-manager的處理次數
  
−
* <code>designate-pool-manager</code> can do active/passive failover for periodic tasks.
+
* <code>designate-pool-manager</code> 可以做 active/passive 故障轉移的週期性任務.
−
** It is recommended to use a supported tooz backend.
+
** 建議使用支援 tooz 後台.
−
** If a tooz backend is not used, all pool-managers will assume ownership of the pool, and multiple periodic tasks will run. This can result in unforeseen consequences.
+
** 如果不使用tooz 當作後台, 所有pool-managers 將承擔pool的所有權，  和多個週期性任務將運行。 這可能導致無法預期的結果.
  
−
=== Deprecated Features ===
+
=== 已棄用的功能 ===
  
 
* V1 API
 
* V1 API
−
** An initial notice of intent, as there are operations that still require the Designate CLI interface which talks to V1, and Horizon panels that only talk to V1.
+
**目標初步通知, 因為有操作扔然需要Designate CLI interface 其中 talks to V1, 和 Horizon panels 只有talk to V1.
  
−
== OpenStack Messaging Service (Zaqar) ==
+
== OpenStack 訊息佇列服務  (Zaqar) ==
  
−
=== Key New Features ===
+
=== 新功能 ===
−
* Pre-signed URL - A new REST API endpoint to support pre-signed URL, which provides enough control over the resource being shared, without compromising security.
+
* Pre-signed URL - 一個新的REST API 端點支援 pre-signed URL, 他提供足夠的控制權限被源共享, 不影響安全性.
−
* Email Notification - A new task driver for notification service, which can take a Zaqar subscriber's email address. When there is a new message posted to the queue, the subscriber will receive the message by email.
+
* Email Notification - 一個新的通知服務任務driver, 這可能需要一個 Zaqar 用戶的電子郵件位址。當有新的訊息發佈到queue，使用者將通過電子郵件收到訊息
−
* Policy Support - Support fine-grained permission control with the <code>policy.json</code> file like most of the other OpenStack components.
+
* Policy Support - 支援 fine-grained 權限控制與 <code>policy.json</code> 文件向大多數的其他OpenStack組件.
−
* Persistent Transport - Added support for websocket as a persistent transport alternative for Zaqar. Now users will be able to establish long-lived connections between their applications and Zaqar to interchange large amounts of data without the connection setup adding overhead.
+
* Persistent Transport - 增加了對websocket支援，對Zaqar一個持久傳輸的代替。現在使用者可以建立long-lived連接之間他們應用程式和Zaqar相互交換大量數據，而不是連接建立增加消耗。
  
−
== OpenStack Dashboard (Horizon) ==
+
== OpenStack 儀表板服務 (Horizon) ==
  
−
=== Key New Features ===
+
=== 新功能 ===
  
−
* A new network topology – The network topology diagram has been replaced with an interactive graph containing collapsible networks, and scales far better in large deployments (https://blueprints.launchpad.net/horizon/+spec/curvature-network-topology).
+
* 新的網路拓樸圖 - 網路拓樸圖已替換為互動式圖形包含可折疊網路(collapsible networks)，且 scales 在大規模的部署做的更好
  
−
* Plugin improvements – Horizon auto discovers JavaScript files for inclusion, and now has mechanisms for pluggable SCSS and Django template overrides.
+
* 插件的改善 - Horizon 能自動偵測到被列入的JavaScript 檔案，且現在有機制能將可插拔的 SCSS 與 Django 模板進行覆寫。
  
−
* Compute (Nova)
+
* Compute (Nova)
−
** Support for shelving and unshelving of instances (https://blueprints.launchpad.net/horizon/+spec/horizon-shelving-command).
+
** 支援擱置與非擱置的實例  (https://blueprints.launchpad.net/horizon/+spec/horizon-shelving-command).
−
** Support for v2 block device mapping, falling back to v1 when unavailable (https://blueprints.launchpad.net/horizon/+spec/horizon-block-device-mapping-v2).
+
** 支援 v2 區塊裝置配對(BDM)，回朔到 v1 將不再適用 (https://blueprints.launchpad.net/horizon/+spec/horizon-block-device-mapping-v2).
  
 
* Networking (Neutron)
 
* Networking (Neutron)
−
** Added support for subnet allocation via subnet pools (https://blueprints.launchpad.net/horizon/+spec/neutron-subnet-allocation).
+
** 新增支援透過子網路池的子網路分配 (https://blueprints.launchpad.net/horizon/+spec/neutron-subnet-allocation).
−
** Added actions to easily associate LBaaS VIP with a floating IP (https://blueprints.launchpad.net/horizon/+spec/lbaas-vip-fip-associate).
+
** 新增更容易聯繫 LBaaS VIP 與浮動 IP 功能 (https://blueprints.launchpad.net/horizon/+spec/lbaas-vip-fip-associate).
  
 
* Images (Glance)
 
* Images (Glance)
−
** The metadata editor has been updated with AngularJS (https://blueprints.launchpad.net/horizon/+spec/angularize-metadata-update-modals).
+
** metadata 編輯器已更新為 AngularJS (https://blueprints.launchpad.net/horizon/+spec/angularize-metadata-update-modals).
−
** Compute images metadata can now be edited from the Project dashboard, using the new metadata editor (https://blueprints.launchpad.net/horizon/+spec/project-images-metadata).
+
** Compute 的映像檔 metadata 現在能夠在 dashboard 編輯,使用新的 metadata 編輯器(https://blueprints.launchpad.net/horizon/+spec/project-images-metadata).
  
 
* Block Storage (Cinder)
 
* Block Storage (Cinder)
−
** Enabled support for migrating volumes (https://blueprints.launchpad.net/horizon/+spec/volume-migration).
+
** 允許支援移轉的 volumes (https://blueprints.launchpad.net/horizon/+spec/volume-migration).
−
** Volume types can be now edited, and include description fields (https://blueprints.launchpad.net/horizon/+spec/volume-type-description).
+
** Volume 類型現在能被編輯,且包含描述欄位 (https://blueprints.launchpad.net/horizon/+spec/volume-type-description).
  
 
* Orchestration (Heat)
 
* Orchestration (Heat)
−
** Improvements to the heat topology, making more resources identifiable where previously they had no icons and were displayed as unknown resources (https://blueprints.launchpad.net/horizon/+spec/heat-topology-display-improvement).
+
** 改善 Heat 拓樸，更多可識別的資源，其中先前沒有 icon 的資源將被顯示為未知資源 (https://blueprints.launchpad.net/horizon/+spec/heat-topology-display-improvement).
  
 
* Data Processing (Sahara)
 
* Data Processing (Sahara)
−
** Unified job interface map. This is a human readable method for passing in configuration data that a job may require or accept (https://blueprints.launchpad.net/horizon/+spec/unified-job-interface-map-ui).
+
** 統一工作介面，讓傳送配置數據中一個工作可能為需求或接受變得更容易理解 (https://blueprints.launchpad.net/horizon/+spec/unified-job-interface-map-ui).
−
** Added editing capabilities for job binaries (https://blueprints.launchpad.net/horizon/+spec/allow-editing-of-job-binaries).
+
** 新增 job binaries編輯功能 (https://blueprints.launchpad.net/horizon/+spec/allow-editing-of-job-binaries).
−
** Added editing capabilities for data sources (https://blueprints.launchpad.net/horizon/+spec/allow-editing-of-data-sources).
+
** 新增來源資料編輯功能 (https://blueprints.launchpad.net/horizon/+spec/allow-editing-of-data-sources).
−
** Added editing capabilities for job templates (https://blueprints.launchpad.net/horizon/+spec/data-processing-edit-templates).
+
** 新增job templates編輯功能 (https://blueprints.launchpad.net/horizon/+spec/data-processing-edit-templates).
−
** Exposed event log for clusters (https://blueprints.launchpad.net/horizon/+spec/sahara-event-log).
+
** 公開clusters的event log (https://blueprints.launchpad.net/horizon/+spec/sahara-event-log).
−
** Added support for shell job types (https://blueprints.launchpad.net/horizon/+spec/sahara-shell-action-form).
+
**新增支援shell job類型(https://blueprints.launchpad.net/horizon/+spec/sahara-shell-action-form).
  
 
* Databases (Trove)
 
* Databases (Trove)
−
** Added initial support for database cluster creation and management. Vertica and MongoDB are currently supported (https://blueprints.launchpad.net/horizon/+spec/database-clustering-support).
+
** 新增初始化去支援database cluster創建和管理，目前支援Vertica與MongoDB (https://blueprints.launchpad.net/horizon/+spec/database-clustering-support).
  
 
* Identity (Keystone)
 
* Identity (Keystone)
−
** Added mapping for Identity Provider and Protocol specific WebSSO (https://github.com/openstack/horizon/commit/3b4021c0ad0e8d7b10aa8c2dcd8c13a5717c450c).
+
** 新增Identity Provider與WebSSO協定的配對(https://github.com/openstack/horizon/commit/3b4021c0ad0e8d7b10aa8c2dcd8c13a5717c450c).
−
** Configurable token hashing (https://github.com/openstack/django_openstack_auth/commit/ece924a79d27ede1a8475d7f98e6d66bc3cffd6c and https://github.com/openstack/horizon/commit/48e651d05cbe9366884868c5331d49a501945adc).
+
** 配置 token hashing (https://github.com/openstack/django_openstack_auth/commit/ece924a79d27ede1a8475d7f98e6d66bc3cffd6c and https://github.com/openstack/horizon/commit/48e651d05cbe9366884868c5331d49a501945adc).
  
 
* Horizon (internal improvements)
 
* Horizon (internal improvements)
−
** Full support for translation in AngularJS, along with simpler tooling (https://blueprints.launchpad.net/horizon/+spec/angular-translate-makemessages).
+
** 完全支援AngularJS翻譯，以及簡單的工具 (https://blueprints.launchpad.net/horizon/+spec/angular-translate-makemessages).
−
** Added Karma for JavaScript testing (https://blueprints.launchpad.net/horizon/+spec/karma).
+
** 新增Karma 對 JavaScript 測試 (https://blueprints.launchpad.net/horizon/+spec/karma).
−
** Added ESLint for JavaScript linting, using the eslint-config-openstack rules (https://blueprints.launchpad.net/horizon/+spec/jscs-cleanup).
+
** 新增ESLint for JavaScript linting, 使用eslint-config-openstack 規則 (https://blueprints.launchpad.net/horizon/+spec/jscs-cleanup).
−
** Horizon now supports overriding of existing Django templates (https://blueprints.launchpad.net/horizon/+spec/horizon-theme-templates).
+
** Horizon 現在支援複寫已存在的Django templates (https://blueprints.launchpad.net/horizon/+spec/horizon-theme-templates).
−
** JavaScript files are now automatically included (https://blueprints.launchpad.net/horizon/+spec/auto-js-file-finding).
+
** JavaScript 文件現在已經自動包含在內 (https://blueprints.launchpad.net/horizon/+spec/auto-js-file-finding).
  
−
=== Upgrade Notes ===
+
=== 升級提示 ===
  
−
* Django 1.8 is now supported, and Django 1.7 is our minimum supported version (https://blueprints.launchpad.net/horizon/+spec/drop-django14-support).
+
* 目前支援Django 1.8版本，而最低支援版本為Django 1.7 (https://blueprints.launchpad.net/horizon/+spec/drop-django14-support).
−
* Database-backed sessions will likely not persist across upgrades due to a change in their structure (https://github.com/openstack/django_openstack_auth/commit/8c64de92f4148d85704b10ea1f7bc441db2ddfee and https://github.com/openstack/horizon/commit/ee2771ab1a855342089abe5206fc6a5071a6d99e).
+
* Database-backed sessions 將不會持續更新，因為牽扯到架構的改變(https://github.com/openstack/django_openstack_auth/commit/8c64de92f4148d85704b10ea1f7bc441db2ddfee and https://github.com/openstack/horizon/commit/ee2771ab1a855342089abe5206fc6a5071a6d99e).
−
* Horizon no longer uses QUnit in testing, and it has been removed from our requirements (https://blueprints.launchpad.net/horizon/+spec/replace-qunit-tests-with-jasmine).
+
* Horizon不再使用QUnit測試，且將從我們的系統需求中移除  (https://blueprints.launchpad.net/horizon/+spec/replace-qunit-tests-with-jasmine).
−
* Horizon now has multiple configuration options for the default web URL (<code>WEBROOT</code>), static file location (<code>STATIC_ROOT</code>) and static file URL (<code>STATIC_URL</code>) in its settings files.
+
* Horizon目前在設定檔中提供預設網頁URL (<code>WEBROOT</code>), 靜態文件位置 (<code>STATIC_ROOT</code>) 與靜態URL檔案 (<code>STATIC_URL</code>) 在設定文件中修改
−
* Themes have moved location from <code>openstack_dashboard/static/themes</code>, to <code>openstack_dashboard/themes</code>. Paths may need to be updated accordingly. Furthermore, Horizon is aligning closer with Bootstrap markup, and themes should be built around this ideology; see the top bar and side navigation for details.
+
* Themes已經從<code>openstack_dashboard/static/themes</code>, 搬移到<code>openstack_dashboard/themes</code>. 因此路徑可能需要相對應的更新，此外，Horizon依照Bootstrap markup調整，而themes應按照此方法去設計；更詳細的訊息請參閱最上方欄位與側邊的navigation
−
* The deprecated <code>OPENSTACK_QUANTUM_NETWORK</code> configuration option has been removed. If you still use it, replace it with <code>OPENSTACK_NEUTRON_NETWORK</code>
+
* 不建議使用<code>OPENSTACK_QUANTUM_NETWORK</code> 設定已經被刪除. 如果你扔然在使用請使用<code>OPENSTACK_NEUTRON_NETWORK</code>作為替換
−
* There is now an <code>OPENSTACK_NOVA_EXTENSIONS_BLACKLIST</code> option in the settings, to disable selected extensions for performance reasons (https://github.com/openstack/horizon/commit/18f4b752b8653c9389f8b0471eccaa0659707ebe).
+
* 目前提供設定<code>OPENSTACK_NOVA_EXTENSIONS_BLACKLIST</code> 的選項, 可禁用被選取的擴充來提升效能 (https://github.com/openstack/horizon/commit/18f4b752b8653c9389f8b0471eccaa0659707ebe).
−
* Trove and Sahara panels now reside in <code>openstack_dashboard/contrib</code>. This is to provide separation for reviews provided mostly by the service teams. In the future, these panels may become plugins rather than being kept in Horizon (https://blueprints.launchpad.net/horizon/+spec/plugin-sanity).
+
* Trove 和 Sahara panels 目前移動到 <code>openstack_dashboard/contrib</code>. 這是由服務團隊去提供主要的分類審查. 在未來，這些panels將成為plugins，而非繼續保存在Horizon (https://blueprints.launchpad.net/horizon/+spec/plugin-sanity).
−
* Horizon requires both a <code>volume</code> and <code>volumev2</code> endpoint for Cinder, even if only using v2.
+
* 即使Cinder使用v2，Horizon還是需求<code>volume</code> 和 <code>volumev2</code> 兩個端點.
  
−
== OpenStack Trove (DBaaS) ==
+
== OpenStack 資料庫即服務 (Trove) ==
  
−
=== Key New Features ===
+
=== 新功能 ===
  
 
* Redis
 
* Redis
−
** Configuration Groups for Redis
+
** Redis 的組態群組
−
** Cluster support
+
** 支援叢集
 
* MongoDB
 
* MongoDB
−
** Backup and restore for a single instance
+
** 單一實例的備份與恢復
−
** User and database management
+
** 使用者與資料庫管理
−
** Configuration Groups
+
** 組態群組 (Configuration Groups)
−
* Percona XtraDB Cluster Server
+
* Percona XtraDB 叢集伺服器
−
** Cluster support
+
** 支援叢集
−
* Allow deployer to associate instance flavors with specific datastores
+
* 允許部署人員分配實例的規格於特定資料儲存
−
* Horizon support for database clusters
+
* Horizon 支援資料庫叢集
−
* Management API for datastore and versions
+
* 資料儲存(datastore)與版本管理 API
−
* Ability to deploy Trove instances in a single admin tenant, so that the nova instances are hidden from the user
+
* 能在一個 admin tenant 中部署 Trove 實例, 這樣實例就可以對使用者隱藏
  
−
== OpenStack Bare metal (Ironic) ==
+
== OpenStack 裸機服務(Ironic)==
  
−
Ironic has switched to an [http://git.openstack.org/cgit/openstack/governance/tree/reference/tags/release_cycle-with-intermediary.rst intermediate release model] and released version 4.0 during Liberty, followed by two minor updates. Version 4.2 forms the basis for the OpenStack Integrated Liberty release and will receive stable updates.
+
Ironic 已經切換到 [http://git.openstack.org/cgit/openstack/governance/tree/reference/tags/release_cycle-with-intermediary.rst intermediate release model] 並在Liberty版本期間發行4.0版。4.2版本形式是基於OpenStack整合Liberty版本並獲得穩定更新。
  
−
Please see full release notes here: http://docs.openstack.org/developer/ironic/releasenotes/index.html
+
請參閱完整版本發行說明: http://docs.openstack.org/developer/ironic/releasenotes/index.html
  
−
=== New Features ===
+
=== 新功能 ===
  
−
* Added "ENROLL" hardware state, which is the default state for newly created nodes.
+
* 增加 "ENROLL" 硬體狀態，這是預設的狀態對於新創建的節點。
−
* Added "abort" verb, which allows a user to interrupt certain operations while they are in progress.
+
* 增加 "abort"，當使用者正在進行時，允許使用者中斷一些操作。
−
* Improved query and filtering support in the REST API.
+
* 在REST API改進查詢跟過濾的支援。
−
* Added support for CORS middleware.
+
* 增加支援 CORS middleware.
  
−
==== Hardware Drivers ====
+
==== 硬體驅動程式 ====
  
−
* Added a new BootInterface for hardware drivers, which splits functionality out of the DeployInterface.
+
* 增加硬體drivers一個新的BootInterface，which splits functionality out of the DeployInterface.
−
* iLO virtual media drivers can work without Swift.
+
* iLO 虛擬介面drivers可以不用Swift運作.
−
* Added Cisco IMC driver.
+
* 新增Cisco IMC driver.
−
* Added OCS Driver.
+
* 新增OCS Driver.
−
* Added UCS Driver.
+
* 新增UCS Driver.
−
* Added Wake-On-Lan Power Driver.
+
* 新增Wake-On-Lan Power Driver.
−
* ipmitool driver supports IPMI v1.5.
+
* ipmitool driver 支援 IPMI v1.5.
−
* Added support to SNMP driver for “APC MasterSwitchPlus” series PDU’s.
+
* 增加支援 SNMP driver for “APC MasterSwitchPlus” series PDU’s.
−
* pxe_ilo driver now supports UEFI Secure Boot (previous releases of theiLO driver only supported this for agent_ilo and iscsi_ilo).
+
* pxe_ilo driver 現在支援 UEFI Secure Boot (previous releases of theiLO driver only supported this for agent_ilo and iscsi_ilo).
−
* Added Virtual Media support to iRMC Driver.
+
* 新增 Virtual Media support to iRMC Driver.
−
* Added BIOS configuration to DRAC Driver.
+
* 新增 BIOS configuration to DRAC Driver.
 
* PXE drivers now support GRUB2.
 
* PXE drivers now support GRUB2.
  
−
=== Deprecated Features ===
+
=== 已棄用的功能 ===
  
−
* The "vendor_passthru" and "driver_vendor_passthru" methods of the DriverInterface have been removed. These were deprecated in Kilo and replaced with the @passthru decorator.
+
* "vendor_passthru" 和 "driver_vendor_passthru" DriverInterface的方法已經被刪除。這些在Kilo版本已經過時並且被@passthru decorator取代。
−
* The migration tools to import data from a Nova "baremetal" deployment have been removed.
+
* 遷移工具從Nova "baremetal"部署導入數據已經被移除
−
* Deprecated the "parallel" option to periodic task decorator.
+
* 捨棄 "parallel" 選項以週期性任務decorator.
−
* Removed deprecated ‘admin_api’ policy rule.
+
* 刪除過時 ‘admin_api’ 策略規則.
−
* Support for the original "bash" deploy ramdisk is deprecated and will be removed in two cycles. The ironic-python-agent project should be used for all deploy drivers.
+
* 原始"bash"部屬ramdisk支援已經被棄用並會在兩個周期刪除。 ironic-python-agent專案應被用於所有部屬drivers
  
−
=== Upgrade Notes ===
+
=== 升級提示 ===
  
−
* Newly created nodes default to the new ENROLL state. Previously, nodes defaulted to AVAILABLE, which could lead to hardware being exposed prematurely to Nova.
+
* 新創建的節點預設為新ENROLL狀態. 在之前, 節點預設為AVAILABLE, 這可能導致硬體提早出現在Nova.
−
* The addition of API version headers in Kilo means that any client wishing to interact with the Liberty API must pass the appropriate version string in each HTTP request. Current API version is 1.14.
+
* 在Kilo版本增加API headers，意味著希望與Liberty API 進行互動的任何用戶端必須通過每個HTTP請求相應版本的字串。目前API版本為1.14
  
−
== OpenStack Key Manager (Barbican) ==
+
== OpenStack 金鑰管理服務 (Barbican) ==
  
−
=== New Features ===
+
=== 新功能 ===
  
−
* Added the ability for project administrators to create certificate authorities per project.  Also, project administrators are able to define and manage a set of preferred certificate authorities (CAs) per project.  This allows projects to achieve project specific security domains.
+
* 新增專案管理員能力去創建每個專案憑證授權。此外, 專案管理員能夠定義和管理每一個專案優先憑證配發機構(CAs)。讓允許專案實現特定安全性domains
−
* Barbican now has per project quota support for limiting number of Barbican resources that can be created under a project. By default the quota is set to unlimited and can be overridden in Barbican configuration.
+
* Barbican現在有每個專案支援額度限制，可以一個專案下創建Barbican資源數量。在默認的情況下quota設定為沒有限制可以在Barbican更改設定。
−
* Support for a rotating master key which is used for wrapping project level keys. In this lightweight approach, only the project level key (KEK) is re-wrapped with new master key (MKEK). This is currently applicable only for the PKCS11 plug-in. (http://specs.openstack.org/openstack/barbican-specs/specs/liberty/add-crypto-mkek-rotation-support-lightweight.html)
+
* 支援其使用於包含專案級別 keys的輪轉主要key。在這種輕量級的方法，只有專案級別key (KEK) 是re-wrapped 新的主要的key (MKEK)。目前只適用於 PKCS11 plug-in 。(http://specs.openstack.org/openstack/barbican-specs/specs/liberty/add-crypto-mkek-rotation-support-lightweight.html)
−
* Updated Barbican's root resource to return version information matching Keystone, Nova and Manila format. This is used by keystoneclient's versioned endpoint discovery feature.
+
* 更新Barbican's root資源返回版本訊息符合Keystone, Nova 和 Manila 格式。這是使用keystoneclient's的版本端點查詢功能。
−
* Removed administrator endpoint as all operations are available on a regular endpoint. No separate endpoint is needed as access restrictions are enforced via Oslo policy.
+
* 移除管理員對任何一端點的所有操作。不需要單獨終端訪問權限是透過Oslo進行管理.
−
* Added configuration for enabling sqlalchemy pool for the management of SQL connections.
+
* 新增對啟用sqlalchemy pool連接SQL管理配置。
−
* Added ability to list secrets which are accessible via ACL using GET /v1/secrets?acl-only=true request.
+
* 新增功能列出secrets，透過使用GET /v1/secrets?acl-only=true 訪問ACL。
−
* Improved functional test coverage around Barbican APIs related to ACL operations, RBAC policy and secrets.
+
* 改進功能測試覆蓋率，圍繞著有關ACL操作Barbican APIs，RBAC政策和secret
−
* Fixed issues around creation of SnakeOil CA plug-in instance.
+
* 修復創建SnakeOil CA plug-in instance問題
−
* Barbican client CLI can now take a Keystone token for authentication. Earlier only username and password based authentication was supported.
+
* Barbican client CLI 現在可以採取Keystone token認證。支援在以前唯一的使用者名稱和密碼認證
−
* Barbican client now has ability to create and list certificate orders.
+
* Barbican client 現在有能裡創建和列表憑證命令
  
−
=== Upgrade Notes ===
+
=== 升級提示 ===
  
−
* Removed project secret association table. Secret project relationship is maintained by foreign key. For more detail, see http://specs.openstack.org/openstack/barbican-specs/specs/liberty/data-remove-tenant-secret-assoc.html .
+
* 刪除專案secret關聯表。Secret專案的關係是透過foreign key維護。欲瞭解更多詳細資訊，請參閱 http://specs.openstack.org/openstack/barbican-specs/specs/liberty/data-remove-tenant-secret-assoc.html .
−
* Renamed barbican configuration file to <code>barbican.conf</code>.
+
* 更改 barbican名稱設定文件為<code>barbican.conf</code>.
  
−
== OpenStack Image Service (Glance) ==
+
== OpenStack 映像檔服務 (Glance) ==
  
−
Updated project guide that includes some details on operating, installing, configuring, developing to and using the service: http://docs.openstack.org/developer/glance/
+
更新的專案指南,包括細節的操作、安裝、配置、開發與使用的文件在：http://docs.openstack.org/developer/glance/
  
−
=== Key New Features ===
+
=== 新功能 ===
  
−
* Added support for uploading signed images. For more information, see http://specs.openstack.org/openstack/glance-specs/specs/liberty/image-signing-and-verification-support.html .
+
* 新增支援簽署的映像檔上傳功能。更多的資訊,請參考 :http://specs.openstack.org/openstack/glance-specs/specs/liberty/image-signing-and-verification-support.html .
−
* Scrubbing of images in parallel is now possible. For more information, see http://specs.openstack.org/openstack/glance-specs/specs/liberty/scrub-images-in-parallel.html .
+
* 平行映像檔的擦洗,現在是可能的。更多的資訊,請參考: http://specs.openstack.org/openstack/glance-specs/specs/liberty/scrub-images-in-parallel.html .
−
* The health of a Glance node can be monitored using the healthcheck middleware. For more information, see http://specs.openstack.org/openstack/glance-specs/specs/liberty/healtcheck-middleware.html .
+
* Glance 節點的健康狀況可以使用 healthcheck 中介軟體進行監控。更多資訊,請參考:http://specs.openstack.org/openstack/glance-specs/specs/liberty/healtcheck-middleware.html .
−
* The EXPERIMENTAL Artifacts API is now available for use. Please note, it is subject to change in the future until it becomes a standard API.
+
* 實驗性的 Artifacts API 現在已可以使用。請注意,在成為正式的 API 之前有可能會變化。
−
* S3 store now has proxy support. For more information, see http://specs.openstack.org/openstack/glance-specs/specs/liberty/http-proxy-support-for-s3.html .
+
* S3 儲存現在有 Proxy。更多的資訊,請參考: http://specs.openstack.org/openstack/glance-specs/specs/liberty/http-proxy-support-for-s3.html .
−
* Swift store now has v3 authentication support.
+
* Swift 儲存現在支援了 v3 認證
−
* python-glanceclient now support some advanced aspects of keystone sessions.
+
* python-glanceclient 現在支援了一些高級的 keystone session
−
* python-glanceclient now supports tags for Metadata Definition Catalog.
+
* python-glanceclient 現在支援 tags 來定義 Metadata 目錄
  
−
=== Upgrade Notes ===
+
=== 升級提示 ===
  
−
* python-glanceclient now defaults to using Glance API v2 and if v2 is unavailable, it will fallback to v1.
+
* python-glanceclien現在預設使用Glance API v2 如果 v2 不可以使用, 將會使用 v1.
−
* Dependencies for backend stores are now optionally installed corresponding to each store specified.
+
* 後端儲存的依賴現在可以選擇安裝對應規定的儲存
−
* Some stores like swift, s3, vmware now have python 3 support.
+
* 有一些儲存像是swift, s3, vmware 現在已經支援python 3.
−
* Some new as well as updated default metadata definitions ship with the source code.
+
* 一些新的以及更新的預設metadata定義附帶source code.
−
* More python 3 support added to Glance API, and now continuous support is extended by the means of tests to ensure compatibility.
+
* 更多的python 3 支援增加到 Glance API, 現在持續支援測試確保相容性
−
* utf-8 is now the default charset for the backend MySQL DB.
+
* utf-8 現在已經是後台MySQL DB的預設charset .
−
* Migration scripts have been updated to perform a sanity check for the table charset.
+
* 遷移腳本已經被更新並月來進行晚整性檢查的charset
−
* 'ram_disk' and 'kernel' properties can now be null in the schema and 'id' is now read only attribute for v2 API.
+
* 'ram_disk' 和 'kernel' 特性現在在架構中為null而且'id'對v2 API現在只是已讀.
−
* A configuration option <code>client_socket_timeout</code> has been added  to take advantage of the recent eventlet socket timeout behaviour.
+
* 一個設定選項<code>client_socket_timeout</code>已經被新增到最近的eventlet socket逾時設定.
−
* A configuration option <code>scrub_pool_size</code> has been added to set the number of parallel threads that a scrubber should run and defaults to 1.
+
* 一個設定選項 <code>scrub_pool_size</code> 已經被新增到scrubber同時線程預設為1
−
* An important bug that allowed to change the image status using the Glance v1 API has now been fixed.
+
* 允許使用Glance v1 API 來改變image狀態這個重要的錯誤已經被修正
  
−
=== Deprecated Features ===
+
=== 已棄用的功能 ===
  
−
* The experimental Catalog Index Service has been removed and now is a separate project called Searchlight.
+
* 實驗性的Catalog Index服務已經被刪除，現在為一個新的專案叫做Searchlight.
−
* The configuration options <code>scrubber_datadir</code>, <code>cleanup_scrubber</code> and <code>cleanup_scrubber_time</code> have been removed following the removal of the file backed queuing for scrubber.
+
* 設定選項 <code>scrubber_datadir</code>, <code>cleanup_scrubber</code> 和 <code>cleanup_scrubber_time</code>已經從被刪除，被刪除的還有scrubber文件後台陣列
  
−
== OpenStack Shared File System (Manila) ==
+
== OpenStack 共享式檔案系統服務 (Manila) ==
  
−
=== New Features ===
+
=== 新功能 ===
  
−
* Enabled support for availability zones.
+
* 可用區域啟用支援.
−
* Added administrator API components to share instances.
+
* 新增 administrator API 元件到share instances.
−
* Added pool weigher which allows Manila scheduler to place new shares on pools with existing share servers.
+
* 增加pool weigher來允許Manila scheduler在資源池中使用現有的share servers來提供新的共享。
−
* Support for share migration from one hostpool to another hostpool (experimental).
+
* 支援共享遷移從hostpool到另一個hostpool (試驗階段)。
−
* Added shared extend capability in the generic driver.
+
* 在共通的driver中新增共享擴展能力。
−
* Support for adding consistency groups, which allow snapshots for multiple filesystem shares to created at the same point in time (experimental).
+
* 支援新增consistency groups，允許建立多個filesystem，且在同一時間共享快照 (試驗階段)。
−
* Support for consistency groups in the NetApp cDOT driver and generic driver.
+
* 支援NetApp cDOT driver和通用驅動程式的一致性群組。
−
* Support for oversubscription in thin provisioning.
+
* 支援精簡配置的oversubscription。
−
* New Windows SMB driver:
+
* 新的Windows SMB driver:
−
** Support for handling Windows service instances and exporting SMB shares.
+
** 支援處理Windows服務instance和輸出SMB共享。
−
* Added new <code>osapi_share_workers</code> configuration option to improve the total throughput of the Manila API service.
+
* 增加新的<code>osapi_share_workers</code>配置選項來改善Manila API service總體的吞吐量(throughput)。
−
* Added share hooks feature, which allows actions to be performed before and after share drive methods calls, call additional periodic hook for each 'N' tick, and update the results of a driver's action.
+
* 新增share hooks功能，允許共享驅動程式方法呼叫之後或動作執行之前，每N次呼叫額外的hook更新驅動動作的結果。
−
* Improvements to the NetApp cDOT driver:  
+
* 改善NetApp cDOT driver:  
−
** Added variables netapp:dedup, and netapp:compression when creating the flexvol that backs up a new manila share.
+
** 新增變數netapp:dedup和netapp:compression當建立flexvol，備份一個新的manila share。
−
** Added manage/unmanage support and shrink_share support.
+
** 新增manage/unmanage 支援和shrink_share支援。
−
** Support for <code>extended_share</code> API component.
+
** 支援<code>extended_share</code>API元件。
−
** Support for netapp-lib PyPI project to communicate with storage arrays.
+
** 支援netapp-lib PyPI project讓儲存陣列溝通。
−
* Improvements to the HP 3PAR driver:
+
* 改善HP 3PAR driver:
−
**Added reporting of dedupe, thin provisioning and hp3par_flash_cache capabilities. This allows share types and the CapabilitiesFilter to place shares on hosts with the requested capabilities.
+
**新增dedupe, thin provisioning和hp3par_flash_cache的容量報告。這樣允許共享類型和CapabilitiesFilter根據請求的容量在主機分配共享。
−
**Added share server support.
+
**新增分享伺服器支援。
−
* Improvements to the Huawei Manila driver:
+
* 改善Huawei Manila driver:
−
** Added support for storage pools, extend_share, manage_existing, shrink_share, read-only share, smartcache and smartpartition.
+
** 新增支援儲存池、extend_share、manage_existing、shrink_share、read-only share、smartcache以及smartpartition。
−
** Added reporting of dedupe, thin provisioning and compression capabilities.
+
** 新增重複刪除(dedupe)的報告，簡化配置和壓縮能力。
−
* Added access-level support to the VNX Manila driver.
+
* 新增access-level來支援VNX Manila driver。
−
* Added support for the Manila HDS HNAS driver.
+
* 新增支援Manila HDS HNAS driver。
−
* Added GlusterFS native driver.
+
* 新增GlusterFS native driver。
−
** GlusterFS drivers can now specify the list of compatible share layouts.
+
** GlusterFS drivers現在可以列出指定相容share layouts。
−
* Added microversion support (v2 API).
+
* 新增microversion支援 (v2 API)。
  
−
=== Deprecated Features ===
+
=== 已棄用的功能 ===
  
−
* The <code>share_reset_status</code> API component is deprecated and replaced by <code>share_instance_reset_status</code>.
+
* <code>share_reset_status</code> API 元件已棄用,並 被取代為 <code>share_instance_reset_status</code>.

Latest revision as of 06:39, 30 October 2015

Other languages:
Deutsch • ‎English • ‎日本語 • ‎한국어 • ‎中文（简体）‎ • ‎中文（台灣）‎

OpenStack Liberty更新說明

Contents

OpenStack 物件儲存 (Swift)

完整的版本更新說明請參閱 https://github.com/openstack/swift/blob/master/CHANGELOG

新功能

  • 透過設定一個大於0的整數，允許一個以上的object-servers-per-disk，在[DEFAULT]中的"servers_per_port"設定，設定object-server或是replication server的設定。這個設定值決定了許多不同的object-server workers處理一個唯一local port 在ring。在這個模式下，父類別swift-object-server處理繼續使用原本使用者去執行(例如:如果需要low-port綁定須使用root帳號)。他綁定所有在ring定義的ports。然後為每一個監聽socket分離出一個指定數量的workers。子類別，每一個port的服務，降低權限並且表現出object-server workers狀態，但有一個例外:ring在每個disk擁有唯一的port， object-server只單獨處理每一個disk請求。父類別偵測到已經掛掉的服務並且重新啟動他們(用正確的監聽socket)。當發現一個更新的ring檔案，新啟動停止的服務，並在服務中仔入一個新的port，並且當在ring找不到的時候，後停用多餘的服務。ring檔案啟動是在每個object-server設定中由"ring_check_interval"參數進行設定(預設為15秒)。在測試的時候，這種部屬配置(預設3秒)降低了請求延遲，改善了每秒的請求，與存在在"workers" 設定比較的話，隔離速度比較慢的disk IO請求。若要使用這個設定，每個device必須要增加到ring並使用不同的port。
  • object server 包括一個 "container_update_timeout" 設定 (預設設定為1秒)。這個值包含object server服務等待container返回object PUT操作之前更新列表秒數。以前，object server將會等待container server 3秒回應。當叢集container繁忙時新的行為大幅降低了object PUT的延遲(例如:當container非常大的時候)。如果將這個值設定太底可能導致 client PUT'ing一個objcet中無法馬上找到對象。如果設定值太高會增加client延遲當container servers繁忙。
  • 可以對靜態大型物件(Static Large Object, SLO)分段指定範圍。
  • 允許 SLO PUT 操作放棄預先分段完整性的檢查。之前方式是在 manifest 的每個分段引用,且也需要設定一個正確的 etag 與 bytes。這些欄位現在允許 設定 "null" 直來跳過這些特定的檢查。
  • Replicator設定現在支援"rsync_module" 來允許每個設備rsync模組。此設定可以讓操作人員能夠控制並調整Swift叢集流量並且隔離複製硬碟的IO到指定的設備。情參閱文件檔和設定範例文件的詳細訊息。
  • Ring 的改變
    • Partition 的配置不再使用port號來配置分區。在一個小型叢集運行一個object server提高分散性，並且他不會影響正在執行的object server。
    • 新增 ring-builder-analyzer 工具來簡化測試與分析 ring 管理維護
    • Ring 驗證時如果一個設備被分配到同一區很多次就會跳出警告。這個情況發生在ring不平衡的時候(例如:兩個server其中一個server有多餘的空間大於另外一個)
  • TempURL被修復了(關閉 CVE-2015-5223)

    不要允許 PUT tempurls 建立指向其他資料。具體來說,不允許透過 PUT tempurl 建立 DLO 物件 manifests。這防止發現性攻擊,這種攻擊能夠利用任何的 PUT tempurl 偵測到被 DLO 物件 manifest 建立的私有資料,並且使用 PUT tempurl 指向物件

  • Swift 現在會再每一個策略基礎上發送 StatsD metrics。
  • 修復了一個 Keystone 整合問題,這問題會導致服務帳戶的 COPY 請求能成功，即使這個服務沒有 token 包含在這個請求中。.
  • 批量上傳現在在檔案上處理使用者 xattrs,在處理建立物件時,使用給定的存檔作為物件 metadata。
  • 在物件複製中提交警告 Log，如果 "handoffs_first" 和 "handoff_delete" 有設定
  • 允許在 Swift-recon 開啟物件複製失敗的次數
  • 在分散工具中新增支援儲存策略
  • 在 swift-dispersion 支援了 keystone v3 domains
  • 在 /info endpoint 新增了 domain_remap 資訊
  • 在 domain_remap 中介軟體配置中支援 “default_reseller_prefix”
  • 透過設定 "rsync_compress" 配置,允許 rsync 使用壓縮。如果設定為 true，壓縮僅在不同區域 rsync 時生效。在一些情況下，這能加速跨領域複製時的資料傳輸。
  • 在 swift-recon 中新增時間同步檢查(--time 參數)
  • 一個大型的 accounts 上 account 收割機執行速度加快。
  • 各式各樣的其他小 Bug 修復與優化。

升級提示

  • 相依性改變
    • 新增 six 相依。這部分作為支援 Python 3 的一部分。
    • 捨棄對 Python 2.6 的支援。
  • 配置改變
    • 最近 Python 版本將請求 Headers 的數量限制為 100。對於客制化的中介軟體來說大低了。swift.conf 新的 "extra_header_count" 配置值能夠用來增加 Headers 的數量。
    • 將 "run_pause" 設定為 "interval" (目前配置採用 run_pause 仍可以運作)。未來的版本將移除 run_pause。
  • 版本化的寫入功能已被重構，並且在中介軟體重新實現。需要明確的在 versioned_writes 中介軟體新增你的 proxy pipeline,但是不要去掉或者停用已經存在的Container 服務配置("allow_versions")。這個已經存在的 Container 服務配置開啟保證已經存在的 Container 繼續被版本化。更多詳細的升級資訊請參考：http://swift.openstack.org/middleware.html#how-to-enable-object-versioning-in-a-swift-cluster

OpenStack 網路服務 (Neutron)

新功能

  • Neutron現在支援IPv6 Prefix Delegation，來自動分配IPv6子網路的CIDRs，此功能的詳細資訊與使用配置請參考 OpenStack Networking Guide.
  • Neutron現在公開了QoS API，而初步提供的頻寬為port level，API, CLI, 配置和其他訊息請參閱： [1].
  • 路由的高可靠(L3 HA/VRRP)現在在第二層population(l2pop)被啟動時工作。 [2].
  • VPNaaS相關驅動現在和HA路由器相容。
  • Networks的HA路由器使用VRRP traffic 現在需要配置使用特定區段類型或實體網路標籤。 [3].
  • OVS agent重新啟動不會影響資料層連接。
  • Neutron網路現在支援role base access control。 [4].
  • LBaaS V2 相關驅動現在是基於Octavia，一個operator級別的擴展、可靠的負載平衡平台。
  • LBaaS V2 API 目前已經穩定，不再是試驗版本。
  • Neutron現在提供admin手動調度agents，讓tenant使用之前使主機資源被測試。 [5].
  • Neutron現在有一套pluggable IP的管理工具，可以選擇是否使用或第三方IPAM。當初，預設使用IPAM non-pluggable版本。

已棄用和移除的Plugin和Driver

  • metaplugin在Liberty版本中被刪除。
  • IBM SDN-VE monolithic plugin在Liberty版本中被刪除。
  • Cisco N1kV monolithic plugin在Liberty版本中被刪除 (由ML2 mechanism driver取而代之)。
  • Embrane plugin被棄用，將在下一個版本Mitaka中刪除。

已棄用的功能

  • Liberty中FWaaS API被標記為試驗版本，此外，目前的API將會在下一個版本Mitaka被移除，且相關團隊已經在開發新的FWaaS API來取代。
  • LBaaS V1 API已被標記為捨棄，並計畫在將來的版本中刪除。往後則應使用LBaaS V2 API。
  • L3 agent 中的'external_network_bridge'選項已被棄用，支援pyhsnet的bridge_mapping。更多訊息請參考network guide中"Network Node"小節的場景 : http://docs.openstack.org/networking-guide/scenario_legacy_ovs.html

影響效能的因素

  • 舊版本的Trusty Tahr kernel (3.13) 在命名空間增加執行"ip netns exec"效能會出現的線性下樣。 在這樣的情況下可擴展性是很重要的，應該使用之後的kernel版本 (例如 3.19) 。 [在版本 3.13 出現的問題，大多數版本已經被修復了。]


注意： 這個問題應該在Trusty Thar 3.13.0-36.63以及之後的版本被修復。更多訊息請參閱： https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1328088

使用Octavia驅動程式，建立Neutron-LBaaS負載平衡時，不使用硬體虛擬化將會導致效能低下，這是因為環境中QEMU使用TCG加速套件替代KVM加速套件而沒有使用KVM可用的硬體虛擬化。我們建議開啟運算節點的硬體虛擬化，或在使用Octavia驅動程式時使用巢狀虛擬化來代替虛擬環境。 以下連結查看在DevStack中如何設定巢狀虛擬化來代替KVM：http://docs.openstack.org/developer/devstack/guides/devstack-with-nested-kvm.html

OpenStack 運算服務 (Nova)

新功能

API

Scheduler

在Scheduler架構演變扔在持續中，以及關鍵的bug修復:

Cells v2

Cells v2 目前還是處於不能用的狀態, 但我們增加了一些配套基礎設施:

Compute Driver 功能

Libvirt
VMware
Hyper-V
Ironic

其他功能

升級提示

  • 如果你是從Kilo版本來的，再升級到Liberty之前請先升級到最新版本。由於bug https://bugs.launchpad.net/nova/+bug/1474074 修正從Kilo版本訪問Liberty節版本節點問題
  • RAM 和 CPU分配比率現在是由nova-compute所定義的(所以每個compute節點)。分配率也需要提供scheduler服務。取決於compute節點是否運行 Kilo 或是 Liberty，分配比率表現不同 : 如果compute節點運行Kilo該compute的節點CPU and RAM預設設定將會是在controller的nova.conf上，或是compute節點是Liberty那麼你就可以配置compute分配率為CPU and RAM。為了給操作者提供的分配率所有compute節點，預設分配比勒將是在nova.conf設定為0.0(即使對於controller)。這並不代表分配率實際上是0.0，指示操作者提供那些在下一個版本之前 (例如 Mitaka)。需要了解的是，預設配置扔然是16.0為cpu_allocation_ratio 和 1.5為ram_allocation_ratio。
  • 升級Neutron服務"network-vif-deleted"之前nova-compute應該升級到Liberty版本事件event: https://review.openstack.org/#/c/187871/
  • Rootwrap過濾必須升級之後版本加入 'touch'指令。
    • 在Launchpad中bug提到 imagebackend 和 imagecache之間的條件競爭 1256838.
    • 在這情況下如果base image被 ImageCacheManager刪除當 imagebackend的image複製到instance路徑，那麼instance會出現錯誤狀態
    • 為了解決這個問題，有必要改變並增加在compute.filters 'touch'指令 https://review.openstack.org/#/c/217579/.
    • 在案例競爭條件，當libvirt已經改變基本文件所有權 libvirt-qemu同時imagebackend被複製image，然後我們使用os.utime更新檔案時發生拒絕錯誤。要解決這個錯誤我們需要使用root使用者權限去更新存取'touch'指令。
  • DiskFilter現在是由部分 scheduler_default_filters 在Liberty https://review.openstack.org/#/c/207942/
  • 現在只能對應一個vCenter 叢集到一個nova-compute節點 https://review.openstack.org/#/c/103916/
  • Libvirt driver parallels 已經更名為 virtuozzo
  • Orphaned tables - iscsi_targets, volumes - 已經被刪除
  • 預設paste.ini已經被所有節點更新使用v2.1 API，而v3 節點已經被移除。相容模式middlewear是用來放寬v2.1對/v2 和 /v1.1驗證
  • 對於DB模式降階代碼已經被刪除 : https://blueprints.launchpad.net/nova/+spec/nova-no-downward-sql-migration
  • 預設DB driver我們目前測試是在pymysql 而不是Python-MySQL
  • "powervm" hv_type shim 已經被移除。這只會影響PowerVC driver on stackforge哪個使用舊的images與with hv_type=powervm在image metadata
  • libvirt在Mitaka最低需求版本將會是0.10.2。libvirt本本 < 0.10.2將不再 Liberty使用: https://review.openstack.org/#/c/183220/
  • libvirt.remove_unused_kernels設定選項已經廢除，現在預設為True: https://review.openstack.org/#/c/182315/

已棄用的功能

  • 在禁用tree API擴展的能力已經被棄用 (https://blueprints.launchpad.net/nova/+spec/nova-api-deprecate-extensions)
  • 從 2.21.0開始novaclient.v1_1 模組已經被棄用 [[6]][[7]] 我們將會在第一個Mitaka版本釋出移除python-novaclient Mitaka.
  • 從2.29.0開始方法`novaclient.client.get_client_class` 已經過時 [[8]] 該方法將在Mitaka版本刪除。
  • weighers上使用mute_weight_value已經被否決， 包括使用Cells。
  • '在Libvirt driver上使用remove_unused_kernels 已經不被使用.
  • 目前使用的vcenter driver最小版本為5.1.0，在 Liberty版本會跳出警告訊息，在Mitaka版本低於5.1.0將會被刪除不使用
  • API v3 將會不再使用，並在paste.ini中刪除

OpenStack 計量服務 (Ceilometer)

關鍵的新功能

  • 創建Aodh來處理警報功能。
  • Metadata caching - 減少nova API輪詢(polling)的負載。
  • meters的聲明
    • 能夠根據定義meter樣板來產生meters。
    • 能夠輪詢(poll)特別定義的SNMP。
  • 支援資料從Ceilometer發佈至Gnocchi。
  • 強制limit - limit強制查詢執行。limit必須明確地提供給查詢，否則結果強制設為默認limit。
  • 分散, 協調notification agents - 支援工作負載分割跨多個notification agents。
  • Events RBAC 支援。
  • PowerVM hypervisor 支援。
  • 改善MongoDB查詢支援 - 改善statistic calculations.。
  • 其他meter支援 :
    • Magnum meters
    • DBaaS meters
    • DNSaaS meters

Gnocchi功能

  • 實現第一個版本的influxdb driver。

Aodh功能

  • 事件警報 - 當接收到事件能夠觸發一個動作。
  • 警報的信任支持 link.

升級提示

  • ceilometer使用的一些middleware名字改變採用向後不相容的方式。 再升級之前， 編輯 paste.ini 檔案，修改 oslo.middleware 為 oslo_middleware. 例如：使用 sed -ri 's/oslo\.middleware/oslo_middleware/' api_paste.ini
  • Ceilometer中notification agent是收集資料的核心服務，它處理所有的transformations和publishing。 Polling agents現在延緩所有processing到notification agents，且必須部署為tandem。
  • 強制limit添加到每個請求中，如果沒有limit，將會被強制視為預設limit。

已棄用的功能

  • 不推薦使用Ceilometer Alarms，支持使用Aodh。
  • 不推薦使用RPC publisher和collector，支持使用topic based notifier publisher。
  • 依然不推薦使用Non-metric meters，且在未來版本將被移除。

OpenStack 身份驗證服務 (Keystone)

新功能

  • 實驗性: Domain 特定設定選項可以儲存在SQL代替設定文件, 使用新的REST APIs.
  • 實驗性: Keystone 現在支援不用 token授權， 使用 X.509 SSL 使用者驗證.
  • 現在支援per-Identity配置WebSSO.
  • openstack_user_domain 和 openstack_project_domain 屬性增加到SAML判定，用來分別對應用戶與project domains
  • credentials 列表的調用現在能夠使用credential 類型進行過濾.
  • 支持優化out-of-tree drivers 定義穩定Driver Interfaces.
  • 一些功能進行了加強，包括Fernet tokens, Federation, 從資料庫指定domain和角色分配
  • keystone.conf現在有了新的選項，用來判定使用者設定是不是有效的

升級提示

  • EC2 token middleware, 在Juno版本已經捨棄, keystone已經不存在. 已經完全被移到keystonemiddleware package中.
  • compute_port configuration 選項, 在Juno版本中已經不使用,已經不存在.
  • XML middleware 已經完全被刪除, 所以相關配置也從 keystone-paste.ini 設定檔中刪除.
  • stats_monitoring 和 stats_reporting 中的篩選器已經被刪除,所以相關配置檔案也從 keystone-paste.ini 移除.
  • 而外認證的plugin ExternalDefault, ExternalDomain, LegacyDefaultDomain, 與 LegacyDomain, 在Icehouse版本中已經不再使用.
  • keystone.conf 現在為drivers關係入口.例如, drivers現在被定義成 "sql", "ldap", "uuid", 而不是一個完整的路徑.查看設定檔案中的範例
  • 我們現在為keystone-manage 公開entrypoints指令取代文件.
  • 聽過架構keystone-manage db_sync 降級已經不再支援. 僅支援升級.
  • 之前版本增加的"extensions"功能 (OAuth delegation, Federated Identity support, Endpoint Policy, etc) 目前預設都是開啟.
  • 一個新的secure_proxy_ssl_header 設定選項，用於keystone運行在proxy之後的情形.
  • 一些設定選項已經不再使用，重新命名或是移動到新的地方在keystone.conf文件.
  • Domain name 資訊現在可以在策略規則與屬性domain_name.

已棄用的功能

  • 在Eventlet運行Keystone 依然不建議使用，將Mitaka版本中刪除.
  • 使用LDAP 做為後端的資源, 例如projects 和 domains, 目前已經不再使用，在Mitaka版本將刪除.
  • 使用完整路徑driver已經不建議使用，使用entrypoint的方式。在Mitaka版本，entrypoint 必須被使用.
  • 在keystone.conf中[resource] 和 [role]不建議使用指定driver或是不指定driver.在Mitaka版本釋出 resource 和 role drivers預設會使用SQL driver.
  • 在keystone-paste.ini, 使用paste.filter_factory 不建議使用，因為"use" 指令，指定entrypoint.
  • 不指定domain新增user、group和project，在有問題的情況下他會回到預設的domain，目前不建議使用，並且在N版本終將會刪除.
  • 分配管理不建議使用的方式已經刪除，使用 [resource] 和 [role]相同的方式管理

OpenStack 區塊儲存 (Cinder)

新功能

  • 通用的映像檔快取解決方案,常用的 VM 映像檔都能被快取起來,且以 copy-on-write 方式到一個新的 Volume 獲取更多的資訊
  • 無中斷的備份 獲取更多的資訊.
  • 能夠對一致性 Volume的群組進行 clone 獲取更多的資訊
  • 獲取 Volume 儲存後端的列表 (取得 extra-specs).
  • 嵌套的配額
  • 預設的 LVM 後端採用 thin-provisioned
  • 修復 cinder service-list,當驅動程式載入失敗時會顯示為 Down
  • 優化 volume 移轉管理:
    • 能夠查看之前嘗試的移轉是否成功
    • 管理人員可以透過 cinder list 查看移轉狀態
    • 新的 Volume 狀態"維護狀態",保證當移轉進行時,會阻止任何操作行為
    • 優化 Volumes 的 name/id,在移轉完成後的一致性

升級提示

  • 對於 RPC API 的參數變化和在物件化轉化導致無法使用 Liberty c-vol 和 c-api 服務相容 Kilo 或者更早的版本的相關服務

已棄用的功能

  • 已移除 Simple 和 Chance 兩種 Schedulers
  • 已移除棄用的 HDS HUS iSCSI 驅動程式
  • 已移除 Coraid 驅動程式
  • 已移除 Solaris iSCSI 驅動程式
  • 已移除 --force 選項,該選項用於允許上傳映像檔到已經附加的 Volume
  • 將 v1 API 標示為已棄用

OpenStack 編配服務 (Heat)

新功能

Convergence

Convergence是一個新的編配引擎，在Heat中日趨成熟。在Liberty中，使用Convergence的好處為：

  • 更好的資源平行處理 (為了更好的大型templates擴展)
  • 能夠在已經執行更新操作過程中執行stack-update。
  • 更好的處理heat-engine的錯誤 (仍然WIP)

convergence engine可以透過設置 /etc/heat/heat/conf [DEFAULT]中的 convergence_engine=true，設定完成需重新啟動heat-engine。 完成之後，之後創建的stack將會使用convergence engine，而操作之前已存在的stack仍然會使用傳統引擎。

Convergence並未經過產品的測試，因此應該視為beta版本，小心使用。 在Liberty版本中，如果你的目的是評估或擴展測試，我們建議可以啟用convergence。我們考慮在下一個版本Mitaka中將convergence設為預設引擎。 Convergence相關的bugs追蹤在以下launchpadconvergence-bugs tag.

有條件的資源公開

只有在雲端服務中安裝使用者才能使用。 維運人員可以透過標準的政策(policy)規則進一步來控制使用者的使用，請參考 policy.json on per-resource type basis.

heat_template_version: 2015-10-15

2015-10-15 表示YAML文件是HOT template並且包含了到Liberty之前新增或刪除的功能。

  • 移除Fn::Select 功能 (path based get_attr/get_param references should be used instead).
  • 如果get_attr沒有指定<attribute name>， 所有屬性會以的字典格式回傳， 例如：{ get_attr: [<resource name>]}。
  • 增加新的str_split內部函式。
  • 加入支援傳送多list到已存在的list_join函式。
  • 加入支援解析map/list資料到 str_replace和list_join (它們會自動進行json serialized)

REST API/heatclient 新增

  • Stacks現在可以分配一組tag，且stack-list可以透過這些tag來過濾與排序。
  • "heat stack-preview ..."將會回傳已提出stack-update先前的改變。
  • "heat template-validate --show-nested ..." 將會驗證所有的template資源且回傳有用的nested data來建立使用者介面。
  • "heat resource-type-template --template-type hot ..."產生HOT format的樣板(template)。
  • "heat resource-type-list"只顯示可用的類型給使用者，且可透過name、version、support_status來過濾結果。
  • "heat template-version-list"列出template版本。
  • "heat template-function-list ..."列出template版本可用的功能。

加強現有資源

新資源

以下為Heat發佈的新資源:

[1] 這些已存在Kilo的contrib資源因為它們不是非整合專案。這些資源為隨著Heat發佈，且為Big Tent專案。

[2] 這些已存在Kilo的contrib資源因為這些使用者需要管理者。它們隨著Heat的發佈。 維運人員現在能夠透過修改policy.json來隱藏沒有權限的使用者(僅供參考：OS::Nova::Flavor對於非管理的使用者預設隱藏)。

[3] 這些已存在Kilo的contrib資源它們使用的方法不被Heat專案認同。它們現在隨著Heat的發佈且標記不支援(UNSUPPORTED)。

[4] 這些資源還不是OpenStack Big Tene專案，因此標記不支援(UNSUPPORTED)。

使用新的OS::Keystone::*資源，現在能使雲端維運人員來使用Heat templates管理Keystone服務目錄和使用者。

不推薦的資源屬性

許多資源屬性先前已被標記為DEPRECATED， 其中有15個屬性現在標記為隱藏(HIDDEN)， 這代表它們將不再被記錄， 但是已存在的stacks和templates在Heat升級之後繼續運做。 資源類型參考 應需要討論來決定可用資源特性和屬性。

升級提示

配置檔案改變

/etc/heat/heat.conf [DEFAULT] 中明顯的改變：

  • hidden_stack_tags已經被新增，且stack包含這些標籤名字將會從stack-list結果中被隱藏(預設為data-processing-cluster，其中隱藏sahara-created stacks)
  • instance_user將被棄用，且已經完全移除。 Nova servers created with OS::Nova::Server resource will now boot configured with the default user set up with the cloud image. AWS::EC2::Instance仍然創建"ec2-user"。
  • max_resources_per_stack現在可以設為-1來禁止執行。
  • enable_cloud_watch_lite預設為flase，因為這個REST API已被棄用。
  • default_software_config_transport新增新選項ZAQAR_MESSAGE。
  • default_deployment_signal_transport新增新選項ZAQAR_SIGNAL。
  • auth_encryption_key現在記錄要求精確地32個字。
  • list_notifier_drivers 已被棄用且現在已被移除。
  • policy options被移動至[oslo_policy]中。
  • use_syslog_rfc_format已被移除，現在預設為true。

heat.conf中其他明顯的改變：

  • [clients_keystone] auth_uri已經被新增到特定的unversioned keystone url。
  • [heat_api] workers現在預設為4(之前為0，為每一個主機CPU創見一個worker)

policy檔案 /etc/heat/policy.json 現在能夠為每一種資源類型單獨配置訪問策略(policy)，例如： 

   "resource_types:OS::Nova::Flavor": "rule:context_is_admin"

從Kilo升級至Liberty

目前正在進行支援即時sql遷移， 但是仍然建議在升級的過程中暫停Heat服務。 向下SQL schema遷移不再支援。 rollback至Kilo需要恢復預升級資料庫的快照。

OpenStack 資料處理服務 (Sahara)

新功能

  • 新插件與版本:
    • Ambari 插件支援 HDP 2.2 / 2.3
    • 新增 Apache Hadoop 2.7.1, Apache Hadoop 2.6.0 已棄用
    • 新增 CDH 5.4.0, 並支援 NameNode 與 ResourceManager 的 HA
    • 新增 MapR 5.0.0
    • 新增 Spark 1.3.1, Spark 1.0.0 已棄用
    • HDP 1.3.2 與 Apache Hadoop 1.2.1 被移除了
  • 新增支援 Spark EDP jobs 結合 Swift 使用
  • CDH 與 Ambari 插件支援 Spark EDP jobs
  • 支援 public 與 protected 資源
  • 已開始整合 OpenStack Client
  • 支援編輯所有的 Sahara 資源
  • 支援叢集的自動 Hadoop 配置
  • 已棄用直接提供的引擎,並且在 Mitaka 版本將被移除
  • 對 job binaries和資料來源新增 OpenStack Manila NFS 共享作為儲存後端選項
  • 支援對 EDP job 的板模定義和使用介面配置

已棄用的功能

  • 直接提供的引擎(Direct provisioning engine)
  • Apache Hadoop 2.6.0
  • Spark 1.0.0
  • 所有 Hadoop 1.X 版本已移除

OpenStack Search (Searchlight)

這是第一個Searchlight版本. Searchlight的目的是大幅提高通過請求使用者搜索查詢的功能和各種OpenStack 雲的服務性能. 它提供了跨OpenStack的服務Keystone RBAC 基於搜索通過檢驗自己的數據到ElasticSearch並提供一個安全層面對輸入搜索查詢.ElasticSearch是基於Lucene搜索服務.他提供了一個distributed, scalable, near real-time, faceted, multitenant-capable, and full-text 的一個RESTful web 引擎介面

新功能

新的資源類型索引

升級提示

N/A

已棄用的功能

N/A

OpenStack DNS管理服務 (Designate)

新功能

  • 實驗的: Hook Point API
  • Horizon Plugin 移除 tree
  • Purging 刪除 domains
  • Ceilometer "exists" 每個周期事件 domain
  • ASync actions
    • Import
    • Export
  • Active /passive 對於designate-pool-manager 週期性任務故障轉移
  • OpenStack 用戶端集合

其他的 DNS 伺服器後端

  • InfoBlox
  • Designate

升級提示

  • 新的服務designate-zone-manager
    • 建議使用 tooz 支援後台.
    • 建議ZooKeeper ,或是任何tooz支援.
    • 如果tooz 後台不能使用, 所有zone-managers 將承擔所有區域的擁有權，而且在每個小時會有 'n' "exists" ，其中 'n' 是 zone-manager的處理次數
  • designate-pool-manager 可以做 active/passive 故障轉移的週期性任務.
    • 建議使用支援 tooz 後台.
    • 如果不使用tooz 當作後台, 所有pool-managers 將承擔pool的所有權， 和多個週期性任務將運行。 這可能導致無法預期的結果.

已棄用的功能

  • V1 API
    • 目標初步通知, 因為有操作扔然需要Designate CLI interface 其中 talks to V1, 和 Horizon panels 只有talk to V1.

OpenStack 訊息佇列服務 (Zaqar)

新功能

  • Pre-signed URL - 一個新的REST API 端點支援 pre-signed URL, 他提供足夠的控制權限被源共享, 不影響安全性.
  • Email Notification - 一個新的通知服務任務driver, 這可能需要一個 Zaqar 用戶的電子郵件位址。當有新的訊息發佈到queue，使用者將通過電子郵件收到訊息
  • Policy Support - 支援 fine-grained 權限控制與 policy.json 文件向大多數的其他OpenStack組件.
  • Persistent Transport - 增加了對websocket支援，對Zaqar一個持久傳輸的代替。現在使用者可以建立long-lived連接之間他們應用程式和Zaqar相互交換大量數據，而不是連接建立增加消耗。

OpenStack 儀表板服務 (Horizon)

新功能

  • 新的網路拓樸圖 - 網路拓樸圖已替換為互動式圖形包含可折疊網路(collapsible networks)，且 scales 在大規模的部署做的更好
  • 插件的改善 - Horizon 能自動偵測到被列入的JavaScript 檔案，且現在有機制能將可插拔的 SCSS 與 Django 模板進行覆寫。

升級提示

OpenStack 資料庫即服務 (Trove)

新功能

  • Redis
    • Redis 的組態群組
    • 支援叢集
  • MongoDB
    • 單一實例的備份與恢復
    • 使用者與資料庫管理
    • 組態群組 (Configuration Groups)
  • Percona XtraDB 叢集伺服器
    • 支援叢集
  • 允許部署人員分配實例的規格於特定資料儲存
  • Horizon 支援資料庫叢集
  • 資料儲存(datastore)與版本管理 API
  • 能在一個 admin tenant 中部署 Trove 實例, 這樣實例就可以對使用者隱藏

OpenStack 裸機服務(Ironic)

Ironic 已經切換到 intermediate release model 並在Liberty版本期間發行4.0版。4.2版本形式是基於OpenStack整合Liberty版本並獲得穩定更新。

請參閱完整版本發行說明: http://docs.openstack.org/developer/ironic/releasenotes/index.html

新功能

  • 增加 "ENROLL" 硬體狀態，這是預設的狀態對於新創建的節點。
  • 增加 "abort"，當使用者正在進行時，允許使用者中斷一些操作。
  • 在REST API改進查詢跟過濾的支援。
  • 增加支援 CORS middleware.

硬體驅動程式

  • 增加硬體drivers一個新的BootInterface，which splits functionality out of the DeployInterface.
  • iLO 虛擬介面drivers可以不用Swift運作.
  • 新增Cisco IMC driver.
  • 新增OCS Driver.
  • 新增UCS Driver.
  • 新增Wake-On-Lan Power Driver.
  • ipmitool driver 支援 IPMI v1.5.
  • 增加支援 SNMP driver for “APC MasterSwitchPlus” series PDU’s.
  • pxe_ilo driver 現在支援 UEFI Secure Boot (previous releases of theiLO driver only supported this for agent_ilo and iscsi_ilo).
  • 新增 Virtual Media support to iRMC Driver.
  • 新增 BIOS configuration to DRAC Driver.
  • PXE drivers now support GRUB2.

已棄用的功能

  • "vendor_passthru" 和 "driver_vendor_passthru" DriverInterface的方法已經被刪除。這些在Kilo版本已經過時並且被@passthru decorator取代。
  • 遷移工具從Nova "baremetal"部署導入數據已經被移除
  • 捨棄 "parallel" 選項以週期性任務decorator.
  • 刪除過時 ‘admin_api’ 策略規則.
  • 原始"bash"部屬ramdisk支援已經被棄用並會在兩個周期刪除。 ironic-python-agent專案應被用於所有部屬drivers

升級提示

  • 新創建的節點預設為新ENROLL狀態. 在之前, 節點預設為AVAILABLE, 這可能導致硬體提早出現在Nova.
  • 在Kilo版本增加API headers，意味著希望與Liberty API 進行互動的任何用戶端必須通過每個HTTP請求相應版本的字串。目前API版本為1.14

OpenStack 金鑰管理服務 (Barbican)

新功能

  • 新增專案管理員能力去創建每個專案憑證授權。此外, 專案管理員能夠定義和管理每一個專案優先憑證配發機構(CAs)。讓允許專案實現特定安全性domains
  • Barbican現在有每個專案支援額度限制，可以一個專案下創建Barbican資源數量。在默認的情況下quota設定為沒有限制可以在Barbican更改設定。
  • 支援其使用於包含專案級別 keys的輪轉主要key。在這種輕量級的方法，只有專案級別key (KEK) 是re-wrapped 新的主要的key (MKEK)。目前只適用於 PKCS11 plug-in 。(http://specs.openstack.org/openstack/barbican-specs/specs/liberty/add-crypto-mkek-rotation-support-lightweight.html)
  • 更新Barbican's root資源返回版本訊息符合Keystone, Nova 和 Manila 格式。這是使用keystoneclient's的版本端點查詢功能。
  • 移除管理員對任何一端點的所有操作。不需要單獨終端訪問權限是透過Oslo進行管理.
  • 新增對啟用sqlalchemy pool連接SQL管理配置。
  • 新增功能列出secrets，透過使用GET /v1/secrets?acl-only=true 訪問ACL。
  • 改進功能測試覆蓋率，圍繞著有關ACL操作Barbican APIs，RBAC政策和secret
  • 修復創建SnakeOil CA plug-in instance問題
  • Barbican client CLI 現在可以採取Keystone token認證。支援在以前唯一的使用者名稱和密碼認證
  • Barbican client 現在有能裡創建和列表憑證命令

升級提示

OpenStack 映像檔服務 (Glance)

更新的專案指南,包括細節的操作、安裝、配置、開發與使用的文件在：http://docs.openstack.org/developer/glance/

新功能

升級提示

  • python-glanceclien現在預設使用Glance API v2 如果 v2 不可以使用, 將會使用 v1.
  • 後端儲存的依賴現在可以選擇安裝對應規定的儲存
  • 有一些儲存像是swift, s3, vmware 現在已經支援python 3.
  • 一些新的以及更新的預設metadata定義附帶source code.
  • 更多的python 3 支援增加到 Glance API, 現在持續支援測試確保相容性
  • utf-8 現在已經是後台MySQL DB的預設charset .
  • 遷移腳本已經被更新並月來進行晚整性檢查的charset
  • 'ram_disk' 和 'kernel' 特性現在在架構中為null而且'id'對v2 API現在只是已讀.
  • 一個設定選項client_socket_timeout已經被新增到最近的eventlet socket逾時設定.
  • 一個設定選項 scrub_pool_size 已經被新增到scrubber同時線程預設為1
  • 允許使用Glance v1 API 來改變image狀態這個重要的錯誤已經被修正

已棄用的功能

  • 實驗性的Catalog Index服務已經被刪除，現在為一個新的專案叫做Searchlight.
  • 設定選項 scrubber_datadir, cleanup_scrubber 和 cleanup_scrubber_time已經從被刪除，被刪除的還有scrubber文件後台陣列

OpenStack 共享式檔案系統服務 (Manila)

新功能

  • 可用區域啟用支援.
  • 新增 administrator API 元件到share instances.
  • 增加pool weigher來允許Manila scheduler在資源池中使用現有的share servers來提供新的共享。
  • 支援共享遷移從hostpool到另一個hostpool (試驗階段)。
  • 在共通的driver中新增共享擴展能力。
  • 支援新增consistency groups，允許建立多個filesystem，且在同一時間共享快照 (試驗階段)。
  • 支援NetApp cDOT driver和通用驅動程式的一致性群組。
  • 支援精簡配置的oversubscription。
  • 新的Windows SMB driver:
    • 支援處理Windows服務instance和輸出SMB共享。
  • 增加新的osapi_share_workers配置選項來改善Manila API service總體的吞吐量(throughput)。
  • 新增share hooks功能，允許共享驅動程式方法呼叫之後或動作執行之前，每N次呼叫額外的hook更新驅動動作的結果。
  • 改善NetApp cDOT driver:
    • 新增變數netapp:dedup和netapp:compression當建立flexvol，備份一個新的manila share。
    • 新增manage/unmanage 支援和shrink_share支援。
    • 支援extended_shareAPI元件。
    • 支援netapp-lib PyPI project讓儲存陣列溝通。
  • 改善HP 3PAR driver:
    • 新增dedupe, thin provisioning和hp3par_flash_cache的容量報告。這樣允許共享類型和CapabilitiesFilter根據請求的容量在主機分配共享。
    • 新增分享伺服器支援。
  • 改善Huawei Manila driver:
    • 新增支援儲存池、extend_share、manage_existing、shrink_share、read-only share、smartcache以及smartpartition。
    • 新增重複刪除(dedupe)的報告，簡化配置和壓縮能力。
  • 新增access-level來支援VNX Manila driver。
  • 新增支援Manila HDS HNAS driver。
  • 新增GlusterFS native driver。
    • GlusterFS drivers現在可以列出指定相容share layouts。
  • 新增microversion支援 (v2 API)。

已棄用的功能

  • share_reset_status API 元件已棄用,並 被取代為 share_instance_reset_status.
Retrieved from "https://wiki.openstack.org/w/index.php?title=ReleaseNotes/Liberty/zh-tw&oldid=95160"