Jump to: navigation, search

Difference between revisions of "ReleaseNotes/Liberty/ja"

Line 481: Line 481:
 
== OpenStack DNS (Designate) ==
 
== OpenStack DNS (Designate) ==
  
=== 主要な新機能 ===
+
=== 新機能 ===
  
 
* '''''Experimental''''': Hook Point API
 
* '''''Experimental''''': Hook Point API

Revision as of 15:55, 17 October 2015

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

OpenStack Liberty リリースノート

Contents

OpenStack Object Storage (Swift)

リリースノート全文は https://github.com/openstack/swift/blob/master/CHANGELOG を参照して下さい。

新機能

object-server とレプリケーションサーバ用の設定ファイルの [DEFAULT] 設定セクション中の servers_per_port 設定値を 1 以上の整数にすることで、object-servers-per-disk (ディスク単位のオブジェクトサーバ)を複数にする事ができるようになりました。この設定の整数値は、Ring 中の単一ローカルポートにおいて、いくつの個別の object-server ワーカーがリクエストを処理するかを決定します。このモードでは、親となる swift-object-server プロセスが元々のユーザとして実行を継続します(低レベルポートのバインディングが必要な場合は root になります)。このプロセスは Ring 中で定義された全てのポートをバインドします。その後、親プロセスはリッスンソケット単位で指定された数のワーカーを fork します。子プロセス(ポート単位サーバ)は特権を破棄し、object-server ワーカーが通常持っている挙動とほとんど同じ動作をしますが、1つ例外があります: Ring はディスク単位に個別のポートを持っており、object-server は単一ディスクに対するリクエストのみ処理します。親プロセスはワーカープロセスが死んだ事を検知し、(適切なリッスンソケットを持つ)ワーカープロセスを再起動します。新しいポートを持つサーバ上のデバイスを持った、Ring ファイルのアップデートが見つかった場合、親プロセスは不足しているサーバを新たに実行し、Ring に最早見当たらないポートがあった場合、このポートを持っていた余分のサーバを停止します。Ring ファイルは、長くても object-server 設定ファイル中の各 ring_check_interval パラメータ(いずれもデフォルトは 15秒)で設定されたスケジュールで Ring ファイルがスタートします。テストでは、既存の workers 設定に比べ、このデプロイ設定(値=3)が応答遅延を最も削減し、秒間リクエストを改善し、低速なディスク I/O を分断します。この機能の使用の為、各デバイスは異なるポートを使用して Ring に追加されなければなりません。

  • object server は container_update_timeout 設定(デフォルトは 1秒)を持っています。この値は、オブジェクトの PUT 操作の結果を返す前、 object server が container server による一覧更新を待つ秒数です。従来、object server は container server の応答を最大3秒待っていました。新しい動作では、クラスタ中の container server がビジーの際(例えば、コンテナが非常に大きい場合)、オブジェクトの PUT 遅延を動的に削減します。この値を必要以上に小さく設定する事は、クライアントのオブジェクト PUT 時に、そのオブジェクトが一覧中で即時に発見出来なくなる事になります。この値を必要以上に大きく設定する事は、container server がビジーの際にクライアントへの遅延が大きくなる事になります。
  • Large Object (SLO) セグメント用の範囲指定ができるようになりました。
  • SLO PUT がセグメント単位の統合チェックをしなくてもよくなりました。従来、各セグメントはマニフェスト中で参照され、また正しい etag とバイト設定を必要としていました。これらのフィールドは今回、null を指定する事で指定されたセグメント特有のチェックをスキップできるようになりました。
  • Replicator 設定は今回、デバイス毎の rsync モジュール指定を可能にする rsync_module 値をサポートしました。この設定は、運用者が1つの Swift クラスタ中のレプリケーションを最適化し、特定のデバイスに対するレプリケーションディスク I/O を分離できるようにします。詳細な情報と設定例は、ドキュメントとサンプル設定ファイルを参照して下さい。
  • Ring の変更
    • ポート番号は最早、パーティションの配置に使用されなくなりました。これにより、1 object server/サーバで稼働するクラスタには影響を与えずに、1 object server/ドライブで稼働する小規模クラスタ中のデータ分散を改善します。
    • 一連の Ring 管理操作のより簡単なテストと分析のため、ring-builder-analyzer ツールを追加しました。
    • Ring 検証は今回、同じデバイスに対するパーティション配置が重複した場合、警告を出すようになりました。Ring 中のデバイスが平準化されていない場合(例えば、2サーバのうち1台が明らかにより大きな容量を持っているなど)、この状態が発生します。
  • TempURLの修正(CVE-2015-5223)tempurlを用いたPUTにより他のデータへのポインタを作ることをできないようにしました。特にPUT tempurlによってDLOマニフェストオブジェクトの作成が禁止されました。これにより、PUT tempurlを用いてDLOマニフェストを作り、別のオブジェクトに対するHEADをするといった、プライベートデータに対する発見可能性攻撃を防ぎます。
  • SwiftはStatsDのメトリクスをポリシー毎に出力するようになりました。
  • Keystoneを利用した際にServiceトークンがリクエストに含まれていない場合にServiceアカウントに対するコピーリクエストが成功しうる問題を修正しました。
  • Bulkアップロードでアップロードされたアーカイブに含まれるファイルのユーザxattrが展開されたオブジェクトのメタデータに保存されるようになりました
  • object-replicatorの設定に"handoff_first"か”handoff_delete”が設定されている場合はwarning logが出力されます。
  • object-replicatorの失敗数がswift-reconに記録されるようになりました
  • ストレージポリシーがサポートがswift-dispersionツールでされました。
  • Keystone v3のドメインがswift-dispersionツールでサポートされました。
  • domain_remap middlewareの情報が/infoエンドポイントに追加されました。
  • domain_remap middlewareのコンフィグで"default_reseller_prefix"がサポートされました。
  • "rsync_compress"という設定でrsyncの圧縮機能が使えるようになりました。これをTrueに設定すると、他のリージョンのデバイス転送の場合のみ転送データが圧縮されます。これによりリージョン間のデータ転送が高速化される場合があります。
  • swift-reconで時刻同期チェックのオプションが追加されました。(--timeオプション)
  • account-reaperが大きなアカウントに対してより高速に動作するようになりました。
  • それ以外の多種の小さなバグ修正や改善がありました。

