April 2016 - OpenStack-announce - lists.openstack.org

[release][murano] murano-agent 2.0.0 release (mitaka)
by no-reply＠openstack.org 06 Apr '16

06 Apr '16

We are jazzed to announce the release of: murano-agent 2.0.0: Python Murano Agent This release is part of the mitaka release series. For more details, please see below. Changes in murano-agent 2.0.0.0rc1..2.0.0 ----------------------------------------- 8738324 Restores SIGPIPE on script processes a333528 Update .gitreview for stable/mitaka Diffstat (except docs and test files) ------------------------------------- .gitreview | 1 + muranoagent/executors/application/__init__.py | 20 +++++++++++++------- 2 files changed, 14 insertions(+), 7 deletions(-)

1 0

[release][neutron] neutron-vpnaas 8.0.0 release (mitaka)
by no-reply＠openstack.org 06 Apr '16

06 Apr '16

We are satisfied to announce the release of: neutron-vpnaas 8.0.0: OpenStack Networking VPN as a Service This release is part of the mitaka release series. For more details, please see below. 8.0.0 ^^^^^ Generation of sample Neutron VPNaaS configuration files. New Features ************ * Neutron VPNaaS no longer includes static example configuration files. Instead, use tools/generate_config_file_samples.sh to generate them. The files are generated with a .sample extension. Changes in neutron-vpnaas 8.0.0.0rc2..8.0.0 ------------------------------------------- a1b1260 Constraint requirements using mitaka upper-constraints.txt file Diffstat (except docs and test files) ------------------------------------- tools/tox_install.sh | 2 +- tox.ini | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-)

1 0

[release][mistral] mistral 2.0.0 release (mitaka)
by no-reply＠openstack.org 06 Apr '16

06 Apr '16

