Browse Source

Merge "[RN] Adds Fuel RN for Newton"

Jenkins 2 years ago
parent
commit
406ede46e0

+ 12
- 12
userdocs/release-notes.rst View File

@@ -4,23 +4,23 @@
4 4
 Fuel Release Notes
5 5
 ==================
6 6
 
7
-The community is releasing Fuel Mitaka.
7
+The community is releasing Fuel Newton.
8 8
 
9 9
 The following table lists the released revisions of this documentation:
10 10
 
11
-+-----------------------+----------------+-------------+
12
-| Revision              | Date           | Description |
13
-+=======================+================+=============+
14
-| Mitaka G.A.           | April 20, 2016 | G.A.        |
15
-+-----------------------+----------------+-------------+
11
++-----------------------+------------------+-------------+
12
+| Revision              | Date             | Description |
13
++=======================+==================+=============+
14
+| Newton G.A.           | October 20, 2016 | G.A.        |
15
++-----------------------+------------------+-------------+
16 16
 
17
-These release notes supplement the product documentation and list
17
+These release notes supplement the Fuel documentation and list
18 18
 enhancements, resolved and known issues in this version of Fuel.
19 19
 
20 20
 .. toctree::
21
-   :maxdepth: 3
21
+   :maxdepth: 1
22 22
 
23
-   release-notes/new_features.rst
24
-   release-notes/fuel_resolved_issues.rst
25
-   release-notes/fuel_known_issues.rst
26
-   release-notes/obtain_product.rst
23
+   release-notes/new-features.rst
24
+   release-notes/fuel-resolved-issues.rst
25
+   release-notes/fuel-known-issues.rst
26
+   release-notes/obtain-product.rst

+ 70
- 0
userdocs/release-notes/fuel-known-issues.rst View File

@@ -0,0 +1,70 @@
1
+============
2
+Known issues
3
+============
4
+
5
+This section lists known issues in the Newton release:
6
+
7
+* Excluded the Glare configuration for Murano from the Ubuntu
8
+  Cloud archive (UCA) deployments of OpenStack, since UCA packages do not
9
+  contain the Glare artifacts plugin. Therefore, in the UCA deployments of
10
+  OpenStack, the Murano packages are located in the Murano database instead
11
+  of the Glare artifacts repository. `LP1586141`_
12
+
13
+* A DPDK-based application on a guest VM may stop incorrectly and restart. The
14
+  workaround is to re-mount HugePages on the guest VM to avoid OVS-DPDK
15
+  segmentation fault on the compute node. `LP1615012`_
16
+
17
+* Murano OSTF tests fail for deployments with the TLS feature enabled. This
18
+  does not affect Murano functionality but affects OSTF tests because these
19
+  tests use proxy service on OpenStack controller nodes to work with OpenStack
20
+  API. `LP1590633`_
21
+
22
+* If you add a hot pluggable Fuel plugin to an existing OpenStack
23
+  environment, the following warning displays in :guilabel:`Settings -> Other`
24
+  of the Fuel web UI instead of the plugin configuration fields: *You have
25
+  just activated the XXX plugin. The developer of this plugin has not
26
+  specified it a "hot pluggable", so the cloud environment may stop
27
+  functioning properly if this plugin is applied in post-deployment stage.*
28
+  The workaround is to refresh the Fuel web UI page. `LP1616825`_
29
+
30
+* Fuel fails to deploy changes after modifying settings on the
31
+  :guilabel:`VMware` tab. `LP1593277`_
32
+
33
+* Fuel fails to change a datastore regex value on the :guilabel:`VMware` tab
34
+  in the Fuel web UI. `LP1616457`_
35
+
36
+* OSTF tests may fail with the following error message: *vCenter: Create
37
+  volume and attach it to instance* because after scaling the environment,
38
+  the ``cinder-volume`` service cannot establish connection to the AMQP
39
+  server. The workaround is to restart the ``cinder-volume`` service.
40
+  `LP1628940`_
41
+
42
+* Adding numbers and symbols to a new role name causes the *400 Client Error*.
43
+  `LP1625293`_
44
+
45
+* File download error occurs when downloading the YAML workflow for
46
+  ``Neutron VMware DVS ML2 plugin`` using the Fuel web UI.
47
+  The workaround is to download `deployment_tasks.yaml`_ directly
48
+  from the plugin's repository. `LP1619341`_
49
+
50
+* If you add a new VMware vSphere environment and configure the Nova compute
51
+  instances on controllers of an existing environment with VMware vSphere,
52
+  the new VMware configuration is not applied to the controller nodes after
53
+  the environment redeployment. `LP1598834`_
54
+
55
+* The Fuel web UI does not detect the changes made in the :guilabel:`VMware`
56
+  tab. The workaround is to make and deploy the changes using the Fuel CLI.
57
+  `LP1593277`_
58
+
59
+.. _`LP1586141`: https://bugs.launchpad.net/fuel/+bug/1586141
60
+.. _`LP1625293`: https://bugs.launchpad.net/fuel/+bug/1625293
61
+.. _`LP1615012`: https://bugs.launchpad.net/fuel/+bug/1615012
62
+.. _`LP1590633`: https://bugs.launchpad.net/fuel/+bug/1590633
63
+.. _`LP1616825`: https://bugs.launchpad.net/fuel/+bug/1616825
64
+.. _`LP1593277`: https://bugs.launchpad.net/fuel/+bug/1593277
65
+.. _`LP1616457`: https://bugs.launchpad.net/fuel/+bug/1616457
66
+.. _`LP1628940`: https://bugs.launchpad.net/fuel/+bug/1628940
67
+.. _`LP1619341`: https://bugs.launchpad.net/fuel/+bug/1619341
68
+.. _`deployment_tasks.yaml`: https://github.com/openstack/fuel-plugin-vmware-dvs/blob/master/deployment_tasks.yaml
69
+.. _`LP1593277`: https://bugs.launchpad.net/fuel/+bug/1593277
70
+.. _`LP1598834`: https://bugs.launchpad.net/fuel/+bug/1598834