アップグレード時の注意点

  • 依存パッケージの変更
    • sixパッケージが必要になりました。これはPython3サポートに向けた変更です。
    • Python2.6のサポートを終了しました。
  • コンフィグの変更
    • 直近のバージョンのPythonでは1リクエストあたりのHTTPヘッダー数を100に制限しています。この数値はカスタムミドルウェアに対して小さすぎる場合があります。swift.conf中の"extra_header_count"という新しいコンフィグ値はこの許容できるヘッダー数を増やすために使うことができます。
    • "run_pause"の設定が"interval"という名前に変更されました。(現在はrun_pauseのままでも動作します)将来的にはrun_pauseの設定は削除される可能性があります。
  • Versioned Writes (Object Versioning) 機能がリファクタされ、Middlewareとして再実装されました。Proxyのpipelineに明示的にversioned_writes middlewareを挿入すべきですが、もし現在container serverのコンフィグで”allow_versions”を有効にしているならば設定を削除したり無効にしてはいけません。既存のcontainer serverコンフィグの設定は既存のversioningを有効にするのに必要です。さらなるアップグレードに関する注意についてはhttp://swift.openstack.org/middleware.html#how-to-enable-object-versioning-in-a-swift-clusterを参照してください。

OpenStack Networking (Neutron)

新機能

  • Neutron は今回、IPv6 サブネットに対する CIDR の自動割当において IPv6 プレフィックスデリゲーションに対応しました。この機能の使用・設定に関する詳細な情報は、OpenStack Networking Guide を参照してください。
  • Neutron は今回、ポートレベルの帯域幅制限機能を初めて提供する QoS API を公開しました。この機能の API、CLI、設定、追加情報は

