diff --git a/userdocs/release-notes.rst b/userdocs/release-notes.rst index a423a545c..b95ac174f 100644 --- a/userdocs/release-notes.rst +++ b/userdocs/release-notes.rst @@ -4,23 +4,23 @@ Fuel Release Notes ================== -The community is releasing Fuel Mitaka. +The community is releasing Fuel Newton. The following table lists the released revisions of this documentation: -+-----------------------+----------------+-------------+ -| Revision | Date | Description | -+=======================+================+=============+ -| Mitaka G.A. | April 20, 2016 | G.A. | -+-----------------------+----------------+-------------+ ++-----------------------+------------------+-------------+ +| Revision | Date | Description | ++=======================+==================+=============+ +| Newton G.A. | October 20, 2016 | G.A. | ++-----------------------+------------------+-------------+ -These release notes supplement the product documentation and list +These release notes supplement the Fuel documentation and list enhancements, resolved and known issues in this version of Fuel. .. toctree:: - :maxdepth: 3 + :maxdepth: 1 - release-notes/new_features.rst - release-notes/fuel_resolved_issues.rst - release-notes/fuel_known_issues.rst - release-notes/obtain_product.rst + release-notes/new-features.rst + release-notes/fuel-resolved-issues.rst + release-notes/fuel-known-issues.rst + release-notes/obtain-product.rst diff --git a/userdocs/release-notes/fuel-known-issues.rst b/userdocs/release-notes/fuel-known-issues.rst new file mode 100644 index 000000000..49d388ddc --- /dev/null +++ b/userdocs/release-notes/fuel-known-issues.rst @@ -0,0 +1,70 @@ +============ +Known issues +============ + +This section lists known issues in the Newton release: + +* Excluded the Glare configuration for Murano from the Ubuntu + Cloud archive (UCA) deployments of OpenStack, since UCA packages do not + contain the Glare artifacts plugin. Therefore, in the UCA deployments of + OpenStack, the Murano packages are located in the Murano database instead + of the Glare artifacts repository. `LP1586141`_ + +* A DPDK-based application on a guest VM may stop incorrectly and restart. The + workaround is to re-mount HugePages on the guest VM to avoid OVS-DPDK + segmentation fault on the compute node. `LP1615012`_ + +* Murano OSTF tests fail for deployments with the TLS feature enabled. This + does not affect Murano functionality but affects OSTF tests because these + tests use proxy service on OpenStack controller nodes to work with OpenStack + API. `LP1590633`_ + +* If you add a hot pluggable Fuel plugin to an existing OpenStack + environment, the following warning displays in :guilabel:`Settings -> Other` + of the Fuel web UI instead of the plugin configuration fields: *You have + just activated the XXX plugin. The developer of this plugin has not + specified it a "hot pluggable", so the cloud environment may stop + functioning properly if this plugin is applied in post-deployment stage.* + The workaround is to refresh the Fuel web UI page. `LP1616825`_ + +* Fuel fails to deploy changes after modifying settings on the + :guilabel:`VMware` tab. `LP1593277`_ + +* Fuel fails to change a datastore regex value on the :guilabel:`VMware` tab + in the Fuel web UI. `LP1616457`_ + +* OSTF tests may fail with the following error message: *vCenter: Create + volume and attach it to instance* because after scaling the environment, + the ``cinder-volume`` service cannot establish connection to the AMQP + server. The workaround is to restart the ``cinder-volume`` service. + `LP1628940`_ + +* Adding numbers and symbols to a new role name causes the *400 Client Error*. + `LP1625293`_ + +* File download error occurs when downloading the YAML workflow for + ``Neutron VMware DVS ML2 plugin`` using the Fuel web UI. + The workaround is to download `deployment_tasks.yaml`_ directly + from the plugin's repository. `LP1619341`_ + +* If you add a new VMware vSphere environment and configure the Nova compute + instances on controllers of an existing environment with VMware vSphere, + the new VMware configuration is not applied to the controller nodes after + the environment redeployment. `LP1598834`_ + +* The Fuel web UI does not detect the changes made in the :guilabel:`VMware` + tab. The workaround is to make and deploy the changes using the Fuel CLI. + `LP1593277`_ + +.. _`LP1586141`: https://bugs.launchpad.net/fuel/+bug/1586141 +.. _`LP1625293`: https://bugs.launchpad.net/fuel/+bug/1625293 +.. _`LP1615012`: https://bugs.launchpad.net/fuel/+bug/1615012 +.. _`LP1590633`: https://bugs.launchpad.net/fuel/+bug/1590633 +.. _`LP1616825`: https://bugs.launchpad.net/fuel/+bug/1616825 +.. _`LP1593277`: https://bugs.launchpad.net/fuel/+bug/1593277 +.. _`LP1616457`: https://bugs.launchpad.net/fuel/+bug/1616457 +.. _`LP1628940`: https://bugs.launchpad.net/fuel/+bug/1628940 +.. _`LP1619341`: https://bugs.launchpad.net/fuel/+bug/1619341 +.. _`deployment_tasks.yaml`: https://github.com/openstack/fuel-plugin-vmware-dvs/blob/master/deployment_tasks.yaml +.. _`LP1593277`: https://bugs.launchpad.net/fuel/+bug/1593277 +.. _`LP1598834`: https://bugs.launchpad.net/fuel/+bug/1598834 diff --git a/userdocs/release-notes/fuel-resolved-issues.rst b/userdocs/release-notes/fuel-resolved-issues.rst new file mode 100644 index 000000000..1473196a0 --- /dev/null +++ b/userdocs/release-notes/fuel-resolved-issues.rst @@ -0,0 +1,83 @@ +=============== +Resolved issues +=============== + +This section lists a number of resolved issues. For a +complete list, see the +`Fuel for OpenStack `__ Launchpad +project. + +* Added the partition alignment option that enables + alignment modes: none, cylinder, minimal, and optimal. + ``fuel-agent`` may mistakenly assume that partition can not + fit the specified boundaries throwing the ``WrongPartitionSchemeError`` + error. This happens when the end of a particular partition crosses 1 M + boundary and because of partition boundaries are rounded up. To resolve the + issue, change the default partition alignment mode from ``optimal`` to + ``minimal`` in the ``/etc/fuel-agent/fuel-agent.conf`` configuration file + in the bootstrap image. `LP1584804`_ + +* Improved performance of the tasks serialization process in case when + an environment contains many nodes by making the serialization + process work in parallel. `LP1587278`_ + +* Fixed the ``keystone-manage db_sync`` failure because of the temporary + unavailability of the database. `LP1592819`_ | `LP1592401`_ + +* Fixed the issue that prevented a user from logging in to an environment node + using the :command:`ssh node-` command. `LP1567957`_ + +* Fixed the DHCP checker issue that resulted in the following error: + ``Spawning listener for failed. : That device is not up``. + `LP1569325`_ + +* Fixed the issue with swapping incorrectly plugged network interfaces. + `LP1593190`_ + +* Fixed the issue with the :command:`fuel2 task history` command showing + irrelevant tasks. + `LP1590872`_ + +* Fixed the issue with OpenStack occasionally failing to install from + virtual media. + `LP1605740`_ + +* Fixed the issue with Nailgun becoming unresponsive when attempting + to deploy 200 nodes. + `LP1569859`_ + +* Fixed the issue with provisioning of approximately 200 nodes failing due to + the Astute and Cobbler timeouts. `LP1608700`_ + +* Updated ``mysql-wsrep`` to v5.6.33 to avoid failures in connecting + to MySQL during an environment deployment. `LP1607793`_ + +* Replaced the ``merge_yaml_settings`` resource with an advanced + ``merge_yaml`` module that contains additional options to control the + behavior of merging the YAML configuration. The fix eliminates the + idempotency issues when several instances require a modification of the + same file, and, as a result, arrays are merged incorrectly. `LP1614279`_ + +* Fixed the issue with the DHCP checker failing on bootstrap nodes with the + following error message: *Spawning listener for failed. : That + device is not up*. `LP1569325`_ + +* Now, the hardcoded ``['controller', 'primary-controller']`` roles names + of the NTP server can be overridden. `LP1563465`_ + +.. _`LP1584804`: https://bugs.launchpad.net/fuel/+bug/1584804 +.. _`LP1587278`: https://bugs.launchpad.net/fuel/+bug/1587278 +.. _`LP1592819`: https://bugs.launchpad.net/fuel/+bug/1592819 +.. _`LP1592401`: https://bugs.launchpad.net/fuel/+bug/1592401 +.. _`LP1567957`: https://bugs.launchpad.net/fuel/+bug/1567957 +.. _`LP1569325`: https://bugs.launchpad.net/fuel/+bug/1569325 +.. _`LP1593190`: https://bugs.launchpad.net/fuel/+bug/1593190 +.. _`LP1590872`: https://bugs.launchpad.net/fuel/+bug/1590872 +.. _`LP1605740`: https://bugs.launchpad.net/fuel/+bug/1605740 +.. _`LP1603084`: https://bugs.launchpad.net/fuel/+bug/1603084 +.. _`LP1569859`: https://bugs.launchpad.net/fuel/+bug/1569859 +.. _`LP1608700`: https://bugs.launchpad.net/fuel/+bug/1608700 +.. _`LP1607793`: https://bugs.launchpad.net/fuel/+bug/1607793 +.. _`LP1614279`: https://bugs.launchpad.net/fuel/+bug/1614279 +.. _`LP1569325`: https://bugs.launchpad.net/fuel/+bug/1569325 +.. _`LP1563465`: https://bugs.launchpad.net/fuel/+bug/1563465 diff --git a/userdocs/release-notes/fuel_known_issues.rst b/userdocs/release-notes/fuel_known_issues.rst deleted file mode 100644 index ad9aabfb4..000000000 --- a/userdocs/release-notes/fuel_known_issues.rst +++ /dev/null @@ -1,124 +0,0 @@ -============ -Known Issues -============ - -This section lists known issues in this release: - -* Disk partitioning on controllers does not automatically reset back - to the default state if you change the Glance backend. - See `LP1450100 `_. - -* No option to connect to a remote repository via HTTP Proxy without - building a local mirror. - See `LP1460169 `_. - -* Default disk allocation may not use entire disk space. - To prevent this, before deploying, check that you do not - have unallocated disk space by going to :guilabel:`Nodes`, selecting - a node and clicking :guilabel:`Configure Disks`. - See `LP1490597 `_. - -* A system with CentOS 7.2 and e1000 network interface may become temporarily - unresponsive with the system log entries similar to the following ones: - - .. code-block:: console - - [ 2045.553869] e1000 0000:00:03.0 enp0s3: Detected Tx Unit Hang - [ 2045.553869] Tx Queue <0> - [ 2045.553869] TDH <3> - [ 2045.553869] TDT <3> - [ 2045.553869] next_to_use - [ 2045.553869] next_to_clean <3> - [ 2045.553869] buffer_info[next_to_clean] - [ 2045.553869] time_stamp <1001a8c59> - [ 2045.553869] next_to_watch <16> - [ 2045.553869] jiffies <1001aa291> - [ 2045.553869] next_to_watch.status <0> - [ 2046.720054] ------------[ cut here ]------------ - [ 2046.720084] WARNING: at net/sched/sch_generic.c:297 - dev_watchdog+0x270/0x280() - [ 2046.720100] NETDEV WATCHDOG: enp0s3 (e1000): transmit queue 0 timed out - [ 2046.720104] Modules linked in: loop xt_CHECKSUM iptable_mangle nf_log_ipv4 - nf_log_common xt_LOG xt_limit ipt_MASQUERADE nf_nat_masque - [ 2046.721693] CPU: 0 PID: 0 Comm: swapper/0 Not tainted - 3.10.0-327.3.1.el7.x86_64 #1 - [ 2046.721693] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), - BIOS 1.7.5-20151012_155810-obs-1 04/01/2014 - [ 2046.721693] ffff88007fc03d88 76f0075ca754d7b4 ffff88007fc03d40 ffffffff8163516c - [ 2046.721693] ffff88007fc03d78 ffffffff8107b200 0000000000000000 ffff88007a352000 - [ 2046.721693] ffff88007878ac80 0000000000000001 0000000000000000 ffff88007fc03de0 - [ 2046.721693] Call Trace: - [ 2046.721693] [] dump_stack+0x19/0x1b - [ 2046.721693] [] warn_slowpath_common+0x70/0xb0 - [ 2046.721693] [] warn_slowpath_fmt+0x5c/0x80 - [ 2046.721693] [] dev_watchdog+0x270/0x280 - [ 2046.721693] [] ? dev_graft_qdisc+0x80/0x80 - [ 2046.721693] [] call_timer_fn+0x36/0x110 - [ 2046.721693] [] ? dev_graft_qdisc+0x80/0x80 - [ 2046.721693] [] run_timer_softirq+0x237/0x340 - [ 2046.721693] [] __do_softirq+0xef/0x280 - [ 2046.721693] [] call_softirq+0x1c/0x30 - [ 2046.721693] [] do_softirq+0x65/0xa0 - [ 2046.721693] [] irq_exit+0x115/0x120 - [ 2046.721693] [] smp_apic_timer_interrupt+0x45/0x60 - [ 2046.721693] [] apic_timer_interrupt+0x6d/0x80 - - - The issue is with both hardware and virtual e1000 network interface. - The time during which the system is unresponsive is less than a minute. - The cause of the issue is network interface restart. - System logs - This is a known e1000 driver issue with various distributions: CentOS, - Ubuntu, RHEL. - See `LP1526544 `_. - - **Solutions:** - - * Use "virtio" driver: To work around the issue with the virtual interface, - use the "virtio" driver. This solution may have limitations - -- for example, bonding interface does not work with "virtio". - Please check if this workaround is compatible with your use case. - - * Disable TSO offloading -- run-time only: Disable the setting in run-time - with the command: - - .. code-block:: console - - ethtool -K tso off - - * Disable TSO offloading -- persistent change: To make the change persistent, - create a script that will set this option on every 'ifup': - - #. Create an empty file: - - .. code-block:: console - - touch /sbin/ifup-local - - #. Make the file executable: - - .. code-block:: console - - chmod +x /sbin/ifup-local - - #. Put the following lines into the file: - - .. code-block:: console - - #!/bin/bash - if [[ -z "${1}" ]]; then - exit - fi - devpath=$(readlink -m /sys/class/net/${1}) - if [[ "${devpath}" == /sys/devices/virtual/* ]]; then - exit - fi - ethtool -K ${1} tso off - -* Deployment with enabled SR-IOV fails on some hardware with - the "sriov_iommu_check" entry in the log. - This is a known issue with Linux kernel and some hardware platforms. - See `LP1556854 `_. - -* For performance reasons, integration of S3 API/Keystone is disabled by - default. See `LP1446704 `_. \ No newline at end of file diff --git a/userdocs/release-notes/fuel_resolved_issues.rst b/userdocs/release-notes/fuel_resolved_issues.rst deleted file mode 100644 index 7f888003c..000000000 --- a/userdocs/release-notes/fuel_resolved_issues.rst +++ /dev/null @@ -1,123 +0,0 @@ -=============== -Resolved Issues -=============== - -This section lists a number of resolved issues. For a -complete list, see the -`Fuel for OpenStack `__ Launchpad -project. - -* Added possibility to control restries count for Puppet-based - tasks. See `example `__. - See `LP1457794 `__. - -* Fixed the formula for the placement groups count in Ceph. See - `LP1464656 `_. - -* You can now create and manage vitual IP addresses through Nailgun - and fuel client. - See `LP1482399 `__. - -* Fixed the issue with MySQL server going down because of the incorrect - processing of the ``ignore-db-dir`` option. - See `LP1484552 `_. - -* Added an ability to connect to virtual machines in an OpenStack environment - integrated with VMware vSphere through the VNC client. - See `LP1511422 `__. - -* Added support for the be2net-dkms kernel module on the - HP ProLiant BL460c server on Ubuntu 14.04. See - `LP1533501 `_. - -* Fixed the rabbitmqctl issue that caused atom table overflow in Erlang VM. - See `LP1534519 `_. - -* Enabled the user to specify the disk on which to install - the Fuel Master node and whether to format the disk before - the installation or not by passing the ``installdrive`` and - ``forceformat`` parameters to the kernel using the grub command - line in the Fuel installation menu. See - `LP1535712 `__. - -* Enabled deployment of the OpenStack environments without controller nodes. - Thereby, the user can replace controller roles with custom roles using - Fuel plugins. - See `LP1538233 `__. - -* Fixed the issue for Swift/v1 endpoint containing an IP address instead of a - FQDN in cases when Ceph was deployed with RadosGW. - See `LP1540133 `_. - -* Introduced a feature that allows specifying the order of network - templates execution for a deployment. See - `LP1540374 `_. - -* Added the capability to forcefully update the settings and the - attributes of an environment in the operational state by - implementing an optional ``--force`` flag to the following commands: - - .. code-block:: console - - fuel settings --env --upload --force - fuel env --env --attributes --upload --force - - See `LP1540434 `_. - - Also implemented the ``fuel redeploy-changes`` and ``fuel2 redeploy`` - commands to apply the changes to an environment in the operational state. - - .. code-block:: console - - fuel redeploy-changes --env - fuel2 env redeploy - - See `LP1540558 `_. - -* Enabled ``compute-vmware`` and ``cinder-vmware`` roles combination - for the same node. - See `LP1540756 `__. - -* Now, ``network_scheme`` contains information about the network gateway if it - is defined in ``network-groups``. - See `LP1549034 `_. - -* You can now allow removing the default gateway by overriding it - as an empty string. - See `LP1549550 `__. - -* Nodes do not enter the ``error`` state when running :command:`puppet apply` - and detecting other Puppet instances. - See `LP1552805 `__. - -* Previously, during the upload of a new network YAML file, an error might - appear pointing to the type of networks with the wrong configuration. - Having many networks, it was difficult to determine which network had - issues. Now, the error message contains network IDs. - See `LP1554106 `_. - -* Added the capability to override the ``primary-controller``, - ``controller``, and ``compute`` node roles through Hiera - for the ``openstack-network`` manifests. See - `LP1554796 `_. - -* Changed the Fuel serialization process to fix the Nailgun behavior - in VLAN network environments with multiple node groups - and network templates. Previously, it was impossible to deploy such - a configuration due to a broken serialization module. - See `LP1556917 `_. - -* Previously, when specifying ``heartbeat`` and ``handshake_timeout`` - parameters in ``rabbitmq.config``, the default parameters disappeared. Now, - ``rabbit.* ``configuration options can be handled by - ``rabbit_config_variables`` in Hiera. - See `LP1560687 `_. - -* The order of tasks in the YAML file in ``/openstack-network/`` is - now strict to avoid incorrect functioning when introducting new - elements. - See `LP1561648 `__. - -* Added an ability for plugin deployment tasks to depend on the settings - of another plugin even if the latter is not installed. - See `LP1564131 `__. \ No newline at end of file diff --git a/userdocs/release-notes/new-features.rst b/userdocs/release-notes/new-features.rst new file mode 100644 index 000000000..8279260ad --- /dev/null +++ b/userdocs/release-notes/new-features.rst @@ -0,0 +1,24 @@ +============ +New features +============ + +This section includes the detailed description of features and enhancements +introduced in the Newton release. + +.. note:: Fuel Newton uses Ubuntu 16.04 as a host operating system + for OpenStack nodes. + +.. toctree:: + :maxdepth: 2 + + new-features/master-backup-restore + new-features/fuel-web-ui + new-features/fuel-cli + new-features/fuel-plugins + new-features/task-graphs + new-features/vmware-certificate + new-features/brute-force + new-features/snapshots-timmy + new-features/s3-api + new-features/dmz + new-features/user-documentation \ No newline at end of file diff --git a/userdocs/release-notes/new-features/brute-force.rst b/userdocs/release-notes/new-features/brute-force.rst new file mode 100644 index 000000000..3b9761ce4 --- /dev/null +++ b/userdocs/release-notes/new-features/brute-force.rst @@ -0,0 +1,18 @@ +========================== +SSH brute force protection +========================== + +Implemented the possibility to add SSH brute force protection +for your OpenStack environment. + +To activate SSH brute force protection: + +#. Log in to the Fuel web UI. +#. Open the :guilabel:`Settings` tab. +#. Expand :guilabel:`Security` section. +#. In the :guilabel:`SSH Security` section, select + :guilabel:`Restrict SSH service on network` check box. +#. Optionally, add secure networks. +#. Select :guilabel:`Brute force protection` check box. + +See :ref:`settings-ug` | `LP1563721 `__ \ No newline at end of file diff --git a/userdocs/release-notes/new-features/dmz.rst b/userdocs/release-notes/new-features/dmz.rst new file mode 100644 index 000000000..60a0f922c --- /dev/null +++ b/userdocs/release-notes/new-features/dmz.rst @@ -0,0 +1,9 @@ +==================== +Basic DMZ enablement +==================== + +Implemented the possibility to place public API endpoints and +OpenStack Dashboard into a separate secured network segment +usually called demilitarized zone (DMZ). + +See `blueprint `__ \ No newline at end of file diff --git a/userdocs/release-notes/new-features/fuel-cli.rst b/userdocs/release-notes/new-features/fuel-cli.rst new file mode 100644 index 000000000..70599050c --- /dev/null +++ b/userdocs/release-notes/new-features/fuel-cli.rst @@ -0,0 +1,10 @@ +=============================== +Fuel CLI versions consolidation +=============================== + +Consolidated two versions of the Fuel CLI ``fuel`` and ``fuel2``. The ``fuel2`` +entry point now provides a complete set of features as well as contains +advanced capabilities and a better structured syntax of commands. The old +Fuel CLI will be deprecated in one of the future releases. + +See :ref:`cli_comparison_matrix` | `blueprint `__ \ No newline at end of file diff --git a/userdocs/release-notes/new-features/fuel-plugins.rst b/userdocs/release-notes/new-features/fuel-plugins.rst new file mode 100644 index 000000000..2fb5f6550 --- /dev/null +++ b/userdocs/release-notes/new-features/fuel-plugins.rst @@ -0,0 +1,44 @@ +===================== +Fuel plugins features +===================== + +Fuel Newton includes a number of enhancements related to Fuel +plugins. + +Consumption of Fuel plugins from a public YUM repository +~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ + +Extended the Fuel plugins distribution model by installing and updating +plugins from YUM repositories. + +The advantages of such approach are as follows: + +* Installation of a plugin on the Fuel Master node using + the :command:`yum install ` command. + +* Updating a plugin on the Fuel Master node using + the :command:`yum update ` command. + +* Ability to pre-populate a plugin YUM repository into Fuel Master node + settings based on the Fuel Master node version. + +See :ref:`plugins_install_userguide` + +Deployment of plugins updates on a running environment +~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ + +Implemented a mechanism enabling plugins to bring their own scenarios +that can prepare a deployed OpenStack environment for plugins updates. + +See :ref:`plugins_update_userguide` + +Definition of Fuel release through the plugin framework +~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ + +Introduced a capability to express a Fuel release as a Fuel plugin. +The new functionality enables the user to define, maintain, and deploy +various flavors of customized OpenStack deployments. For example, the user +can deploy OpenStack Kilo using Fuel Mitaka or deploy a standalone Ceph +environment specifying a particular Ceph-only release. + +See :ref:`describe-plugin` | `spec `__ \ No newline at end of file diff --git a/userdocs/release-notes/new-features/fuel-web-ui.rst b/userdocs/release-notes/new-features/fuel-web-ui.rst new file mode 100644 index 000000000..d3f957566 --- /dev/null +++ b/userdocs/release-notes/new-features/fuel-web-ui.rst @@ -0,0 +1,28 @@ +==================== +Fuel web UI features +==================== + +Fuel Newton includes a number of enhancements related to the Fuel web UI. + +Custom deployment workflows management +~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ + +Extended the Fuel web UI with an ability to manage custom deployment +workflows. Now, you can list, remove, upload, download, and execute custom +deployment workflows in the :guilabel:`Dashboard` and :guilabel:`Workflows` +tabs on the :guilabel:`Environments` page. + +See :ref:`workflows_manage` | `blueprint `__ + +Deployment details overview +~~~~~~~~~~~~~~~~~~~~~~~~~~~ + +Enabled the capability to view details about deployments for specific +OpenStack environments and their nodes in the Fuel web UI: + +* To view a deployment task in progress, click :guilabel:`Show Details` + under the deployment progress bar on the :guilabel:`Dashboard` tab. +* To view information about a deployed OpenStack environment, go to + the :guilabel:`History` tab and select the required deployment. + +See :ref:`view_history` | `blueprint `__ \ No newline at end of file diff --git a/userdocs/release-notes/new-features/master-backup-restore.rst b/userdocs/release-notes/new-features/master-backup-restore.rst new file mode 100644 index 000000000..f0a0f28c8 --- /dev/null +++ b/userdocs/release-notes/new-features/master-backup-restore.rst @@ -0,0 +1,12 @@ +=================================== +Fuel Master node backup and restore +=================================== + +Added support for the backup and restore of the Fuel Master node features. +You can use the backup archives to restore the Fuel Master node in case +of a hardware failure or other system malfunction. + +See the Fuel User guide: + +* :ref:`back-up-fuel` +* :ref:`restore-fuel` \ No newline at end of file diff --git a/userdocs/release-notes/new-features/s3-api.rst b/userdocs/release-notes/new-features/s3-api.rst new file mode 100644 index 000000000..e1e1ad3f7 --- /dev/null +++ b/userdocs/release-notes/new-features/s3-api.rst @@ -0,0 +1,17 @@ +====================================== +S3 API authentication through Keystone +====================================== + +Implemented the possibility to enable Keystone to authenticate queries +to S3 API on RadosGW using the Fuel CLI and Fuel web UI. + +.. note:: + + Enablement of the Keystone authentication for S3 API increases the load + on the Keystone service. Consult with documentation and support on + mitigating the risks related with the high load of the Keystone service. + +See `LP1540426`_ | `spec`_ + +.. _`LP1540426`: https://bugs.launchpad.net/mos/+bug/1540426 +.. _`spec`: https://specs.openstack.org/openstack/fuel-specs/specs/10.0/s3-keystone-integration.html \ No newline at end of file diff --git a/userdocs/release-notes/new-features/snapshots-timmy.rst b/userdocs/release-notes/new-features/snapshots-timmy.rst new file mode 100644 index 000000000..859eeede9 --- /dev/null +++ b/userdocs/release-notes/new-features/snapshots-timmy.rst @@ -0,0 +1,21 @@ +==================================================== +Creation of targeted diagnostic snapshots with Timmy +==================================================== + +Replaced Shotgun with Timmy, a diagnostic utility for OpenStack environments +that simplifies and optimizes OpenStack troubleshooting. + +Timmy enables you to create a diagnostic snapshot of your OpenStack +environment through CLI depending on your needs: + +* Gather logging information from a single node or a subset of nodes + filtered by an assigned role or a service running on the node. +* Designate the time frame which logging information should cover. +* Specify services, the logging information of which to be included into + a snapshot. +* Specify a folder or a list of folders from where logging information + should be retrieved, filter the logging files included in that folders + by date and time, and include this logging information into the diagnostic + snapshot. + +See :ref:`create-snapshot` | `blueprint `__ \ No newline at end of file diff --git a/userdocs/release-notes/new-features/task-graphs.rst b/userdocs/release-notes/new-features/task-graphs.rst new file mode 100644 index 000000000..cc6a56208 --- /dev/null +++ b/userdocs/release-notes/new-features/task-graphs.rst @@ -0,0 +1,12 @@ +==================================================== +Data-driven workflows for basic environment actions +==================================================== + +In addition to a node deployment workflow, introduced a capability +to execute workflows for the following basic actions in an environment: + +* Node provisioning +* Node deletion +* Environment verification, that is network configuration check + +See :ref:`workflow-intro` | `blueprint `__ \ No newline at end of file diff --git a/userdocs/release-notes/new-features/user-documentation.rst b/userdocs/release-notes/new-features/user-documentation.rst new file mode 100644 index 000000000..8c7ce49e8 --- /dev/null +++ b/userdocs/release-notes/new-features/user-documentation.rst @@ -0,0 +1,12 @@ +================== +User documentation +================== + +Fuel Newton includes a number of major user documentation updates: + +* :ref:`upgrade_intro` +* :ref:`cli_comparison_matrix` +* :ref:`workflow-intro` +* :ref:`workflows_manage` +* :ref:`create-snapshot` +* :ref:`ug-troubleshooting` \ No newline at end of file diff --git a/userdocs/release-notes/new-features/vmware-certificate.rst b/userdocs/release-notes/new-features/vmware-certificate.rst new file mode 100644 index 000000000..4a9d02111 --- /dev/null +++ b/userdocs/release-notes/new-features/vmware-certificate.rst @@ -0,0 +1,27 @@ +===================================================== +Verification of the VMware vCenter server certificate +===================================================== + +Added a capability to specify a Certificate Authority (CA) bundle file +to use for verifying the VMware vCenter server certificate for +the OpenStack Compute service, OpenStack Block Storage service, and +OpenStack Image service. + +Depending on the needs of your environment, you can configure the VMware +vCenter server certificate verification on the :guilabel:`VMware` tab in +the Fuel web UI: + +* If you plan to deploy an environment for testing purposes or want + to speed up the deployment process, you can disable the certificate + verification by checking + :guilabel:`Bypass vCenter certificate verification`. + +* If VMware vCenter is using a self-signed certificate, upload a CA + certificate in the :guilabel:`CA file` field. + Leave :guilabel:`Bypass vCenter certificate verification` unchecked. + +* If a VMware vCenter server certificate is emitted by a known CA, + for example, GeoTrust, leave the :guilabel:`CA file` field empty + and :guilabel:`Bypass vCenter certificate verification` unchecked. + +See :ref:`configure-vmware-vcenter-settings` \ No newline at end of file diff --git a/userdocs/release-notes/new_features.rst b/userdocs/release-notes/new_features.rst deleted file mode 100644 index a1c8413b9..000000000 --- a/userdocs/release-notes/new_features.rst +++ /dev/null @@ -1,95 +0,0 @@ -============ -New Features -============ - -Fuel Mitaka is the release of new features and bug fixes for -the leading purpose-built open source deployment and management tool -for OpenStack. - -Fuel Mitaka introduces a set of new features and enhancements. -This section lists these improvements: - -* Plugin developers can now dynamically add configuration fields to their - plugins. - See `blueprint `__. - -* Added ability to stop and restart environment deployment without resetting - the deployment process. See the :ref:`stop_deployment` section in the Fuel - User Guide. - This allows users to fix deployment errors and resume the deployment process - without having to start it over completely. - See `blueprint `__. - -* Improved deployment orchestration to reduce deployment time and minimize - technical and architectural efforts through task-based deployment with Astute. - This further enables Fuel to provide the lifecycle management features such - as :guilabel:`Unlocked Settings Tab`. - -* Fuel plugins can now be managed on a deployed cloud through the Fuel web UI - in :guilabel:`Unlocked Settings Tab`: - - * You can install plugins through the Fuel web UI. - * Plugins can insert tasks in deployment graphs. - * You can now change the settings of a plugin if supported. Consult with - the plugin developer if not sure. - -* Fuel now stores detailed information about all deployments. You can download - the actual cluster settings, network configuration, and serialized cluster - data. - See :ref:`view_history` and :ref:`deployment-information`. - -* You can now execute a particular deployment workflow with the ability to merge - it with the existing deployment workflows of the upstream master release. - This allows you to implement complex orchestrated workflows -- bugfixes - application, reference architecture altering, or even upgrades. - See :ref:`workflows_manage`. - -* Fuel now supports lifecycle management tasks based on the history of - cluster states. This data-driven feature allows the deployment engineers - and plugin developers that use Fuel library deployment tasks to introduce - expressions that can be computed within the context of cluster configuration. - You can now control the tasks assignment and execution depending on the - configuration or changes in the configuration. - See :ref:`data-driven`. - -* All deployment tasks that Fuel uses when configuring OpenStack are now - idempotent. This enables the lifecycle management features that require - re-running of deployment tasks with the updated input data in the - post-deployment stage of cloud lifecycle. - See `blueprint `__. - -* Fuel can now deploy UCA packages. - See `blueprint `__. - -* Operators can now change OpenStack settings on the :guilabel:`Settings` - tab in Fuel web UI for the cloud that is already deployed and apply the - settings. - See `blueprint `__. - -* Fuel API now allows to manually set virtual IP address to any valid - IP address. - See `blueprint `__. - -* The node roles panel on the Fuel web UI has been redesigned to accommodate - for the standard screen estate. - See `blueprint `__. - -* Enabled separate node deployment and operating system provisioning in the - Fuel web UI. - This allows users to adjust configuration and fix errors on a specific node - or a subset of nodes without having to re-deploy or re-provision the entire - cloud environment. - See `blueprint `__. - -* Enabled control groups management. OpenStack operators can configure - resource utilization thresholds for the OpenStack services and underlying - software components using ``cgroups``. Specifying optimal values helps - to increase performance and reliability of your cloud. - See :ref:`cgroups-intro`. - -* The OpenStack Application Catalog service is now also installable as a - plugin for Fuel. This plugin is designed to enable upgrading of the - OpenStack Application Catalog together with plugin installation. This plugin - update mechanism will be used to deliver future updates to the OpenStack - Application Catalog service. - See `Murano plugin for Fuel `__. \ No newline at end of file diff --git a/userdocs/release-notes/obtain_product.rst b/userdocs/release-notes/obtain-product.rst similarity index 100% rename from userdocs/release-notes/obtain_product.rst rename to userdocs/release-notes/obtain-product.rst