+ 83
- 0
userdocs/release-notes/fuel-resolved-issues.rst View File

@@ -0,0 +1,83 @@
1
+===============
2
+Resolved issues
3
+===============
4
+
5
+This section lists a number of resolved issues. For a
6
+complete list, see the
7
+`Fuel for OpenStack <https://bugs.launchpad.net/fuel>`__ Launchpad
8
+project.
9
+
10
+* Added the partition alignment option that enables
11
+  alignment modes: none, cylinder, minimal, and optimal.
12
+  ``fuel-agent`` may mistakenly assume that partition can not
13
+  fit the specified boundaries throwing the ``WrongPartitionSchemeError``
14
+  error. This happens when the end of a particular partition crosses 1 M
15
+  boundary and because of partition boundaries are rounded up. To resolve the
16
+  issue, change the default partition alignment mode from ``optimal`` to
17
+  ``minimal`` in the ``/etc/fuel-agent/fuel-agent.conf`` configuration file
18
+  in the bootstrap image. `LP1584804`_
19
+
20
+* Improved performance of the tasks serialization process in case when
21
+  an environment contains many nodes by making the serialization
22
+  process work in parallel. `LP1587278`_
23
+
24
+* Fixed the ``keystone-manage db_sync`` failure because of the temporary
25
+  unavailability of the database. `LP1592819`_ | `LP1592401`_
26
+
27
+* Fixed the issue that prevented a user from logging in to an environment node
28
+  using the :command:`ssh node-<SLAVE_NODE_ID>` command. `LP1567957`_
29
+
30
+* Fixed the DHCP checker issue that resulted in the following error:
31
+  ``Spawning listener for <NIC> failed. <NIC>: That device is not up``.
32
+  `LP1569325`_
33
+
34
+* Fixed the issue with swapping incorrectly plugged network interfaces.
35
+  `LP1593190`_
36
+
37
+* Fixed the issue with the :command:`fuel2 task history` command showing
38
+  irrelevant tasks.
39
+  `LP1590872`_
40
+
41
+* Fixed the issue with OpenStack occasionally failing to install from
42
+  virtual media.
43
+  `LP1605740`_
44
+
45
+* Fixed the issue with Nailgun becoming unresponsive when attempting
46
+  to deploy 200 nodes.
47
+  `LP1569859`_
48
+
49
+* Fixed the issue with provisioning of approximately 200 nodes failing due to
50
+  the Astute and Cobbler timeouts. `LP1608700`_
51
+
52
+* Updated ``mysql-wsrep`` to v5.6.33 to avoid failures in connecting
53
+  to MySQL during an environment deployment. `LP1607793`_
54
+
55
+* Replaced the ``merge_yaml_settings`` resource with an advanced
56
+  ``merge_yaml`` module that contains additional options to control the
57
+  behavior of merging the YAML configuration. The fix eliminates the
58
+  idempotency issues when several instances require a modification of the
59
+  same file, and, as a result, arrays are merged incorrectly. `LP1614279`_
60
+
61
+* Fixed the issue with the DHCP checker failing on bootstrap nodes with the
62
+  following error message: *Spawning listener for <NIC> failed. <NIC>: That
63
+  device is not up*. `LP1569325`_
64
+
65
+* Now, the hardcoded ``['controller', 'primary-controller']`` roles names
66
+  of the NTP server can be overridden. `LP1563465`_
67
+
68
+.. _`LP1584804`: https://bugs.launchpad.net/fuel/+bug/1584804
69
+.. _`LP1587278`: https://bugs.launchpad.net/fuel/+bug/1587278
70
+.. _`LP1592819`: https://bugs.launchpad.net/fuel/+bug/1592819
71
+.. _`LP1592401`: https://bugs.launchpad.net/fuel/+bug/1592401
72
+.. _`LP1567957`: https://bugs.launchpad.net/fuel/+bug/1567957
73
+.. _`LP1569325`: https://bugs.launchpad.net/fuel/+bug/1569325
74
+.. _`LP1593190`: https://bugs.launchpad.net/fuel/+bug/1593190
75
+.. _`LP1590872`: https://bugs.launchpad.net/fuel/+bug/1590872
76
+.. _`LP1605740`: https://bugs.launchpad.net/fuel/+bug/1605740
77
+.. _`LP1603084`: https://bugs.launchpad.net/fuel/+bug/1603084
78
+.. _`LP1569859`: https://bugs.launchpad.net/fuel/+bug/1569859
79
+.. _`LP1608700`: https://bugs.launchpad.net/fuel/+bug/1608700
80
+.. _`LP1607793`: https://bugs.launchpad.net/fuel/+bug/1607793
81
+.. _`LP1614279`: https://bugs.launchpad.net/fuel/+bug/1614279
82
+.. _`LP1569325`: https://bugs.launchpad.net/fuel/+bug/1569325
83
+.. _`LP1563465`: https://bugs.launchpad.net/fuel/+bug/1563465