[1] にあるでしょう。

  • ルータ高可用性(L3 HA/VRRP)は今回、レイヤー2ポピュレーション(l2pop)が有効の場合に機能します。[2]
  • VPNaaS リファレンスドライバは今回、HA ルータ上で動作するようになりました。
  • HA ルータの VRRP トラフィック用に使用されるネットワークは今回、特定のセグメントタイプまたは物理ネットワークタグを使用して設定されるようになりました。[3]
  • OVS エージェントは今回、データプレーンの接続性に影響を与えずに再起動できるようになりました。
  • Neutron は今回、ネットワーク用のロールベースアクセス制御(RBAC)を提供するようになりました。[4]
  • LBaaS V2 リファレンスドライバは今回、Octavia(事業者品質のスケーラブル・高信頼ロードバランサプラットフォーム)ベースになりました。
  • LBaaS V2 API は最早実験的(experimental)ではありません。今回安定版(stable)となりました。
  • Neutron は今回、管理者が手動でエージェントをスケジュールする方法を提供するようになりました。これにより、ホストリソースがテナント用に有効になる前にテストできるようになりました。[5]
  • Neutron は今回、プラグイン可能な IP アドレス管理(IPAM)フレームワークを実装しました。これにより、サードパーティ製 IPAM や代替機能を利用可能になります。デフォルトでは元々の非プラグイン版 IPAM が有効になります。

廃止予定・廃止されたプラグインとドライバ

  • metaplugin は Liberty リリースで削除されました。
  • IBM SDN-VE 一体型プラグインは Liberty リリースで削除されました。
  • Cisco N1kV 一体型プラグインは Liberty リリースで削除されました(ML2 メカニズムドライバで置換されました)
  • Embrane プラグインは廃止予定になり、Mitaka リリースで廃止されます。

廃止予定の機能

  • FWaaS API は Liberty では experimental(実験的)な機能の扱いです。今後、現在の API が Mitaka で削除され、(Neutron チームが開発中の)新しい FWaaS API で置換される予定です。
  • LBaaS V1 API は廃止予定となり、将来のリリースで削除される予定です。今後は LBaaS V2 API を使用すべきです。
  • L3 エージェントの external_network_bridge オプションは廃止予定となりました。 bridge_mapping の physnet 指定を使用してください。詳細な情報は、ネットワーキングガイドの Network Node の節を参照してください。http://docs.openstack.org/networking-guide/scenario_legacy_ovs.html

性能に関する考察

  • Trusty Tahr に含まれるカーネル (3.13) は、ネームスペース数の増加に伴い「ip netns exec」の実行時に性能が線形に劣化します。スケーラビリティが重要な場合、より後のバージョンのカーネル (例えば 3.19) を使うべきです。【3.13 のどのバージョンでこの問題が発生するかを明記する必要がある。ほとんどのバージョンではこの問題は既に修正済みである】


[注意] この問題は Trusty Thar の 3.13.0-36.63 以降のカーネルバージョンで修正済みです。詳細は次の URL を参照して下さい。 https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1328088

  • Octavia ドライバ使用時には、ハードウェア仮想化のない環境での Neutron-LBaaS ロードバランサの作成が遅いかもしれません。これは、ハードウェア仮想化なしの環境では QEMU が KVM アクセラレータではなく TCG アクセラレータを使用するためです。Octavia ドライバを仮想環境内で使用する場合、compute ノード上でハードウェア仮想化を有効にするか、nested virtualization(訳注:仮想化環境上の仮想化支援機構)を有効にする事をお勧めします。KVM 中で実行される DevStack 用に、nested virtualization をセットアップする詳細な方法については、次のリンクを参照して下さい。http://docs.openstack.org/developer/devstack/guides/devstack-with-nested-kvm.html

OpenStack Compute (Nova)

新機能

API

スケジューラー

scheduler の構造革新は継続中で、これに伴い重要なバグ修正が行われました。

Cells v2

Cells v2 は現在使用可能な状態にありませんが、Cells v2 を支えるインフラの幾つかが追加されました。

Compute ドライバの機能

Libvirt
VMware
Hyper-V
Ironic

その他の機能

