Browse Source

Merge "Release notes for the Havana release"

Jenkins 5 years ago
parent
commit
737ef39e08
1 changed files with 254 additions and 0 deletions
  1. 254
    0
      doc/source/releases/2013_2.rst

+ 254
- 0
doc/source/releases/2013_2.rst View File

@@ -0,0 +1,254 @@
1
+=======================
2
+Horizon 2013.2 "Havana"
3
+=======================
4
+
5
+Release Overview
6
+================
7
+
8
+The Havana release cycle brings support for *three* new projects, plus
9
+significant new features for several existing projects. On top of that, many
10
+aspects of user experience have been improved for both end users and
11
+administrators. The community continues to grow and expand. The Havana release
12
+is solidly the best release of the OpenStack Dashboard project yet!
13
+
14
+Highlights
15
+==========
16
+
17
+New Features
18
+------------
19
+
20
+Heat
21
+~~~~
22
+
23
+The OpenStack Orchestration project (Heat) debuted in Havana, and Horizon
24
+delivers full support for managing your Heat stacks. Highlights include
25
+support for dynamic form generation from supported Heat template formats,
26
+stack topology visualizations, and full stack resource inspection.
27
+
28
+Ceilometer
29
+~~~~~~~~~~
30
+
31
+Also debuting in Havana is the OpenStack Metering project (Ceilometer). Initial
32
+support for Ceilometer is included in Horizon so that it is possible for an
33
+administrator to query the usage of the cloud through the OpenStack Dashboard
34
+and better understand how the system is functioning and being utilized.
35
+
36
+Domains, Groups, and More: Keystone v3 API Support
37
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
38
+
39
+With the OpenStack Identity Service (Keystone) v3 API fully fledged in the
40
+Havana release, Horizon has added full support for all the new features such
41
+as Domains and Groups, Role management and assignment to Domains and Groups,
42
+Domain-based authentication, and Domain context switching.
43
+
44
+Trove Databases
45
+~~~~~~~~~~~~~~~
46
+
47
+The OpenStack Database as a Service project (Trove) graduated from incubation
48
+in the Havana cycle, and thanks to their industriousness they delivered a
49
+set of panels for the OpenStack dashboard to allow for provisioning and managing
50
+your Trove databases and backups. Disclaimer: Given that Trove's first official
51
+release as an integrated project will not be until Icehouse this feature should
52
+still be considered experimental and may be subject to change.
53
+
54
+Nova Features
55
+~~~~~~~~~~~~~
56
+
57
+The number of OpenStack Compute (Nova) features that are supported in Horizon
58
+continues to grow. New features in the Havana release include:
59
+
60
+* Editable default quotas.
61
+* The ability for an administrator to reset the password of a server/instance.
62
+* Availablity zone support.
63
+* Improved region support.
64
+* Instance resizing.
65
+* Improved boot-from-volume support.
66
+* Per-project flavor support.
67
+
68
+All of these provide a richer set of options for controlling where, when and how
69
+instances are launched, and improving how they're managed once they're up and
70
+running.
71
+
72
+Neutron Features
73
+~~~~~~~~~~~~~~~~
74
+
75
+A number of important new OpenStack Networking (Neutron) features are showcased
76
+in the Havana release, most notably:
77
+
78
+* VPN as a Service.
79
+* Firewall as a Service.
80
+* Editable and interactive network topology visualizations.
81
+* Full security group and quota parity between Neutron and Nova network.
82
+
83
+These features allow for tremendous flexibility when constructing
84
+software-defined networks for your cloud using Neutron.
85
+
86
+
87
+User Experience Improvements
88
+----------------------------
89
+
90
+Self-Service Password Change
91
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~
92
+
93
+Empowered by changes to the Keystone API, users can now change their own
94
+passwords without the need to involve an administrator. This is more secure and
95
+takes the hassle out of things for everyone.
96
+
97
+Better Admin Information Architecture
98
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
99
+
100
+Several sections of the Admin dashboard have been rearranged to more logically
101
+group information together. Additionally, new sources of information have been
102
+added to allow Admins to better understand the state of the hosts in the cloud
103
+and their relationship to host aggregates, availability zones, etc.
104
+
105
+Improved Messaging To Users On Logout
106
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
107
+
108
+Several new indicators have been added to inform users why they've been logged
109
+out when they land on the login screen unexpectedly. These indicators make it
110
+clear whether the user's session has expired, they timed out due to inactivity,
111
+or they are not authorized for the section of the dashboard they attempted to
112
+access.
113
+
114
+Security Group Rule Templates
115
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
116
+
117
+Since there are many very common security group rules which users tediously
118
+re-add each time (rules for SSH and ping, for example) the Horizon team has
119
+added pre-configured templates for common rules which a user can select and
120
+add to their security group with two clicks. These rules are configurable
121
+via the ``SECURITY_GROUP_RULES`` setting.
122
+
123
+
124
+Community
125
+---------
126
+
127
+Translation Team
128
+~~~~~~~~~~~~~~~~
129
+
130
+The OpenStack Translations team came fully into its own during the Havana cycle
131
+and the quality of the translations in Horizon are the best yet by far.
132
+Congratulations to that team for their success in building the community that
133
+started primarily within the OpenStack Dashboard project.
134
+
135
+User Experience Group
136
+~~~~~~~~~~~~~~~~~~~~~
137
+
138
+A fledgling OpenStack User Experience Group formed during the Havana cycle with
139
+the mission of improving UX throughout OpenStack. They have quickly made
140
+themselves indispensable to the process of designing and improving features in
141
+the OpenStack Dashboard. Expect significant future improvement in User
142
+Experience now that there are dedicated people actively collaborating in the
143
+open to raise the bar.
144
+
145
+
146
+Under The Hood
147
+--------------
148
+
149
+Less Complicated LESS Compilation: No More NodeJS
150
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
151
+
152
+Due to outcry from various parties, and made possible by improvements in the
153
+Python community's support for LESS, Horizon has removed all traces of NodeJS
154
+from the project. We now use the ``lesscpy`` module to compile our LESS into
155
+the final stylesheets. This should not affect most users in any way, but it
156
+should make life easier for downstream distributions and the like.
157
+
158
+Role-Based Access Controls
159
+~~~~~~~~~~~~~~~~~~~~~~~~~~
160
+
161
+Horizon has begun the transition to using the other OpenStack projects'
162
+``policy.json`` files to enforce access controls in the dashboard if the files
163
+are provided. This means access controls are more configurable and can be kept
164
+in sync between the originating project and Horizon. Currently this is only
165
+supported for Keystone and parts of Nova's policy files. Full support will
166
+come in the next release. You will need to set the ``POLICY_FILES_PATH`` and
167
+``POLICY_FILES`` settings in order to enable this feature.
168
+
169
+
170
+Other Improvements and Fixes
171
+----------------------------
172
+
173
+* Swift container and object metadata are now supported.
174
+* New visualizations for utilization and quotas.
175
+* The Cisco N1K Router plugin's additional features are available through a
176
+  special additional dashboard when enabled and supported in Neutron.
177
+* Support for self-signed or other specified SSL certificate checking.
178
+* Glance image types are now configurable.
179
+* Sorting has been improved in many places through the dashboard.
180
+* API call efficiency optimizations.
181
+* Required fields in forms are now better indicated.
182
+* Session timeout can now be enabled to log out the user after a period of
183
+  inactivity as a security feature.
184
+* Significant PEP8 and code quality compliance improvements.
185
+* Hundreds of bugfixes and minor user experience improvements.
186
+
187
+
188
+Upgrade Information
189
+===================
190
+
191
+Allowed Hosts
192
+-------------
193
+
194
+For production deployments of Horizon you must add the ``ALLOWED_HOSTS``
195
+setting to your ``settings.py`` or ``local_settings.py`` file. This setting
196
+was added in Django 1.5 and is an important security feature. For more
197
+information on it please consult the ``local_settings.py.example`` file
198
+or Django's documentation.
199
+
200
+Enabling Keystone and Neutron Features
201
+--------------------------------------
202
+
203
+If you have existing configurations for the ``OPENSTACK_KEYSTONE_BACKEND``
204
+or ``OPENSTACK_NEUTRON_NETWORK`` settings, you will want to consult the
205
+``local_settings.example.py`` file for information on the new options that
206
+have been added. Existing configurations will continue to work, but may not
207
+have the correct keys to enable some of the new features in Havana.
208
+
209
+
210
+Known Issues and Limitations
211
+============================
212
+
213
+Session Creation and Health Checks
214
+----------------------------------
215
+
216
+If you use a health monitoring service that pings the home page combined with
217
+a database-backed session backend you may experience excessive session creation.
218
+This issue is slated to be fixed soon, but in the interim the recommended
219
+solution is to write a periodic job that deletes expired sessions from your
220
+session store on a regular basis.
221
+
222
+Deleting large numbers of resources simultaneously
223
+--------------------------------------------------
224
+
225
+Using the "select all" checkbox to delete large numbers of resources at once
226
+can cause network timeouts (depending on configuration). This is due to the
227
+underlying APIs not supporting bulk-deletion natively, and consequently Horizon
228
+has to send requests to delete each resource individually behind the scenes.
229
+
230
+Conflicting Security Group Names With Neutron
231
+---------------------------------------------
232
+
233
+Whereas Nova Network uses only the name of a security group when specifying
234
+security groups at instance launch time, Neutron can accept either a name or
235
+a UUID. In order to support both, Horizon passes in the name of the selected
236
+security groups. However, due to some data-isolation issues in Neutron there is
237
+an issue that can arise if an admin user tries to specify a security group with
238
+the same name as another security group in a different project which they also
239
+have access to. Neutron will find multiple matches for the security group
240
+name and will fail to launch the instance. The current workaround is to treat
241
+security group names as unique for admin users.
242
+
243
+
244
+Backwards Compatibility
245
+=======================
246
+
247
+The Havana Horizon release should be fully compatible with both Havana and
248
+Grizzly versions of the rest of the OpenStack integrated projects (Nova, Swift,
249
+etc.). New features in other OpenStack projects which did not exist in Grizzly
250
+will obviously only work in Horizon if the rest of the stack supports them as
251
+well.
252
+
253
+Overall, great effort has been made to maintain compatibility for
254
+third-party developers who have built on Horizon so far.

Loading…
Cancel
Save