+ 0
- 124
userdocs/release-notes/fuel_known_issues.rst View File

@@ -1,124 +0,0 @@
1
-============
2
-Known Issues
3
-============
4
-
5
-This section lists known issues in this release:
6
-
7
-* Disk partitioning on controllers does not automatically reset back
8
-  to the default state if you change the Glance backend.
9
-  See `LP1450100 <https://bugs.launchpad.net/bugs/1450100>`_.
10
-
11
-* No option to connect to a remote repository via HTTP Proxy without
12
-  building a local mirror.
13
-  See `LP1460169 <https://bugs.launchpad.net/bugs/1460169>`_.
14
-
15
-* Default disk allocation may not use entire disk space.
16
-  To prevent this, before deploying, check that you do not
17
-  have unallocated disk space by going to :guilabel:`Nodes`, selecting
18
-  a node and clicking :guilabel:`Configure Disks`.
19
-  See `LP1490597 <https://bugs.launchpad.net/bugs/1490597>`_.
20
-
21
-* A system with CentOS 7.2 and e1000 network interface may become temporarily
22
-  unresponsive with the system log entries similar to the following ones:
23
-  
24
-  .. code-block:: console
25
-
26
-     [ 2045.553869] e1000 0000:00:03.0 enp0s3: Detected Tx Unit Hang
27
-     [ 2045.553869] Tx Queue <0>
28
-     [ 2045.553869] TDH <3>
29
-     [ 2045.553869] TDT <3>
30
-     [ 2045.553869] next_to_use <de>
31
-     [ 2045.553869] next_to_clean <3>
32
-     [ 2045.553869] buffer_info[next_to_clean]
33
-     [ 2045.553869] time_stamp <1001a8c59>
34
-     [ 2045.553869] next_to_watch <16>
35
-     [ 2045.553869] jiffies <1001aa291>
36
-     [ 2045.553869] next_to_watch.status <0>
37
-     [ 2046.720054] ------------[ cut here ]------------
38
-     [ 2046.720084] WARNING: at net/sched/sch_generic.c:297
39
-     dev_watchdog+0x270/0x280()
40
-     [ 2046.720100] NETDEV WATCHDOG: enp0s3 (e1000): transmit queue 0 timed out
41
-     [ 2046.720104] Modules linked in: loop xt_CHECKSUM iptable_mangle nf_log_ipv4
42
-     nf_log_common xt_LOG xt_limit ipt_MASQUERADE nf_nat_masque
43
-     [ 2046.721693] CPU: 0 PID: 0 Comm: swapper/0 Not tainted
44
-     3.10.0-327.3.1.el7.x86_64 #1
45
-     [ 2046.721693] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996),
46
-     BIOS 1.7.5-20151012_155810-obs-1 04/01/2014
47
-     [ 2046.721693] ffff88007fc03d88 76f0075ca754d7b4 ffff88007fc03d40 ffffffff8163516c
48
-     [ 2046.721693] ffff88007fc03d78 ffffffff8107b200 0000000000000000 ffff88007a352000
49
-     [ 2046.721693] ffff88007878ac80 0000000000000001 0000000000000000 ffff88007fc03de0
50
-     [ 2046.721693] Call Trace:
51
-     [ 2046.721693] <IRQ> [<ffffffff8163516c>] dump_stack+0x19/0x1b
52
-     [ 2046.721693] [<ffffffff8107b200>] warn_slowpath_common+0x70/0xb0
53
-     [ 2046.721693] [<ffffffff8107b29c>] warn_slowpath_fmt+0x5c/0x80
54
-     [ 2046.721693] [<ffffffff8154ca50>] dev_watchdog+0x270/0x280
55
-     [ 2046.721693] [<ffffffff8154c7e0>] ? dev_graft_qdisc+0x80/0x80
56
-     [ 2046.721693] [<ffffffff8108b0a6>] call_timer_fn+0x36/0x110
57
-     [ 2046.721693] [<ffffffff8154c7e0>] ? dev_graft_qdisc+0x80/0x80
58
-     [ 2046.721693] [<ffffffff8108dd97>] run_timer_softirq+0x237/0x340
59
-     [ 2046.721693] [<ffffffff81084b0f>] __do_softirq+0xef/0x280
60
-     [ 2046.721693] [<ffffffff816471dc>] call_softirq+0x1c/0x30
61
-     [ 2046.721693] [<ffffffff81016fc5>] do_softirq+0x65/0xa0
62
-     [ 2046.721693] [<ffffffff81084ea5>] irq_exit+0x115/0x120
63
-     [ 2046.721693] [<ffffffff81647e55>] smp_apic_timer_interrupt+0x45/0x60
64
-     [ 2046.721693] [<ffffffff8164651d>] apic_timer_interrupt+0x6d/0x80
65
-
66
-
67
-  The issue is with both hardware and virtual e1000 network interface.
68
-  The time during which the system is unresponsive is less than a minute.
69
-  The cause of the issue is network interface restart.
70
-  System logs 
71
-  This is a known e1000 driver issue with various distributions: CentOS,
72
-  Ubuntu, RHEL.
73
-  See `LP1526544 <https://bugs.launchpad.net/bugs/1526544>`_.
74
-
75
-  **Solutions:**
76
-
77
-  * Use "virtio" driver: To work around the issue with the virtual interface,
78
-    use the "virtio" driver. This solution may have limitations
79
-    -- for example, bonding interface does not work with "virtio".
80
-    Please check if this workaround is compatible with your use case.
81
-
82
-  * Disable TSO offloading -- run-time only: Disable the setting in run-time
83
-    with the command:
84
-
85
-    .. code-block:: console
86
-
87
-       ethtool -K <ifname> tso off
88
-
89
-  * Disable TSO offloading -- persistent change: To make the change persistent,
90
-    create a script that will set this option on every 'ifup':
91
-
92
-    #. Create an empty file:
93
-
94
-       .. code-block:: console
95
-
96
-          touch /sbin/ifup-local
97
-
98
-    #. Make the file executable:
99
-
100
-       .. code-block:: console
101
-
102
-          chmod +x /sbin/ifup-local
103
-
104
-    #. Put the following lines into the file:
105
-
106
-       .. code-block:: console
107
-
108
-           #!/bin/bash
109
-           if [[ -z "${1}" ]]; then
110
-            exit
111
-           fi
112
-           devpath=$(readlink -m /sys/class/net/${1})
113
-           if [[ "${devpath}" == /sys/devices/virtual/* ]]; then
114
-             exit
115
-           fi
116
-           ethtool -K ${1} tso off
117
-
118
-* Deployment with enabled SR-IOV fails on some hardware with
119
-  the "sriov_iommu_check" entry in the log.
120
-  This is a known issue with Linux kernel and some hardware platforms.
121
-  See `LP1556854 <https://bugs.launchpad.net/bugs/1556854>`_.
122
-
123
-* For performance reasons, integration of S3 API/Keystone is disabled by
124
-  default. See `LP1446704 <https://bugs.launchpad.net/fuel/+bug/1446704>`_.

+ 0
- 123
userdocs/release-notes/fuel_resolved_issues.rst View File

@@ -1,123 +0,0 @@
1
-===============
2
-Resolved Issues
3
-===============
4
-
5
-This section lists a number of resolved issues. For a
6
-complete list, see the
7
-`Fuel for OpenStack <https://bugs.launchpad.net/fuel>`__ Launchpad
8
-project.
9
-
10
-* Added possibility to control restries count for Puppet-based
11
-  tasks. See `example <https://review.openstack.org/#/c/222149/4/fuel_plugin_example_v3/tasks.yaml>`__.
12
-  See `LP1457794 <https://bugs.launchpad.net/fuel/+bug/1457794>`__.
13
-
14
-* Fixed the formula for the placement groups count in Ceph. See
15
-  `LP1464656 <https://bugs.launchpad.net/fuel/+bug/1464656>`_.
16
-
17
-* You can now create and manage vitual IP addresses through Nailgun
18
-  and fuel client.
19
-  See `LP1482399 <https://bugs.launchpad.net/fuel/+bug/1482399>`__.
20
-
21
-* Fixed the issue with MySQL server going down because of the incorrect
22
-  processing of the ``ignore-db-dir`` option.
23
-  See `LP1484552 <https://bugs.launchpad.net/fuel/+bug/1484552>`_.
24
-
25
-* Added an ability to connect to virtual machines in an OpenStack environment
26
-  integrated with VMware vSphere through the VNC client.
27
-  See `LP1511422 <https://bugs.launchpad.net/fuel/+bug/1511422>`__.
28
-
29
-* Added support for the be2net-dkms kernel module on the
30
-  HP ProLiant BL460c server on Ubuntu 14.04. See
31
-  `LP1533501 <https://bugs.launchpad.net/fuel/+bug/1533501>`_.
32
-
33
-* Fixed the rabbitmqctl issue that caused atom table overflow in Erlang VM.
34
-  See `LP1534519 <https://bugs.launchpad.net/fuel/+bug/1534519>`_.
35
-
36
-* Enabled the user to specify the disk on which to install
37
-  the Fuel Master node and whether to format the disk before
38
-  the installation or not by passing the ``installdrive`` and
39
-  ``forceformat`` parameters to the kernel using the grub command
40
-  line in the Fuel installation menu. See
41
-  `LP1535712 <https://bugs.launchpad.net/fuel/+bug/1535712>`__.
42
-
43
-* Enabled deployment of the OpenStack environments without controller nodes.
44
-  Thereby, the user can replace controller roles with custom roles using
45
-  Fuel plugins.
46
-  See `LP1538233 <https://bugs.launchpad.net/fuel/+bug/1538233>`__.
47
-
48
-* Fixed the issue for Swift/v1 endpoint containing an IP address instead of a
49
-  FQDN in cases when Ceph was deployed with RadosGW.
50
-  See `LP1540133 <https://bugs.launchpad.net/fuel/+bug/1540133>`_.
51
-
52
-* Introduced a feature that allows specifying the order of network
53
-  templates execution for a deployment. See
54
-  `LP1540374 <https://bugs.launchpad.net/fuel/+bug/1540374>`_.
55
-
56
-* Added the capability to forcefully update the settings and the
57
-  attributes of an environment in the operational state by
58
-  implementing an optional ``--force`` flag to the following commands:
59
-
60
-  .. code-block:: console
61
-
62
-   fuel settings --env <env_id> --upload --force
63
-   fuel env --env <env_id> --attributes --upload --force
64
-
65
-  See `LP1540434 <https://bugs.launchpad.net/fuel/+bug/1540434>`_.
66
-
67
-  Also implemented the ``fuel redeploy-changes`` and ``fuel2 redeploy``
68
-  commands to apply the changes to an environment in the operational state.
69
-
70
-  .. code-block:: console
71
-
72
-   fuel redeploy-changes --env <env_id>
73
-   fuel2 env redeploy <env_id>
74
-
75
-  See `LP1540558 <https://bugs.launchpad.net/fuel/+bug/1540558>`_.
76
-
77
-* Enabled ``compute-vmware`` and ``cinder-vmware`` roles combination
78
-  for the same node.
79
-  See `LP1540756 <https://bugs.launchpad.net/fuel/+bug/1540756>`__.
80
-
81
-* Now, ``network_scheme`` contains information about the network gateway if it
82
-  is defined in ``network-groups``.
83
-  See `LP1549034 <https://bugs.launchpad.net/fuel/+bug/1549034>`_.
84
-
85
-* You can now allow removing the default gateway by overriding it
86
-  as an empty string.
87
-  See `LP1549550 <https://bugs.launchpad.net/fuel/+bug/1549550>`__.
88
-
89
-* Nodes do not enter the ``error`` state when running :command:`puppet apply`
90
-  and detecting other Puppet instances.
91
-  See `LP1552805 <https://bugs.launchpad.net/fuel/+bug/1552805>`__.
92
-
93
-* Previously, during the upload of a new network YAML file, an error might
94
-  appear pointing to the type of networks with the wrong configuration.
95
-  Having many networks, it was difficult to determine which network had
96
-  issues. Now, the error message contains network IDs.
97
-  See `LP1554106 <https://bugs.launchpad.net/fuel/+bug/1554106>`_.
98
-
99
-* Added the capability to override the ``primary-controller``,
100
-  ``controller``, and ``compute`` node roles through Hiera
101
-  for the ``openstack-network`` manifests. See
102
-  `LP1554796 <https://bugs.launchpad.net/fuel/+bug/1554796>`_.
103
-
104
-* Changed the Fuel serialization process to fix the Nailgun behavior
105
-  in VLAN network environments with multiple node groups
106
-  and network templates. Previously, it was impossible to deploy such
107
-  a configuration due to a broken serialization module.
108
-  See `LP1556917 <https://bugs.launchpad.net/fuel/+bug/1556917>`_.
109
-
110
-* Previously, when specifying ``heartbeat`` and ``handshake_timeout``
111
-  parameters in ``rabbitmq.config``, the default parameters disappeared. Now,
112
-  ``rabbit.* ``configuration options can be handled by
113
-  ``rabbit_config_variables`` in Hiera.
114
-  See `LP1560687 <https://bugs.launchpad.net/fuel/+bug/1560687>`_.
115
-
116
-* The order of tasks in the YAML file in ``/openstack-network/`` is
117
-  now strict to avoid incorrect functioning when introducting new
118
-  elements.
119
-  See `LP1561648 <https://bugs.launchpad.net/fuel/+bug/1561648>`__.
120
-
121
-* Added an ability for plugin deployment tasks to depend on the settings
122
-  of another plugin even if the latter is not installed.
123
-  See `LP1564131 <https://bugs.launchpad.net/fuel/+bug/1564131>`__.

+ 24
- 0
userdocs/release-notes/new-features.rst View File

@@ -0,0 +1,24 @@
1
+============
2
+New features
3
+============
4
+
5
+This section includes the detailed description of features and enhancements
6
+introduced in the Newton release.
7
+
8
+.. note:: Fuel Newton uses Ubuntu 16.04 as a host operating system
9
+          for OpenStack nodes.
10
+
11
+.. toctree::
12
+   :maxdepth: 2
13
+
14
+   new-features/master-backup-restore
15
+   new-features/fuel-web-ui
16
+   new-features/fuel-cli
17
+   new-features/fuel-plugins
18
+   new-features/task-graphs
19
+   new-features/vmware-certificate
20
+   new-features/brute-force
21
+   new-features/snapshots-timmy
22
+   new-features/s3-api
23
+   new-features/dmz
24
+   new-features/user-documentation

+ 18
- 0
userdocs/release-notes/new-features/brute-force.rst View File

@@ -0,0 +1,18 @@
1
+==========================
2
+SSH brute force protection
3
+==========================
4
+
5
+Implemented the possibility to add SSH brute force protection
6
+for your OpenStack environment.
7
+
8
+To activate SSH brute force protection:
9
+
10
+#. Log in to the Fuel web UI.
11
+#. Open the :guilabel:`Settings` tab.
12
+#. Expand :guilabel:`Security` section.
13
+#. In the :guilabel:`SSH Security` section, select
14
+   :guilabel:`Restrict SSH service on network` check box.
15
+#. Optionally, add secure networks.
16
+#. Select :guilabel:`Brute force protection` check box.
17
+
18
+See :ref:`settings-ug` | `LP1563721 <https://bugs.launchpad.net/fuel/+bug/1563721>`__

+ 9
- 0
userdocs/release-notes/new-features/dmz.rst View File

@@ -0,0 +1,9 @@
1
+====================
2
+Basic DMZ enablement
3
+====================
4
+
5
+Implemented the possibility to place public API endpoints and
6
+OpenStack Dashboard into a separate secured network segment
7
+usually called demilitarized zone (DMZ).
8
+
9
+See `blueprint <https://blueprints.launchpad.net/fuel/+spec/separate-public-floating>`__

+ 10
- 0
userdocs/release-notes/new-features/fuel-cli.rst View File

@@ -0,0 +1,10 @@
1
+===============================
2
+Fuel CLI versions consolidation
3
+===============================
4
+
5
+Consolidated two versions of the Fuel CLI ``fuel`` and ``fuel2``. The ``fuel2``
6
+entry point now provides a complete set of features as well as contains
7
+advanced capabilities and a better structured syntax of commands. The old
8
+Fuel CLI will be deprecated in one of the future releases.
9
+
10
+See :ref:`cli_comparison_matrix` | `blueprint <https://blueprints.launchpad.net/fuel/+spec/re-thinking-fuel-client>`__

+ 44
- 0
userdocs/release-notes/new-features/fuel-plugins.rst View File

@@ -0,0 +1,44 @@
1
+=====================
2
+Fuel plugins features
3
+=====================
4
+
5
+Fuel Newton includes a number of enhancements related to Fuel
6
+plugins.
7
+
8
+Consumption of Fuel plugins from a public YUM repository
9
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
10
+
11
+Extended the Fuel plugins distribution model by installing and updating
12
+plugins from YUM repositories.
13
+
14
+The advantages of such approach are as follows:
15
+
16
+* Installation of a plugin on the Fuel Master node using
17
+  the :command:`yum install <PLUGIN_NAME>` command.
18
+
19
+* Updating a plugin on the Fuel Master node using
20
+  the :command:`yum update <PLUGIN_NAME>` command.
21
+
22
+* Ability to pre-populate a plugin YUM repository into Fuel Master node
23
+  settings based on the Fuel Master node version.
24
+
25
+See :ref:`plugins_install_userguide`
26
+
27
+Deployment of plugins updates on a running environment
28
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
29
+
30
+Implemented a mechanism enabling plugins to bring their own scenarios
31
+that can prepare a deployed OpenStack environment for plugins updates.
32
+
33
+See :ref:`plugins_update_userguide`
34
+
35
+Definition of Fuel release through the plugin framework
36
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
37
+
38
+Introduced a capability to express a Fuel release as a Fuel plugin.
39
+The new functionality enables the user to define, maintain, and deploy
40
+various flavors of customized OpenStack deployments. For example, the user
41
+can deploy OpenStack Kilo using Fuel Mitaka or deploy a standalone Ceph
42
+environment specifying a particular Ceph-only release.
43
+
44
+See :ref:`describe-plugin` | `spec <https://specs.openstack.org/openstack/fuel-specs/specs/10.0/release-as-a-plugin.html>`__

+ 28
- 0
userdocs/release-notes/new-features/fuel-web-ui.rst View File

@@ -0,0 +1,28 @@
1
+====================
2
+Fuel web UI features
3
+====================
4
+
5
+Fuel Newton includes a number of enhancements related to the Fuel web UI.
6
+
7
+Custom deployment workflows management
8
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
9
+
10
+Extended the Fuel web UI with an ability to manage custom deployment
11
+workflows. Now, you can list, remove, upload, download, and execute custom
12
+deployment workflows in the :guilabel:`Dashboard` and :guilabel:`Workflows`
13
+tabs on the :guilabel:`Environments` page.
14
+
15
+See :ref:`workflows_manage` | `blueprint <https://blueprints.launchpad.net/fuel/+spec/ui-custom-graph>`__
16
+
17
+Deployment details overview
18
+~~~~~~~~~~~~~~~~~~~~~~~~~~~
19
+
20
+Enabled the capability to view details about deployments for specific
21
+OpenStack environments and their nodes in the Fuel web UI:
22
+
23
+* To view a deployment task in progress, click :guilabel:`Show Details`
24
+  under the deployment progress bar on the :guilabel:`Dashboard` tab.
25
+* To view information about a deployed OpenStack environment, go to
26
+  the :guilabel:`History` tab and select the required deployment.
27
+
28
+See :ref:`view_history` | `blueprint <https://blueprints.launchpad.net/fuel/+spec/ui-deployment-history>`__

+ 12
- 0
userdocs/release-notes/new-features/master-backup-restore.rst View File

@@ -0,0 +1,12 @@
1
+===================================
2
+Fuel Master node backup and restore
3
+===================================
4
+
5
+Added support for the backup and restore of the Fuel Master node features.
6
+You can use the backup archives to restore the Fuel Master node in case
7
+of a hardware failure or other system malfunction.
8
+
9
+See the Fuel User guide:
10
+
11
+* :ref:`back-up-fuel`
12
+* :ref:`restore-fuel`

+ 17
- 0
userdocs/release-notes/new-features/s3-api.rst View File

@@ -0,0 +1,17 @@
1
+======================================
2
+S3 API authentication through Keystone
3
+======================================
4
+
5
+Implemented the possibility to enable Keystone to authenticate queries
6
+to S3 API on RadosGW using the Fuel CLI and Fuel web UI.
7
+
8
+.. note::
9
+
10
+   Enablement of the Keystone authentication for S3 API increases the load
11
+   on the Keystone service. Consult with documentation and support on
12
+   mitigating the risks related with the high load of the Keystone service.
13
+
14
+See `LP1540426`_ | `spec`_
15
+
16
+.. _`LP1540426`: https://bugs.launchpad.net/mos/+bug/1540426
17
+.. _`spec`: https://specs.openstack.org/openstack/fuel-specs/specs/10.0/s3-keystone-integration.html

+ 21
- 0
userdocs/release-notes/new-features/snapshots-timmy.rst View File

@@ -0,0 +1,21 @@
1
+====================================================
2
+Creation of targeted diagnostic snapshots with Timmy
3
+====================================================
4
+
5
+Replaced Shotgun with Timmy, a diagnostic utility for OpenStack environments
6
+that simplifies and optimizes OpenStack troubleshooting.
7
+
8
+Timmy enables you to create a diagnostic snapshot of your OpenStack
9
+environment through CLI depending on your needs:
10
+
11
+* Gather logging information from a single node or a subset of nodes
12
+  filtered by an assigned role or a service running on the node.
13
+* Designate the time frame which logging information should cover.
14
+* Specify services, the logging information of which to be included into
15
+  a snapshot.
16
+* Specify a folder or a list of folders from where logging information
17
+  should be retrieved, filter the logging files included in that folders
18
+  by date and time, and include this logging information into the diagnostic
19
+  snapshot.
20
+
21
+See :ref:`create-snapshot` | `blueprint <https://blueprints.launchpad.net/fuel/+spec/shotgun-retirement>`__

+ 12
- 0
userdocs/release-notes/new-features/task-graphs.rst View File

@@ -0,0 +1,12 @@
1
+====================================================
2
+Data-driven workflows for basic environment actions
3
+====================================================
4
+
5
+In addition to a node deployment workflow, introduced a capability
6
+to execute workflows for the following basic actions in an environment:
7
+
8
+* Node provisioning
9
+* Node deletion
10
+* Environment verification, that is network configuration check
11
+
12
+See :ref:`workflow-intro` | `blueprint <https://blueprints.launchpad.net/fuel/+spec/graph-concept-extension>`__

+ 12
- 0
userdocs/release-notes/new-features/user-documentation.rst View File

@@ -0,0 +1,12 @@
1
+==================
2
+User documentation
3
+==================
4
+
5
+Fuel Newton includes a number of major user documentation updates:
6
+
7
+* :ref:`upgrade_intro`
8
+* :ref:`cli_comparison_matrix`
9
+* :ref:`workflow-intro`
10
+* :ref:`workflows_manage`
11
+* :ref:`create-snapshot`
12
+* :ref:`ug-troubleshooting`

+ 27
- 0
userdocs/release-notes/new-features/vmware-certificate.rst View File

@@ -0,0 +1,27 @@
1
+=====================================================
2
+Verification of the VMware vCenter server certificate
3
+=====================================================
4
+
5
+Added a capability to specify a Certificate Authority (CA) bundle file
6
+to use for verifying the VMware vCenter server certificate for
7
+the OpenStack Compute service, OpenStack Block Storage service, and
8
+OpenStack Image service.
9
+
10
+Depending on the needs of your environment, you can configure the VMware
11
+vCenter server certificate verification on the :guilabel:`VMware` tab in
12
+the Fuel web UI:
13
+
14
+* If you plan to deploy an environment for testing purposes or want
15
+  to speed up the deployment process, you can disable the certificate
16
+  verification by checking
17
+  :guilabel:`Bypass vCenter certificate verification`.
18
+
19
+* If VMware vCenter is using a self-signed certificate, upload a CA
20
+  certificate in the :guilabel:`CA file` field.
21
+  Leave :guilabel:`Bypass vCenter certificate verification` unchecked.
22
+
23
+* If a VMware vCenter server certificate is emitted by a known CA,
24
+  for example, GeoTrust, leave the :guilabel:`CA file` field empty
25
+  and :guilabel:`Bypass vCenter certificate verification` unchecked.
26
+
27
+See :ref:`configure-vmware-vcenter-settings`

+ 0
- 95
userdocs/release-notes/new_features.rst View File

@@ -1,95 +0,0 @@
1
-============
2
-New Features
3
-============
4
-
5
-Fuel Mitaka is the release of new features and bug fixes for
6
-the leading purpose-built open source deployment and management tool
7
-for OpenStack.
8
-
9
-Fuel Mitaka introduces a set of new features and enhancements.
10
-This section lists these improvements:
11
-
12
-* Plugin developers can now dynamically add configuration fields to their
13
-  plugins.
14
-  See `blueprint <https://blueprints.launchpad.net/fuel/+spec/dynamic-fields>`__.
15
-
16
-* Added ability to stop and restart environment deployment without resetting
17
-  the deployment process. See the :ref:`stop_deployment` section in the Fuel
18
-  User Guide.
19
-  This allows users to fix deployment errors and resume the deployment process
20
-  without having to start it over completely.
21
-  See `blueprint <https://blueprints.launchpad.net/fuel/+spec/graceful-stop-restart-deployment>`__.
22
-
23
-* Improved deployment orchestration to reduce deployment time and minimize
24
-  technical and architectural efforts through task-based deployment with Astute.
25
-  This further enables Fuel to provide the lifecycle management features such
26
-  as :guilabel:`Unlocked Settings Tab`.
27
-
28
-* Fuel plugins can now be managed on a deployed cloud through the Fuel web UI
29
-  in :guilabel:`Unlocked Settings Tab`:
30
-
31
-  * You can install plugins through the Fuel web UI.
32
-  * Plugins can insert tasks in deployment graphs.
33
-  * You can now change the settings of a plugin if supported. Consult with
34
-    the plugin developer if not sure.
35
-
36
-* Fuel now stores detailed information about all deployments. You can download
37
-  the actual cluster settings, network configuration, and serialized cluster
38
-  data.
39
-  See :ref:`view_history` and :ref:`deployment-information`.
40
-
41
-* You can now execute a particular deployment workflow with the ability to merge
42
-  it with the existing deployment workflows of the upstream master release.
43
-  This allows you to implement complex orchestrated workflows -- bugfixes
44
-  application, reference architecture altering, or even upgrades.
45
-  See :ref:`workflows_manage`.
46
-
47
-* Fuel now supports lifecycle management tasks based on the history of
48
-  cluster states. This data-driven feature allows the deployment engineers
49
-  and plugin developers that use Fuel library deployment tasks to introduce
50
-  expressions that can be computed within the context of cluster configuration.
51
-  You can now control the tasks assignment and execution depending on the
52
-  configuration or changes in the configuration.
53
-  See :ref:`data-driven`.
54
-
55
-* All deployment tasks that Fuel uses when configuring OpenStack are now
56
-  idempotent. This enables the lifecycle management features that require
57
-  re-running of deployment tasks with the updated input data in the
58
-  post-deployment stage of cloud lifecycle.
59
-  See `blueprint <https://blueprints.launchpad.net/fuel/+spec/granular-task-lcm-readiness>`__.
60
-
61
-* Fuel can now deploy UCA packages.
62
-  See `blueprint <https://blueprints.launchpad.net/fuel/+spec/deploy-with-uca-packages>`__.
63
-
64
-* Operators can now change OpenStack settings on the :guilabel:`Settings`
65
-  tab in Fuel web UI for the cloud that is already deployed and apply the
66
-  settings.
67
-  See `blueprint <https://blueprints.launchpad.net/fuel/+spec/granular-task-lcm-readiness>`__.
68
-
69
-* Fuel API now allows to manually set virtual IP address to any valid
70
-  IP address.
71
-  See `blueprint <https://blueprints.launchpad.net/fuel/+spec/allow-any-vip>`__.
72
-
73
-* The node roles panel on the Fuel web UI has been redesigned to accommodate
74
-  for the standard screen estate.
75
-  See `blueprint <https://blueprints.launchpad.net/fuel/+spec/redesign-of-node-roles-panel>`__.
76
-
77
-* Enabled separate node deployment and operating system provisioning in the
78
-  Fuel web UI.
79
-  This allows users to adjust configuration and fix errors on a specific node
80
-  or a subset of nodes without having to re-deploy or re-provision the entire
81
-  cloud environment.
82
-  See `blueprint <https://blueprints.launchpad.net/fuel/+spec/allow-choosing-nodes-for-provisioning-and-deployment>`__.
83
-
84
-* Enabled control groups management. OpenStack operators can configure
85
-  resource utilization thresholds for the OpenStack services and underlying
86
-  software components using ``cgroups``. Specifying optimal values helps
87
-  to increase performance and reliability of your cloud.
88
-  See :ref:`cgroups-intro`.
89
-
90
-* The OpenStack Application Catalog service is now also installable as a
91
-  plugin for Fuel. This plugin is designed to enable upgrading of the
92
-  OpenStack Application Catalog together with plugin installation. This plugin
93
-  update mechanism will be used to deliver future updates to the OpenStack
94
-  Application Catalog service.
95
-  See `Murano plugin for Fuel <https://github.com/openstack/fuel-plugin-murano>`__.

userdocs/release-notes/obtain_product.rst → userdocs/release-notes/obtain-product.rst View File


Loading…
Cancel
Save