アップグレード時の注意

  • 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.
  • 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.
  • 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/
  • Rootwrap filters must be updated after release to add the 'touch' command.
    • There is a race condition between imagebackend and imagecache mentioned in the Launchpad Bug 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.
    • 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/.
    • 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.
  • The DiskFilter is now part of the scheduler_default_filters in Liberty per 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.
  • The Libvirt driver parallels has been renamed to virtuozzo
  • Orphaned tables - iscsi_targets, volumes - have been removed.
  • 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.
  • The code for DB schema downgrades has now been removed: 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
  • The "powervm" hv_type shim has been removed. This only affects users of the PowerVC driver on stackforge which are using older images with hv_type=powervm in the 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/
  • The libvirt.remove_unused_kernels config option is deprecated for removal and now defaults to 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)
  • The novaclient.v1_1 module has been deprecated [[6]][[7]] since 2.21.0 and we are going to remove it in the first python-novaclient release in Mitaka.
  • Method `novaclient.client.get_client_class` is deprecated [[8]] since 2.29.0. The method will be removed in Mitaka.
  • The mute_weight_value option on weighers has been deprecated, including for use with Cells.
  • The remove_unused_kernels configuration option for the Libvirt driver is now deprecated.
  • 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.
  • API v3 specific components have all been deprecated and removed from the default paste.ini

OpenStack Telemetry (Ceilometer)

Key New Features

  • Creation of Aodh to handle alarming service.
  • Metadata caching - reduced load of nova API polling.
  • Declarative meters
    • Ability to generate meters by defining meter definition template.
    • Ability to define specific SNMP meters to poll.
  • Support for data publishing from Ceilometer to 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.
  • Distributed, coordinated notification agents - support for workload partitioning across multiple notification agents.
  • Events RBAC support.
  • PowerVM hypervisor support.
  • Improved MongoDB query support - performance improvement to statistic calculations.
  • Additional meter support:
    • Magnum meters
    • DBaaS meters
    • DNSaaS meters

Gnocchi Features

  • Initial influxdb driver implemented.

Aodh Features

  • Event alarms - ability to trigger an action when an event is received.
  • Trust support in alarms link.

Upgrade Notes

  • The name of some middleware used by ceilometer changed in a backward incompatible way. Before upgrading, edit the paste.ini file for ceilometer to change oslo.middleware to oslo_middleware. For example, using sed -ri 's/oslo\.middleware/oslo_middleware/' api_paste.ini
  • 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.
  • A mandatory limit is applied to each request. If no limit is given, it will be restricted to a default limit.

Deprecated Features

  • Ceilometer Alarms is deprecated in favour or Aodh.
  • RPC publisher and collector is deprecated in favour of a topic based notifier publisher.
  • Non-metric meters are still deprecated, and are to be removed in a future release.

OpenStack Identity (Keystone)

Key New Features

  • Experimental: Domain specific configuration options can be stored in SQL instead of configuration files, using the new REST APIs.
  • Experimental: Keystone now supports tokenless authorization with X.509 SSL client certificate.
  • Configuring per-Identity Provider WebSSO is now supported.
  • openstack_user_domain and openstack_project_domain attributes were added to SAML assertion in order to map user and project domains, respectively.
  • The credentials list call can now have its results filtered by credential type.
  • Support was improved for out-of-tree drivers by defining stable Driver Interfaces.
  • Several features were hardened, including Fernet tokens, Federation, domain specific configurations from database and role assignments.
  • Certain variables in keystone.conf now have options, which determine if the user's setting is valid.

アップグレード時の注意

  • The EC2 token middleware, deprecated in Juno, is no longer available in keystone. It has been moved to the keystonemiddleware package.
  • The compute_port configuration option, deprecated in Juno, is no longer available.
  • The XML middleware stub has been removed, so references to it must be removed from the keystone-paste.ini configuration file.
  • stats_monitoring and stats_reporting paste filters have been removed, so references to it must be removed from the keystone-paste.ini configuration file.
  • The external authentication plugins ExternalDefault, ExternalDomain, LegacyDefaultDomain, and LegacyDomain, deprecated in Icehouse, are no longer available.
  • keystone.conf 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.
  • We now expose entrypoints for the keystone-manage command instead of a file.
  • Schema downgrades via keystone-manage db_sync are no longer supported. Only upgrades are supported.
  • Features that were "extensions" in previous releases (OAuth delegation, Federated Identity support, Endpoint Policy, etc) are now enabled by default.
  • A new secure_proxy_ssl_header configuration option is available when running keystone behind a proxy.
  • Several configuration options have been deprecated, renamed, or moved to new sections in the keystone.conf file.
  • Domain name information can now be used in policy rules with the attribute domain_name.