We are delighted to announce the release of: mistral 2.0.0: Mistral Project This release is part of the mitaka release series. For more details, please see below. 2.0.0 ^^^^^ Pre-installed Mistral docker image is now available to get quick idea of Mistral. Tempest plugin has been implemented. Now Mistral tests can be run from Mistral repo as well as from Tempest repo. Actions of several OpenStack services are supported out of the box in Mitaka, including Barbican, Cinder(V2), Swift, Trove, Zaqar and Mistral. New Features ************ * Add support for workflow sharing feature. users of one project can share workflows to other projects using this feature. (https://specs.openstack.org/openstack/mistral- specs/specs/mitaka/approved/mistral-workflow-resource-sharing.html) Upgrade Notes ************* * During an upgrade to Mitaka, operators or administrators need to run "python tools/get_action_list.py <service name>" command to generate service action names and values for updating "mistral/actions/openstack/mapping.json", then, run "python tools/sync_db.py" to populate database. Please note, some services like Neutron, Swift, Zaqar don't support the command yet. Deprecation Notes ***************** * Usage of workflow name in the system(e.g. creating executions/cron- triggers , workfow CRUD operations, etc.) is deprecated, please use workflow UUID instead. The workflow sharing feature can only be used with workflow UUID. Security Issues *************** * [bug 1521802 (https://bugs.launchpad.net/mistral/+bug/1521802) Fixing the problem that sometimes sub-workflow executions were run/saved under the wrong tenant in cron trigger periodic task in multi-tenancy deployment. Bug Fixes ********* * [bug 1518012 (https://bugs.launchpad.net/mistral/+bug/1518012) [bug 1513456 (https://bugs.launchpad.net/mistral/+bug/1513456) Fix concurrency issues by using READ_COMMITTED This release note describes bugs: * #1513456 - task stuck in RUNNING state when all action executions are finished regarding the problem and the fix. * #1518012- WF execution stays in RUNNING although task and action executions are in SUCCESS. This fix does not require any action from Mistral users and does not have any implications other than the bug fix. The state of a workflow execution was not updated even when all task executions were completed if some tasks finished at the same time as other tasks. Because we were using our connections with transaction isolation level = REPEATABLE_READ - Each process was using a snapshot of the DB created at the first read statement in that transaction. When a task finished and evaluated the state of all the other tasks it did not see the up-to-date state of those tasks - and so, because not all tasks were completed - the task did not change the workflow execution state. Similar behavior happened with multiple action executions under same task. On completion, each action execution checked the status of the other action executions and did not see the up-to-date state of these action execution - causing task execution to stay in RUNNING state. The solution is to change DB transaction isolation level from REPEATABLE_READ to READ_COMMITTED so process A can see changes committed in other transactions even if process A is in the middle of a transaction. A short explanation regarding the different isolation levels: * REPEATABLE_READ - while in transaction, the first read operation to the DB creates a snapshot of the entire DB so you are guarantee that all the data in the DB will remain the same until the end of the transaction. REPEATABLE_READ example: * ConnectionA selects from tableA in a transaction. * ConnectionB deletes all rows from tableB in a transaction. * ConnectionB commits. * ConnectionA loops over the rows of tableA and fetches from tableB using the tableA_tableB_FK - ConnectionA will get rows from tableB. * READ_COMMITTED - while in a transaction, every query to the DB will get the committed data. READ_COMMITTED example: * ConnectionA starts a transaction. * ConnectionB starts a transaction. * ConnectionA insert row to tableA and commits. * ConnectionB insert row to tableA. * ConnectionB selects tableA and gets two rows. * ConnectionB commits / rollback. Two good articles about isolation levels are: * Differences between READ-COMMITTED and REPEATABLE-READ transaction isolation levels (https://www.percona.com/blog/2015/01/14/mysql-performance- implications-of-innodb-isolation-modes/). * MySQL performance implications of InnoDB isolation modes (https://www.percona.com/blog/2012/08/28/differences-between- read-committed-and-repeatable-read-transaction-isolation- levels/). Changes in mistral 2.0.0.0rc2..2.0.0 ------------------------------------ 1293ea5 Fixing issue with different versions of oslo_messaging Diffstat (except docs and test files) ------------------------------------- mistral/engine/rpc.py | 59 ++++++++++++++++++++++++++++++++++++--------------- 1 file changed, 42 insertions(+), 17 deletions(-)

1 0

[release][neutron] neutron-lbaas 8.0.0 release (mitaka)
by no-reply＠openstack.org 06 Apr '16

06 Apr '16

We are pumped to announce the release of: neutron-lbaas 8.0.0: OpenStack Networking Load Balancing as a Service This release is part of the mitaka release series. For more details, please see below. 8.0.0 ^^^^^ Generation of sample Neutron LBaaS configuration files. New Features ************ * Neutron LBaaS no longer includes static example configuration files. Instead, use tools/generate_config_file_samples.sh to generate them. The files are generated with a .sample extension. Known Issues ************ * CLI update does not allow clearing session_persistence. In the process of fixing the session_persistence update bug, we discovered that the CLI for updating LBaaS v2 pools does not allow one to clear the session_persistence for a pool once set. A fix for this is being prepared, but in the mean time, the following work- arounds are possible if a given pool's session_persistence parameter needs to be changed: * The pool can be deleted and recreated without session_persistence. * A tenant can update the session persistence by talking directly to the API using curl. Bug Fixes ********* * session_persistence on a LBaaSv2 pool is no longer deleted when other pool parameters are updated via the CLI or API. Changes in neutron-lbaas 8.0.0.0rc2..8.0.0 ------------------------------------------ 19b18f0 Constraint requirements using mitaka upper-constraints.txt file Diffstat (except docs and test files) ------------------------------------- tools/tox_install.sh | 2 +- tox.ini | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-)

1 0

[release] cinder 8.0.0 release (mitaka)
by no-reply＠openstack.org 06 Apr '16

06 Apr '16

We are glad to announce the release of: cinder 8.0.0: OpenStack Block Storage This release is part of the mitaka release series. For more details, please see below. 8.0.0 ^^^^^ New Features ************ * Added support for creating a consistency group from a source consistency group in the HPE 3PAR driver. * Disable standard capabilities based on 3PAR licenses. * Added snapshot manage/unmanage support to the HPE 3PAR driver. * Added replication v2.1 support to the Dell Storage Center drivers. * Added v2.1 replication support in Huawei Cinder driver. * Added support for creating, deleting, and updating consistency groups for NetApp 7mode and CDOT backends. * Added support for taking, deleting, and restoring a cgsnapshot for NetApp 7mode and CDOT backends. * Added backend driver for Coho Data storage. * Added cinder backup driver for Google Cloud Storage. * Added driver for Tegile IntelliFlash arrays. * Added ability to backup snapshots. * Support balanced FC port selection for Huawei drivers. * HTTP connector for the Cinder Brocade FC Zone plugin. This connector allows for communication between the Brocade FC zone plugin and the switch to be over HTTP or HTTPs. To make use of this connector, the user would add a configuration setting in the fabric block for a Brocade switch with the name as 'fc_southbound_protocol' with a value as 'HTTP' or 'HTTPS'. * Support for configuring Fibre Channel zoning on Brocade switches through Cinder Fibre Channel Zone Manager and Brocade Fibre Channel zone plugin. To zone in a Virtual Fabric, set the configuration option 'fc_virtual_fabric_id' for the fabric. * The consistency group API now returns volume type IDs. * Added support for API microversions, as well as /v3 API endpoint. * Retype support added to CloudByte iSCSI driver. * All Datera DataFabric backed volume-types will now use API version 2 with Datera DataFabric * It is now possible to delete a volume and its snapshots by passing an additional argument to volume delete, "cascade=True". * New config option to enable discard (trim/unmap) support for any backend. * Added backend driver for DISCO storage. * Cinder FC Zone Manager Friendly Zone Names This feature adds support for Fibre Channel user friendly zone names if implemented by the volume driver. If the volume driver passes the host name and storage system to the Fibre Channel Zone Manager in the conn_info structure, the zone manager will use these names in structuring the zone name to provide a user friendly zone name. * Added backend driver for Fujitsu ETERNUS DX (FC). * Added backend driver for Fujitsu ETERNUS DX (iSCSI). * Added manage/unmanage snapshot support for Huawei drivers. * Added manage/unmanage volume support for Huawei drivers. * Support cinder_img_volume_type property in glance image metadata to specify volume type. * Consistency group support has been added to the LeftHand backend driver. * Added snapshot manage/unmanage support to the HPE LeftHand driver. * Added iSCSI CHAP uni-directional authentication for NetApp drivers. * Support for Consistency Groups in the NetApp E-Series Volume Driver. * Added backend driver for Nexenta Edge iSCSI storage. * Added backend driver for NexentaStor5 iSCSI storage. * Added backend driver for NexentaStor5 NFS storage. * Manage and unmanage support has been added to the Nimble backend driver. * Added additional metrics reported to the scheduler for Pure Volume Drivers for better filtering and weighing functions. * Added config option to enable/disable automatically calculation an over-subscription ratio max for Pure Volume Drivers. When disabled the drivers will now respect the max_oversubscription_ratio config option. * New config option for Pure Storage volume drivers pure_eradicate_on_delete. When enabled will permanantly eradicate data instead of placing into pending eradication state. * Added Cheesecake (v2.1) replication support to the Pure Storage Volume drivers. * Added Migrate and Extend for Nexenta NFS driver. * Added Retype functionality to Nexenta iSCSI and NFS drivers. * Added v2.1 replication support to the HPE 3PAR driver. * Added v2.1 replication support to the HPE LeftHand driver. * Added replication v2.1 support to the IBM Storwize driver. * Added RPC backward compatibility layer similar to the one implemented in Nova. This means that Cinder services can be upgraded one-by-one without breakage. After all the services are upgraded SIGHUP signals should be issued to all the services to signal them to reload cached minimum RPC versions. Alternative is of course restart of them. Please note that cinder-api service doesn't support SIGHUP yet. Please also take into account that all the rolling upgrades capabilities are considered tech preview, as we don't have a CI testing it yet. * Added Consistency Group support in ScaleIO driver. * Added support for manage/unmanage volume in the ScaleIO driver. * Added QoS support in ScaleIO driver. * cinder-backup service is now decoupled from cinder-volume, which allows more flexible scaling. * Split nested quota support into a separate driver. In order to use nested quotas, change the following config "quota_driver = cinder.quota.NestedDbQuotaDriver" after running the following admin API "os-quota-sets/validate_setup_for_nested_quota_use" command to ensure the existing quota values make sense to nest. * Added multiple management IP support to Storwize SVC driver. * Added multiple pools support to Storwize SVC driver. * Added support for ZeroMQ messaging driver in cinder single backend config. * Locks may use Tooz as abstraction layer now, to support distributed lock managers and prepare Cinder to better support HA configurations. * The updated_at timestamp is now returned in listing detail. * Added support for manage volume in the VMware VMDK driver. * Configrable migration rate in VNX driver via metadata * Adds v2.1 replication support in VNX Cinder driver. * Cloning of consistency group added to EMC VNX backend driver. * Added replication v2.1 support to the IBM XIV/DS8K driver. * Support for creating a consistency group from consistency group in XtremIO. * Volume manage/unmanage support for Oracle ZFSSA iSCSI and NFS drivers. Known Issues ************ * Cinder services are now automatically downgrading RPC messages to be understood by the oldest version of a service among all the deployment. Disabled and dead services are also taken into account. It is important to keep service list up to date, without old, unused records. This can be done using "cinder-manage service remove" command. Once situation is cleaned up services should be either restarted or "SIGHUP" signal should be issued to their processes to force them to reload version pins. Please note that cinder-api does not support "SIGHUP" signal. Upgrade Notes ************* * It is required to copy new rootwrap.d/volume.filters file into /etc/cinder/rootwrap.d directory. * Violin Memory 6000 array series drivers are removed. * Adding or removing volume_type_access from any project during DB migration 62 must not be performed. * When running PostgreSQL it is required to upgrade and restart all the cinder-api services along with DB migration 62. * Users of the Datera Cinder driver are now required to use Datera DataFabric version 1.0+. Versions before 1.0 will not be able to utilize this new driver since they still function on v1 of the Datera DataFabric API * The VMware VMDK driver now enforces minimum vCenter version of 5.1. * If during a *live* upgrade from Liberty a backup service will be killed while processing a restore request it may happen that such backup status won't be automatically cleaned up on the service restart. Such orphaned backups need to be cleaned up manually. * When performing a *live* upgrade from Liberty it may happen that retype calls will reserve additional quota. As by default quota reservations are invalidated after 24 hours (config option "reservation_expire=86400"), we recommend either decreasing that time or watching for unused quota reservations manually during the upgrade process. * HP drivers have been rebranded to HPE. Existing configurations will continue to work with the legacy name, but will need to be updated by the next release. * The deprecated HP CLIQ proxy driver has now been removed. * Users of the ibmnas driver should switch to using the IBM GPFS driver to enable Cinder access to IBM NAS resources. For details configuring the IBM GPFS driver, see the GPFS config reference. - http://docs.openstack.org/liberty/config-reference/content/GPFS- driver.html * Removed deprecated LVMISCSIDriver and LVMISERDriver. These should be switched to use the LVMVolumeDriver with the desired iscsi_helper configuration set to the desired iSCSI helper. * Removed the deprecated NPIV options for the Storwize backend driver. * Backend driver for Scality SRB has been removed. * Rename Huawei18000ISCSIDriver and Huawei18000FCDriver to HuaweiISCSIDriver and HuaweiFCDriver. * Starting from Mitaka release Cinder is having a tech preview of rolling upgrades support. * Removed force_delete option from ScaleIO configuration. * As cinder-backup was strongly reworked in this release, the recommended upgrade order when executing live (rolling) upgrade is c-api->c-sch->c-vol->c-bak. * Nested quotas will no longer be used by default, but can be configured by setting "quota_driver = cinder.quota.NestedDbQuotaDriver" * Removed storwize_svc_connection_protocol config setting. Users will now need to set different values for volume_driver in cinder.conf. FC:volume_driver = cinder.volume.drivers.ibm.storwize_svc.storwize_ svc_fc.StorwizeSVCFCDriver iSCSI:volume_driver = cinder.volume.driv ers.ibm.storwize_svc.storwize_svc_iscsi.StorwizeSVCISCSIDriver * The VMware VMDK driver for ESX server has been removed. Deprecation Notes ***************** * datera_api_token -- this has been replaced by san_login and san_password * The XML API has been marked deprecated and will be removed in a future release. * Deprecated IBM driver _multipath_enabled config flags. Security Issues *************** * Pure Storage Volume Drivers can now utilize driver_ssl_cert_verify and driver_ssl_cert_path config options to allow for secure https requests to the FlashArray. Bug Fixes ********* * Fixed bug causing snapshot creation to fail on systems with LC_NUMERIC set to locale using ',' as decimal separator. * Cinder will now correctly read Keystone's endpoint for quota calls from keystone_authtoken.auth_uri instead of keymgr.encryption_auth_url config option. * Fixed service state reporting when backup manager is unable to initialize one of the backup drivers. * Consistency group creation previously scheduled at the pool level. Now it is fixed to schedule at the backend level as designed. * Removed the need for deployers to run tox for config reference generation. * upload-to-image using Image API v2 now correctly handles custom image properties. * Enabled a cloud operator to correctly manage policy for volume type operations. To permit volume type operations for specific user, you can for example do as follows. * Add "storage_type_admin" role. * Add "admin_or_storage_type_admin" rule to "policy.json", e.g. ""admin_or_storage_type_admin": "is_admin:True or role:storage_type_admin"," * Modify rule for types_manage and volume_type_access, e.g. ""volume_extension:types_manage": "rule:admin_or_storage_type_admin", "volume_extension:volume_type_access:addProjectAccess": "rule:admin_or_storage_type_admin", "volume_extension:volume_type_access:removeProjectAccess": "rule:admin_or_storage_type_admin"," * Fixed issue where Pure Volume Drivers would ignore reserved_percentage config option. * Allow for eradicating Pure Storage volumes, snapshots, and pgroups when deleting their Cinder counterpart. * Corrected quota usage when transferring a volume between tenants. * Previously the only way to remove volumes in error states from a consistency-group was to delete the consistency group and create it again. Now it is possible to remove volumes in error and error_deleting states. * Fix for Tintri image direct clone feature. Fix for the bug 1400966 prevents user from specifying image "nfs share location" as location value for an image. Now, in order to use Tintri image direct clone, user can specify "provider_location" in image metadata to specify image nfs share location. NFS share which hosts images should be specified in a file using tintri_image_shares_config config option. * Filtering volumes by their display name now correctly handles display names with single and double quotes. Other Notes *********** * Due to the ibmnas (SONAS) driver being rendered redundant by the addition of NFS capabilities to the IBM GPFS driver, the ibmnas driver is being removed in the Mitaka release. Changes in cinder 8.0.0.0rc1..8.0.0 ----------------------------------- 73b9976 Huawei: Fix getting admin_metadata 2adc8bb Imported Translations from Zanata e2cf243 NexentaStor4 iSCSI: convert blocksize to str da28ab6 Imported Translations from Zanata 9a8f9ee Imported Translations from Zanata 4dbb274 XtremIO handle errors in terminate_connection: ee4dc38 Imported Translations from Zanata 9d90a0a Imported Translations from Zanata 5424566 Imported Translations from Zanata ae388af Imported Translations from Zanata f9ad35a Imported Translations from Zanata c1e6472 Report 2.0 as supported version of RPC APIs 37c0556 Fix volume RPC API methods related to backups 755253e Imported Translations from Zanata a6b4a84 Imported Translations from Zanata 16a1d80 Imported Translations from Zanata d292fe1 Dell SC: create_cgsnapshot returning wrong structure 50e124e Imported Translations from Zanata cf686d8 Fix race condition when toggling SP 6138aca Huawei: Record and check LUN wwn 691db5a SMBFS: fix parsing volume type extra specs and metadata 38fc0b4 VMware: Bump driver version e784fcf Update .gitreview for stable/mitaka Diffstat (except docs and test files) ------------------------------------- .gitreview | 1 + cinder/backup/manager.py | 8 +- cinder/exception.py | 5 + cinder/locale/cinder-log-error.pot | 493 +- cinder/locale/cinder-log-info.pot | 554 +- cinder/locale/cinder-log-warning.pot | 433 +- cinder/locale/cinder.pot | 1354 +-- cinder/locale/cs/LC_MESSAGES/cinder-log-error.po | 7 +- cinder/locale/cs/LC_MESSAGES/cinder-log-info.po | 35 +- cinder/locale/cs/LC_MESSAGES/cinder-log-warning.po | 20 +- cinder/locale/cs/LC_MESSAGES/cinder.po | 24 +- cinder/locale/de/LC_MESSAGES/cinder.po | 2616 ++++- cinder/locale/es/LC_MESSAGES/cinder.po | 2641 ++++- cinder/locale/fr/LC_MESSAGES/cinder.po | 2770 ++++- cinder/locale/it/LC_MESSAGES/cinder-log-error.po | 995 +- cinder/locale/it/LC_MESSAGES/cinder-log-info.po | 3773 +++++++ cinder/locale/it/LC_MESSAGES/cinder.po | 59 +- cinder/locale/ja/LC_MESSAGES/cinder.po | 10677 +++++++++++++++++++ .../locale/ko_KR/LC_MESSAGES/cinder-log-error.po | 3500 ++++++ cinder/locale/ko_KR/LC_MESSAGES/cinder-log-info.po | 3593 +++++++ cinder/locale/ko_KR/LC_MESSAGES/cinder.po | 2496 ++++- cinder/locale/pt_BR/LC_MESSAGES/cinder.po | 2568 ++++- cinder/locale/ru/LC_MESSAGES/cinder.po | 2535 ++++- .../locale/tr_TR/LC_MESSAGES/cinder-log-error.po | 7 +- cinder/locale/tr_TR/LC_MESSAGES/cinder-log-info.po | 12 +- cinder/locale/zh_CN/LC_MESSAGES/cinder.po | 88 +- cinder/locale/zh_TW/LC_MESSAGES/cinder.po | 101 +- cinder/scheduler/manager.py | 8 +- .../drivers/dell/dell_storagecenter_common.py | 8 +- cinder/volume/drivers/emc/emc_vnx_cli.py | 80 +- cinder/volume/drivers/emc/xtremio.py | 45 +- cinder/volume/drivers/huawei/constants.py | 3 + cinder/volume/drivers/huawei/huawei_driver.py | 182 +- cinder/volume/drivers/huawei/huawei_utils.py | 13 + cinder/volume/drivers/huawei/replication.py | 15 +- cinder/volume/drivers/huawei/rest_client.py | 7 +- cinder/volume/drivers/nexenta/iscsi.py | 3 +- cinder/volume/drivers/smbfs.py | 38 +- cinder/volume/drivers/vmware/vmdk.py | 3 +- cinder/volume/manager.py | 8 +- cinder/volume/rpcapi.py | 14 +- 47 files changed, 40089 insertions(+), 2043 deletions(-)

1 0

[release][neutron] neutron 8.0.0 release (mitaka)
by no-reply＠openstack.org 06 Apr '16

06 Apr '16

We are overjoyed to announce the release of: neutron 8.0.0: OpenStack Networking This release is part of the mitaka release series. For more details, please see below. 8.0.0 ^^^^^ The ML2 plug-in supports calculating the MTU for instances using overlay networks by subtracting the overlay protocol overhead from the value of 'path_mtu', ideally the physical (underlying) network MTU, and providing the smaller value to instances via DHCP. Prior to Mitaka, 'path_mtu' defaults to 0 which disables this feature. In Mitaka, 'path_mtu' defaults to 1500, a typical MTU for physical networks, to improve the "out of box" experience for typical deployments. The ML2 plug-in supports calculating the MTU for networks that are realized as flat or VLAN networks, by consulting the 'segment_mtu' option. Prior to Mitaka, 'segment_mtu' defaults to 0 which disables this feature. This creates slightly confusing API results when querying Neutron networks, since the plugins that support the MTU API extension would return networks with the MTU equal to zero. Networks with an MTU of zero make little sense, since nothing could ever be transmitted. In Mitaka, 'segment_mtu' now defaults to 1500 which is the standard MTU for Ethernet networks in order to improve the "out of box" experience for typical deployments. The LinuxBridge agent now supports QoS bandwidth limiting. External networks can now be controlled using the RBAC framework that was added in Liberty. This allows networks to be made available to specific tenants (as opposed to all tenants) to be used as an external gateway for routers and floating IPs. DHCP and L3 Agent scheduling is availability zone aware. The "get-me-a-network" feature simplifies the process for launching an instance with basic network connectivity (via an externally connected private tenant network). Support integration with external DNS service. Add popular IP protocols to the security group code. End-users can specify protocol names instead of protocol numbers in both RESTful API and python-neutronclient CLI. ML2: ports can now recover from binding failed state. RBAC support for QoS policies Add description field to security group rules, networks, ports, routers, floating IPs, and subnet pools. Add tag mechanism for network resources Timestamp fields are now added to neutron core resources. Announcement of tenant prefixes and host routes for floating IP's via BGP is supported Allowed address pairs can now be cleared by passing None in addition to an empty list. This is to make it possible to use the --action=clear option with the neutron client. neutron port-update <uuid> --allowed-address-pairs action=clear Core configuration files are automatically generated. max_fixed_ips_per_port has been deprecated and will be removed in the Newton or Ocata cycle depending on when all identified usecases of the options are satisfied via another quota system. OFAgent is decomposed and deprecated in the Mitaka cycle. Add new VNIC type for SR-IOV physical functions. High Availability (HA) of SNAT service is supported for Distributed Virtual Routers (DVRs). An OVS agent configured to run in DVR mode will fail to start if it cannot get proper DVR configuration values from the server on start- up. The agent will no longer fallback to non-DVR mode, since it may lead to inconsistency in the DVR-enabled cluster as the Neutron server does not distinguish between DVR and non-DVR OVS agents. Improve DVR's resiliency during Nova VM live migration events. The Linuxbridge agent now supports l2 agent extensions. Adding MacVtap ML2 driver and L2 Agent as new vswitch choice Support for MTU selection and advertisement. Neutron now provides network IP availability information. Neutron is integrated with Guru Meditation Reports library. oslo.messaging.notify.drivers entry points are deprecated New Features ************ * In Mitaka, the combination of 'path_mtu' defaulting to 1500 and 'advertise_mtu' defaulting to True provides a value of MTU accounting for any overlay protocol overhead on the network to instances using DHCP. For example, an instance attaching to a VXLAN network receives a 1450 MTU from DHCP accounting for 50 bytes of overhead from the VXLAN overlay protocol if using IPv4 endpoints. * In Mitaka, queries to the Networking API for network objects will now return network objects that contain a sane MTU value. * The LinuxBridge agent can now configure basic bandwidth limiting QoS rules set for ports and networks. It introduces two new config options for LinuxBridge agent. First is 'kernel_hz' option which is value of host kernel HZ setting. It is necessary for proper calculation of minimum burst value in tbf qdisc setting. Second is 'tbf_latency' which is value of latency to be configured in tc-tbf setting. Details about this option can be found in tc-tbf manual (http://linux.die.net/man/8/tc-tbf) * External networks can now be controlled using the RBAC framework that was added in Liberty. This allows networks to be made available to specific tenants (as opposed to all tenants) to be used as an external gateway for routers and floating IPs. By default this feature will also allow regular tenants to make their networks available as external networks to other individual tenants (or even themselves), but they are prevented from using the wildcard to share to all tenants. This behavior can be adjusted via policy.json by the operator if desired. * A DHCP agent is assigned to an availability zone; the network will be hosted by the DHCP agent with availability zone specified by the user. * An L3 agent is assigned to an availability zone; the router will be hosted by the L3 agent with availability zone specified by the user. This supports the use of availability zones with HA routers. DVR isn't supported now because L3HA and DVR integration isn't finished. * Once Nova takes advantage of this feature, a user can launch an instance without explicitly provisioning network resources. * Floating IPs can have dns_name and dns_domain attributes associated with them * Ports can have a dns_name attribute associated with them. The network where a port is created can have a dns_domain associated with it * Floating IPs and ports will be published in an external DNS service if they have dns_name and dns_domain attributes associated with them. * The reference driver integrates neutron with designate * Drivers for other DNSaaS can be implemented * Driver is configured in the default section of neutron.conf using parameter 'external_dns_driver' * Ports that failed to bind when an L2 agent was offline can now recover after the agent is back online. * Neutron now supports sharing of QoS policies between a subset of tenants. * Security group rules, networks, ports, routers, floating IPs, and subnet pools may now contain an optional description which allows users to easily store details about entities. * Users can set tags on their network resources. * Networks can be filtered by tags. The supported filters are 'tags', 'tags-any', 'not-tags' and 'not-tags-any'. * Add timestamp fields 'created_at', 'updated_at' into neutron core resources like network, subnet, port and subnetpool. * And support for querying these resources by changed-since, it will return the resources changed after the specfic time string like YYYY-MM-DDTHH:MM:SS * By default, the DHCP agent provides a network MTU value to instances using the corresponding DHCP option if core plugin calculates the value. For ML2 plugin, calculation mechanism is enabled by setting [ml2] path_mtu option to a value greater than zero. * Allow non-admin users to define "external" extra-routes. * Announcement of tenant subnets via BGP using centralized Neutron router gateway port as the next-hop * Announcement of floating IP host routes via BGP using the centralized Neutron router gateway port as the next-hop * Announcement of floating IP host routes via BGP using the floating IP agent gateway as the next-hop when the floating IP is associated through a distributed router * Neutron no longer includes static example configuration files. Instead, use tools/generate_config_file_samples.sh to generate them. The files are generated with a .sample extension. * Add derived attributes to the network to tell users which address scopes the network is in. * The subnet API now includes a new use_default_subnetpool attribute. This attribute can be specified on creating a subnet in lieu of a subnetpool_id. The two are mutually exclusive. If it is specified as True, the default subnet pool for the requested ip_version will be looked up and used. If no default exists, an error will be returned. * Neutron now supports creation of ports for exposing physical functions as network devices to guests. * High Availability support for SNAT services on Distributed Virtual Routers. Routers can now be created with the flags distributed=True and ha=True. The created routers will provide Distributed Virtual Routing as well as SNAT high availability on the l3 agents configured for dvr_snat mode. * Use the value of the network 'mtu' attribute for the MTU of virtual network interfaces such as veth pairs, patch ports, and tap devices involving a particular network. * Enable end-to-end support for arbitrary MTUs including jumbo frames between instances and provider networks by moving MTU disparities between flat or VLAN networks and overlay networks from layer-2 devices to layer-3 devices that support path MTU discovery (PMTUD). * The Linuxbridge agent can now be extended by 3rd parties using a pluggable mechanism. * Libvirt qemu/kvm instances can now be attached via MacVtap in bridge mode to a network. VLAN and FLAT attachments are supported. Other attachmentes than compute are not supported. * When advertise_mtu is set in the config, Neutron supports advertising the LinkMTU using Router Advertisements. * A new API endpoint /v2.0/network-ip-availabilities that allows an admin to quickly get counts of used_ips and total_ips for network(s) is available. New endpoint allows filtering by network_id, network_name, tenant_id, and ip_version. Response returns network and nested subnet data that includes used and total IPs. * SriovNicSwitchMechanismDriver driver now exposes a new VIF type 'hostdev_physical' for ports with vnic type 'direct-physical' (used for SR-IOV PF passthrough). This will enable Nova to provision PFs as Neutron ports. * The RPC and notification queues have been separated into different queues. Specify the transport_url to be used for notifications within the [oslo_messaging_notifications] section of the configuration file. If no transport_url is specified in [oslo_messaging_notifications], the transport_url used for RPC will be used. * Neutron services should respond to SIGUSR2 signal by dumping valuable debug information to standard error output. * New security groups firewall driver is introduced. It's based on OpenFlow using connection tracking. * Neutron can interact with keystone v3. Known Issues ************ * The combination of 'path_mtu' and 'advertise_mtu' only adjusts the MTU for instances rather than all virtual network components between instances and provider/public networks. In particular, setting 'path_mtu' to a value greater than 1500 can cause packet loss even if the physical network supports it. Also, the calculation does not consider additional overhead from IPv6 endpoints. * When using DVR, if a floating IP is associated to a fixed IP direct access to the fixed IP is not possible when traffic is sent from outside of a Neutron tenant network (north-south traffic). Traffic sent between tenant networks (east-west traffic) is not affected. When using a distributed router, the floating IP will mask the fixed IP making it inaccessible, even though the tenant subnet is being announced as accessible through the centralized SNAT router. In such a case, traffic sent to the instance should be directed to the floating IP. This is a limitation of the Neutron L3 agent when using DVR and will be addressed in a future release. * Only creation of dvr/ha routers is currently supported. Upgrade from other types of routers to dvr/ha router is not supported on this release. * More synchronization between Nova and Neutron is needed to properly handle live migration failures on either side. For instance, if live migration is reverted or canceled, some dangling Neutron resources may be left on the destination host. * To ensure any kind of migration works between all compute nodes, make sure that the same physical_interface_mappings is configured on each MacVtap compute node. Having different mappings could cause live migration to fail (if the configured physical network interface does not exist on the target host), or even worse, result in an instance placed on the wrong physical network (if the physical network interface exists on the target host, but is used by another physical network or not used at all by OpenStack). Such an instance does not have access to its configured networks anymore. It then has layer 2 connectivity to either another OpenStack network, or one of the hosts networks. * OVS firewall driver doesn't work well with other features using openflow. Upgrade Notes ************* * Operators using the ML2 plug-in with 'path_mtu' defaulting to 0 may need to perform a database migration to update the MTU for existing networks and possibly disable existing workarounds for MTU problems such as increasing the physical network MTU to 1550. * Operators using the ML2 plug-in with existing data may need to perform a database migration to update the MTU for existing networks * Add popular IP protocols to security group code. * To disable, use [DEFAULT] advertise_mtu = False. * The router_id option is deprecated and will be removed in the 'N' cycle. * Does not change MTU for existing virtual network interfaces. * Actions that create virtual network interfaces on an existing network with the 'mtu' attribute containing a value greater than zero could cause issues for network traffic traversing existing and new virtual network interfaces. * The Hyper-V Neutron Agent has been fully decomposed from Neutron. The *neutron.plugins.hyperv.agent.security_groups_driver.HyperVSecu rityGroupsDriver* firewall driver has been deprecated and will be removed in the 'O' cycle. Update the *neutron_hyperv_agent.conf* files on the Hyper-V nodes to use *hyperv.neutron.security_groups_driver.HyperVSecurityGroupsDriver*, which is the networking_hyperv security groups driver. * When using ML2 and the Linux Bridge agent, the default value for the ARP Responder under L2Population has changed. The responder is now disabled to improve compatibility with the allowed-address-pair extension and to match the default behavior of the ML2 OVS agent. The logical network will now utilize traditional flood and learn through the overlay. When upgrading, existing vxlan devices will retain their old setup and be unimpacted by changes to this flag. To apply this to older devices created with the Liberty agent, the vxlan device must be removed and then the Mitaka agent restarted. The agent will recreate the vxlan devices with the current settings upon restart. To maintain pre-Mitaka behavior, enable the arp_responder in the Linux Bridge agent VXLAN config file prior to starting the updated agent. * Neutron depends on keystoneauth instead of keystoneclient. Deprecation Notes ***************** * The default_subnet_pools option is now deprecated and will be removed in the Newton release. The same functionality is now provided by setting is_default attribute on subnetpools to True using the API or client. * The 'force_gateway_on_subnet' option is deprecated and will be removed in the 'Newton' cycle. * The 'network_device_mtu' option is deprecated and will be removed in the 'Newton' cycle. Please use the system-wide segment_mtu setting which the agents will take into account when wiring VIFs. * max_fixed_ips_per_port has been deprecated and will be removed in the Newton or Ocata cycle depending on when all identified usecases of the options are satisfied via another quota system. If you depend on this configuration option to stop tenants from consuming IP addresses, please leave a comment on the bug report (https://launchpad.net/bugs/1502356) * The 'segment_mtu' option of the ML2 configuration has been deprecated and replaced with the 'global_physnet_mtu' option in the main Neutron configuration. This option is meant to be used by all plugins for an operator to reference their physical network's MTU, regardless of the backend plugin. Plugins should access this config option via the 'get_deployment_physnet_mtu' method added to neutron.plugins.common.utils to avoid being broken on any potential renames in the future. Bug Fixes ********* * Prior to Mitaka, the settings that control the frequency of router advertisements transmitted by the radvd daemon were not able to be adjusted. Larger deployments may wish to decrease the frequency in which radvd sends multicast traffic. The 'min_rtr_adv_interval' and 'max_rtr_adv_interval' settings in the L3 agent configuration file map directly to the 'MinRtrAdvInterval' and 'MaxRtrAdvInterval' in the generated radvd.conf file. Consult the manpage for radvd.conf for more detailed information. * Fixes bug 1537734 * Prior to Mitaka, name resolution in instances requires specifying DNS resolvers via the 'dnsmasq_dns_servers' option in the DHCP agent configuration file or via neutron subnet options. In this case, the data plane must provide connectivity between instances and upstream DNS resolvers. Omitting both of these methods causes the dnsmasq service to offer the IP address on which it resides to instances for name resolution. However, the static dnsmasq '--no-resolv' process argument prevents name resolution via dnsmasq, leaving instances without name resolution. Mitaka introduces the 'dnsmasq_local_resolv' option, default value False to preserve backward-compatibility, that enables the dnsmasq service to provide name resolution for instances via DNS resolvers on the host running the DHCP agent. In this case, the data plane must provide connectivity between the host and upstream DNS resolvers rather than between the instances and upstream DNS resolvers. Specifying DNS resolvers via the 'dnsmasq_dns_servers' option in the DHCP agent configuration overrides the 'dnsmasq_local_resolv' option for all subnets using the DHCP agent. * Before Mitaka, when a default subnetpool was defined in the configuration, a request to create a subnet would fall back to using it if no specific subnet pool was specified. This behavior broke the semantics of subnet create calls in this scenario and is now considered an API bug. This bug has been fixed so that there is no automatic fallback with the presence of a default subnet pool. Workflows which depended on this new behavior will have to be modified to set the new use_default_subnetpool attribute when creating a subnet. * Create DVR router namespaces pro-actively on the destination node during live migration events. This helps minimize packet loss to floating IP traffic. * Explicitly configure MTU of virtual network interfaces rather than using default values or incorrect values that do not account for overlay protocol overhead. * The server will fail to start if any of the declared required extensions, as needed by core and service plugins, are not properly configured. * partially closes bug 1468803 * The Linuxbridge agent now supports the ability to toggle the local ARP responder when L2Population is enabled. This ensures compatibility with the allowed-address-pairs extension. closes bug 1445089 * Fix SR-IOV agent macvtap assigned VF check when linux kernel < 3.13 * Loaded agent extensions of SR-IOV agent are now shown in agent state API. Other Notes *********** * Please read the OpenStack Networking Guide (http://docs.openstack.org/networking- guide/adv_config_availability_zone.html). * For overlay networks managed by ML2 core plugin, the calculation algorithm subtracts the overlay protocol overhead from the value of [ml2] path_mtu. The DHCP agent provides the resulting (smaller) MTU to instances using overlay networks. * The [DEFAULT] advertise_mtu option must contain a consistent value on all hosts running the DHCP agent. * Typical networks can use [ml2] path_mtu = 1500. * The Openflow Agent(OFAgent) mechanism driver is decomposed completely from neutron tree in the Mitaka. The OFAgent driver and its agent also are deprecated in favor of OpenvSwitch mechanism driver with "native" of_interface in the Mitaka and will be removed in the next release. * For details please read Blueprint mtu-selection-and-advertisement (https://specs.openstack.org/openstack/neutron-specs/specs/kilo/mtu- selection-and-advertisement.html). * OVS firewall driver requires OVS 2.5 version or higher with linux kernel 4.3 or higher. More info at OVS github page (https://github.com/openvswitch/ovs/blob/master/FAQ.md) * The oslo.messaging.notify.drivers entry points that were left in tree for backward compatibility with Icehouse are deprecated and will be removed after liberty-eol. Configure notifications using the oslo_messaging configuration options in neutron.conf. Changes in neutron 8.0.0.0rc2..8.0.0 ------------------------------------ 3213eb1 Support Routes==2.3 4283a7e Constraint requirements using mitaka upper-constraints.txt file fc69097 Imported Translations from Zanata 41be555 Imported Translations from Zanata b435ec5 Imported Translations from Zanata bec65f6 api tests: Check correct extensions 99915fa Fix setting peer to bridge interfaces 4b86f17 Skip fullstack L3 HA test 4504a74 conn_testers: Bump timeout for ICMPv6 echo tests Diffstat (except docs and test files) ------------------------------------- neutron/api/extensions.py | 10 +- neutron/locale/es/LC_MESSAGES/neutron.po | 1701 +++++++++++++++++++- neutron/locale/fr/LC_MESSAGES/neutron.po | 1286 ++++++++++++++- neutron/locale/ja/LC_MESSAGES/neutron.po | 161 +- .../locale/ko_KR/LC_MESSAGES/neutron-log-error.po | 1270 +++++++++++++++ .../locale/ko_KR/LC_MESSAGES/neutron-log-info.po | 862 ++++++++++ .../ko_KR/LC_MESSAGES/neutron-log-warning.po | 616 +++++++ neutron/locale/ko_KR/LC_MESSAGES/neutron.po | 1577 +++++++++++++++++- .../drivers/openvswitch/agent/ovs_neutron_agent.py | 4 +- .../api/admin/test_external_network_extension.py | 4 +- .../api/admin/test_shared_network_extension.py | 4 +- .../openvswitch/agent/test_ovs_neutron_agent.py | 16 +- .../drivers/openvswitch/agent/test_ovs_tunnel.py | 4 +- tox.ini | 2 +- 17 files changed, 7369 insertions(+), 171 deletions(-)

1 0

[release][nova] nova 13.0.0 release (mitaka)
by no-reply＠openstack.org 06 Apr '16

06 Apr '16

We are pleased to announce the release of: nova 13.0.0: Cloud computing fabric controller This release is part of the mitaka release series. For more details, please see below. 13.0.0 ^^^^^^ Nova 13.0.0 release is including a lot of new features and bugfixes. It can be extremely hard to mention all the changes we introduced during that release but we beg you to read at least the upgrade section which describes the required modifications that you need to do for upgrading your cloud from 12.0.0 (Liberty) to 13.0.0 (Mitaka). That said, a few major changes are worth to notice here. This is not an exhaustive list of things to notice, rather just important things you need to know : * Latest API microversion supported for Mitaka is v2.25 * Nova now requires a second database (called 'API DB'). * A new nova-manage script allows you to perform all online DB migrations once you upgrade your cloud * EC2 API support is fully removed. New Features ************ * Enables NUMA topology reporting on PowerPC architecture from the libvirt driver in Nova but with a caveat as mentioned below. NUMA cell affinity and dedicated cpu pinning code assumes that the host operating system is exposed to threads. PowerPC based hosts use core based scheduling for processes. Due to this, the cores on the PowerPC architecture are treated as threads. Since cores are always less than or equal to the threads on a system, this leads to non- optimal resource usage while pinning. This feature is supported from libvirt version 1.2.19 for PowerPC. * A new REST API to cancel an ongoing live migration has been added in microversion 2.24. Initially this operation will only work with the libvirt virt driver. * It is possible to call attach and detach volume API operations for instances which are in shelved and shelved_offloaded state. For an instance in shelved_offloaded state Nova will set to None the value for the device_name field, the right value for that field will be set once the instance will be unshelved as it will be managed by a specific compute manager. * It is possible to block live migrate instances with additional cinder volumes attached. This requires libvirt version to be >=1.2.17 and does not work when live_migration_tunnelled is set to True. * Project-id and user-id are now also returned in the return data of os-server-groups APIs. In order to use this new feature, user have to contain the header of request microversion v2.13 in the API request. * Add support for enabling uefi boot with libvirt. * A new host_status attribute for servers/detail and servers/{server_id}. In order to use this new feature, user have to contain the header of request microversion v2.16 in the API request. A new policy "os_compute_api:servers:show:host_status" added to enable the feature. By default, this is only exposed to cloud administrators. * A new server action trigger_crash_dump has been added to the REST API in microversion 2.17. * When RBD is used for ephemeral disks and image storage, make snapshot use Ceph directly, and update Glance with the new location. In case of failure, it will gracefully fallback to the "generic" snapshot method. This requires changing the typical permissions for the Nova Ceph user (if using authx) to allow writing to the pool where vm images are stored, and it also requires configuring Glance to provide a v2 endpoint with direct_url support enabled (there are security implications to doing this). See http://docs.ceph.com/docs/master/rbd/rbd-openstack/ for more information on configuring OpenStack with RBD. * A new option "live_migration_inbound_addr" has been added in the configuration file, set None as default value. If this option is present in pre_migration_data, the ip address/hostname provided will be used instead of the migration target compute node's hostname as the uri for live migration, if it's None, then the mechanism remains as it is before. * Added support for CPU thread policies, which can be used to control how the libvirt virt driver places guests with respect to CPU SMT "threads". These are provided as instance and image metadata options, 'hw:cpu_thread_policy' and 'hw_cpu_thread_policy' respectively, and provide an additional level of control over CPU pinning policy, when compared to the existing CPU policy feature. These changes were introduced in commits '83cd67c' and 'aaaba4a'. * Add support for enabling discard support for block devices with libvirt. This will be enabled for Cinder volume attachments that specify support for the feature in their connection properties. This requires support to be present in the version of libvirt (v1.0.6+) and qemu (v1.6.0+) used along with the configured virtual drivers for the instance. The virtio-blk driver does not support this functionality. * A new "auto" value for the configuration option "upgrade_levels.compute" is accepted, that allows automatic determination of the compute service version to use for RPC communication. By default, we still use the newest version if not set in the config, a specific version if asked, and only do this automatic behavior if 'auto' is configured. When 'auto' is used, sending a SIGHUP to the service will cause the value to be re- calculated. Thus, after an upgrade is complete, sending SIGHUP to all services will cause them to start sending messages compliant with the newer RPC version. * Libvirt driver in Nova now supports Cinder DISCO volume driver. * A disk space scheduling filter is now available, which prefers compute nodes with the most available disk space. By default, free disk space is given equal importance to available RAM. To increase the priority of free disk space in scheduling, increase the disk_weight_multiplier option. * A new REST API to force live migration to complete has been added in microversion 2.22. * The os-instance-actions methods now read actions from deleted instances. This means that 'GET /v2.1/{tenant-id}/servers/{server-id }/os-instance-actions' and 'GET /v2.1/{tenant-id}/servers/{server-id }/os-instance-actions/{req-id}' will return instance-action items even if the instance corresponding to '{server-id}' has been deleted. * When booting an instance, its sanitized 'hostname' attribute is now used to populate the 'dns_name' attribute of the Neutron ports the instance is attached to. This functionality enables the Neutron internal DNS service to know the ports by the instance's hostname. As a consequence, commands like 'hostname -f' will work as expected when executed in the instance. When a port's network has a non-blank 'dns_domain' attribute, the port's 'dns_name' combined with the network's 'dns_domain' will be published by Neutron in an external DNS as a service like Designate. As a consequence, the instance's hostname is published in the external DNS as a service. This functionality is added to Nova when the 'DNS Integration' extension is enabled in Neutron. The publication of 'dns_name' and 'dns_domain' combinations to an external DNS as a service additionaly requires the configuration of the appropriate driver in Neutron. When the 'Port Binding' extension is also enabled in Neutron, the publication of a 'dns_name' and 'dns_domain' combination to the external DNS as a service will require one additional update operation when Nova allocates the port during the instance boot. This may have a noticeable impact on the performance of the boot process. * The libvirt driver now has a live_migration_tunnelled configuration option which should be used where the VIR_MIGRATE_TUNNELLED flag would previously have been set or unset in the live_migration_flag and block_migration_flag configuration options. * For the libvirt driver, by default hardware properties will be retrieved from the Glance image and if such haven't been provided, it will use a libosinfo database to get those values. If users want to force a specific guest OS ID for the image, they can now use a new glance image property "os_distro" (eg. "--property os_distro=fedora21"). In order to use the libosinfo database, you need to separately install the related native package provided for your operating system distribution. * Add support for allowing Neutron to specify the bridge name for the OVS, Linux Bridge, and vhost-user VIF types. * Added a *nova-manage db online_data_migrations* command for forcing online data migrations, which will run all registered migrations for the release, instead of there being a separate command for each logical data migration. Operators need to make sure all data is migrated before upgrading to the next release, and the new command provides a unified interface for doing it. * Provides API 2.18, which makes the use of project_ids in API urls optional. * Libvirt with Virtuozzo virtualisation type now supports snapshot operations * Remove "onSharedStorage" parameter from server's evacuate action in microversion 2.14. Nova will automatically detect if the instance is on shared storage. Also adminPass is removed from the response body which makes the response body empty. The user can get the password with the server's os-server-password action. * Add two new list/show API for server-migration. The list API will return the in progress live migratons information of a server. The show API will return a specified in progress live migration of a server. This has been added in microversion 2.23. * A new service.status versioned notification has been introduced. When the status of the Service object is changed nova will send a new service.update notification with versioned payload according to bp versioned-notification-api. The new notification is documented in http://docs.openstack.org/developer/nova/notifications.html * Two new policies soft-affinty and soft-anti-affinity have been implemented for the server-group feature of Nova. This means that POST /v2.1/{tenant_id}/os-server-groups API resource now accepts 'soft-affinity' and 'soft-anti-affinity' as value of the 'policies' key of the request body. * In Nova Compute API microversion 2.19, you can specify a "description" attribute when creating, rebuilding, or updating a server instance. This description can be retrieved by getting server details, or list details for servers. Refer to the Nova Compute API documentation for more information. Note that the description attribute existed in prior Nova versions, but was set to the server name by Nova, and was not visible to the user. So, servers you created with microversions prior to 2.19 will return the description equals the name on server details microversion 2.19. * As part of refactoring the notification interface of Nova a new config option 'notification_format' has been added to specifies which notification format shall be used by nova. The possible values are 'unversioned' (e.g. legacy), 'versioned', 'both'. The default value is 'both'. The new versioned notifications are documented in http://docs.openstack.org/developer/nova/notifications.html * For the VMware driver, the flavor extra specs for quotas has been extended to support: * quota:cpu_limit - The cpu of a virtual machine will not exceed this limit, even if there are available resources. This is typically used to ensure a consistent performance of virtual machines independent of available resources. Units are MHz. * quota:cpu_reservation - guaranteed minimum reservation (MHz) * quota:cpu_shares_level - the allocation level. This can be 'custom', 'high', 'normal' or 'low'. * quota:cpu_shares_share - in the event that 'custom' is used, this is the number of shares. * quota:memory_limit - The memory utilization of a virtual machine will not exceed this limit, even if there are available resources. This is typically used to ensure a consistent performance of virtual machines independent of available resources. Units are MB. * quota:memory_reservation - guaranteed minimum reservation (MB) * quota:memory_shares_level - the allocation level. This can be 'custom', 'high', 'normal' or 'low'. * quota:memory_shares_share - in the event that 'custom' is used, this is the number of shares. * quota:disk_io_limit - The I/O utilization of a virtual machine will not exceed this limit. The unit is number of I/O per second. * quota:disk_io_reservation - Reservation control is used to provide guaranteed allocation in terms of IOPS * quota:disk_io_shares_level - the allocation level. This can be 'custom', 'high', 'normal' or 'low'. * quota:disk_io_shares_share - in the event that 'custom' is used, this is the number of shares. * quota:vif_limit - The bandwidth limit for the virtual network adapter. The utilization of the virtual network adapter will not exceed this limit, even if there are available resources. Units in Mbits/sec. * quota:vif_reservation - Amount of network bandwidth that is guaranteed to the virtual network adapter. If utilization is less than reservation, the resource can be used by other virtual network adapters. Reservation is not allowed to exceed the value of limit if limit is set. Units in Mbits/sec. * quota:vif_shares_level - the allocation level. This can be 'custom', 'high', 'normal' or 'low'. * quota:vif_shares_share - in the event that 'custom' is used, this is the number of shares. Upgrade Notes ************* * All noVNC proxy configuration options have been added to the 'vnc' group. They should no longer be included in the 'DEFAULT' group. * All VNC XVP configuration options have been added to the 'vnc' group. They should no longer be included in the 'DEFAULT' group. * Upon first startup of the scheduler service in Mitaka, all defined aggregates will have UUIDs generated and saved back to the database. If you have a significant number of aggregates, this may delay scheduler start as that work is completed, but it should be minor for most deployments. * During an upgrade to Mitaka, operators must create and initialize a database for the API service. Configure this in [api_database]/connection, and then run "nova-manage api_db sync" * We can not use microversion 2.25 to do live-migration during upgrade, nova-api will raise bad request if there is still old compute node in the cluster. * The option "scheduler_driver" is now changed to use entrypoint instead of full class path. Set one of the entrypoints under the namespace 'nova.scheduler.driver' in 'setup.cfg'. Its default value is 'host_manager'. The full class path style is still supported in current release. But it is not recommended because class path can be changed and this support will be dropped in the next major release. * The option "scheduler_host_manager" is now changed to use entrypoint instead of full class path. Set one of the entrypoints under the namespace 'nova.scheduler.host_manager' in 'setup.cfg'. Its default value is 'host_manager'. The full class path style is still supported in current release. But it is not recommended because class path can be changed and this support will be dropped in the next major release. * The local conductor mode is now deprecated and may be removed as early as the 14.0.0 release. If you are using local conductor mode, plan on deploying remote conductor by the time you upgrade to the 14.0.0 release. * The Extensible Resource Tracker is deprecated and will be removed in the 14.0.0 release. If you use this functionality and have custom resources that are managed by the Extensible Resource Tracker, please contact the Nova development team by posting to the openstack-dev mailing list. There is no future planned support for the tracking of custom resources. * For Liberty compute nodes, the disk_allocation_ratio works as before, you must set it on the scheduler if you want to change it. For Mitaka compute nodes, the disk_allocation_ratio set on the compute nodes will be used only if the configuration is not set on the scheduler. This is to allow, for backwards compatibility, the ability to still override the disk allocation ratio by setting the configuration on the scheduler node. In Newton, we plan to remove the ability to set the disk allocation ratio on the scheduler, at which point the compute nodes will always define the disk allocation ratio, and pass that up to the scheduler. None of this changes the default disk allocation ratio of 1.0. This matches the behaviour of the RAM and CPU allocation ratios. * (Only if you do continuous deployment) 1337890ace918fa2555046c01c8624be014ce2d8 drops support for an instance major version, which means that you must have deployed at least commit 713d8cb0777afb9fe4f665b9a40cac894b04aacb before deploying this one. * nova now requires ebtables 2.0.10 or later * nova recommends libvirt 1.2.11 or later * Filters internal interface changed using now the RequestSpec NovaObject instead of an old filter_properties dictionary. In case you run out-of-tree filters, you need to modify the host_passes() method to accept a new RequestSpec object and modify the filter internals to use that new object. You can see other in-tree filters for getting the logic or ask for help in #openstack-nova IRC channel. * The "force_config_drive" configuration option provided an "always" value which was deprecated in the previous release. That "always" value is now no longer accepted and deployments using that value have to change it to "True" before upgrading. * Support for Windows / Hyper-V Server 2008 R2 has been deprecated in Liberty (12.0.0) and it is no longer supported in Mitaka (13.0.0). If you have compute nodes running that version, please consider moving the running instances to other compute nodes before upgrading those to Mitaka. * The libvirt driver will now correct unsafe and invalid values for the live_migration_flag and block_migration_flag configuration options. The live_migration_flag must not contain VIR_MIGRATE_SHARED_INC but block_migration_flag must contain it. Both options must contain the VIR_MIGRATE_PEER2PEER, except when using the 'xen' virt type this flag is not supported. Both flags must contain the VIR_MIGRATE_UNDEFINE_SOURCE flag and not contain the VIR_MIGRATE_PERSIST_DEST flag. * The libvirt driver has changed the default value of the 'live_migration_uri' flag, that now is dependent on the 'virt_type'. The old default 'qemu+tcp://%s/system' now is adjusted for each of the configured hypervisors. For Xen this will be 'xenmigr://%s/system', for kvm/qemu this will be 'qemu+tcp://%s/system'. * The minimum required libvirt is now version 0.10.2. The minimum libvirt for the N release has been set to 1.2.1. * In order to make project_id optional in urls, we must constrain the set of allowed values for project_id in our urls. This defaults to a regex of "[0-9a-f\-]+", which will match hex uuids (with / without dashes), and integers. This covers all known project_id formats in the wild. If your site uses other values for project_id, you can set a site specific validation with "project_id_regex" config variable. * The old neutron communication options that were slated for removal in Mitaka are no longer available. This means that going forward communication to neutron will need to be configured using auth plugins. * All code and tests for Nova's EC2 and ObjectStore API support which was deprecated in Kilo (https://wiki.openstack.org/wiki/ReleaseNotes/Kilo#Upgrade_Notes_2) has been completely removed in Mitaka. This has been replaced by the new ec2-api project (http://git.openstack.org/cgit/openstack/ec2-api/) * The commit with change-id Idd4bbbe8eea68b9e538fa1567efd304e9115a02a requires that the nova_api database is setup and Nova is configured to use it. Instructions on doing that are provided below. Nova now requires that two databases are available and configured. The existing nova database needs no changes, but a new nova_api database needs to be setup. It is configured and managed very similarly to the nova database. A new connection string configuration option is available in the api_database group. An example: [api_database] connection = mysql+pymysql://user:secret@127.0.0.1/nova_api?charset=utf8 And a new nova-manage command has been added to manage db migrations for this database. "nova-manage api_db sync" and "nova-manage api_db version" are available and function like the parallel "nova- manage db ..." version. * A new "use_neutron" option is introduced which replaces the obtuse "network_api_class" option. This defaults to 'False' to match existing defaults, however if "network_api_class" is set to the known Neutron value Neutron networking will still be used as before. * The FilterScheduler is now including disabled hosts. Make sure you include the ComputeFilter in the "scheduler_default_filters" config option to avoid placing instances on disabled hosts. * Upgrade the rootwrap configuration for the compute service, so that patches requiring new rootwrap configuration can be tested with grenade. * For backward compatible support the setting "CONF.vmware.integration_bridge" needs to be set when using the Neutron NSX|MH plugin. The default value has been set to "None". * XenServer hypervisor type has been changed from "xen" to "XenServer". It could impact your aggregate metadata or your flavor extra specs if you provide only the former. * The glance xenserver plugin has been bumped to version 1.3 which includes new interfaces for referencing glance servers by url. All dom0 will need to be upgraded with this plugin before upgrading the nova code. Deprecation Notes ***************** * It is now deprecated to use [glance] api_servers without a protocol scheme (http / https). This is required to support urls throughout the system. Update any api_servers list with fully qualified https / http urls. * The conductor.manager configuration option is now deprecated and will be removed. * Deprecate "compute_stats_class" config option. This allowed loading an alternate implementation for collecting statistics for the local compute host. Deployments that felt the need to use this facility are encoraged to propose additions upstream so we can create a stable and supported interface here. * Deprecate the "db_driver" config option. Previously this let you replace our SQLAlchemy database layer with your own. This approach is deprecated. Deployments that felt the need to use the facility are encourage to work with upstream Nova to address db driver concerns in the main SQLAlchemy code paths. * The host, port, and protocol options in the [glance] configuration section are deprecated, and will be removed in the N release. The api_servers value should be used instead. * Deprecate the use of nova.hooks. This facility used to let arbitrary out of tree code be executed around certain internal actions, but is unsuitable for having a well maintained API. Anyone using this facility should bring forward their use cases in the Newton cycle as nova-specs. * Nova used to support the concept that "service managers" were replaceable components. There are many config options where you can replace a manager by specifying a new class. This concept is deprecated in Mitaka as are the following config options. * [cells] manager * metadata_manager * compute_manager * console_manager * consoleauth_manager * cert_manager * scheduler_manager Many of these will be removed in Newton. Users of these options are encouraged to work with Nova upstream on any features missing in the default implementations that are needed. * Deprecate "security_group_api" configuration option. The current values are "nova" and "neutron". In future the correct security_group_api option will be chosen based on the value of "use_neutron" which provides a more coherent user experience. * Deprecate the "vendordata_driver" config option. This allowed creating a different class loader for defining vendordata metadata. The default driver loads from a json file that can be arbitrarily specified, so is still quite flexible. Deployments that felt the need to use this facility are encoraged to propose additions upstream so we can create a stable and supported interface here. * The configuration option "api_version" in the "ironic" group was marked as deprecated and will be removed in the future. The only possible value for that configuration was "1" (because Ironic only has 1 API version) and the Ironic team came to an agreement that setting the API version via configuration option should not be supported anymore. As the Ironic driver in Nova requests the Ironic v1.8 API, that means that Nova 13.0.0 ("Mitaka") requires Ironic 4.0.0 ("Liberty") or newer if you want to use the Ironic driver. * The libvirt live_migration_flag and block_migration_flag config options are deprecated. These options gave too fine grained control over the flags used and, in some cases, misconfigurations could have dangerous side effects. Please note the availability of a new live_migration_tunnelled configuration option. * The "network_device_mtu" option in Nova is deprecated for removal since network MTU should be specified when creating the network with nova-network. With Neutron networks, the MTU value comes from the "segment_mtu" configuration option in Neutron. * The old top-level resource */os-migrations* is deprecated, it won't be extended anymore. And migration_type for /os-migrations, also add ref link to the /servers/{uuid}/migrations/{id} for it when the migration is an in-progress live-migration. This has been added in microversion 2.23. * Deprecate "volume_api_class" and "network_api_class" config options. We only have one sensible backend for either of these. These options will be removed and turned into constants in Newton. * Option "memcached_servers" is deprecated in Mitaka. Operators should use oslo.cache configuration instead. Specifically "enabled" option under [cache] section should be set to True and the url(s) for the memcached servers should be in [cache]/memcache_servers option. * The Zookeeper Service Group driver has been removed. The driver has no known users and is not actively mantained. A warning log message about the driver's state was added for the Kilo release. Also, evzookeeper library that the driver depends on is unmaintained and incompatible with recent eventlet releases. A future release of Nova will use the Tooz library to track service liveliness, and Tooz supports Zookeeper. (https://bugs.launchpad.net/nova/+bug/1443910) (http://specs.openstack.org/openstack/nova- specs/specs/liberty/approved/service-group-using-tooz.html) Security Issues *************** * [OSSA 2016-001] Nova host data leak through snapshot (CVE-2015-7548) * Bug 1524274 (https://bugs.launchpad.net/nova/+bug/1524274) * Announcement [OSSA 2016-002] Xen connection password leak in logs via StorageError (CVE-2015-8749) * Bug 1516765 (https://bugs.launchpad.net/nova/+bug/1516765) * Announcement [OSSA 2016-007] Host data leak during resize/migrate for raw-backed instances (CVE-2016-2140) * Bug 1548450 (https://bugs.launchpad.net/nova/+bug/1548450) * Announcement Bug Fixes ********* * In a race condition 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 this case 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. Fixed this issue by updating the base file access time with root user privileges using 'touch' command. * When plugging virtual interfaces of type vhost-user the MTU value will not be applied to the interface by nova. vhost-user ports exist only in userspace and are not backed by kernel netdevs, for this reason it is not possible to set the mtu on a vhost-user interface using standard tools such as ifconfig or ip link. Other Notes *********** * Conductor RPC API no longer supports v2.x. * The service subcommand of nova-manage is deprecated. Use the nova service-* commands from python-novaclient instead or the os-services REST resource. The service subcommand will be removed in the 14.0 release. * The Neutron network MTU value is now used when plugging virtual interfaces in nova-compute. If the value is 0, which is the default value for the "segment_mtu" configuration option in Neutron before Mitaka, then the (deprecated) "network_device_mtu" configuration option in Nova is used, which defaults to not setting an MTU value. * The sample policy file shipped with Nova contained many policies set to ""(allow all) which was not the proper default for many of those checks. It was also a source of confusion as some people thought "" meant to use the default rule. These empty policies have been updated to be explicit in all cases. Many of them were changed to match the default rule of "admin_or_owner" which is a more restrictive policy check but does not change the restrictiveness of the API calls overall because there are similar checks in the database already. This does not affect any existing deployment, just the sample file included for use by new deployments. * Nova's EC2 API support which was deprecated in Kilo (https://wiki.openstack.org/wiki/ReleaseNotes/Kilo#Upgrade_Notes_2) is removed from Mitaka. This has been replaced by the new ec2-api project (http://git.openstack.org/cgit/openstack/ec2-api/) Changes in nova 13.0.0.0rc2..13.0.0 ----------------------------------- 7105f88 Imported Translations from Zanata 5de98cb Imported Translations from Zanata a9d5542 Fix detach SR-IOV when using LibvirtConfigGuestHostdevPCI 5b6ee70 Imported Translations from Zanata 29042e0 Imported Translations from Zanata 3e9819d Update cells blacklist regex for test_server_basic_ops c71c4e0 Stop providing force_hosts to the scheduler for move ops Diffstat (except docs and test files) ------------------------------------- devstack/tempest-dsvm-cells-rc | 2 +- nova/conductor/manager.py | 8 + nova/conductor/tasks/live_migrate.py | 4 + nova/locale/de/LC_MESSAGES/nova.po | 22 +- nova/locale/fr/LC_MESSAGES/nova.po | 34 +- nova/locale/ja/LC_MESSAGES/nova.po | 1315 ++++++++++++-- nova/locale/ko_KR/LC_MESSAGES/nova-log-warning.po | 1914 ++++++++++++++++++++ nova/objects/request_spec.py | 12 + .../unit/conductor/tasks/test_live_migrate.py | 3 + nova/virt/libvirt/driver.py | 13 +- 13 files changed, 3194 insertions(+), 194 deletions(-)

1 0

[release][mistral] mistral-dashboard 2.0.0 release (mitaka)
by no-reply＠openstack.org 06 Apr '16

06 Apr '16

We are gleeful to announce the release of: mistral-dashboard 2.0.0: Mistral dashboard This release is part of the mitaka release series. For more details, please see below. Changes in mistral-dashboard 2.0.0.0rc1..2.0.0 ---------------------------------------------- f49b147 Update .gitreview for stable/mitaka Diffstat (except docs and test files) ------------------------------------- .gitreview | 1 + 1 file changed, 1 insertion(+)

1 0

[release][designate] designate-dashboard 2.0.0 release (mitaka)
by no-reply＠openstack.org 06 Apr '16

06 Apr '16

We are tickled pink to announce the release of: designate-dashboard 2.0.0: Designate Horizon UI bits This release is part of the mitaka release series. For more details, please see below. Changes in designate-dashboard 2.0.0.0rc1..2.0.0 ------------------------------------------------ 7fbe18a Imported Translations from Zanata 2fdca52 Fix unit tests under Django 1.9 72d45d6 Add ADD_INSTALLED_APPS to 'enabled' file 76df49e Extract strings from django templates 03813a8 Imported Translations from Zanata 202300b Imported Translations from Zanata a829a1b Update .gitreview for stable/mitaka Diffstat (except docs and test files) ------------------------------------- .gitreview | 1 + babel-django.cfg | 4 + .../templates/dns_domains/domain_detail.html | 2 +- .../dns_domains/templates/dns_domains/records.html | 2 +- .../enabled/_1720_project_dns_panel.py | 2 + designatedashboard/locale/django.pot | 238 +++++++++++++--- designatedashboard/locale/ja/LC_MESSAGES/django.po | 134 ++++++++- .../locale/ko_KR/LC_MESSAGES/django.po | 227 +++++++++++++++ .../locale/pt_BR/LC_MESSAGES/django.po | 305 +++++++++++++++++++++ 16 files changed, 939 insertions(+), 120 deletions(-)

1 0

[release][sahara] sahara 4.0.0 release (mitaka)
by no-reply＠openstack.org 06 Apr '16

06 Apr '16

We are jazzed to announce the release of: sahara 4.0.0: Sahara project This release is part of the mitaka release series. With source available at: http://git.openstack.org/cgit/openstack/sahara For more details, please see below. 4.0.0 ^^^^^ New Features ************ * Add ability of scheduling EDP jobs for sahara * Added support of running sahara-api as wsgi application. Use 'sahara-wsgi-api' command for use this feature. * CDH 5.5.0 is supported in CDH plugin. * OpenStack Key Manager service can now be used by sahara to enable storage of sensitive information in an external service such as barbican. Upgrade Notes ************* * HDP plugin removed from default configuration list. End users who are using HDP should ensure that their configuration files continue to list "hdp". * Move notifications options into oslo_messaging_notifications Deprecation Notes ***************** * The HDP 2.0.6 plugin is deprecated in Mitaka release and will be removed in Newton release. Please, use the Ambari 2.3 instead. * Removed support of Vanilla 2.6.0 plugin. * Removed support for the Spark 1.0.0 plugin. Bug Fixes ********* * Fixed api_insecure handling in sessions. Closed bug 1539498. * Add regular expression matching on search values for certain string fields of sahara objects. This applies to list operations through the REST API and therefore applies to the dashboard and sahara client as well. Closes bug 1503345. Changes in sahara 4.0.0.0rc1..4.0.0 ----------------------------------- 65330b8 Set libext path for Oozie 4.0.1, 4.1.0 6daf4c0 Update .gitreview for stable/mitaka Diffstat (except docs and test files) ------------------------------------- .gitreview | 1 + sahara/plugins/mapr/services/oozie/oozie.py | 12 +++++++----- 2 files changed, 8 insertions(+), 5 deletions(-)

1 0

[release][freezer] freezer-api 2.0.0 release (mitaka)
by no-reply＠openstack.org 06 Apr '16

06 Apr '16

We are eager to announce the release of: freezer-api 2.0.0: OpenStack Backup and Restore API Service This release is part of the mitaka release series. For more details, please see below. Changes in freezer-api 2.0.0.0rc1..2.0.0 ---------------------------------------- ea70bbc This is incorrect url in example doc and conf 13f0b7b Add Freezer API Version Test e38f650 Fix url from stackforge to openstack Diffstat (except docs and test files) ------------------------------------- .pylintrc | 2 +- devstack/README.rst | 2 +- devstack/gate_hook.sh | 1 + devstack/local.conf.example | 2 +- devstack/settings | 2 +- .../services/freezer_api_client.py | 34 ++++++++++++++++++++++ 14 files changed, 155 insertions(+), 12 deletions(-)

1 0

[release][neutron] neutron-fwaas 8.0.0 release (mitaka)
by no-reply＠openstack.org 06 Apr '16

06 Apr '16

We are gleeful to announce the release of: neutron-fwaas 8.0.0: OpenStack Networking FWaaS This release is part of the mitaka release series. For more details, please see below. 8.0.0 ^^^^^ Generation of sample Neutron FWaaS configuration files. Enable quotas for FWaaS. New Features ************ * Neutron FWaaS no longer includes static example configuration files. Instead, use tools/generate_config_file_samples.sh to generate them. The files are generated with a .sample extension. * The FWaaS extension will register quotas. The default values for quota_firewall and quota_firewall_policy are set to 10. The default value for quota_firewall_rule is set to 100. Quotas can be adjusted in the conf files, including -1 values to allow unlimited. Known Issues ************ * Tenants may receive a 409 Conflict error with a message body containing a quota exceeded message during resource creation if their quota is exceeded. Other Notes *********** * Operators that increase the default limit for quota_routers from 10 may want to bump FWaaS quotas as well, since with router insertion a tenant can potentially have a unique policy and firewall for each router. Changes in neutron-fwaas 8.0.0.0rc2..8.0.0 ------------------------------------------ ab56228 Constraint requirements using mitaka upper-constraints.txt file Diffstat (except docs and test files) ------------------------------------- tools/tox_install.sh | 2 +- tox.ini | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-)

1 0

[release][freezer] freezer 2.0.0 release (mitaka)
by no-reply＠openstack.org 06 Apr '16

06 Apr '16

We are jazzed to announce the release of: freezer 2.0.0: The OpenStack Backup Restore and Disaster Recovery as a Service Platform This release is part of the mitaka release series. For more details, please see below. Changes in freezer 2.0.0.0rc1..2.0.0 ------------------------------------ 367a225 Fix creation of jobs with stopped state fd5d6ba Updated from global requirements 9efa12f Added --overwrite parameter for removing all files from restore directory. Default value --overwrite=False 0973cf7 Use correct type for freezer arguments a6b771f Provides more details in the help of --restore-from-date option. Explains the behavior with an example. 7c0f5bc Rename mode default to fs 219fb2b Start to introduce tempest tests. 34d2168 enable output of metadata to a file Diffstat (except docs and test files) ------------------------------------- devstack/settings | 3 ++ freezer/common/config.py | 49 ++++++++++++++-------- freezer/engine/engine.py | 6 ++- freezer/job.py | 2 +- freezer/main.py | 11 ++++- freezer/mode/default.py | 35 ---------------- freezer/mode/fs.py | 35 ++++++++++++++++ freezer/scheduler/scheduler_job.py | 6 ++- .../freezer_tempest_plugin/services/__init__.py | 0 freezer/utils/utils.py | 4 ++ requirements.txt | 35 +++++++++------- setup.cfg | 3 ++ setup.py | 36 +++++++++------- test-requirements.txt | 26 +++++++----- 23 files changed, 263 insertions(+), 99 deletions(-) Requirements updates -------------------- diff --git a/requirements.txt b/requirements.txt index adeefc3..741e429 100644 --- a/requirements.txt +++ b/requirements.txt @@ -1,3 +1,6 @@ -astroid<1.4.0 # breaks pylint 1.4.4 -setuptools>=16.0 -pbr>=1.6 +# The order of packages is significant, because pip processes them in the order +# of appearance. Changing the order has an impact on the overall integration +# process, which may cause wedges in the gate later. +astroid<1.4.0 # LGPL # breaks pylint 1.4.4 +setuptools>=16.0 # PSF/ZPL +pbr>=1.6 # Apache-2.0 @@ -5,9 +8,9 @@ python-swiftclient>=2.2.0 # Apache-2.0 -python-keystoneclient>=1.6.0,!=1.8.0 -python-cinderclient>=1.3.1 -python-glanceclient>=1.2.0 # Apache-2.0 -python-novaclient>=2.29.0,!=2.33.0 # Apache-2.0 -python-openstackclient>=2.0.0 # Apache-2.0 -oslo.utils>=3.2.0 -oslo.i18n>=1.5.0 # Apache-2.0 -oslo.log>=1.14.0 -oslo.config>=3.2.0 # Apache-2.0 +python-keystoneclient!=1.8.0,!=2.1.0,>=1.6.0 # Apache-2.0 +python-cinderclient>=1.3.1 # Apache-2.0 +python-glanceclient>=2.0.0 # Apache-2.0 +python-novaclient!=2.33.0,>=2.29.0 # Apache-2.0 +python-openstackclient>=2.1.0 # Apache-2.0 +oslo.utils>=3.5.0 # Apache-2.0 +oslo.i18n>=2.1.0 # Apache-2.0 +oslo.log>=1.14.0 # Apache-2.0 +oslo.config>=3.7.0 # Apache-2.0 @@ -15,3 +18,3 @@ oslo.config>=3.2.0 # Apache-2.0 -PyMySQL>=0.6.2 # MIT License -pymongo>=3.0.2 -paramiko>=1.13.0 +PyMySQL>=0.6.2 # MIT License +pymongo!=3.1,>=3.0.2 # Apache-2.0 +paramiko>=1.16.0 # LGPL @@ -21 +24 @@ six>=1.9.0 # MIT -apscheduler +apscheduler # MIT License diff --git a/test-requirements.txt b/test-requirements.txt index b830d53..c7c96a9 100644 --- a/test-requirements.txt +++ b/test-requirements.txt @@ -1,5 +1,8 @@ -flake8>=2.2.4,<=2.4.1 -hacking>=0.10.2,<0.11 -coverage>=3.6 -discover -mock>=1.2 +# The order of packages is significant, because pip processes them in the order +# of appearance. Changing the order has an impact on the overall integration +# process, which may cause wedges in the gate later. +flake8<2.6.0,>2.4.1 # MIT +hacking<0.11,>=0.10.2 +coverage>=3.6 # Apache-2.0 +discover # BSD +mock>=1.2 # BSD @@ -7,5 +10,8 @@ pylint==1.4.5 # GNU GPL v2 -python-subunit>=0.0.18 -sphinx>=1.1.2,!=1.2.0,!=1.3b1,<1.3 # BSD -oslosphinx>=2.5.0,!=3.4.0 # Apache-2.0 -testrepository>=0.0.18 -testtools>=1.4.0 +python-subunit>=0.0.18 # Apache-2.0/BSD +sphinx!=1.2.0,!=1.3b1,<1.3,>=1.1.2 # BSD +oslosphinx!=3.4.0,>=2.5.0 # Apache-2.0 +testrepository>=0.0.18 # Apache-2.0/BSD +testtools>=1.4.0 # MIT + +# Tempest Plugin +tempest-lib>=0.14.0 # Apache-2.0

1 0

[release][keystone] keystone 9.0.0 release (mitaka)
by no-reply＠openstack.org 06 Apr '16

06 Apr '16

We are satisfied to announce the release of: keystone 9.0.0: OpenStack Identity This release is part of the mitaka release series. For more details, please see below. 9.0.0 ^^^^^ New Features ************ * [blueprint domain-specific-roles (https://blueprints.launchpad.net/keystone/+spec/domain-specific- roles)] Roles can now be optionally defined as domain specific. Domain specific roles are not referenced in policy files, rather they can be used to allow a domain to build their own private inference rules with implied roles. A domain specific role can be assigned to a domain or project within its domain, and any subset of global roles it implies will appear in a token scoped to the respective domain or project. The domain specific role itself, however, will not appear in the token. * [blueprint bootstrap (https://blueprints.launchpad.net/keystone/+spec/bootstrap) keystone-manage now supports the bootstrap command on the CLI so that a keystone install can be initialized without the need of the admin_token filter in the paste-ini. * [blueprint domain-config-default (https://blueprints.launchpad.net/keystone/+spec/domain-config- default)] The Identity API now supports retrieving the default values for the configuration options that can be overriden via the domain specific configuration API. * [blueprint url-safe-naming (https://blueprints.launchpad.net/keystone/+spec/url-safe-naming) The names of projects and domains can optionally be ensured to be url safe, to support the future ability to specify projects using hierarchical naming. * [bug 1490804 (https://bugs.launchpad.net/keystone/+bug/1490804) Audit IDs are included in the token revocation list. * [bug 1519210 (https://bugs.launchpad.net/keystone/+bug/1519210) A user may now opt-out of notifications by specifying a list of event types using the *notification_opt_out* option in *keystone.conf*. These events are never sent to a messaging service. * [bug 1542417 (https://bugs.launchpad.net/keystone/+bug/1542417) Added support for a *user_description_attribute* mapping to the LDAP driver configuration. * [bug 1526462 (https://bugs.launchpad.net/keystone/+bug/1526462) Support for posixGroups with OpenDirectory and UNIX when using the LDAP identity driver. * [bug 1489061 (https://bugs.launchpad.net/keystone/+bug/1489061) Caching has been added to catalog retrieval on a per user ID and project ID basis. This affects both the v2 and v3 APIs. As a result this should provide a performance benefit to fernet-based deployments. * Keystone supports "$(project_id)s" in the catalog. It works the same as "$(tenant_id)s". Use of "$(tenant_id)s" is deprecated and catalog endpoints should be updated to use "$(project_id)s". * [bug 1525317 (https://bugs.launchpad.net/keystone/+bug/1525317) Enable filtering of identity providers based on *id*, and *enabled* attributes. * [bug 1555830 (https://bugs.launchpad.net/keystone/+bug/1555830) Enable filtering of service providers based on *id*, and *enabled* attributes. * [blueprint federation-group-ids-mapped-without-domain-reference (https://blueprints.launchpad.net/keystone/+spec/federation-group- ids-mapped-without-domain-reference)] Enhanced the federation mapping engine to allow for group IDs to be referenced without a domain ID. * [blueprint implied-roles (https://blueprints.launchpad.net/keystone/+spec/implied-roles) Keystone now supports creating implied roles. Role inference rules can now be added to indicate when the assignment of one role implies the assignment of another. The rules are of the form *prior_role* implies *implied_role*. At token generation time, user/group assignments of roles that have implied roles will be expanded to also include such roles in the token. The expansion of implied roles is controlled by the *prohibited_implied_role* option in the *[assignment]* section of *keystone.conf*. * [bug 96869 (https://bugs.launchpad.net/keystone/+bug/968696) A pair of configuration options have been added to the "[resource]" section to specify a special "admin" project: "admin_project_domain_name" and "admin_project_name". If these are defined, any scoped token issued for that project will have an additional identifier "is_admin_project" added to the token. This identifier can then be checked by the policy rules in the policy files of the services when evaluating access control policy for an API. Keystone does not yet support the ability for a project acting as a domain to be the admin project. That will be added once the rest of the code for projects acting as domains is merged. * [bug 1515302 (https://bugs.launchpad.net/keystone/+bug/1515302) Two new configuration options have been added to the *[ldap]* section. *user_enabled_emulation_use_group_config* and *project_enabled_emulation_use_group_config*, which allow deployers to choose if they want to override the default group LDAP schema option. * [bug 1501698 (https://bugs.launchpad.net/keystone/+bug/1501698) Support parameter *list_limit* when LDAP is used as identity backend. * [bug 1479569 (https://bugs.launchpad.net/keystone/+bug/1479569) Names have been added to list role assignments (GET /role_assignments?include_names=True), rather than returning just the internal IDs of the objects the names are also returned. * Domains are now represented as top level projects with the attribute *is_domain* set to true. Such projects will appear as parents for any previous top level projects. Projects acting as domains can be created, read, updated, and deleted via either the project API or the domain API (V3 only). * [bug 1500222 (https://bugs.launchpad.net/keystone/+bug/1500222) Added information such as: user ID, project ID, and domain ID to log entries. As a side effect of this change, both the user's domain ID and project's domain ID are now included in the auth context. * [bug 1473042 (https://bugs.launchpad.net/keystone/+bug/1473042) Keystone's S3 compatibility support can now authenticate using AWS Signature Version 4. * [blueprint totp-auth (https://blueprints.launchpad.net/keystone/+spec/totp-auth) Keystone now supports authenticating via Time-based One-time Password (TOTP). To enable this feature, add the "totp" auth plugin to the *methods* option in the *[auth]* section of *keystone.conf*. More information about using TOTP can be found in keystone's developer documentation (http://docs.openstack.org/developer/keystone/auth-totp.html) * [blueprint x509-ssl-client-cert-authn (https://blueprints.launchpad.net/keystone/+spec/x509-ssl-client- cert-authn)] Keystone now supports tokenless client SSL x.509 certificate authentication and authorization. Upgrade Notes ************* * [bug 1473553 (https://bugs.launchpad.net/keystone/+bug/1473553) The *keystone-paste.ini* must be updated to put the "admin_token_auth" middleware before "build_auth_context". See the sample *keystone- paste.ini* for the correct *pipeline* value. Having "admin_token_auth" after "build_auth_context" is deprecated and will not be supported in a future release. * The LDAP driver now also maps the user description attribute after user retrieval from LDAP. If this is undesired behavior for your setup, please add *description* to the *user_attribute_ignore* LDAP driver config setting. The default mapping of the description attribute is set to *description*. Please adjust the LDAP driver config setting *user_description_attribute* if your LDAP uses a different attribute name (for instance to *displayName* in case of an AD backed LDAP). If your *user_additional_attribute_mapping* setting contains *description:description* you can remove this mapping, since this is now the default behavior. * The default setting for the *os_inherit* configuration option is changed to True. If it is required to continue with this portion of the API disabled, then override the default setting by explicitly specifying the os_inherit option as False. * The *keystone-paste.ini* file must be updated to remove extension filters, and their use in "[pipeline:api_v3]". Remove the following filters: "[filter:oauth1_extension]", "[filter:federation_extension]", "[filter:endpoint_filter_extension]", and "[filter:revoke_extension]". See the sample keystone-paste.ini (https://git.openstack.org/cgit/openstack/keystone/tree/etc /keystone-paste.ini) file for guidance. * The *keystone-paste.ini* file must be updated to remove extension filters, and their use in "[pipeline:public_api]" and "[pipeline:admin_api]" pipelines. Remove the following filters: "[filter:user_crud_extension]", "[filter:crud_extension]". See the sample keystone-paste.ini (https://git.openstack.org/cgit/openstack/keystone/tree/etc /keystone-paste.ini) file for guidance. * A new config option, *insecure_debug*, is added to control whether debug information is returned to clients. This used to be controlled by the *debug* option. If you'd like to return extra information to clients set the value to "true". This extra information may help an attacker. * The configuration options for LDAP connection pooling, *[ldap] use_pool* and *[ldap] use_auth_pool*, are now both enabled by default. Only deployments using LDAP drivers are affected. Additional configuration options are available in the *[ldap]* section to tune connection pool size, etc. * [bug 1541092 (https://bugs.launchpad.net/keystone/+bug/1541092) Only database upgrades from Kilo and newer are supported. * Keystone now uses oslo.cache. Update the *[cache]* section of *keystone.conf* to point to oslo.cache backends: "oslo_cache.memcache_pool" or "oslo_cache.mongo". Refer to the sample configuration file for examples. See oslo.cache (http://docs.openstack.org/developer/oslo.cache) for additional documentation. Deprecation Notes ***************** * [blueprint deprecated-as-of-mitaka (https://blueprints.launchpad.net/keystone/+spec/deprecated-as-of- mitaka)] The V8 Assignment driver interface is deprecated. Support for the V8 Assignment driver interface is planned to be removed in the 'O' release of OpenStack. * [blueprint deprecated-as-of-mitaka (https://blueprints.launchpad.net/keystone/+spec/deprecated-as-of- mitaka)] The V8 Role driver interface is deprecated. Support for the V8 Role driver interface is planned to be removed in the 'O' release of OpenStack. * The V8 Resource driver interface is deprecated. Support for the V8 Resource driver interface is planned to be removed in the 'O' release of OpenStack. * [blueprint deprecated-as-of-mitaka (https://blueprints.launchpad.net/keystone/+spec/deprecated-as-of- mitaka)] The "admin_token_auth" filter must now be placed before the "build_auth_context" filter in *keystone-paste.ini*. * Use of "$(tenant_id)s" in the catalog endpoints is deprecated in favor of "$(project_id)s". * [blueprint deprecated-as-of-mitaka (https://blueprints.launchpad.net/keystone/+spec/deprecated-as-of- mitaka)] Deprecate the "enabled" option from "[endpoint_policy]", it will be removed in the 'O' release, and the extension will always be enabled. * [blueprint deprecated-as-of-mitaka (https://blueprints.launchpad.net/keystone/+spec/deprecated-as-of- mitaka)] The token memcache and memcache_pool persistence backends have been deprecated in favor of using Fernet tokens (which require no persistence). * [blueprint deprecated-as-of-mitaka (https://blueprints.launchpad.net/keystone/+spec/deprecated-as-of- mitaka)] Deprecated all v2.0 APIs. The keystone team recommends using v3 APIs instead. Most v2.0 APIs will be removed in the 'Q' release. However, the authentication APIs and EC2 APIs are indefinitely deprecated and will not be removed in the 'Q' release. * [blueprint deprecated-as-of-mitaka (https://blueprints.launchpad.net/keystone/+spec/deprecated-as-of- mitaka)] As of the Mitaka release, the PKI and PKIz token formats have been deprecated. They will be removed in the 'O' release. Due to this change, the *hash_algorithm* option in the *[token]* section of the configuration file has also been deprecated. Also due to this change, the "keystone-manage pki_setup" command has been deprecated as well. * [blueprint deprecated-as-of-mitaka (https://blueprints.launchpad.net/keystone/+spec/deprecated-as-of- mitaka)] As of the Mitaka release, write support for the LDAP driver of the Identity backend has been deprecated. This includes the following operations: create user, create group, delete user, delete group, update user, update group, add user to group, and remove user from group. These operations will be removed in the 'O' release. * [blueprint deprecated-as-of-mitaka (https://blueprints.launchpad.net/keystone/+spec/deprecated-as-of- mitaka)] As of the Mitaka release, the auth plugin *keystone.auth.plugins.saml2.Saml2* has been deprecated. It is recommended to use *keystone.auth.plugins.mapped.Mapped* instead. The "saml2" plugin will be removed in the 'O' release. * [blueprint deprecated-as-of-mitaka (https://blueprints.launchpad.net/keystone/+spec/deprecated-as-of- mitaka)] As of the Mitaka release, the simple_cert_extension is deprecated since it is only used in support of the PKI and PKIz token formats. It will be removed in the 'O' release. * The *os_inherit* configuration option is disabled. In the future, this option will be removed and this portion of the API will be always enabled. * [blueprint deprecated-as-of-mitaka (https://blueprints.launchpad.net/keystone/+spec/deprecated-as-of- mitaka)] The file "httpd/keystone.py" has been deprecated in favor of "keystone-wsgi-admin" and "keystone-wsgi-public" and may be removed in the 'O' release. * [blueprint deprecated-as-of-mitaka (https://blueprints.launchpad.net/keystone/+spec/deprecated-as-of- mitaka)] "keystone.common.cache.backends.memcache_pool", "keystone.common.cache.backends.mongo", and "keystone.common.cache.backends.noop" are deprecated in favor of oslo.cache backends. The keystone backends will be removed in the 'O' release. * The V8 Federation driver interface is deprecated in favor of the V9 Federation driver interface. Support for the V8 Federation driver interface is planned to be removed in the 'O' release of OpenStack. Security Issues *************** * The use of admin_token filter is insecure compared to the use of a proper username/password. Historically the admin_token filter has been left enabled in Keystone after initialization due to the way CMS systems work. Moving to an out-of-band initialization using "keystone-manage bootstrap" will eliminate the security concerns around a static shared string that conveys admin access to keystone and therefore to the entire installation. * The admin_token method of authentication was never intended to be used for any purpose other than bootstrapping an install. However many deployments had to leave the admin_token method enabled due to restrictions on editing the paste file used to configure the web pipelines. To minimize the risk from this mechanism, the *admin_token* configuration value now defaults to a python *None* value. In addition, if the value is set to *None*, either explicitly or implicitly, the *admin_token* will not be enabled, and an attempt to use it will lead to a failed authentication. * [bug 1490804 (https://bugs.launchpad.net/keystone/+bug/1490804) [CVE-2015-7546 (http://cve.mitre.org/cgi- bin/cvename.cgi?name=CVE-2015-7546)] A bug is fixed where an attacker could avoid token revocation when the PKI or PKIZ token provider is used. The complete remediation for this vulnerability requires the corresponding fix in the keystonemiddleware project. Bug Fixes ********* * [bug 1535878 (https://bugs.launchpad.net/keystone/+bug/1535878) Originally, to perform GET /projects/{project_id}, the provided policy files required a user to have at least project admin level of permission. They have been updated to allow it to be performed by any user who has a role on the project. * [bug 1516469 (https://bugs.launchpad.net/keystone/+bug/1516469) Endpoints filtered by endpoint_group project association will be included in the service catalog when a project scoped token is issued and "endpoint_filter.sql" is used for the catalog driver. * Support has now been added to send notification events on user/group membership. When a user is added or removed from a group a notification will be sent including the identifiers of both the user and the group. * [bug 1527759 (https://bugs.launchpad.net/keystone/+bug/1527759) Reverted the change that eliminates the ability to get a V2 token with a user or project that is not in the default domain. This change broke real-world deployments that utilized the ability to authenticate via V2 API with a user not in the default domain or with a project not in the default domain. The deployer is being convinced to update code to properly handle V3 auth but the fix broke expected and tested behavior. * [bug 1480270 (https://bugs.launchpad.net/keystone/+bug/1480270) Endpoints created when using v3 of the keystone REST API will now be included when listing endpoints via the v2.0 API. Other Notes *********** * The list_project_ids_for_user(), list_domain_ids_for_user(), list_user_ids_for_project(), list_project_ids_for_groups(), list_domain_ids_for_groups(), list_role_ids_for_groups_on_project() and list_role_ids_for_groups_on_domain() methods have been removed from the V9 version of the Assignment driver. * [blueprint move-extensions (https://blueprints.launchpad.net/keystone/+spec/move-extensions) If any extension migrations are run, for example: "keystone-manage db_sync --extension endpoint_policy" an error will be returned. This is working as designed. To run these migrations simply run: "keystone-manage db_sync". The complete list of affected extensions are: "oauth1", "federation", "endpoint_filter", "endpoint_policy", and "revoke". * [bug 1367113 (https://bugs.launchpad.net/keystone/+bug/1367113) The "get entity" and "list entities" functionality for the KVS catalog backend has been reimplemented to use the data from the catalog template. Previously this would only act on temporary data that was created at runtime. The create, update and delete entity functionality now raises an exception. * "keystone-manage db_sync" will no longer create the Default domain. This domain is used as the domain for any users created using the legacy v2.0 API. A default domain is created by "keystone- manage bootstrap" and when a user or project is created using the legacy v2.0 API. * The ability to validate a trust-scoped token against the v2.0 API has been removed, in favor of using the version 3 of the API. * [blueprint removed-as-of-mitaka (https://blueprints.launchpad.net/keystone/+spec/removed-as-of- mitaka)] Removed "extras" from token responses. These fields should not be necessary and a well-defined API makes this field redundant. This was deprecated in the Kilo release. * [blueprint removed-as-of-mitaka (https://blueprints.launchpad.net/keystone/+spec/removed-as-of- mitaka)] Removed "RequestBodySizeLimiter" from keystone middleware. The keystone team suggests using "oslo_middleware.sizelimit.RequestBodySizeLimiter" instead. This was deprecated in the Kilo release. * [blueprint removed-as-of-mitaka (https://blueprints.launchpad.net/keystone/+spec/removed-as-of- mitaka)] Notifications with event_type "identity.created.role_assignment" and "identity.deleted.role_assignment" have been removed. The keystone team suggests listening for "identity.role_assignment.created" and "identity.role_assignment.deleted" instead. This was deprecated in the Kilo release. * [blueprint removed-as-of-mitaka (https://blueprints.launchpad.net/keystone/+spec/removed-as-of- mitaka)] Removed "check_role_for_trust" from the trust controller, ensure policy files do not refer to this target. This was deprecated in the Kilo release. * [blueprint removed-as-of-mitaka (https://blueprints.launchpad.net/keystone/+spec/removed-as-of- mitaka)] Removed Catalog KVS backend ("keystone.catalog.backends.sql.Catalog"). This was deprecated in the Icehouse release. * [blueprint removed-as-of-mitaka (https://blueprints.launchpad.net/keystone/+spec/removed-as-of- mitaka)] The LDAP backend for Assignment has been removed. This was deprecated in the Kilo release. * [blueprint removed-as-of-mitaka (https://blueprints.launchpad.net/keystone/+spec/removed-as-of- mitaka)] The LDAP backend for Resource has been removed. This was deprecated in the Kilo release. * [blueprint removed-as-of-mitaka (https://blueprints.launchpad.net/keystone/+spec/removed-as-of- mitaka)] The LDAP backend for Role has been removed. This was deprecated in the Kilo release. * [blueprint removed-as-of-mitaka (https://blueprints.launchpad.net/keystone/+spec/removed-as-of- mitaka)] Removed Revoke KVS backend ("keystone.revoke.backends.kvs.Revoke"). This was deprecated in the Juno release. Changes in keystone 9.0.0.0rc2..9.0.0 ------------------------------------- 3e5fca0 Update federated user display name with shadow_users_api Diffstat (except docs and test files) ------------------------------------- keystone/identity/core.py | 4 ++-- 2 files changed, 30 insertions(+), 2 deletions(-)

1 0

[release][heat] heat 6.0.0 release (mitaka)
by no-reply＠openstack.org 06 Apr '16

06 Apr '16

We are glad to announce the release of: heat 6.0.0: OpenStack Orchestration This release is part of the mitaka release series. For more details, please see below. 6.0.0 ^^^^^ New Features ************ * Added new functionality for showing and listing stack outputs without resolving all outputs during stack initialisation. * Added new API calls for showing and listing stack outputs "/stack/outputs" and "/stack/outputs/output_key". * Added using of new API in python-heatclient for "output_show" and "output_list". Now, if version of Heat API is 1.19 or above, Heat client will use API calls "output_show" and "output_list" instead of parsing of stack get response. If version of Heat API is lower than 1.19, outputs resolve in Heat client as well as before. * Add new "OS::Barbican::GenericContainer" resource for storing arbitrary barbican secrets. * Add new "OS::Barbican::RSAContainer" resource for storing RSA public keys, private keys, and private key pass phrases. * A new "OS::Barbican::CertificateContainer" resource for storing the secrets that are relevant to certificates. * OS::Nova::HostAggregate resource plugin is added to support host aggregate, which is provided by nova "aggregates" API extension. * nova.host constraint is added to support to validate host attribute which is provided by nova "host" API extension. * OS::Neutron::QoSPolicy resource plugin is added to support QoS policy, which is provided by neutron "qos" API extension. * OS::Neutron::QoSBandwidthLimitRule resource plugin is added to support neutron QoS bandwidth limit rule, which is provided by neutron "qos" API extension. * Resources "OS::Neutron::Port" and "OS::Neutron::Net" now support "qos_policy" optional property, that will associate with QoS policy to offer different service levels based on the policy rules. * OS::Neutron::RBACPolicy resource plugin is added to support RBAC policy, which is used to manage RBAC policy in Neutron. This resource creates and manages Neutron RBAC policy, which allows to share Neutron networks to subsets of tenants. * Added a new "event-sinks" element to the environment which allows specifying a target where events from the stack are sent. It supports the "zaqar-queue" element for now. * Adds a new "immutable" boolean field to the parameters section in a HOT template. This gives template authors the ability to mark template parameters as immutable to restrict updating parameters which have destructive effects on the application. A value of True results in the engine rejecting stack-updates that include changes to that parameter. When not specified in the template, "immutable" defaults to False to ensure backwards compatibility with old templates. * A new "OS::Keystone::Region" resource that helps in managing the lifecycle of keystone region. * A new "OS::Neutron:AddressScope" resource that helps in managing the lifecycle of neutron address scope. Availability of this resource depends on availability of neutron "address-scope" API extension. This resource can be associated with multiple subnet pools in a one- to-many relationship. The subnet pools under an address scope must not overlap. * New resources for Neutron Load Balancer version 2. These are unique for version 2 and do not support or mix with existing version 1 resources. * New resource "OS::Neutron::LBaaS::LoadBalancer" is added to create and manage Load Balancers which allow traffic to be directed between servers. * New resource "OS::Neutron::LBaaS::Listener" is added to create and manage Listeners which represent a listening endpoint for the Load Balancer. * New resource "OS::Neutron::LBaaS::Pool" is added to create and manage Pools which represent a group of nodes. Pools define the subnet where nodes reside, the balancing algorithm, and the nodes themselves. * New resource "OS::Neutron::LBaaS::PoolMember" is added to create and manage Pool members which represent a single backend node. * New resource "OS::Neutron::LBaaS::HealthMonitor" is added to create and manage Health Monitors which watch status of the Load Balanced servers. * A stack can be searched for resources based on their name, status, type, action, id and physcial_resource_id. And this feature is enabled both in REST API and CLI. For more details, please refer orchestration API document and heat CLI user guide. * Adds a new feature to restrict update or replace of a resource when a stack is being updated. Template authors can set "restricted_actions" in the "resources" section of "resource_registry" in an environment file to restrict update or replace. * New resource "OS::Senlin::Cluster" is added to create a cluster in senlin. A cluster is a group of homogeneous nodes. * New resource "OS::Senlin::Node" is added to create a node in senlin. Node represents a physical object exposed by other OpenStack services. * New resource "OS::Senlin::Receiver" is added to create a receiver in senlin. Receiver can be used to hook the engine to some external event/alarm sources. * New resource "OS::Senlin::Profile" is added to create a profile in senlin. Profile is a module used for creating nodes, it's the definition of a node. * New resource "OS::Senlin::Policy" is added to create a policy in senlin. Policy is a set of rules that can be checked and/or enforced when an Action is performed on a Cluster. * The OS::Nova::Server now supports a new property user_data_update_policy, which may be set to either 'REPLACE' (default) or 'IGNORE' if you wish to allow user_data updates to be ignored on stack update. This is useful when managing a group of servers where changed user_data should apply to new servers without replacing existing servers. * Multiple environment files may be passed to the server in the files dictionary along with an ordered list of the environment file names. The server will generate the stack's environment from the provided files rather than requiring the client to merge the environments together. This is optional; the existing interface to pass in the already resolved environment is still present. * A new "OS::Neutron:SubnetPool" resource that helps in managing the lifecycle of neutron subnet pool. Availability of this resource depends on availability of neutron "subnet_allocation" API extension. * Resource "OS::neutron::Subnet" now supports "subnetpool" optional property, that will automate the allocation of CIDR for the subnet from the specified subnet pool. * Template validation is improved to ignore the given set of error codes. For example, heat will report template as invalid one, if it does not find any required OpenStack services in the cloud deployment and while authoring the template, user might wants to avoid such scenarios, so that (s)he could create valid template without bothering about run-time environments. Please refer the API documentation of validate template for more details. Upgrade Notes ************* * If upgrading with pre-icehouse stacks which contain resources that create users (such as OS::Nova::Server, OS::Heat::SoftwareDeployment, and OS::Heat::WaitConditionHandle), it is possible that the users will not be removed upon stack deletion due to the removal of a legacy fallback code path. In such a situation, these users will require manual removal. Changes in heat 6.0.0.0rc2..6.0.0 --------------------------------- bea576f Sync integration tests requirements 950505d Revert "Check RBAC policy for nested stacks" 184b09a Imported Translations from Zanata 0c407b8 Add translation rule to delete ssh auth key from Magnum baymodel Diffstat (except docs and test files) ------------------------------------- heat/common/policy.py | 8 +- heat/engine/resources/openstack/magnum/baymodel.py | 11 + heat/engine/stack.py | 2 - heat/locale/de/LC_MESSAGES/heat.po | 21 +- heat/locale/fr/LC_MESSAGES/heat.po | 9 +- heat/locale/it/LC_MESSAGES/heat.po | 9 +- heat/locale/ja/LC_MESSAGES/heat.po | 173 +++++++------- heat/locale/ko_KR/LC_MESSAGES/heat-log-error.po | 251 +++++++++++++++++++++ heat/locale/ko_KR/LC_MESSAGES/heat-log-warning.po | 10 +- .../functional/test_conditional_exposure.py | 21 -- 11 files changed, 396 insertions(+), 147 deletions(-)

1 0

[release][glance] glance 12.0.0 release (mitaka)
by no-reply＠openstack.org 06 Apr '16

06 Apr '16

We are happy to announce the release of: glance 12.0.0: OpenStack Image Service This release is part of the mitaka release series. For more details, please see below. 12.0.0 ^^^^^^ New Features ************ * Implement the ability to filter images by the properties *id*, *name*, *status*,`container_format`, *disk_format* using the 'in' operator between the values. Following the pattern of existing filters, new filters are specified as query parameters using the field to filter as the key and the filter criteria as the value in the parameter. Filtering based on the principle of full compliance with the template, for example 'name = in:deb' does not match 'debian'. Changes apply exclusively to the API v2 Image entity listings An example of an acceptance criteria using the 'in' operator for name ?name=in:name1,name2,name3. These filters were added using syntax that conforms to the latest guidelines from the OpenStack API Working Group. * Implemented re-authentication with trusts when updating image status in registry after image upload. When long-running image upload takes some a lot of time (more than token expiration time) glance uses trusts to receive new token and update image status in registry. It allows users to upload big size images without increasing token expiration time. Upgrade Notes ************* * Metadata definitions previously associated with OS::Nova::Instance have been changed to be associated with OS::Nova::Server in order to align with Heat and Searchlight. You may either upgrade them using glance-manage db load_metadefs [path] [merge] [prefer_new] or glance-manage db upgrade 44. * The task API is being deprecated and it has been made admin only. If deployers of Glance would like to have this API as a public one, it is necessary to change the *policy.json* file and remove *role:admin* from every *task* related field. Deprecation Notes ***************** * The use_user_token, admin_user, admin_password, admin_tenant_name, auth_url, auth_strategy and auth_region options in the [DEFAULT] configuration section in glance-api.conf are deprecated, and will be removed in the O release. See https://wiki.openstack.org/wiki/OSSN/OSSN-0060 * The task API was added to allow users for uploading images asynchronously and for deployers to have more control in the upload process. Unfortunately, this API has not worked the way it was expected to. Therefore, the task API has entered a deprecation period and it is meant to be replaced by the new import API. This change makes the task API admin only by default so that it is not accidentally deployed as a public API. * OSprofiler support requires passing of trace information between various OpenStack services. This information is signed by one of HMAC keys, which we historically defined in glance-api-paste.ini and glance-registry-paste.ini files (together with enabled option, that in fact was duplicated in the corresponding configuration files). OSprofiler 0.3.1 and higher supports passing this information via configuration files, therefore it's recommended to modify the "[filter:osprofiler]" section in *-paste.ini to look like "paste.filter_factor = osprofiler.web:WsgiMiddleware.factory" and set the "hmac_keys" option in the glance-*.conf files. Security Issues *************** * Fixing bug 1525915; image might be transitioning from active to queued by regular user by removing last location of image (or replacing locations with empty list). This allows user to re-upload data to the image breaking Glance's promise of image data immutability. From now on, last location cannot be removed and locations cannot be replaced with empty list. Bug Fixes ********* * Metadata definitions previously associated with OS::Nova::Instance have been changed to be associated with OS::Nova::Server in order to align with Heat and Searchlight. Changes in glance 12.0.0.0rc1..12.0.0 ------------------------------------- 02ef2ab Imported Translations from Zanata 768f168 Imported Translations from Zanata 1cb2bda Imported Translations from Zanata ab05625 Imported Translations from Zanata d4aaa1b Imported Translations from Zanata 869e551 Imported Translations from Zanata 040d5fa Update .gitreview for stable/mitaka Diffstat (except docs and test files) ------------------------------------- .gitreview | 1 + glance/locale/de/LC_MESSAGES/glance.po | 461 ++++++++-------- glance/locale/es/LC_MESSAGES/glance.po | 345 +++++++++++- glance/locale/fr/LC_MESSAGES/glance.po | 29 +- glance/locale/it/LC_MESSAGES/glance.po | 353 +++++++++++- glance/locale/ja/LC_MESSAGES/glance.po | 595 +++++++++++++++++++-- .../locale/ko_KR/LC_MESSAGES/glance-log-error.po | 376 +++++++++++++ glance/locale/ko_KR/LC_MESSAGES/glance-log-info.po | 315 +++++++++++ .../locale/ko_KR/LC_MESSAGES/glance-log-warning.po | 274 ++++++++++ glance/locale/ko_KR/LC_MESSAGES/glance.po | 368 ++++++++++++- glance/locale/pt_BR/LC_MESSAGES/glance.po | 351 +++++++++++- 11 files changed, 3165 insertions(+), 303 deletions(-)

1 0

[release][horizon] horizon 9.0.0 release (mitaka)
by no-reply＠openstack.org 06 Apr '16

06 Apr '16

We are amped to announce the release of: horizon 9.0.0: OpenStack Dashboard This release is part of the mitaka release series. For more details, please see below. 9.0.0 ^^^^^ Cinder defines storage size in gibibytes (GiB), which is inconsistent with Horizon panels that show/request storage size in gigabytes (GB). New Features ************ * Added the Metadata tab to the new Launch Instance workflow to allow adding key-value metadata to an instance at launch. This includes any properties from the OS::Nova::Server namespace of the glance metadata definitions. * Allows to attach ports during instance launch <https://blueprints.launchpad.net/horizon/+spec/allow-launching- ports> * [blueprint angular-performance-strict-di (https://blueprints.launchpad.net/horizon/+spec/angular-performance- strict-di)] This blueprint enforces strict dependency injection in AngularJS code, for improvements to minification and thus performance. * Move OpenStack Dashboard Swift panel rendering logic to client- side using AngularJS for significant usability improvements. * Added the Developer dashboard plugin to contrib. This runs when "DEBUG=True", and adds tooling to the UI to aid in development. * Added the Bootstrap Theme Preview panel to the Developer dashboard. This panel contains a list of Bootstrap components with source code, so that developers can see examples of how to structure this code and the effects their theme will have upon it. * Added the Django template cached loader, so templates are stored in memory. See https://docs.djangoproject.com/en/1.8/ref/templates/api /#django.template.loaders.cached.Loader * [blueprint cinder-consistency-groups (https://blueprints.launchpad.net/horizon/+spec/cinder-consistency- groups)] This feature adds a new Consistency Groups tab to the Project Volumes panel. Consistency Groups (GG) contain existing volumes, and allow the user to perform actions on the volumes in one step. Actions include: create a CG, manage volumes associated with the CG, update a CG, and delete a CGs. Note that a CG can not be deleted if it contains any volumes. * Instance metadata can be updated (https://blueprints.launchpad.net/horizon/+spec/edit-server- metadata) * Made the Angular Launch Instance workflow the default in Horizon. * [blueprint integrate-magic-search (https://blueprints.launchpad.net/horizon/+spec/integrate-magic- search)] Magic Search was an external dependency that was being heavily modified or overwritten in sections, so the used parts of code base have been moved into Horizon. * [blueprint integration-tests-hardening (https://blueprints.launchpad.net/horizon/+spec/integration-tests- hardening)] This blueprint reduced failures in the integration tests caused by structure or styling changes, by making them less dependent on aspects of page structure, such as ordering or CSS classes. * Added the Update Encryption action for encrypted volume types. * [blueprint keystone-federation-protocol-mapping (https://blueprints.launchpad.net/horizon/+spec/keystone-federation- protocol-mapping)] This blueprint provides CRUD interaction for identity provider protocols. * Allow to override settings from local_settings.py with file snippets dropped into local_settings.d/ directory. * [blueprint pagination-for-flavor (https://blueprints.launchpad.net/horizon/+spec/pagination-for- flavor)] Added forward and backward pagination to the Flavors panel * Added support for managing domains and projects when using Keystone v3. Horizon now maintains a domain scoped token for users who have a role on a domain, a project scoped token for users who have a role on a project, or both a domain scoped token and project scoped token for users who have roles on both. * Domain management supports the following use cases: * Cloud Admin - View and manage identity resources across domains * Domain Admin - View and manage identity resources in the domain logged in * User - View identity project in the domain logged in * Horizon can be configured to run with multiple themes available at run time. A new selection widget is available through the user menu. It uses a browser cookie to allow users to toggle between the configured themes. By default, Horizon is configured with the two themes available, 'default' and 'material'. * Allow external plugins to contribute translations to the Javascript message catalog. * Selenium tests may now be exercised using the headless PhantomJS driver. * Added the angular extensible service which allows angular horizon elements such as workflows, tables, actions, and forms to be extended dynamically by adding, removing, or replacing items. The extensible service is applied to every workflow created using the horizon workflow service. This includes the angular Launch Instance workflow. * All Volume related panels in Horizon that previously used the term "GB" and "gigabyte" have been replaced with 'GiB' and 'gibibyte'. * [blueprint keystone-federation-idp (https://blueprints.launchpad.net/horizon/+spec/keystone-federation- idp)] Add support for managing keystone identity provider. To enable the panel, set "OPENSTACK_KEYSTONE_FEDERATION_MANAGEMENT" in the local_settting.py to True. * [blueprint keystone-federation-mapping (https://blueprints.launchpad.net/horizon/+spec/keystone-federation- mapping)] Add basic support for managing keystone federation mapping. * Added the LAUNCH_INSTANCE_DEFAULTS setting which allows specifying default values for the Launch Instance workflow. Initially only the Configuration Drive property is supported. * [blueprint message-of-the-day (https://blueprints.launchpad.net/horizon/+spec/message-of-the-day) Message of the day can now be configured in horizon, this will be displayed to the user whenever they login. To enable the feature set "MESSAGES_PATH" in the local_settting.py to the directory where message files are located. The message file must have a .json file extension. * Added policy support to the angular workflow service so each step in a workflow can specify a policy check that must pass in order for the step to be displayed. Known Issues ************ * There are also some Nova related panels (e.g. "Instances") that reference storage size in "GB". These panels will be addressed in subsequent patches. Upgrade Notes ************* * All AngularJS code must use explicit dependency injection. See https://docs.angularjs.org/guide/di#using-strict-dependency- injection * Custom template tags must have a thread-safe Node implementation to work with the the cached loader. See https://docs.djangoproject.com/en/1.8/howto/custom-template-tags /#template-tag-thread-safety * Horizon no longer requires Magic Search as an external dependency. * The Sahara based content has been removed from the Horizon source tree and is now a separate plugin. To continue managing Sahara in Horizon, installing the sahara-dashboard plugin on the Horizon server is required. * The Trove based content has been removed from the Horizon source tree and is now a separate plugin. To continue managing Trove in Horizon, installing the trove-dashboard plugin on the Horizon server is required. * The main engine managing integration with oslo.policy has been moved to django_openstack_auth. The configuration is still managed in Horizon, but the setting for "POLICY_CHECK_FUNCTION" now uses "openstack_auth.policy.check" rather than "openstack_dashboard.policy.check". Current behavior will remain consistent. Deprecation Notes ***************** * The Python Swift panel has been deprecated and no longer displays by default. To use the old interface edit "enabled/_1920_project_containers_panel.py" to change "swift_panel" to "'legacy'". * The Python Launch Instance workflow has been deprecated and no longer displays by default. * The 'default_ipv4_subnet_pool_label' and 'default_ipv6_subnet_pool_label' options has been deprecated and will be removed in the Newton release. Starting with Mitaka you can create one default subnet pool per address family through the Neutron API. These subnet pools will automatically show up in the subnet pool list using the name of the pool as label. * The setting CUSTOM_THEME_PATH is now deprecated. * The setting DEFAULT_THEME_PATH is now deprecated. * The 'webroot' theme has been removed. Security Issues *************** * Policies associated with Consistency Groups exist in the Cinder policy file, and by default, all actions are disabled. Bug Fixes ********* * Provided the ability for plugins to contribute translations to the JavaScript message catalog. Previously the horizon and openstack_dahboard applications were hardcoded. * blueprint gb-to-gib-conversion <https://blueprints.launchpad.net/horizon/+spec/gb-to-gib- conversion/> * Several fixes have been made to the hzTable controller. The list below outline these changes. See inline documentation for usage details. * Properties are now bound to the controller instead of the scope. * Emit the *hzTable:clearSelected* event to clear table row selections. * The property *selections* tracks the checkbox selection state of each row. * The property *selected* is now a list of selected rows. * The property *numSelected* has been removed, use *selected.length* instead. * The *select* method has been renamed to to *toggleSelect*. * The 'webroot' theme was providing an example of how to set the webroot value through SCSS for accessing needed static URL prefixes for assets like font paths. This value is now retrieved directly from the Django settings and is available directly in the SCSS namespace via $static_url. Other Notes *********** * Current limitations on managing identity resources with Keystone v3: * Does not support role assignments across domains, such as giving a user in domain1 access to domain2. * Does not support project admins managing Keystone projects. * Does not support hierarchical project management. Changes in horizon 9.0.0.0rc1..9.0.0 ------------------------------------ 3f4eeaa Imported Translations from Zanata 10e6bf5 Fixing updating user with no default project dd4d1fb Imported Translations from Zanata 19b6a65 Fix opening multiple Launch Instance during jQuery table polling 8ad7d1f Imported Translations from Zanata 2694d45 Imported Translations from Zanata 2143bb6 Imported Translations from Zanata 7f1a831 Imported Translations from Zanata 184b67d Imported Translations from Zanata f1036b4 Imported Translations from Zanata 7c71e21 Imported Translations from Zanata 5d0391f Update .gitreview for stable/mitaka Diffstat (except docs and test files) ------------------------------------- .gitreview | 1 + horizon/locale/en_AU/LC_MESSAGES/django.po | 108 +- horizon/locale/en_AU/LC_MESSAGES/djangojs.po | 84 +- horizon/locale/fr/LC_MESSAGES/django.po | 28 +- horizon/locale/it/LC_MESSAGES/django.po | 110 +- horizon/locale/it/LC_MESSAGES/djangojs.po | 85 +- horizon/locale/ja/LC_MESSAGES/djangojs.po | 8 +- horizon/locale/ko_KR/LC_MESSAGES/django.po | 29 +- horizon/locale/ko_KR/LC_MESSAGES/djangojs.po | 17 +- horizon/locale/pt_BR/LC_MESSAGES/django.po | 10 +- horizon/locale/ru/LC_MESSAGES/django.po | 37 +- horizon/locale/tr_TR/LC_MESSAGES/django.po | 20 +- horizon/locale/tr_TR/LC_MESSAGES/djangojs.po | 15 +- horizon/locale/zh_CN/LC_MESSAGES/django.po | 55 +- horizon/locale/zh_CN/LC_MESSAGES/djangojs.po | 19 +- horizon/locale/zh_TW/LC_MESSAGES/django.po | 66 +- horizon/locale/zh_TW/LC_MESSAGES/djangojs.po | 46 +- horizon/static/framework/framework.module.js | 12 +- horizon/static/horizon/js/horizon.tables.js | 4 +- horizon/static/horizon/js/horizon.tabs.js | 2 +- .../dashboards/identity/users/forms.py | 8 +- .../locale/de/LC_MESSAGES/django.po | 219 ++- .../locale/de/LC_MESSAGES/djangojs.po | 134 +- openstack_dashboard/locale/django.pot | 397 +++- openstack_dashboard/locale/djangojs.pot | 224 ++- .../locale/en_AU/LC_MESSAGES/django.po | 1198 +++++++++++- .../locale/en_AU/LC_MESSAGES/djangojs.po | 1491 ++++++++++++++- .../locale/fr/LC_MESSAGES/django.po | 28 +- .../locale/fr/LC_MESSAGES/djangojs.po | 81 +- .../locale/it/LC_MESSAGES/django.po | 1245 ++++++++++++- .../locale/it/LC_MESSAGES/djangojs.po | 1519 ++++++++++++++- .../locale/ja/LC_MESSAGES/django.po | 268 ++- .../locale/ja/LC_MESSAGES/djangojs.po | 168 +- .../locale/ko_KR/LC_MESSAGES/django.po | 504 +++-- .../locale/ko_KR/LC_MESSAGES/djangojs.po | 296 ++- .../locale/pt_BR/LC_MESSAGES/django.po | 278 ++- .../locale/pt_BR/LC_MESSAGES/djangojs.po | 289 ++- .../locale/ru/LC_MESSAGES/django.po | 838 ++++++++- .../locale/ru/LC_MESSAGES/djangojs.po | 1053 ++++++++++- .../locale/zh_CN/LC_MESSAGES/django.po | 1959 +++++++++++--------- .../locale/zh_CN/LC_MESSAGES/djangojs.po | 248 ++- .../locale/zh_TW/LC_MESSAGES/django.po | 1038 ++++++++++- .../locale/zh_TW/LC_MESSAGES/djangojs.po | 1422 +++++++++++++- 44 files changed, 14134 insertions(+), 1577 deletions(-)

1 0

[release][manila] manila 2.0.0 release (mitaka)
by no-reply＠openstack.org 06 Apr '16

06 Apr '16

We are eager to announce the release of: manila 2.0.0: Shared Storage for OpenStack This release is part of the mitaka release series. For more details, please see below. 2.0.0 ^^^^^ New Features ************ * Added APIs for listing export locations per share and share instances. * Added driver for Tegile IntelliFlash arrays. * Manage and unmanage snapshot. * Shares can be replicated. Replicas can be added, listed, queried for detail, promoted to be 'active' or removed. Deprecation Notes ***************** * Removed 'export_location' and 'export_locations' attributes from share and share instance views starting with microversion '2.9'. Changes in manila 2.0.0.0b3..2.0.0 ---------------------------------- 296c995 Fix call of clients in post_test_hook.sh 7bf4f02 Add tests to ensure snapshots across replicas 430a18b NetApp cDOT: Handle replicated snapshots 94e04c8 Data Replication: Ensure Snapshots across replicas 70f59f7 Fix update_access concurrency issue 2da94bb Fix manage API ignoring type extra specs b161889 Make ZFSonLinux driver handle snapshots of replicated shares properly 7fc492e Fix keystone v3 issues for all clients 9a9bc9c Fix for incorrect LVMMixin exception message e663275 NetApp cDOT: Fix status updates for replicas a4fa859 NetApp cDOT: Raise ShareResourceNotFound in update_access 7bf936b Fix generic and LVM driver access rules for CIDRs c8bce99 Fix report of ZFSonLinux driver capabilities b14566a Fix the scheduler choose a disable share service ffcef13 Fix typos 806f8ba Fix error logged for wrong HPE 3par client 35e67cd 3PAR remove file tree on delete when using nested shares bb9a290 HDS-HNAS: Fix exception in update_access not found 5dfbef4 Revert "LXC/LXD driver" 46eea39 Fix Hitachi HNAS driver version bca18c6 service instance: also recognize instance name 42eccd2 Fix update of access rules in ZFSonLinux driver 3ef988e Check share-network in 'share create' API ec5d9ca glusterfs volume layout: take care of deletion of DOA shares 51d9649 Fix delete when share not found in update_access 02a9a2c Remove default values for update_access() 4a22901 NetApp cDOT driver should not split clones fe6bd97 Fix handling of share server details after error b003e7a HDS-HNAS: fixed exception when export not found e49324f Fix lock decorator usage for LVM and Generic drivers fe0859e Fix HNAS snapshot creation on deleted shares 88c922c Move iso8601 from requirements to test-requirements 8b6cedf Fix typos 8aa37de glusterfs.common: GlusterManager.gluster_call error report fix 6d67c26 glusterfs.GlusterNFSVolHelper: remove __init__ 3c56db6 Add tempest tests for Share Replication 04ce4a4 register the config generator default hook with the right name a7f0fe6 Windows driver: fix share access actions ce6924a Collapse common os_region_name option 0616fcb Disallow scheduling multiple replicas on a given pool ce051b3 update quota of origin user on share extend/shrink 8d3e72f Update quota of proper user on resource delete d2bebca Fix Share Migration access rule mapping 37c6e31 Fix unstable DB migration tests b8e9ae8 Fix Share Migration KeyError on dict.pop 9c42513 NetApp cDOT APIs may get too little data fba9f60 HNAS: Enable no_root_squash option when allowing access to a share e986699 Fix HNAS driver crash with unmounted filesystems e1d696c Fix compatibility with Tempest 2358f91 Set proper image name for tempest fad7709 Remove nsenter dependency f3b8026 Fix ZFSonLinux driver share replica SSHing c357ac5 Fix ZFSonLinux access rules for CIDRs adb6fa1 Fix HNAS driver thin_provisioning support 466a19f Fix pylxd hard dependencies 7da4bd5 Squash consequent DB calls in create_share_instance 9f0bd96 Fix slow unit test 7d3fc0e Run ZfsOnLinux gate tests with SSH enabled bb608e9 Fix status update for replicas ced9d38 Set TCP keepalive options fd449f1 Fix manila devstack plugin for keystone v3 usage 71f8d0f Add /usr/local/{sbin,bin} to rootwrap exec_dirs a243a43 Updated from global requirements bfea3f4 Use official location for service image 1279dd9 Allow devstack plugin to work without Cinder b0c510e Download service image only when needed 7f85400 glusterManager instantiation regexp validation 75d85aa Moved CORS middleware configuration into oslo-config-generator 6a0bd8c Remove unintended exposure of private attribute 7133cb8 glusterfs/common: don't suppress vol set errors 08e3e61 Fix scenario tests Diffstat (except docs and test files) ------------------------------------- contrib/ci/post_test_hook.sh | 58 +- contrib/ci/pre_test_hook.sh | 22 +- devstack/files/debs/manila | 1 + devstack/files/rpms-suse/manila | 1 + devstack/files/rpms/manila | 1 + devstack/plugin.sh | 174 +--- devstack/settings | 20 +- .../share_back_ends_feature_support_mapping.rst | 6 - etc/manila/api-paste.ini | 3 - etc/manila/rootwrap.conf | 2 +- etc/manila/rootwrap.d/share.filters | 41 +- manila/api/v1/share_networks.py | 6 +- manila/api/v1/shares.py | 26 +- manila/api/views/share_snapshots.py | 2 +- manila/cmd/all.py | 3 +- manila/common/client_auth.py | 113 +++ manila/common/config.py | 34 +- manila/common/constants.py | 7 + manila/compute/nova.py | 170 ++-- manila/data/manager.py | 2 +- manila/db/api.py | 22 +- manila/db/sqlalchemy/api.py | 123 ++- manila/db/sqlalchemy/models.py | 77 +- manila/exception.py | 10 +- manila/network/neutron/api.py | 120 ++- manila/network/neutron/neutron_network_plugin.py | 14 +- manila/opts.py | 6 +- manila/quota.py | 20 +- manila/scheduler/filters/share_replication.py | 12 +- manila/scheduler/host_manager.py | 12 +- manila/scheduler/manager.py | 63 +- manila/scheduler/rpcapi.py | 15 +- manila/share/access.py | 51 +- manila/share/api.py | 265 ++++-- manila/share/driver.py | 398 ++++++++- manila/share/drivers/cephfs/cephfs_native.py | 4 +- manila/share/drivers/ganesha/__init__.py | 4 +- manila/share/drivers/ganesha/manager.py | 4 +- manila/share/drivers/generic.py | 12 +- manila/share/drivers/glusterfs/__init__.py | 5 - manila/share/drivers/glusterfs/common.py | 30 +- manila/share/drivers/glusterfs/glusterfs_native.py | 2 +- manila/share/drivers/glusterfs/layout_volume.py | 17 +- manila/share/drivers/helpers.py | 58 +- manila/share/drivers/hitachi/hds_hnas.py | 39 +- manila/share/drivers/hitachi/ssh.py | 33 +- manila/share/drivers/hpe/hpe_3par_driver.py | 34 +- manila/share/drivers/hpe/hpe_3par_mediator.py | 170 +++- manila/share/drivers/huawei/huawei_nas.py | 4 +- manila/share/drivers/huawei/v3/connection.py | 4 +- manila/share/drivers/lvm.py | 15 +- manila/share/drivers/lxd.py | 754 ---------------- .../share/drivers/netapp/dataontap/client/api.py | 8 +- .../netapp/dataontap/client/client_cmode.py | 318 ++++++- .../netapp/dataontap/cluster_mode/drv_multi_svm.py | 27 +- .../dataontap/cluster_mode/drv_single_svm.py | 42 +- .../netapp/dataontap/cluster_mode/lib_base.py | 257 ++++-- .../netapp/dataontap/cluster_mode/lib_multi_svm.py | 1 + .../dataontap/cluster_mode/lib_single_svm.py | 1 + manila/share/drivers/quobyte/quobyte.py | 12 +- manila/share/drivers/service_instance.py | 4 +- manila/share/drivers/tegile/tegile.py | 4 +- manila/share/drivers/windows/windows_smb_driver.py | 21 + manila/share/drivers/zfsonlinux/driver.py | 387 +++++++-- manila/share/drivers/zfsonlinux/utils.py | 25 +- manila/share/manager.py | 595 +++++++++++-- manila/share/migration.py | 34 +- manila/share/rpcapi.py | 27 +- manila/test.py | 4 +- .../scheduler/filters/test_share_replication.py | 20 +- .../share/drivers/glusterfs/test_layout_volume.py | 18 + .../share/drivers/hpe/test_hpe_3par_constants.py | 5 + .../share/drivers/hpe/test_hpe_3par_driver.py | 38 + .../share/drivers/hpe/test_hpe_3par_mediator.py | 350 +++++++- .../share/drivers/netapp/dataontap/client/fakes.py | 243 ++++++ .../drivers/netapp/dataontap/client/test_api.py | 84 ++ .../netapp/dataontap/client/test_client_cmode.py | 588 ++++++++++--- .../netapp/dataontap/cluster_mode/test_lib_base.py | 957 ++++++++++++++++++--- .../dataontap/cluster_mode/test_lib_multi_svm.py | 2 + .../dataontap/cluster_mode/test_lib_single_svm.py | 1 + .../drivers/windows/test_windows_smb_driver.py | 48 +- manila/utils.py | 16 - manila/volume/cinder.py | 153 ++-- manila/wsgi.py | 16 +- .../services/share/v2/json/shares_client.py | 174 ++++ requirements.txt | 5 +- setup.cfg | 2 + test-requirements.txt | 1 + 145 files changed, 9392 insertions(+), 3433 deletions(-) Requirements updates -------------------- diff --git a/requirements.txt b/requirements.txt index a6297d2..0a98c3e 100644 --- a/requirements.txt +++ b/requirements.txt @@ -12 +11,0 @@ greenlet>=0.3.2 # MIT -iso8601>=0.1.9 # MIT @@ -31,2 +30,2 @@ PasteDeploy>=1.5.0 # MIT -pylxd>=0.19.0 # Apache-2.0 -python-neutronclient>=2.6.0 # Apache-2.0 +python-neutronclient!=4.1.0,>=2.6.0 # Apache-2.0 +keystoneauth1>=2.1.0 # Apache-2.0 diff --git a/test-requirements.txt b/test-requirements.txt index f6d70d8..46306c9 100644 --- a/test-requirements.txt +++ b/test-requirements.txt @@ -12,0 +13 @@ mock>=1.2 # BSD +iso8601>=0.1.9 # MIT

1 0

[release][telemetry] ceilometer 6.0.0 release (mitaka)
by no-reply＠openstack.org 06 Apr '16

06 Apr '16

We are jubilant to announce the release of: ceilometer 6.0.0: OpenStack Telemetry This release is part of the mitaka release series. For more details, please see below. 6.0.0 ^^^^^ New Features ************ * Add support for batch processing of messages from queue. This will allow the collector and notification agent to grab multiple messages per thread to enable more efficient processing. * To minimise load on Nova API, an additional configuration option was added to control discovery interval vs metric polling interval. If resource_update_interval option is configured in compute section, the compute agent will discover new instances based on defined interval. The agent will continue to poll the discovered instances at the interval defined by pipeline. * [bug 1480333 (https://bugs.launchpad.net/ceilometer/+bug/1480333) Support ability to configure collector to capture events or meters mutally exclusively, rather than capturing both always. * Support for CORS is added. More information can be found [here (http://specs.openstack.org/openstack/openstack-specs/specs/cors- support.html)] * Support resource caching in Gnocchi dispatcher to improve write performance to avoid additional queries. * Gnocchi dispatcher now uses client rather than direct http requests * [bug 1518338 (https://bugs.launchpad.net/ceilometer/+bug/1518338) Add support for storing SNMP metrics in Gnocchi.This functionality requires Gnocchi v2.1.0 to be installed. * Add support for Keystone v3 authentication * Ceilometer alarms code is now fully removed from code base. Equivalent functionality is handled by Aodh. * Support for CADF-only payload in HTTP dispatcher is dropped as audit middleware in pyCADF was dropped in Kilo cycle. * Remove eventlet from Ceilometer in favour of threaded approach * RPC collector support is dropped. The queue-based notifier publisher and collector was added as the recommended alternative as of Icehouse cycle. * Support for polling Neutron's LBaaS v2 API was added as v1 API in Neutron is deprecated. The same metrics are available between v1 and v2. * [bug 1513731 (https://bugs.launchpad.net/ceilometer/+bug/1513731) Add support for hardware cpu_util in snmp.yaml * [bug 1506959 (https://bugs.launchpad.net/ceilometer/+bug/1506959) Add support to query unique set of meter names rather than meters associated with each resource. The list is available by adding unique=True option to request. Known Issues ************ * Neutron API is not designed to be polled against. When polling against Neutron is enabled, Ceilometer's polling agents may generage a significant load against the Neutron API. It is recommended that a dedicated API be enabled for polling while Neutron's API is improved to handle polling. Upgrade Notes ************* * The options >>`<<requeue_event_on_dispatcher_error' and >>`<<requeue_sample_on_dispatcher_error' have been enabled and removed. <SYSTEM MESSAGE: <string>:47: (WARNING/2) Inline interpreted text or phrase reference start-string without end-string.> <SYSTEM MESSAGE: <string>:47: (WARNING/2) Inline interpreted text or phrase reference start-string without end-string.> * batch_size and batch_timeout configuration options are added to both [notification] and [collector] sections of configuration. The batch_size controls the number of messages to grab before processing. Similarly, the batch_timeout defines the wait time before processing. * The api-paste.ini file can be modified to include or exclude the CORs middleware. Additional configurations can be made to middleware as well. * gnocchiclient library is now a requirement if using ceilometer+gnocchi. * gnocchi_resources.yaml in Ceilometer should be updated. * To utilize the new policy support. The policy.json file should be updated accordingly. The pre-existing policy.json file will continue to function as it does if policy changes are not required. * Run db-sync to add new indices. * audit middleware in keystonemiddleware library should be used for similar support. * Pipeline.yaml files for agents should be updated to notifier:// or udp:// publishers. The rpc:// publisher is no longer supported. * By default, Ceilometer will poll the v2 API. To poll legacy v1 API, add neutron_lbaas_version=v1 option to configuration file. Critical Issues *************** * The previous configuration options default for >>`<<requeue_sample_on_dispatcher_error' and >>`<<requeue_event_on_dispatcher_error' allowed to lose data very easily: if the dispatcher failed to send data to the backend (e.g. Gnocchi is down), then the dispatcher raised and the data were lost forever. This was completely unacceptable, and nobody should be able to configure Ceilometer in that way." <SYSTEM MESSAGE: <string>:71: (WARNING/2) Inline interpreted text or phrase reference start-string without end-string.> <SYSTEM MESSAGE: <string>:71: (WARNING/2) Inline interpreted text or phrase reference start-string without end-string.> * [bug 1533787 (https://bugs.launchpad.net/ceilometer/+bug/1533787) Fix an issue where agents are not properly getting registered to group when multiple notification agents are deployed. This can result in bad transformation as the agents are not coordinated. It is still recommended to set heartbeat_timeout_threshold = 0 in [oslo_messaging_rabbit] section when deploying multiple agents. * [bug 1519767 (https://bugs.launchpad.net/ceilometer/+bug/1519767) fnmatch functionality in python <= 2.7.9 is not threadsafe. this issue and its potential race conditions are now patched. Bug Fixes ********* * [bug 1531626 (https://bugs.launchpad.net/ceilometer/+bug/1531626) Ensure aggregator transformer timeout is honoured if size is not provided. * [bug 1550436 (https://bugs.launchpad.net/ceilometer/+bug/1550436) Cache json parsers when building parsing logic to handle event and meter definitions. This will improve agent startup and setup time. * [bug 1254800 (https://bugs.launchpad.net/ceilometer/+bug/1254800) Add better support to catch race conditions when creating event_types * [bug 1539163 (https://bugs.launchpad.net/ceilometer/+bug/1539163) Add ability to define whether to use first or last timestamps when aggregating samples. This will allow more flexibility when chaining transformers. * [bug 1536338 (https://bugs.launchpad.net/ceilometer/+bug/1536338) Patch was added to fix the broken floatingip pollster that polled data from nova api, but since the nova api filtered the data by tenant, ceilometer was not getting any data back. The fix changes the pollster to use the neutron api instead to get the floating ip info. * [bug 1530793 (https://bugs.launchpad.net/ceilometer/+bug/1530793) network.services.lb.incoming.bytes meter was previous set to incorrect type. It should be a gauge meter. * [bug 255569 (https://bugs.launchpad.net/ceilometer/+bug/255569) Fix caching support in Gnocchi dispatcher. Added better locking support to enable smoother cache access. * Fix samples from Heat to map to correct Gnocchi resource type * [bug 1523124 (https://bugs.launchpad.net/ceilometer/+bug/1523124) Fix gnocchi dispatcher to support UDP collector * [bug 1542189 (https://bugs.launchpad.net/ceilometer/+bug/1542189) Handle malformed resource definitions in gnocchi_resources.yaml gracefully. Currently we raise an exception once we hit a bad resource and skip the rest. Instead the patch skips the bad resource and proceeds with rest of the definitions. * [bug 1504495 (https://bugs.launchpad.net/ceilometer/+bug/1504495) Configure ceilometer to handle policy.json rules when possible. * [bug 1526793 (https://bugs.launchpad.net/ceilometer/+bug/1526793) Additional indices were added to better support querying of event data. * [bug 1536699 (https://bugs.launchpad.net/ceilometer/+bug/1536699) Patch to fix volume field lookup in meter definition file. In case the field is missing in the definition, it raises a keyerror and aborts. Instead we should skip the missing field meter and continue with the rest of the definitions. * [bug 1532661 (https://bugs.launchpad.net/ceilometer/+bug/1532661) Fix statistics query failures due to large numbers stored in MongoDB. Data from MongoDB is returned as Int64 for big numbers when int and float types are expected. The data is cast to appropriate type to handle large data. * [bug 1536498 (https://bugs.launchpad.net/ceilometer/+bug/1536498) Patch to fix duplicate meter definitions causing duplicate samples. If a duplicate is found, log a warning and skip the meter definition. Note that the first occurance of a meter will be used and any following duplicates will be skipped from processing. * [bug 1506738 (https://bugs.launchpad.net/ceilometer/+bug/1506738) [bug 1509677 (https://bugs.launchpad.net/ceilometer/+bug/1509677) Optimise SQL backend queries to minimise query load * [bug 1388680 (https://bugs.launchpad.net/ceilometer/+bug/1388680) Suppose ability to query for None value when using SQL backend. Other Notes *********** * Configure individual dispatchers by specifying meter_dispatchers and event_dispatchers in configuration file. * A dogpile.cache supported backend is required to enable cache. Additional configuration options (http://docs.openstack.org/developer/oslo.cache/opts.html#cache) are also required. Changes in ceilometer 6.0.0.0rc2..6.0.0 --------------------------------------- 2444399 collector: never allow to lose data acd1faf Imported Translations from Zanata Diffstat (except docs and test files) ------------------------------------- ceilometer/collector.py | 36 ++++------------------ ceilometer/locale/ceilometer.pot | 14 ++++++--- ceilometer/locale/ja/LC_MESSAGES/ceilometer.po | 29 +++++++++-------- .../notes/always-requeue-7a2df9243987ab67.yaml | 15 +++++++++ 5 files changed, 46 insertions(+), 83 deletions(-)

1 0

[release][congress] congress 3.0.0 release (mitaka)
by no-reply＠openstack.org 06 Apr '16

06 Apr '16

We are jubilant to announce the release of: congress 3.0.0: Congress: The open policy framework for the cloud. This release is part of the mitaka release series. For more details, please see below. Changes in congress 3.0.0.0rc1..3.0.0 ------------------------------------- 33bbacc Use keystone session in murano_driver 9248b6f Use keystone sessions to authenticate d554770 Update standalone setup instructions e20bcc4 Also package congress_tempest_tests cf8c8b5 Fix for broken antlr3 in stand-alone install 8ed5b84 Build docs using tox cf09349 Minor updates to standalone install b799d37 Remove cloudfoundry from congress.conf instructions f2350cc Update .gitreview for stable/mitaka Diffstat (except docs and test files) ------------------------------------- .gitreview | 1 + README.rst | 42 ++++++++++++++++++++++----------- antlr3runtime/Python/antlr3 | 1 + antlr3runtime/Python3/antlr3 | 1 + congress/datalog/compile.py | 4 ++-- congress/datasources/glancev2_driver.py | 22 +++++++---------- congress/datasources/heatv1_driver.py | 10 ++++++-- congress/datasources/murano_driver.py | 21 ++++++++++------- setup.cfg | 4 +++- tox.ini | 4 ++++ 10 files changed, 69 insertions(+), 41 deletions(-)

1 0

[release][designate] designate 2.0.0 release (mitaka)
by no-reply＠openstack.org 06 Apr '16

06 Apr '16

We are happy to announce the release of: designate 2.0.0: DNS as a Service This release is part of the mitaka release series. With source available at: http://git.openstack.org/cgit/openstack/designate Please report issues through launchpad: http://bugs.launchpad.net/designate For more details, please see below. 2.0.0 ^^^^^ New Features ************ * New method of updating Pools. We have a new sub command on the "designate-manage" utility. * Schedule across pools. See http://doc.openstack.org/developer/designate/pools/scheduler.html #default-provided-filters for the built in filters * Randomize SOA refresh interval to stagger AXFRs across multiple zones and resolvers. Introduce the new configuration parameters default-soa-refresh-min and default-soa-refresh-max Known Issues ************ * The fix for minidns's issues TCP can cause minidns to fail to send some messages. This manifests itself with eventlet not being able to send all the data before socket is closed. Upgrade Notes ************* * Upgrade from Liberty to Mitaka *will* require downtime due to migration of Pool Configuration data from config files, to the database. See the Upgrade Documentation for full details. * Pool Names are now required to be unique. If there is 2 pools with the same name - this will need to be changed before the upgrade is performed. * The default option for the scheduler filters will be "attribute, pool_id_attribute, random". * To maintain exact matching behaviour (if you have multiple pools) you will need to set the "scheduler_filters" option in "[service:central]" to "default_pool" Deprecation Notes ***************** * Create / Update / Delete API methods on /v2/pools/ Using these messages **will** cause unforseen issues with pools. We highly recommend that the policy file be updated to restrict create / update / delete from all users * default-soa-refresh configuration option Critical Issues *************** * Previous versions of eventlet changed the behaviour of socket.send() to match socket.sendall(). in eventlet 0.18.0 this changed and it reverted to the traditional behaviour. MiniDNS has been updated to allow minidns to push large zone transfers over long range network connections Bug Fixes ********* * Designate no longer will attempt to guess content type based on an extension to the URL. So GET /v2/zones.json is no longer an acceptable URL. Changes in designate 2.0.0.0rc1..2.0.0 -------------------------------------- c7b7075 Adding v2 namespaced event to zone manager ed29445 Do not log pool-manager-caches SQL transactions 7b5e1fd Added "view" option to bind9 rndc options 979b67d Partitoner references invalid exception class a54dade devstack: compile message catalogs during stack.sh f591b43 Update .gitreview for stable/mitaka Diffstat (except docs and test files) ------------------------------------- .gitreview | 1 + designate/backend/impl_bind9.py | 18 +++++++++++++++--- designate/coordination.py | 7 +++++-- designate/zone_manager/tasks.py | 1 + devstack/plugin.sh | 8 ++++++++ 7 files changed, 44 insertions(+), 8 deletions(-)

1 0

[release][telemetry] aodh 2.0.0 release (mitaka)
by no-reply＠openstack.org 06 Apr '16

06 Apr '16

We are gleeful to announce the release of: aodh 2.0.0: OpenStack Telemetry Alarming This release is part of the mitaka release series. For more details, please see below. 2.0.0 ^^^^^ New Features ************ * Add a new composite type alarm, which allow users specifying a composite rule to define an alarm with multiple triggering conditions, using a combination of *and*, *or* relationships. The composite rule is composed of multiple threshold rules or gnocchi rules. * Gnocchi dispatcher now uses client rather than direct http requests * Add support for Keystone v3 authentication * Support for queue based communication between alarm evaluator service and alarm notifier services was added. Original implementation involved using RPC but there is significant overhead involved with using RPC. Work queues provided required functionality with better performance. * Remove eventlet from Aodh in favour of threaded approach Upgrade Notes ************* * A new default policy.json is provided to properly handle RBAC control. Existing policy.json files may not grant the appropriate access. * gnocchiclient library is now a requirement if using ceilometer+gnocchi. * Queue based communication is the new default IPC protocol. RPC can still be used by choosing rpc as ipc_protocol option. Only one protocol can be run at any given time. Deprecation Notes ***************** * Drop support for NoSQL backends in Aodh. SQL is a prefectly sufficient backend for handling the scope of alarms. To maximise available resources, NoSQL backends are deprecated so developers do not need to worry about adding features to multiple backends. * Because queues provide the equivalent functionality. RPC support is deprecated and will be removed after Mitaka. Security Issues *************** * Patch was added to address inconsistent RBAC policy handling. Certain rules may not have been given appropriate access. Bug Fixes ********* * [bug 1540395 (https://bugs.launchpad.net/aodh/+bug/1540395) Fix reason string to properly handle transitions when one sample is outside of defined threshold. * [bug 1518447 (https://bugs.launchpad.net/aodh/+bug/1518447) Fix to ensure ceilometerclient is properly initialised on startup. * [bug 1511252 (https://bugs.launchpad.net/aodh/+bug/1511252) Fix an issue with combination alarms where it fails to evaluate all issues in the chain of alarms. * [bug 1539069 (https://bugs.launchpad.net/aodh/+bug/1539069) Fix to handle scenario where no valid statistics exist for specified period. * [bug 1513738 (https://bugs.launchpad.net/aodh/+bug/1513738) Fix an issue where alarms using Gnocchi aggregations are not being evaluated. * [bug 1504495 (https://bugs.launchpad.net/ceilometer/+bug/1504495) Patch was added to address inconsistent RBAC policy handling. Certain rules may not have been given appropriate access. Changes in aodh 2.0.0.0b3..2.0.0 -------------------------------- 2b3cf0d cleanup core list 63bf149 Use assertIn and assertNotIn for test 63b1232 register the config generator default hook with the right name a9c38d2 Replace deprecated LOG.warn with LOG.warning fcc5c91 Properly retrieve keystone user from admin client 592f221 Fixed tempest error due to upstream change 51214d7 Record all the fired alarm state for event-alarm 10bd3e6 tempest: migrate api tests from tempest tree bf9677e add missing mitaka-3 release notes 9c44733 A little typo of doc 7e638e0 Moved CORS middleware configuration into oslo-config-generator Diffstat (except docs and test files) ------------------------------------- MAINTAINERS | 3 - aodh/api/controllers/v2/alarm_rules/combination.py | 2 +- aodh/conf/__init__.py | 0 aodh/conf/defaults.py | 35 +++++++ aodh/evaluator/__init__.py | 4 +- aodh/evaluator/event.py | 8 +- aodh/evaluator/threshold.py | 4 +- aodh/keystone_client.py | 10 +- aodh/service.py | 2 + .../functional/api/v2/test_alarm_scenarios.py | 5 +- .../tempest/api/test_alarming_api_negative.py | 72 +++++++++++++ etc/aodh/api_paste.ini | 5 +- .../bug1540395-reason-string-0aad56966007d0e3.yaml | 6 ++ .../deprecate-nosql-backends-13079883eec7e8e5.yaml | 7 ++ .../fix-empty-statistics-3852da99b1c0b297.yaml | 6 ++ setup.cfg | 3 + 24 files changed, 298 insertions(+), 56 deletions(-)

1 0