非推奨の機能

  • Running Keystone in Eventlet remains deprecated and will be removed in the Mitaka release.
  • Using LDAP as the resource backend, i.e for projects and domains, is now deprecated and will be removed in the Mitaka release.
  • 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.
  • In the [resource] and [role] sections of the keystone.conf 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.
  • In keystone-paste.ini, using paste.filter_factory is deprecated in favor of the "use" directive, specifying an 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.
  • Certain deprecated methods from the assignment manager were removed in favor of the same methods in the [resource] and [role] manager.

OpenStack Block Storage (Cinder)

Key New Features

  • A generic image caching solution, so popular VM images can be cached and copied-on-write to a new volume. Read docs for more info
  • Non-disruptive backups Read docs for more info.
  • Ability to clone consistency groups of volumes Read docs for more info.
  • List capabilities of a volume backend (fetch extra-specs).
  • Nested quotas.
  • Default LVM backends to be thin provisioned if available.
  • Corrected cinder service-list to show as Down when a driver fails to initialize.
  • Improved volume migration management:
    • Able to see if previous migration attempt was successful
    • Admins able to monitor migrations via cinder list
    • New volume status of 'maintenance' to prevent operations being attempted while migration is occurring
    • Improve backend volume name/id consistency after migration completes

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.

Deprecated Features

  • Removed Simple and Chance Schedulers.
  • Removed deprecated HDS HUS iSCSI driver.
  • Removed Coraid driver.
  • Remove Solaris iSCSI driver.
  • Removed --force option for allowing upload of image to attached volume.
  • Marked the v1 API as deprecated.

OpenStack Orchestration (Heat)

新機能

Convergence

convergence は、heat ツリーの中で成熟させている新しいオーケストレーションエンジンです。Liberty では、convergence エンジンを使用する利点は次のとおりです。

  • リソース処理の並列度の改善 (大規模テンプレートのスケーラビリティーの改善)
  • すでに更新処理中の stack-update の実行機能
  • heat-engine 障害の処理の改善 (WIP)

convergence エンジンは、/etc/heat/heat/conf ファイルの [DEFAULT] セクションに convergence_engine=true を設定して、heat-engine を再起動することにより、有効化できます。設定すると、その後作成されるスタックは convergence エンジンを使用するようになります。既存のスタックの処理は、それまでのエンジンを使用し続けます。

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 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 policy.json on per-resource type basis.

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.

  • Removes the Fn::Select function (path based get_attr/get_param references should be used instead).
  • If no <attribute name> is specified for calls to get_attr, a dict of all attributes is returned, e.g. { get_attr: [<resource name>]}.
  • Adds new str_split intrinsic function
  • Adds support for passing multiple lists to the existing list_join function.
  • Adds support for parsing map/list data to str_replace and list_join (they will be json serialized automatically)

REST API/heatclient additions

  • Stacks can now be assigned with a set of tags, and stack-list can filter and sort through those tags
  • "heat stack-preview ..." will return a preview of changes for a proposed stack-update
  • "heat template-validate --show-nested ..." will also validate all template resources and return nested data useful for building user interfaces
  • "heat resource-type-template --template-type hot ..." generates a template in HOT format
  • "heat resource-type-list" only shows types available to the user, and can filter results by name, version and support_status
  • "heat template-version-list" lists available template versions
  • "heat template-function-list ..." lists available functions for a template version

Enhancements to existing resources

New resources

The following new resources are now distributed with the Heat release:

[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.

[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).

[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.

[4] These resources are for projects which are not yet OpenStack Big Tent projects, so are documented as 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.

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.

アップグレード時の注意

Configuration Changes

Notable changes to the /etc/heat/heat.conf [DEFAULT] section:

  • 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)
  • 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"
  • max_resources_per_stack can now be set to -1 to disable enforcement
  • enable_cloud_watch_lite is now false by default as this REST API is deprecated
  • default_software_config_transport has gained the option ZAQAR_MESSAGE
  • default_deployment_signal_transport has gained the option ZAQAR_SIGNAL
  • auth_encryption_key is now documented as requiring exactly 32 characters
  • list_notifier_drivers was deprecated and is now removed
  • policy options have moved to the [oslo_policy] section
  • use_syslog_rfc_format is deprecated and now defaults to true

Notable changes to other sections of heat.conf:

  • [clients_keystone] auth_uri has been added to specify the unversioned keystone url
  • [heat_api] workers now defaults to 4 (was previously 0, which created a worker per host CPU)

The policy file /etc/heat/policy.json can now be configured with per-resource-type access policies, for example:

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

Upgrading from Kilo to 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.

OpenStack Data Processing (Sahara)

主要な新機能

  • New plugins and versions:
    • Ambari plugin with supports HDP 2.2 / 2.3
    • Apache Hadoop 2.7.1 was added, Apache Hadoop 2.6.0 was deprecated
    • CDH 5.4.0 was added with HA support for NameNode and ResourceManager
    • MapR 5.0.0 was added
    • Spark 1.3.1 was added, Spark 1.0.0 was deprecated
    • HDP 1.3.2 and Apache Hadoop 1.2.1 was removed
  • Added support for using Swift with Spark EDP jobs
  • Added support for Spark EDP jobs in CDH and Ambari plugins
  • Added support for public and protected resources
  • Started integration with OpenStack client
  • Added support for editing all Sahara resources
  • Added automatic Hadoop configuration for clusters
  • Direct engine is deprecated and will be removed in Mitaka release
  • Added OpenStack manila NFS shares as a storage backend option for job binaries and data sources
  • Added support for definition and use of configuration interfaces for EDP job templates

非推奨の機能

  • Direct provisioning engine
  • Apache Hadoop 2.6.0
  • Spark 1.0.0
  • All Hadoop 1.X removed

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.

Key New Features

New Resource Types Indexed

アップグレード時の注意

なし

非推奨の機能

なし

OpenStack DNS (Designate)

新機能

  • Experimental: Hook Point API
  • Horizon Plugin moved out of tree
  • Purging deleted domains
  • Ceilometer "exists" periodic event per domain
  • ASync actions
    • Import
    • Export
  • Active /passive failover for designate-pool-manager periodic tasks
  • OpenStack client integration

Addtional DNS Server Backends

  • InfoBlox
  • Designate

アップグレード時の注意

  • New service designate-zone-manager
    • It is recommended to use a supported tooz backend.
    • ZooKeeper is recommended, or anything supported by 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.
  • designate-pool-manager can do active/passive failover for periodic tasks.
    • It is recommended to use a supported tooz backend.
    • 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.

非推奨の機能

  • 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.

OpenStack Messaging Service (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.
  • 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.
  • Policy Support - Support fine-grained permission control with the policy.json file like most of the other OpenStack components.
  • 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.

OpenStack Dashboard (Horizon)

新機能

  • Plugin improvements – Horizon auto discovers JavaScript files for inclusion, and now has mechanisms for pluggable SCSS and Django template overrides.

アップグレード時の注意

OpenStack Trove (DBaaS)

新機能

  • Redis
    • Configuration Groups for Redis
    • Cluster support
  • MongoDB
    • Backup and restore for a single instance
    • User and database management
    • Configuration Groups
  • Percona XtraDB Cluster Server
    • Cluster support
  • Allow deployer to associate instance flavors with specific datastores
  • Horizon support for database clusters
  • Management API for datastore and versions
  • Ability to deploy Trove instances in a single admin tenant, so that the nova instances are hidden from the user

OpenStack Bare metal (Ironic)

Ironic has switched to an 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.

Please see full release notes here: http://docs.openstack.org/developer/ironic/releasenotes/index.html

新機能

  • Added "ENROLL" hardware state, which is the default state for newly created nodes.
  • Added "abort" verb, which allows a user to interrupt certain operations while they are in progress.
  • Improved query and filtering support in the REST API.
  • Added support for CORS middleware.

ハードウェアドライバー

  • Added a new BootInterface for hardware drivers, which splits functionality out of the DeployInterface.
  • iLO virtual media drivers can work without Swift.
  • Added Cisco IMC driver.
  • Added OCS Driver.
  • Added UCS Driver.
  • Added Wake-On-Lan Power Driver.
  • ipmitool driver supports IPMI v1.5.
  • Added support to 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).
  • Added Virtual Media support to iRMC Driver.
  • Added BIOS configuration to DRAC Driver.
  • PXE drivers now support GRUB2.

非推奨の機能

  • 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.
  • The migration tools to import data from a Nova "baremetal" deployment have been removed.
  • Deprecated the "parallel" option to periodic task decorator.
  • Removed deprecated ‘admin_api’ policy rule.
  • 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.

アップグレード時の注意

  • Newly created nodes default to the new ENROLL state. Previously, nodes defaulted to AVAILABLE, which could lead to hardware being exposed prematurely to 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.

OpenStack Key Manager (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.
  • 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.
  • 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)
  • 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.
  • 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.
  • Added configuration for enabling sqlalchemy pool for the management of SQL connections.
  • Added ability to list secrets which are accessible via ACL using GET /v1/secrets?acl-only=true request.
  • Improved functional test coverage around Barbican APIs related to ACL operations, RBAC policy and secrets.
  • Fixed issues around creation of 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 now has ability to create and list certificate orders.

アップグレード時の注意

OpenStack Image Service (Glance)

Updated project guide that includes some details on operating, installing, configuring, developing to and using the service: http://docs.openstack.org/developer/glance/

新機能

アップグレード時の注意

  • python-glanceclient now defaults to using Glance API v2 and if v2 is unavailable, it will fallback to 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.
  • Some new as well as updated default metadata definitions ship with the source code.
  • More python 3 support added to Glance API, and now continuous support is extended by the means of tests to ensure compatibility.
  • utf-8 is now the default charset for the backend MySQL DB.
  • Migration scripts have been updated to perform a sanity check for the table charset.
  • 'ram_disk' and 'kernel' properties can now be null in the schema and 'id' is now read only attribute for v2 API.
  • A configuration option client_socket_timeout has been added to take advantage of the recent eventlet socket timeout behaviour.
  • A configuration option scrub_pool_size has been added to set the number of parallel threads that a scrubber should run and defaults to 1.
  • An important bug that allowed to change the image status using the Glance v1 API has now been fixed.

非推奨の機能

  • The experimental Catalog Index Service has been removed and now is a separate project called Searchlight.
  • The configuration options scrubber_datadir, cleanup_scrubber and cleanup_scrubber_time have been removed following the removal of the file backed queuing for scrubber.

OpenStack Shared File System (Manila)

新機能

  • Enabled support for availability zones.
  • Added administrator API components to share instances.
  • Added pool weigher which allows Manila scheduler to place new shares on pools with existing share servers.
  • Support for share migration from one hostpool to another hostpool (experimental).
  • Added shared extend capability in the generic driver.
  • Support for adding consistency groups, which allow snapshots for multiple filesystem shares to created at the same point in time (experimental).
  • Support for consistency groups in the NetApp cDOT driver and generic driver.
  • Support for oversubscription in thin provisioning.
  • New Windows SMB driver:
    • Support for handling Windows service instances and exporting SMB shares.
  • Added new osapi_share_workers configuration option to improve the total throughput of the Manila API service.
  • 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.
  • Improvements to the NetApp cDOT driver:
    • Added variables netapp:dedup, and netapp:compression when creating the flexvol that backs up a new manila share.
    • Added manage/unmanage support and shrink_share support.
    • Support for extended_share API component.
    • Support for netapp-lib PyPI project to communicate with storage arrays.
  • Improvements to the 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.
    • Added share server support.
  • Improvements to the Huawei Manila driver:
    • Added support for storage pools, extend_share, manage_existing, shrink_share, read-only share, smartcache and smartpartition.
    • Added reporting of dedupe, thin provisioning and compression capabilities.
  • Added access-level support to the VNX Manila driver.
  • Added support for the Manila HDS HNAS driver.
  • Added GlusterFS native driver.
    • GlusterFS drivers can now specify the list of compatible share layouts.
  • Added microversion support (v2 API).

非推奨の機能

  • The share_reset_status API component is deprecated and replaced by share_instance_reset_status.