This repository has been archived by the owner on Apr 18, 2019. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 100
/
CHANGELOG.html
869 lines (809 loc) · 61 KB
/
CHANGELOG.html
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
309
310
311
312
313
314
315
316
317
318
319
320
321
322
323
324
325
326
327
328
329
330
331
332
333
334
335
336
337
338
339
340
341
342
343
344
345
346
347
348
349
350
351
352
353
354
355
356
357
358
359
360
361
362
363
364
365
366
367
368
369
370
371
372
373
374
375
376
377
378
379
380
381
382
383
384
385
386
387
388
389
390
391
392
393
394
395
396
397
398
399
400
401
402
403
404
405
406
407
408
409
410
411
412
413
414
415
416
417
418
419
420
421
422
423
424
425
426
427
428
429
430
431
432
433
434
435
436
437
438
439
440
441
442
443
444
445
446
447
448
449
450
451
452
453
454
455
456
457
458
459
460
461
462
463
464
465
466
467
468
469
470
471
472
473
474
475
476
477
478
479
480
481
482
483
484
485
486
487
488
489
490
491
492
493
494
495
496
497
498
499
500
501
502
503
504
505
506
507
508
509
510
511
512
513
514
515
516
517
518
519
520
521
522
523
524
525
526
527
528
529
530
531
532
533
534
535
536
537
538
539
540
541
542
543
544
545
546
547
548
549
550
551
552
553
554
555
556
557
558
559
560
561
562
563
564
565
566
567
568
569
570
571
572
573
574
575
576
577
578
579
580
581
582
583
584
585
586
587
588
589
590
591
592
593
594
595
596
597
598
599
600
601
602
603
604
605
606
607
608
609
610
611
612
613
614
615
616
617
618
619
620
621
622
623
624
625
626
627
628
629
630
631
632
633
634
635
636
637
638
639
640
641
642
643
644
645
646
647
648
649
650
651
652
653
654
655
656
657
658
659
660
661
662
663
664
665
666
667
668
669
670
671
672
673
674
675
676
677
678
679
680
681
682
683
684
685
686
687
688
689
690
691
692
693
694
695
696
697
698
699
700
701
702
703
704
705
706
707
708
709
710
711
712
713
714
715
716
717
718
719
720
721
722
723
724
725
726
727
728
729
730
731
732
733
734
735
736
737
738
739
740
741
742
743
744
745
746
747
748
749
750
751
752
753
754
755
756
757
758
759
760
761
762
763
764
765
766
767
768
769
770
771
772
773
774
775
776
777
778
779
780
781
782
783
784
785
786
787
788
789
790
791
792
793
794
795
796
797
798
799
800
801
802
803
804
805
806
807
808
809
810
811
812
813
814
815
816
817
818
819
820
821
822
823
824
825
826
827
828
829
830
831
832
833
834
835
836
837
838
839
840
841
842
843
844
845
846
847
848
849
850
851
852
853
854
855
856
857
858
859
860
861
862
863
864
865
866
867
868
869
<!DOCTYPE html>
<html>
<head>
<title>CHANGELOG</title>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
<style type="text/css">
/* GitHub stylesheet for MarkdownPad (http://markdownpad.com) */
/* Author: Nicolas Hery - http://nicolashery.com */
/* Version: b13fe65ca28d2e568c6ed5d7f06581183df8f2ff */
/* Source: https://github.com/nicolahery/markdownpad-github */
/* RESET
=============================================================================*/
html, body, div, span, applet, object, iframe, h1, h2, h3, h4, h5, h6, p, blockquote, pre, a, abbr, acronym, address, big, cite, code, del, dfn, em, img, ins, kbd, q, s, samp, small, strike, strong, sub, sup, tt, var, b, u, i, center, dl, dt, dd, ol, ul, li, fieldset, form, label, legend, table, caption, tbody, tfoot, thead, tr, th, td, article, aside, canvas, details, embed, figure, figcaption, footer, header, hgroup, menu, nav, output, ruby, section, summary, time, mark, audio, video {
margin: 0;
padding: 0;
border: 0;
}
/* BODY
=============================================================================*/
body {
font-family: Helvetica, arial, freesans, clean, sans-serif;
font-size: 14px;
line-height: 1.6;
color: #333;
background-color: #fff;
padding: 20px;
max-width: 960px;
margin: 0 auto;
}
body>*:first-child {
margin-top: 0 !important;
}
body>*:last-child {
margin-bottom: 0 !important;
}
/* BLOCKS
=============================================================================*/
p, blockquote, ul, ol, dl, table, pre {
margin: 15px 0;
}
/* HEADERS
=============================================================================*/
h1, h2, h3, h4, h5, h6 {
margin: 20px 0 10px;
padding: 0;
font-weight: bold;
-webkit-font-smoothing: antialiased;
}
h1 tt, h1 code, h2 tt, h2 code, h3 tt, h3 code, h4 tt, h4 code, h5 tt, h5 code, h6 tt, h6 code {
font-size: inherit;
}
h1 {
font-size: 28px;
color: #000;
}
h2 {
font-size: 24px;
border-bottom: 1px solid #ccc;
color: #000;
}
h3 {
font-size: 18px;
}
h4 {
font-size: 16px;
}
h5 {
font-size: 14px;
}
h6 {
color: #777;
font-size: 14px;
}
body>h2:first-child, body>h1:first-child, body>h1:first-child+h2, body>h3:first-child, body>h4:first-child, body>h5:first-child, body>h6:first-child {
margin-top: 0;
padding-top: 0;
}
a:first-child h1, a:first-child h2, a:first-child h3, a:first-child h4, a:first-child h5, a:first-child h6 {
margin-top: 0;
padding-top: 0;
}
h1+p, h2+p, h3+p, h4+p, h5+p, h6+p {
margin-top: 10px;
}
/* LINKS
=============================================================================*/
a {
color: #4183C4;
text-decoration: none;
}
a:hover {
text-decoration: underline;
}
/* LISTS
=============================================================================*/
ul, ol {
padding-left: 30px;
}
ul li > :first-child,
ol li > :first-child,
ul li ul:first-of-type,
ol li ol:first-of-type,
ul li ol:first-of-type,
ol li ul:first-of-type {
margin-top: 0px;
}
ul ul, ul ol, ol ol, ol ul {
margin-bottom: 0;
}
dl {
padding: 0;
}
dl dt {
font-size: 14px;
font-weight: bold;
font-style: italic;
padding: 0;
margin: 15px 0 5px;
}
dl dt:first-child {
padding: 0;
}
dl dt>:first-child {
margin-top: 0px;
}
dl dt>:last-child {
margin-bottom: 0px;
}
dl dd {
margin: 0 0 15px;
padding: 0 15px;
}
dl dd>:first-child {
margin-top: 0px;
}
dl dd>:last-child {
margin-bottom: 0px;
}
/* CODE
=============================================================================*/
pre, code, tt {
font-size: 12px;
font-family: Consolas, "Liberation Mono", Courier, monospace;
}
code, tt {
margin: 0 0px;
padding: 0px 0px;
white-space: nowrap;
border: 1px solid #eaeaea;
background-color: #f8f8f8;
border-radius: 3px;
}
pre>code {
margin: 0;
padding: 0;
white-space: pre;
border: none;
background: transparent;
}
pre {
background-color: #f8f8f8;
border: 1px solid #ccc;
font-size: 13px;
line-height: 19px;
overflow: auto;
padding: 6px 10px;
border-radius: 3px;
}
pre code, pre tt {
background-color: transparent;
border: none;
}
kbd {
-moz-border-bottom-colors: none;
-moz-border-left-colors: none;
-moz-border-right-colors: none;
-moz-border-top-colors: none;
background-color: #DDDDDD;
background-image: linear-gradient(#F1F1F1, #DDDDDD);
background-repeat: repeat-x;
border-color: #DDDDDD #CCCCCC #CCCCCC #DDDDDD;
border-image: none;
border-radius: 2px 2px 2px 2px;
border-style: solid;
border-width: 1px;
font-family: "Helvetica Neue",Helvetica,Arial,sans-serif;
line-height: 10px;
padding: 1px 4px;
}
/* QUOTES
=============================================================================*/
blockquote {
border-left: 4px solid #DDD;
padding: 0 15px;
color: #777;
}
blockquote>:first-child {
margin-top: 0px;
}
blockquote>:last-child {
margin-bottom: 0px;
}
/* HORIZONTAL RULES
=============================================================================*/
hr {
clear: both;
margin: 15px 0;
height: 0px;
overflow: hidden;
border: none;
background: transparent;
border-bottom: 4px solid #ddd;
padding: 0;
}
/* TABLES
=============================================================================*/
table th {
font-weight: bold;
}
table th, table td {
border: 1px solid #ccc;
padding: 6px 13px;
}
table tr {
border-top: 1px solid #ccc;
background-color: #fff;
}
table tr:nth-child(2n) {
background-color: #f8f8f8;
}
/* IMAGES
=============================================================================*/
img {
max-width: 100%
}
</style>
</head>
<body>
<h2>2.1.0 Final</h2>
<h2>Special Notes</h2>
<ul>
<li>This is 2.1 final release, we made a lot of tests, especially on importing cluster and infernalis supporting. </li>
<li>8 new features are added, and 27 bugs are fixed in this release.</li>
<li>
Spotlights:
<ul>
<li>Import existing cluster (see "Cluster Management\Import Cluster"), user could import existing cluster, and monitor its status, or manipulate it by adding/removing servers or devices.</li>
<li>Manage storage group (see "Cluster Management\Manage Storage group"), user could see the crushmap hierarchy, and understand storage group coverage on the topology.</li>
<li>Manage zone (see "Cluster Management\Manage zone"), user could add new zones then associates servers to those new zones.</li>
</ul>
</li>
</ul>
<h2>New Features</h2>
<ul>
<li><a href="https://01.org/jira/browse/Key">Key</a> Summary</li>
<li><a href="https://01.org/jira/browse/VSM-53">VSM-53</a> Allow VSM to attach to and manage an existing Ceph cluster</li>
<li><a href="https://01.org/jira/browse/VSM-185">VSM-185</a> show SMART information for storage devices</li>
<li><a href="https://01.org/jira/browse/VSM-409">VSM-409</a> add "storage group" column on OSD list page</li>
<li><a href="https://01.org/jira/browse/VSM-418">VSM-418</a> Add support to Ceph infernalis</li>
<li><a href="https://01.org/jira/browse/VSM-385">VSM-385</a> Change PG count even after ceph cluster deployed</li>
<li><a href="https://01.org/jira/browse/VSM-337">VSM-337</a> Upgrade: expect to upgrade from 1.0 to 2.0</li>
<li><a href="https://01.org/jira/browse/VSM-407">VSM-407</a> suggest to split disk status and capacity utilization in different column in device list page</li>
<li><a href="https://01.org/jira/browse/VSM-396">VSM-396</a> Support DNS lookup beside current /etc/hosts lookup</li>
</ul>
<h2>Resolved bugs</h2>
<ul>
<li><a href="https://01.org/jira/browse/Key">Key</a> Summary</li>
<li><a href="https://01.org/jira/browse/VSM-427">VSM-427</a> when updating storage group, it's required to add a hour glass.</li>
<li><a href="https://01.org/jira/browse/VSM-428">VSM-428</a> if storage group is referenced by some pools, it still allows to update its marker.</li>
<li><a href="https://01.org/jira/browse/VSM-423">VSM-423</a> when creating new pool, after spinner is disappeared, the pool is not showing up</li>
<li><a href="https://01.org/jira/browse/VSM-419">VSM-419</a> Stop Server error in 2.1 beta</li>
<li><a href="https://01.org/jira/browse/VSM-172">VSM-172</a> cluster.manifest - request for improvement from Marcin</li>
<li><a href="https://01.org/jira/browse/VSM-261">VSM-261</a> when executing vsm-controller, a TypeError raises</li>
<li><a href="https://01.org/jira/browse/VSM-330">VSM-330</a> When upgrading from Firefly to Giant, the upgrade complains missing python-rados package</li>
<li><a href="https://01.org/jira/browse/VSM-344">VSM-344</a> after a few times install, clean-up, reinstall, we have seem some "eaddrinuse" errors on starting rabbitmq</li>
<li><a href="https://01.org/jira/browse/VSM-354">VSM-354</a> when 'create cluster' page opened,other pages still can be opened</li>
<li><a href="https://01.org/jira/browse/VSM-371">VSM-371</a> When installing with dependent packages pre-prepared, the installer will stop with complains</li>
<li><a href="https://01.org/jira/browse/VSM-395">VSM-395</a> Remove then restore an OSD, the OSD can't hit to in-up state again.</li>
<li><a href="https://01.org/jira/browse/VSM-422">VSM-422</a> stop/start servers should display an "hour glass" during operation</li>
<li><a href="https://01.org/jira/browse/VSM-425">VSM-425</a> Dashboard Monitor widget: boxes too small for hostname font</li>
<li><a href="https://01.org/jira/browse/VSM-426">VSM-426</a> blocked on process indicator</li>
<li><a href="https://01.org/jira/browse/VSM-388">VSM-388</a> VSM fails to create a Monitor daemon (after clicking OK in a popup warning window)</li>
<li><a href="https://01.org/jira/browse/VSM-429">VSM-429</a> VSM agent fail to save ceph.conf when size is above 127 KB.</li>
<li><a href="https://01.org/jira/browse/VSM-225">VSM-225</a> VSM Creates Very Small pg<em>num and pg.</em>num Size for EC Pool</li>
<li><a href="https://01.org/jira/browse/VSM-420">VSM-420</a> VSM 2.0 is<em>server</em>manifest_error</li>
<li><a href="https://01.org/jira/browse/VSM-421">VSM-421</a> During cluster import, vsm agents don't have sufficient rights to /var/lib/ceph</li>
<li><a href="https://01.org/jira/browse/VSM-380">VSM-380</a> it would be nice if install.sh script should take care of agent-tokens, even at the case restart install.sh with prior errors.</li>
<li><a href="https://01.org/jira/browse/VSM-406">VSM-406</a> servers can't be stopped after cluster imported</li>
<li><a href="https://01.org/jira/browse/VSM-410">VSM-410</a> The scrollbar of manage server is missing now.</li>
<li><a href="https://01.org/jira/browse/VSM-413">VSM-413</a> Manage device, click new, popup “internal ERROR” on the top right corner.</li>
<li><a href="https://01.org/jira/browse/VSM-416">VSM-416</a> at import cluster page, the scroll bar for crushmap and ceph.conf can scroll</li>
<li><a href="https://01.org/jira/browse/VSM-417">VSM-417</a> when creating cluster, the monitor status is incorrect</li>
<li><a href="https://01.org/jira/browse/VSM-387">VSM-387</a> ceph version conflicts when reinstall vsm at the case the previous one made ceph upgrade</li>
<li><a href="https://01.org/jira/browse/VSM-377">VSM-377</a> VSM installation failure</li>
</ul>
<h2>Known issues</h2>
<h2>2.1.0 (build 309)</h2>
<h2>Special Notes</h2>
<ul>
<li>This is 2.1 beta 1 release, only very limited tests on it. </li>
<li>27 new features are added, and 51 bugs are fixed in this release.</li>
</ul>
<h2>New Features</h2>
<ul>
<li><a href="https://01.org/jira/browse/VSM-66">VSM-66</a> VSM interoperates with Ceph update</li>
<li><a href="https://01.org/jira/browse/VSM-226">VSM-226</a> Need Documentation for VSM REST API</li>
<li><a href="https://01.org/jira/browse/VSM-78">VSM-78</a> Integration with Cinder capacity filter</li>
<li><a href="https://01.org/jira/browse/VSM-58">VSM-58</a> Calamari Integration</li>
<li><a href="https://01.org/jira/browse/VSM-56">VSM-56</a> Report total RBD Image commit</li>
<li><a href="https://01.org/jira/browse/VSM-32">VSM-32</a> support to define storage group with storage node or rack as unit</li>
<li><a href="https://01.org/jira/browse/VSM-376">VSM-376</a> support to label device with by-uuid</li>
<li><a href="https://01.org/jira/browse/VSM-382">VSM-382</a> undeploy/redeploy ceph cluster</li>
<li><a href="https://01.org/jira/browse/VSM-389">VSM-389</a> Need to automatically retrieve the osd info from existing cluster.</li>
<li><a href="https://01.org/jira/browse/VSM-386">VSM-386</a> batch add osds</li>
<li><a href="https://01.org/jira/browse/VSM-355">VSM-355</a> there are some used disk paths list in the data path field and journal dik path field on page 'add new osd'</li>
<li><a href="https://01.org/jira/browse/VSM-90">VSM-90</a> Monitor Status page improvements.</li>
<li><a href="https://01.org/jira/browse/VSM-96">VSM-96</a> UI responsiveness</li>
<li><a href="https://01.org/jira/browse/VSM-98">VSM-98</a> Server Configuration Change.</li>
<li><a href="https://01.org/jira/browse/VSM-341">VSM-341</a> expect to have some utilties to help make automation tests.</li>
<li><a href="https://01.org/jira/browse/VSM-352">VSM-352</a> servermgmt page autorefrush too frequent</li>
<li><a href="https://01.org/jira/browse/VSM-372">VSM-372</a> narrow the attack surface from VSM to Openstack cluster</li>
<li><a href="https://01.org/jira/browse/VSM-373">VSM-373</a> at adding new OSD page, expect to list device name like /dev/sdd1 instead of pci bus address.</li>
<li><a href="https://01.org/jira/browse/VSM-140">VSM-140</a> Ceph Development (Epic 6): Prototype Calamari/VSM dashboard implementation</li>
<li><a href="https://01.org/jira/browse/VSM-88">VSM-88</a> On monitor status page, report what server each monitor is running on.</li>
<li><a href="https://01.org/jira/browse/VSM-242">VSM-242</a> Allow user to modify ceph.conf outside VSM</li>
<li><a href="https://01.org/jira/browse/VSM-15">VSM-15</a> VSM-backup prompt info not correct</li>
<li><a href="https://01.org/jira/browse/VSM-124">VSM-124</a> [CDEK-1852] VSM | adding possibility to manipulate ceph values in cluster.manifest file</li>
<li><a href="https://01.org/jira/browse/VSM-4">VSM-4</a> Average Response Time" missing in dashboard Overview panel "VSM Status" section.</li>
<li><a href="https://01.org/jira/browse/VSM-184">VSM-184</a> add automated script to help deploy VSM on multiple nodes</li>
<li><a href="https://01.org/jira/browse/VSM-159">VSM-159</a> add issue reporting tool</li>
<li><a href="https://01.org/jira/browse/VSM-156">VSM-156</a> add sanity check tool to help identify potential issues before or after deployment</li>
</ul>
<h2>Resolved bugs</h2>
<ul>
<li><a href="https://01.org/jira/browse/VSM-349">VSM-349</a> click 'create cluster',I got the tip:there are some zones no monitor created</li>
<li><a href="https://01.org/jira/browse/VSM-411">VSM-411</a> When create cluster, there are four servers and choose all servers as storage node but only three as monitors, the cluster can not be created sucessfully.</li>
<li><a href="https://01.org/jira/browse/VSM-329">VSM-329</a> Remove Monitors button in Manage Servers hangs when Monitor node also has MDS daemon</li>
<li><a href="https://01.org/jira/browse/VSM-400">VSM-400</a> the UI of all server operator pages will appear "loading" without any operation</li>
<li><a href="https://01.org/jira/browse/VSM-356">VSM-356</a> I got warning info means that the number of pg in each osd is too large after upgrade ceph from a lower version to hammar</li>
<li><a href="https://01.org/jira/browse/VSM-397">VSM-397</a> mysqld takes up 100% CPU on one core and cause VSM dashboard to become unusable</li>
<li><a href="https://01.org/jira/browse/VSM-412">VSM-412</a> After remove server or remove monitor, failed to add the monitor back.</li>
<li><a href="https://01.org/jira/browse/VSM-391">VSM-391</a> the "ceph df" number is not consistent with pool quota</li>
<li><a href="https://01.org/jira/browse/VSM-399">VSM-399</a> the UI messy of the manage servers page</li>
<li><a href="https://01.org/jira/browse/VSM-402">VSM-402</a> after stop server, then start server, the osd tree changes</li>
<li><a href="https://01.org/jira/browse/VSM-392">VSM-392</a> Have removed the volume from the openstack, but from the vsm rbd status page, the rbd list still include the volume</li>
<li><a href="https://01.org/jira/browse/VSM-384">VSM-384</a> stuck at restart all ceph servers after stopped them all from UI</li>
<li><a href="https://01.org/jira/browse/VSM-394">VSM-394</a> present more than one pool to openstack cinder, it always creates volumes on a pool</li>
<li><a href="https://01.org/jira/browse/VSM-321">VSM-321</a> no upstart mechanism used for ubuntu when controlling ceph service</li>
<li><a href="https://01.org/jira/browse/VSM-336">VSM-336</a> On Dashboard, even no cluster is created, the VSM version and uptime should be displayed</li>
<li><a href="https://01.org/jira/browse/VSM-24">VSM-24</a> [CDEK-1661] VSM Dashboard | Manage Servers | Reset server status - works not correctly.</li>
<li><a href="https://01.org/jira/browse/VSM-365">VSM-365</a> Creating Cluster stucks at ceph.conf creation when running VSM on CentOS 7.1</li>
<li><a href="https://01.org/jira/browse/VSM-19">VSM-19</a> CDEK-1613] VSM | Reset Server Status button - return Error:Network error</li>
<li><a href="https://01.org/jira/browse/VSM-379">VSM-379</a> Trace back in browser when using reset server status action buttons</li>
<li><a href="https://01.org/jira/browse/VSM-381">VSM-381</a> run diamond through service instead of current process launching</li>
<li><a href="https://01.org/jira/browse/VSM-378">VSM-378</a> Performance data is retrieved from outside nodes</li>
<li><a href="https://01.org/jira/browse/VSM-374">VSM-374</a> the down server is not reflected in VSM</li>
<li><a href="https://01.org/jira/browse/VSM-375">VSM-375</a> Malformed JSON in 'Integrate Cluster' function</li>
<li><a href="https://01.org/jira/browse/VSM-366">VSM-366</a> the password for openstack access is shown as plain text</li>
<li><a href="https://01.org/jira/browse/VSM-312">VSM-312</a> vsm-node sets node status="Need more IP" if a Monitor only node does not have a cluster IP address..</li>
<li><a href="https://01.org/jira/browse/VSM-367">VSM-367</a> can't create cluster at public cloud environment</li>
<li><a href="https://01.org/jira/browse/VSM-368">VSM-368</a> The default password is not following the same password policy to include uppercase and digitals.</li>
<li><a href="https://01.org/jira/browse/VSM-369">VSM-369</a> Change password: "!" doesnt' support in password even prompt message says OK</li>
<li><a href="https://01.org/jira/browse/VSM-244">VSM-244</a> Internal server error when installing v1.1</li>
<li><a href="https://01.org/jira/browse/VSM-224">VSM-224</a> Controller node error in /var/log/httpd/error_log - constantly ongoing messages [error] <Response [200]></li>
<li><a href="https://01.org/jira/browse/VSM-239">VSM-239</a> with automatic deployment, the execution is blocked at asking if start mysql service</li>
<li><a href="https://01.org/jira/browse/VSM-193">VSM-193</a> hard-coded cluster id</li>
<li><a href="https://01.org/jira/browse/VSM-179">VSM-179</a> keep ceph.conf up to date when executing "remove server" operations.</li>
<li><a href="https://01.org/jira/browse/VSM-176">VSM-176</a> SSL certificate password is stored in a plain text file</li>
<li><a href="https://01.org/jira/browse/VSM-177">VSM-177</a> wrong /etc/fstab entry for osd device mount point</li>
<li><a href="https://01.org/jira/browse/VSM-166">VSM-166</a> cluster<em>manifest sanity check program gives incorrect advice for auth</em>keys</li>
<li><a href="https://01.org/jira/browse/VSM-171">VSM-171</a> [CDEK1672] VSM_CLI | list shows Admin network in Public IP section</li>
<li><a href="https://01.org/jira/browse/VSM-168">VSM-168</a> [CDEK1800] VSM_CLI | remove mds - doesn't update vsm database</li>
<li><a href="https://01.org/jira/browse/VSM-121">VSM-121</a> Storage node unable to connect to controller although network is OK and all setting correct</li>
<li><a href="https://01.org/jira/browse/VSM-123">VSM-123</a> Storage node will not be able to contact controller node to install if http proxy set</li>
<li><a href="https://01.org/jira/browse/VSM-260">VSM-260</a> the check<em>network in server</em>manifest will be wrong when it has a single network card</li>
<li><a href="https://01.org/jira/browse/VSM-236">VSM-236</a> no way to check manifest correctness after editing them</li>
<li><a href="https://01.org/jira/browse/VSM-233">VSM-233</a> console blocks when running automatic installation procedure</li>
<li><a href="https://01.org/jira/browse/VSM-33">VSM-33</a> negative update time in RBD list</li>
<li><a href="https://01.org/jira/browse/VSM-216">VSM-216</a> Add storage group requires at least 3 nodes</li>
<li><a href="https://01.org/jira/browse/VSM-113">VSM-113</a> [CDEK-1835] VSM | /var/log/httpd/error_log - constantly ongoing messages [error] <Response [200]></li>
<li><a href="https://01.org/jira/browse/VSM-51">VSM-51</a> Install Fails for VSM 0.8.0 Engineering Build Release</li>
<li><a href="https://01.org/jira/browse/VSM-29">VSM-29</a> vsm-agent process causes high i/o on os disk</li>
<li><a href="https://01.org/jira/browse/VSM-230">VSM-230</a> when presenting pool to openstack, cache tiering pools should be listed.</li>
<li><a href="https://01.org/jira/browse/VSM-207">VSM-207</a> can't assume eth0 device name</li>
<li><a href="https://01.org/jira/browse/VSM-26">VSM-26</a> [CDEK-1664] VSM | Not possible to replace node if ceph contain only 3 nodes.</li>
</ul>
<h2>Known issues</h2>
<p>- </p>
<h2>2.1.0 (build 281)</h2>
<h2>Special Notes</h2>
<ul>
<li>This is 2.1 alpha 1 release, only very limited tests on it. </li>
<li>
Some spotlights:
<ul>
<li>
Manage existing cluster through "Cluster Management\Import Cluster"
<ol>
<li>applicable to 2.1 alpha 1.</li>
<li>deploy a ceph cluster external (maybe there is already one running)</li>
<li>deploy VSM with agents deployed on each ceph node with appropriate role defined.</li>
<li>
in VSM web ui:
<ol>
<li>navigate to "Cluster Management\Import Cluster"</li>
<li>you should see all ceph nodes listed.</li>
<li>click "import cluster", then we will see an new page where it asks for crushmap and ceph.conf</li>
</ol>
</li>
<li>
there are two approaches to get crushmap:
<ol>
<li>paste crushmap directly into the text box under "Crushmap"</li>
<li>click "Auto Detect", then a dialog will pop up, you'd select one monitor host, and point where is the monitor keyring file on the monitor host.</li>
</ol>
</li>
<li>for ceph.conf, <strong>we see some ceph.conf doesn't include osd information, if this is the case, you'd manually add them into ceph.conf.</strong></li>
<li>when crushmap and ceph.conf are ready, click "validate" to see if all can pass. If yes, you could click "submit", if succeed, the message tip will show up to say the import is successful.</li>
<li>wait for a few minutes before the status gets synced, then you will see the cluster status.</li>
</ol>
</li>
<li>
Crushmap management
<ol>
<li>only draft UI, not ready.</li>
</ol>
</li>
</ul>
</li>
<li>16 new features are added, and 39 bugs are fixed till this release.</li>
</ul>
<h2>New Features</h2>
<ul>
<li><a href="https://01.org/jira/browse/VSM-355">VSM-355</a> there are some used disk paths list in the data path field and journal dik path field on page 'add new osd'</li>
<li><a href="https://01.org/jira/browse/VSM-90">VSM-90</a> Monitor Status page improvements.</li>
<li><a href="https://01.org/jira/browse/VSM-96">VSM-96</a> UI responsiveness</li>
<li><a href="https://01.org/jira/browse/VSM-98">VSM-98</a> Server Configuration Change.</li>
<li><a href="https://01.org/jira/browse/VSM-352">VSM-352</a> servermgmt page autorefrush too frequent</li>
<li><a href="https://01.org/jira/browse/VSM-372">VSM-372</a> narrow the attack surface from VSM to Openstack cluster</li>
<li><a href="https://01.org/jira/browse/VSM-373">VSM-373</a> at adding new OSD page, expect to list device name like /dev/sdd1 instead of pci bus address.</li>
<li><a href="https://01.org/jira/browse/VSM-140">VSM-140</a> Ceph Development (Epic 6): Prototype Calamari/VSM dashboard implementation</li>
<li><a href="https://01.org/jira/browse/VSM-88">VSM-88</a> On monitor status page, report what server each monitor is running on.</li>
<li><a href="https://01.org/jira/browse/VSM-15">VSM-15</a> VSM-backup prompt info not correct</li>
<li><a href="https://01.org/jira/browse/VSM-242">VSM-242</a> Allow user to modify ceph.conf outside VSM</li>
<li><a href="https://01.org/jira/browse/VSM-124">VSM-124</a> [CDEK-1852] VSM | adding possibility to manipulate ceph values in cluster.manifest file</li>
<li><a href="https://01.org/jira/browse/VSM-4">VSM-4</a> Average Response Time" missing in dashboard Overview panel "VSM Status" section.</li>
<li><a href="https://01.org/jira/browse/VSM-159">VSM-159</a> add issue reporting tool</li>
<li><a href="https://01.org/jira/browse/VSM-184">VSM-184</a> add automated script to help deploy VSM on multiple nodes</li>
<li><a href="https://01.org/jira/browse/VSM-156">VSM-156</a> add sanity check tool to help identify potential issues before or after deployment</li>
</ul>
<h2>Resolved bugs</h2>
<ul>
<li><a href="https://01.org/jira/browse/Key">Key</a> Summary</li>
<li><a href="https://01.org/jira/browse/VSM-321">VSM-321</a> no upstart mechanism used for ubuntu when controlling ceph service</li>
<li><a href="https://01.org/jira/browse/VSM-336">VSM-336</a> On Dashboard, even no cluster is created, the VSM version and uptime should be displayed</li>
<li><a href="https://01.org/jira/browse/VSM-24">VSM-24</a> [CDEK-1661] VSM Dashboard | Manage Servers | Reset server status - works not correctly.</li>
<li><a href="https://01.org/jira/browse/VSM-365">VSM-365</a> Creating Cluster stucks at ceph.conf creation when running VSM on CentOS 7.1</li>
<li><a href="https://01.org/jira/browse/VSM-19">VSM-19</a> CDEK-1613] VSM | Reset Server Status button - return Error:Network error</li>
<li><a href="https://01.org/jira/browse/VSM-379">VSM-379</a> Trace back in browser when using reset server status action buttons</li>
<li><a href="https://01.org/jira/browse/VSM-381">VSM-381</a> run diamond through service instead of current process launching</li>
<li><a href="https://01.org/jira/browse/VSM-378">VSM-378</a> Performance data is retrieved from outside nodes</li>
<li><a href="https://01.org/jira/browse/VSM-374">VSM-374</a> the down server is not reflected in VSM</li>
<li><a href="https://01.org/jira/browse/VSM-375">VSM-375</a> Malformed JSON in 'Integrate Cluster' function</li>
<li><a href="https://01.org/jira/browse/VSM-366">VSM-366</a> the password for openstack access is shown as plain text</li>
<li><a href="https://01.org/jira/browse/VSM-312">VSM-312</a> vsm-node sets node status="Need more IP" if a Monitor only node does not have a cluster IP address..</li>
<li><a href="https://01.org/jira/browse/VSM-367">VSM-367</a> can't create cluster at public cloud environment</li>
<li><a href="https://01.org/jira/browse/VSM-368">VSM-368</a> The default password is not following the same password policy to include uppercase and digitals.</li>
<li><a href="https://01.org/jira/browse/VSM-369">VSM-369</a> Change password: "!" doesnt' support in password even prompt message says OK</li>
<li><a href="https://01.org/jira/browse/VSM-224">VSM-224</a> Controller node error in /var/log/httpd/error_log - constantly ongoing messages [error] <Response [200]></li>
<li><a href="https://01.org/jira/browse/VSM-244">VSM-244</a> Internal server error when installing v1.1</li>
<li><a href="https://01.org/jira/browse/VSM-179">VSM-179</a> keep ceph.conf up to date when executing "remove server" operations.</li>
<li><a href="https://01.org/jira/browse/VSM-176">VSM-176</a> SSL certificate password is stored in a plain text file</li>
<li><a href="https://01.org/jira/browse/VSM-193">VSM-193</a> hard-coded cluster id</li>
<li><a href="https://01.org/jira/browse/VSM-177">VSM-177</a> wrong /etc/fstab entry for osd device mount point</li>
<li><a href="https://01.org/jira/browse/VSM-239">VSM-239</a> with automatic deployment, the execution is blocked at asking if start mysql service</li>
<li><a href="https://01.org/jira/browse/VSM-166">VSM-166</a> cluster<em>manifest sanity check program gives incorrect advice for auth</em>keys</li>
<li><a href="https://01.org/jira/browse/VSM-121">VSM-121</a> Storage node unable to connect to controller although network is OK and all setting correct</li>
<li><a href="https://01.org/jira/browse/VSM-123">VSM-123</a> Storage node will not be able to contact controller node to install if http proxy set</li>
<li><a href="https://01.org/jira/browse/VSM-171">VSM-171</a> [CDEK1672] VSM_CLI | list shows Admin network in Public IP section</li>
<li><a href="https://01.org/jira/browse/VSM-168">VSM-168</a> [CDEK1800] VSM_CLI | remove mds - doesn't update vsm database</li>
<li><a href="https://01.org/jira/browse/VSM-236">VSM-236</a> no way to check manifest correctness after editing them</li>
<li><a href="https://01.org/jira/browse/VSM-233">VSM-233</a> console blocks when running automatic installation procedure</li>
<li><a href="https://01.org/jira/browse/VSM-260">VSM-260</a> the check<em>network in server</em>manifest will be wrong when it has a single network card</li>
<li><a href="https://01.org/jira/browse/VSM-33">VSM-33</a> negative update time in RBD list</li>
<li><a href="https://01.org/jira/browse/VSM-51">VSM-51</a> Install Fails for VSM 0.8.0 Engineering Build Release</li>
<li><a href="https://01.org/jira/browse/VSM-113">VSM-113</a> [CDEK-1835] VSM | /var/log/httpd/error_log - constantly ongoing messages [error] <Response [200]></li>
<li><a href="https://01.org/jira/browse/VSM-29">VSM-29</a> vsm-agent process causes high i/o on os disk</li>
<li><a href="https://01.org/jira/browse/VSM-216">VSM-216</a> Add storage group requires at least 3 nodes</li>
<li><a href="https://01.org/jira/browse/VSM-26">VSM-26</a> [CDEK-1664] VSM | Not possible to replace node if ceph contain only 3 nodes.</li>
<li><a href="https://01.org/jira/browse/VSM-207">VSM-207</a> can't assume eth0 device name</li>
<li><a href="https://01.org/jira/browse/VSM-230">VSM-230</a> when presenting pool to openstack, cache tiering pools should be listed.</li>
</ul>
<h2>Known issues</h2>
<ul>
<li><a href="https://01.org/jira/browse/VSM-393">VSM-393</a> When importing cluster, if there is no OSd and MON sections, the import will fail</li>
</ul>
<h2>2.0.0 (build 216)</h2>
<h2>Special Notes</h2>
<ul>
<li>This is the 2.0 final release, which includes both Ubuntu 14 and CentOS 7 packages. </li>
<li>16 new features are added, and 33 bugs are fixed till this release.</li>
</ul>
<h2>New Features</h2>
<ul>
<li><a href="https//01.org/jira/browse/VSM-342">VSM-342</a> support ceph upgrade on centos 7</li>
<li><a href="https//01.org/jira/browse/VSM-88">VSM-88</a> On monitor status page, report what server each monitor is running on.</li>
<li><a href="https//01.org/jira/browse/VSM-162">VSM-162</a> need to support typical openstack deployment with multiple cinder/nova/glance instances beside currrent all-in-one mode</li>
<li><a href="https//01.org/jira/browse/VSM-246">VSM-246</a> a separate tool to help make a node ready for addition into cluster</li>
<li><a href="https//01.org/jira/browse/VSM-307">VSM-307</a> the operator expects to upgrade ceph cluster</li>
<li><a href="https//01.org/jira/browse/VSM-309">VSM-309</a> Disk identification: the operator expects to identify physical location of failed disks for replacement</li>
<li><a href="https//01.org/jira/browse/VSM-327">VSM-327</a> Dashboard: it's required to have summary for device capacity status to show if full</li>
<li><a href="https//01.org/jira/browse/VSM-358">VSM-358</a> Support normal user instead of root to install vsm</li>
<li><a href="https//01.org/jira/browse/VSM-355">VSM-355</a> there are some used disk paths list in the data path field and journal dik path field on page 'add new osd'</li>
<li><a href="https//01.org/jira/browse/VSM-352">VSM-352</a> servermgmt page autorefrush too frequent</li>
<li><a href="https//01.org/jira/browse/VSM-346">VSM-346</a> Add complete set of Juno features in Horizon; pluggable settings, etc.</li>
<li><a href="https//01.org/jira/browse/VSM-341">VSM-341</a> expect to have some utilties to help make automation tests.</li>
<li><a href="https//01.org/jira/browse/VSM-291">VSM-291</a> The operator expects to present pools to multiple openstack clusters or regions</li>
<li><a href="https//01.org/jira/browse/VSM-331">VSM-331</a> it's necesary to monitor device utilization from dashboard</li>
<li><a href="https//01.org/jira/browse/VSM-339">VSM-339</a> Configuration Management: as more and more features are added, and different scenarios require different settings, configuration is requried.</li>
<li><a href="https//01.org/jira/browse/VSM-337">VSM-337</a> Upgrade: expect to upgrade from 1.0 to 2.0</li>
</ul>
<h2>Resolved bugs</h2>
<ul>
<li><a href="https//01.org/jira/browse/VSM-312">VSM-312</a> vsm-node sets node status="Need more IP" if a Monitor only node does not have a cluster IP address..</li>
<li><a href="https//01.org/jira/browse/VSM-17">VSM-17</a> [CDEK-1608] User can remove himself, but after command execution he is not automatically log out</li>
<li><a href="https//01.org/jira/browse/VSM-329">VSM-329</a> Remove Monitors button in Manage Servers hangs when Monitor node also has MDS daemon</li>
<li><a href="https//01.org/jira/browse/VSM-274">VSM-274</a> a new user logged in vsm and can delete himself</li>
<li><a href="https//01.org/jira/browse/VSM-362">VSM-362</a> there are a lot of "in-Up" log in apache error log</li>
<li><a href="https//01.org/jira/browse/VSM-364">VSM-364</a> when remove one monitor without MDS co-located, the operation keeps running and no end.</li>
<li><a href="https//01.org/jira/browse/VSM-359">VSM-359</a> get smart info inaccurate</li>
<li><a href="https//01.org/jira/browse/VSM-363">VSM-363</a> if removing a monitor where the MDS is co-located, after finished, the status has changed to "available" instead of "active".</li>
<li><a href="https//01.org/jira/browse/VSM-319">VSM-319</a> performance monitor error when restart vsm processes on controller</li>
<li><a href="https//01.org/jira/browse/VSM-322">VSM-322</a> there are exceptions when request vsm dashboard</li>
<li><a href="https//01.org/jira/browse/VSM-330">VSM-330</a> When upgrading from Firefly to Giant, the upgrade complains missing python-rados package</li>
<li><a href="https//01.org/jira/browse/VSM-360">VSM-360</a> No servers list after newly installed with errors " Permission denied: '/tmp/crushmap'"</li>
<li><a href="https//01.org/jira/browse/VSM-332">VSM-332</a> sometimes diamond service start failed</li>
<li><a href="https//01.org/jira/browse/VSM-333">VSM-333</a> Error: "Activation of org.freedesktop.secrets timed out", when installing with 2.0 beta 1</li>
<li><a href="https//01.org/jira/browse/VSM-345">VSM-345</a> remove server error：no pemssion to stop osd service</li>
<li><a href="https//01.org/jira/browse/VSM-348">VSM-348</a> deploy agent node after vsm cluster has been created, the token in .token file is invalid</li>
<li><a href="https//01.org/jira/browse/VSM-361">VSM-361</a> when one osd is full, the dashboard doesn't mark one osd is full</li>
<li><a href="https//01.org/jira/browse/VSM-347">VSM-347</a> When clicking on "add new osd" at device management, a server error page pops up</li>
<li><a href="https//01.org/jira/browse/VSM-353">VSM-353</a> changed the password of current user,an error page pops up</li>
<li><a href="https//01.org/jira/browse/VSM-336">VSM-336</a> On Dashboard, even no cluster is created, the VSM version and uptime should be displayed</li>
<li><a href="https//01.org/jira/browse/VSM-343">VSM-343</a> can't create cache tier with latest code</li>
<li><a href="https//01.org/jira/browse/VSM-344">VSM-344</a> after a few times install, clean-up, reinstall, we have seem some "eaddrinuse" errors on starting rabbitmq</li>
<li><a href="https//01.org/jira/browse/VSM-357">VSM-357</a> 'add new disk':if data disk and journal disk is in the different partitions of the same disk, the opearation will be unsuccessful</li>
<li><a href="https//01.org/jira/browse/VSM-350">VSM-350</a> no response when get latency performance on dashboard</li>
<li><a href="https//01.org/jira/browse/VSM-351">VSM-351</a> ceph upgrade on ubuntu unsuccess</li>
<li><a href="https//01.org/jira/browse/VSM-356">VSM-356</a> I got warning info means that the number of pg in each osd is too large after upgrade ceph from a lower version to hammar</li>
<li><a href="https//01.org/jira/browse/VSM-354">VSM-354</a> when 'create cluster' page opened,other pages still can be opened</li>
<li><a href="https//01.org/jira/browse/VSM-349">VSM-349</a> click 'create cluster',I got the tip:there are some zones no monitor created</li>
<li><a href="https//01.org/jira/browse/VSM-340">VSM-340</a> Manifest: even using the same token generated from agent-token, server_manifest still complains connection error</li>
<li><a href="https//01.org/jira/browse/VSM-328">VSM-328</a> Dashboard: when one disk is full, the warning message is not showing correctly</li>
<li><a href="https//01.org/jira/browse/VSM-338">VSM-338</a> Upgrade: current ceph upgrade requires all agent nodes have internet connections, which normally is not true.</li>
<li><a href="https//01.org/jira/browse/VSM-334">VSM-334</a> upgrade: when set hammer url, then click "submit", the final ceph version is still firefly.</li>
<li><a href="https//01.org/jira/browse/VSM-335">VSM-335</a> The version on UI only shows 2.0.0, but no build number</li>
</ul>
<h2>Known issues</h2>
<h2>2.0.0 (build 163)</h2>
<h2>Special Notes</h2>
<ul>
<li>this is a 2.0 beta 1 release, still plenty of changes in this release, and we did some initial tests on it. </li>
<li>15 new features are added, and 41 bugs are fixed till this release.</li>
</ul>
<h2>New Features</h2>
<ul>
<li><a href="https//01.org/jira/browse/VSM-135">VSM-135</a> CentOS 6.5 and 7.0 Support </li>
<li><a href="https//01.org/jira/browse/VSM-296">VSM-296</a> Show performance on the dashboard </li>
<li><a href="https//01.org/jira/browse/VSM-4">VSM-4</a> Average Response Time" missing in dashboard Overview panel "VSM Status" section. </li>
<li><a href="https//01.org/jira/browse/VSM-159">VSM-159</a> add issue reporting tool </li>
<li><a href="https//01.org/jira/browse/VSM-156">VSM-156</a> add sanity check tool to help identify potential issues before or after deployment </li>
<li><a href="https//01.org/jira/browse/VSM-15">VSM-15</a> VSM-backup prompt info not correct </li>
<li><a href="https//01.org/jira/browse/VSM-124">VSM-124</a> [CDEK-1852] VSM | adding possibility to manipulate ceph values in cluster.manifest file </li>
<li><a href="https//01.org/jira/browse/VSM-242">VSM-242</a> Allow user to modify ceph.conf outside VSM </li>
<li><a href="https//01.org/jira/browse/VSM-184">VSM-184</a> add automated script to help deploy VSM on multiple nodes </li>
<li><a href="https//01.org/jira/browse/VSM-103">VSM-103</a> Suport a Single Keystone Instance in OpenStack Environments </li>
<li><a href="https//01.org/jira/browse/VSM-303">VSM-303</a> Ajust the UI like openstack dashboard </li>
<li><a href="https//01.org/jira/browse/VSM-54">VSM-54</a> On OSD Status page: Provide filter option to only display OSDs that are not up and in </li>
<li><a href="https//01.org/jira/browse/VSM-190">VSM-190</a> Add disks to cluster </li>
<li><a href="https//01.org/jira/browse/VSM-220">VSM-220</a> Operator expects to know what's happending inside ceph cluster through performance counters</li>
<li><a href="https//01.org/jira/browse/VSM-134">VSM-134</a> Ubuntu 14.X Support</li>
</ul>
<h2>Resolved bugs</h2>
<ul>
<li><a href="https//01.org/jira/browse/VSM-318">VSM-318</a> "remove osd" doesn't work</li>
<li><a href="https//01.org/jira/browse/VSM-325">VSM-325</a> Monitor: negative update time shown on monitor status when removing an monitor.</li>
<li><a href="https//01.org/jira/browse/VSM-269">VSM-269</a> Smart info doesn't work in Device mgmt.</li>
<li><a href="https//01.org/jira/browse/VSM-324">VSM-324</a> Monitor: inconsistent monitor number on Monitor status page when removing one monitor</li>
<li><a href="https//01.org/jira/browse/VSM-326">VSM-326</a> UI: the progress indicator is not showing at the center of screen but the top-left</li>
<li><a href="https//01.org/jira/browse/VSM-323">VSM-323</a> Installer: when installing diamond on each agents, there are a lot of File or Folder not found issues</li>
<li><a href="https//01.org/jira/browse/VSM-306">VSM-306</a> when executing buildvsm on ubuntu, the script complains no vsm user created</li>
<li><a href="https//01.org/jira/browse/VSM-263">VSM-263</a> The pie chart in "Storage Group Status" page is disappeared.</li>
<li><a href="https//01.org/jira/browse/VSM-320">VSM-320</a> if installing from a node instead of the controller, the installation will be stopped at missing deployrc</li>
<li><a href="https//01.org/jira/browse/VSM-176">VSM-176</a> SSL certificate password is stored in a plain text file</li>
<li><a href="https//01.org/jira/browse/VSM-230">VSM-230</a> when presenting pool to openstack, cache tiering pools should be listed.</li>
<li><a href="https//01.org/jira/browse/VSM-26">VSM-26</a> [CDEK-1664] VSM | Not possible to replace node if ceph contain only 3 nodes.</li>
<li><a href="https//01.org/jira/browse/VSM-51">VSM-51</a> Install Fails for VSM 0.8.0 Engineering Build Release</li>
<li><a href="https//01.org/jira/browse/VSM-236">VSM-236</a> no way to check manifest correctness after editing them</li>
<li><a href="https//01.org/jira/browse/VSM-29">VSM-29</a> VSM-agent process causes high i/o on os disk</li>
<li><a href="https//01.org/jira/browse/VSM-216">VSM-216</a> Add storage group requires at least 3 nodes</li>
<li><a href="https//01.org/jira/browse/VSM-33">VSM-33</a> negative update time in RBD list</li>
<li><a href="https//01.org/jira/browse/VSM-113">VSM-113</a> [CDEK-1835] VSM | /var/log/httpd/error_log - constantly ongoing messages [error] <Response [200]></li>
<li><a href="https//01.org/jira/browse/VSM-179">VSM-179</a> keep ceph.conf up to date when executing "remove server" operations.</li>
<li><a href="https//01.org/jira/browse/VSM-177">VSM-177</a> wrong /etc/fstab entry for osd device mount point</li>
<li><a href="https//01.org/jira/browse/VSM-233">VSM-233</a> console blocks when running automatic installation procedure</li>
<li><a href="https//01.org/jira/browse/VSM-239">VSM-239</a> with automatic deployment, the execution is blocked at asking if start mysql service</li>
<li><a href="https//01.org/jira/browse/VSM-166">VSM-166</a> cluster<em>manifest sanity check program gives incorrect advice for auth</em>keys</li>
<li><a href="https//01.org/jira/browse/VSM-207">VSM-207</a> can't assume eth0 device name</li>
<li><a href="https//01.org/jira/browse/VSM-224">VSM-224</a> Controller node error in /var/log/httpd/error_log - constantly ongoing messages [error] <Response [200]></li>
<li><a href="https//01.org/jira/browse/VSM-121">VSM-121</a> Storage node unable to connect to controller although network is OK and all setting correct</li>
<li><a href="https//01.org/jira/browse/VSM-244">VSM-244</a> Internal server error when installing v1.1</li>
<li><a href="https//01.org/jira/browse/VSM-123">VSM-123</a> Storage node will not be able to contact controller node to install if http proxy set</li>
<li><a href="https//01.org/jira/browse/VSM-171">VSM-171</a> [CDEK1672] VSM_CLI | list shows Admin network in Public IP section</li>
<li><a href="https//01.org/jira/browse/VSM-168">VSM-168</a> [CDEK1800] VSM_CLI | remove mds - doesn't update vsm database</li>
<li><a href="https//01.org/jira/browse/VSM-193">VSM-193</a> hard-coded cluster id</li>
<li><a href="https//01.org/jira/browse/VSM-260">VSM-260</a> the check<em>network in server</em>manifest will be wrong when it has a single network card</li>
<li><a href="https//01.org/jira/browse/VSM-317">VSM-317</a> the update time in MDS block is empty</li>
<li><a href="https//01.org/jira/browse/VSM-249">VSM-249</a> can not open dashboard and get the debug infomation "Invalid block tag: 'horizon_nav'"</li>
<li><a href="https//01.org/jira/browse/VSM-299">VSM-299</a> when after installed vsm, but no ceph cluster deployed, there is still show 3 storage groups</li>
<li><a href="https//01.org/jira/browse/VSM-310">VSM-310</a> with Firefox, for all tables, the vertical separator between the first and second column gets disappered</li>
<li><a href="https//01.org/jira/browse/VSM-313">VSM-313</a> the logo is disappeared when running on IE 11</li>
<li><a href="https//01.org/jira/browse/VSM-314">VSM-314</a> there is no progress indicator when an operation is not returned.</li>
<li><a href="https//01.org/jira/browse/VSM-316">VSM-316</a> the button style in "device management" page is different from others.</li>
<li><a href="https//01.org/jira/browse/VSM-311">VSM-311</a> The blocks in dashboard are exceed out of the width of heading</li>
<li><a href="https//01.org/jira/browse/VSM-315">VSM-315</a> "add server" doesn't work in alpha 2</li>
</ul>
<h2>Known issues</h2>
<ul>
<li><a href="https//01.org/jira/browse/VSM-332">VSM-332</a> sometimes diamond service start failed </li>
<li><a href="https//01.org/jira/browse/VSM-330">VSM-330</a> When upgrading from Firefly to Giant, the upgrade complains missing python-rados package </li>
</ul>
<h2>2.0.0 (build 149)</h2>
<h2>Special Notes</h2>
<ul>
<li>this is a 2.0 alpha 2 release, we did some initial tests on it. </li>
<li>29 new features are added, and 47 bugs are fixed till this release.</li>
</ul>
<h2>New Features</h2>
<ul>
<li><a href="https//01.org/jira/browse/VSM-63">VSM-63</a> Filter/Identify OSDs that are not up and in</li>
<li><a href="https//01.org/jira/browse/VSM-61">VSM-61</a> Openstack Prod release alignment with VSM</li>
<li><a href="https//01.org/jira/browse/VSM-55">VSM-55</a> Paginate OSD pages</li>
<li><a href="https//01.org/jira/browse/VSM-10">VSM-10</a> VSM1.0 -[CDEK-1190] VSM "Create cluster" cannot select storage nodes or monito</li>
<li><a href="https//01.org/jira/browse/VSM-304">VSM-304</a> Support to present pool to Openstack Juno All in one</li>
<li><a href="https//01.org/jira/browse/VSM-282">VSM-282</a> current installer scripts only support ip address based, it's also required to support host name based</li>
<li><a href="https//01.org/jira/browse/VSM-256">VSM-256</a> current logic enforces 3 replicas, somethings user may require to loose or tighten the enforcement.</li>
<li><a href="https//01.org/jira/browse/VSM-257">VSM-257</a> reorganize functions inside installer to make it's possible to install controller or agent separately</li>
<li><a href="https//01.org/jira/browse/VSM-243">VSM-243</a> the "create cluster" button doesn't take in effect after click on ubuntu 14</li>
<li><a href="https//01.org/jira/browse/VSM-235">VSM-235</a> make scripts can support both rpm and deb packages</li>
<li><a href="https//01.org/jira/browse/VSM-222">VSM-222</a> It's necessary to import a VSM created cluster by VSM itself.</li>
<li><a href="https//01.org/jira/browse/VSM-221">VSM-221</a> upgrade vsm dependent openstack packages to juno</li>
<li><a href="https//01.org/jira/browse/VSM-212">VSM-212</a> request to support ceph hammer release</li>
<li><a href="https//01.org/jira/browse/VSM-209">VSM-209</a> support multiple subnets</li>
<li><a href="https//01.org/jira/browse/VSM-189">VSM-189</a> “Add Server” progress</li>
<li><a href="https//01.org/jira/browse/VSM-163">VSM-163</a> server_manifest does not check for local host in /etc/hosts</li>
<li><a href="https//01.org/jira/browse/VSM-154">VSM-154</a> Request to have a new column on storage-group-status page to have number of OSD's in each storage group.</li>
<li><a href="https//01.org/jira/browse/VSM-143">VSM-143</a> On OSD Status page, limit to 100 OSDs per page</li>
<li><a href="https//01.org/jira/browse/VSM-144">VSM-144</a> On OSD Status page, sort OSDs by status, server, % capacity used</li>
<li><a href="https//01.org/jira/browse/VSM-130">VSM-130</a> OpenStack Juno Support</li>
<li><a href="https//01.org/jira/browse/VSM-94">VSM-94</a> Implement Pass-through Parameters</li>
<li><a href="https//01.org/jira/browse/VSM-85">VSM-85</a> Storage Group Status improvements</li>
<li><a href="https//01.org/jira/browse/VSM-89">VSM-89</a> Full OS disk indication</li>
<li><a href="https//01.org/jira/browse/VSM-84">VSM-84</a> Improved server status reporting</li>
<li><a href="https//01.org/jira/browse/VSM-83">VSM-83</a> Restart stopped monitor</li>
<li><a href="https//01.org/jira/browse/VSM-69">VSM-69</a> Override default PG per OSD value</li>
<li><a href="https//01.org/jira/browse/VSM-73">VSM-73</a> Zone monitor warning</li>
<li><a href="https//01.org/jira/browse/VSM-46">VSM-46</a> overlay vsm with existing ceph cluster</li>
<li><a href="https//01.org/jira/browse/VSM-23">VSM-23</a> Create User UI should prompt more information</li>
</ul>
<h2>Resolved bugs</h2>
<ul>
<li><a href="https//01.org/jira/browse/VSM-305">VSM-305</a> presenting pool should keep backward comatibility, say working with juno, icehouse, havana</li>
<li><a href="https//01.org/jira/browse/VSM-300">VSM-300</a> if no cluster is created, when open "server management"\"manage servers", the Ui becomes messy</li>
<li><a href="https//01.org/jira/browse/VSM-298">VSM-298</a> on dashboard, when adding new monitors, the monitor block doesn't update accordingly</li>
<li><a href="https//01.org/jira/browse/VSM-297">VSM-297</a> on dashboard, the storage group balls have no data</li>
<li><a href="https//01.org/jira/browse/VSM-293">VSM-293</a> wrong version of vsm displayed in the dashboard</li>
<li><a href="https//01.org/jira/browse/VSM-295">VSM-295</a> the installation fails at downloading dependent packages if http proxy is required</li>
<li><a href="https//01.org/jira/browse/VSM-292">VSM-292</a> the background of tool tip is not clear to view</li>
<li><a href="https//01.org/jira/browse/VSM-286">VSM-286</a> present pools to openstack again after you have presented pools, the attach status is always starting</li>
<li><a href="https//01.org/jira/browse/VSM-285">VSM-285</a> present multi pools to openstack cinder, the cinder.conf is not complete</li>
<li><a href="https//01.org/jira/browse/VSM-287">VSM-287</a> messy login window if accessing https://<ip>/dashboard</li>
<li><a href="https//01.org/jira/browse/VSM-284">VSM-284</a> at cluster status monitor, it's expected to provide complete summary instead the partial information from dashboardard</li>
<li><a href="https//01.org/jira/browse/VSM-283">VSM-283</a> after restart ceph cluster, the osd tree becomes messy</li>
<li><a href="https//01.org/jira/browse/VSM-280">VSM-280</a> "Internal Server Error" when click on "Data Device Status"</li>
<li><a href="https//01.org/jira/browse/VSM-278">VSM-278</a> after I add a server by clicking 'add server',the osd tree become messy</li>
<li><a href="https//01.org/jira/browse/VSM-279">VSM-279</a> click 'restart osd' or 'restore osd',the osd tree will become messy</li>
<li><a href="https//01.org/jira/browse/VSM-281">VSM-281</a> on dashboard, the cluster status like "warning" shouldn't be clickable</li>
<li><a href="https//01.org/jira/browse/VSM-276">VSM-276</a> Allow agent to be deployed on nodes where no ceph role assigned</li>
<li><a href="https//01.org/jira/browse/VSM-277">VSM-277</a> click on "add storage group" will tigger "something went wrong" error on UI</li>
<li><a href="https//01.org/jira/browse/VSM-272">VSM-272</a> on OS with newer rabbitmq version like 3.4, message queue can't be accessed</li>
<li><a href="https//01.org/jira/browse/VSM-273">VSM-273</a> "Import Error name Login" received when try to login to web console</li>
<li><a href="https//01.org/jira/browse/VSM-275">VSM-275</a> the overview page is messy with Firefox</li>
<li><a href="https//01.org/jira/browse/VSM-270">VSM-270</a> reinstall the keystone when deploy the vsm</li>
<li><a href="https//01.org/jira/browse/VSM-266">VSM-266</a> Dashboard UI correction</li>
<li><a href="https//01.org/jira/browse/VSM-265">VSM-265</a> Click Manage VSM\"Add/Remove User"\"Change Password", no page shows up</li>
<li><a href="https//01.org/jira/browse/VSM-264">VSM-264</a> on "PG Status" page, the text layout is messy.</li>
<li><a href="https//01.org/jira/browse/VSM-267">VSM-267</a> The logo is not fully shown.</li>
<li><a href="https//01.org/jira/browse/VSM-268">VSM-268</a> Can't create EC pool</li>
<li><a href="https//01.org/jira/browse/VSM-262">VSM-262</a> when clicking on "device management", the page shows "something went wrong"</li>
<li><a href="https//01.org/jira/browse/VSM-258">VSM-258</a> wrong dependencies url</li>
<li><a href="https//01.org/jira/browse/VSM-259">VSM-259</a> script 'vsm-agent' missing LSB tags and overrides</li>
<li><a href="https//01.org/jira/browse/VSM-253">VSM-253</a> A lot of buttons is invalid such as “addmonitor”,“removemonitor”,“addserver”,“removeserver”,“restore osd”,“remove osd” and so on</li>
<li><a href="https//01.org/jira/browse/VSM-254">VSM-254</a> the successful tip boxes can't shut down such as "Success: Successfully created storage pool: "</li>
<li><a href="https//01.org/jira/browse/VSM-255">VSM-255</a> when creating ceph cluster with one zone defined, the ceph cluster keeps in health_warn status</li>
<li><a href="https//01.org/jira/browse/VSM-252">VSM-252</a> Most of the interface's auto refresh function is invalid</li>
<li><a href="https//01.org/jira/browse/VSM-251">VSM-251</a> after clicked clusterManagement->create cluster->create cluster,there is not mds created.</li>
<li><a href="https//01.org/jira/browse/VSM-250">VSM-250</a> Error when packing</li>
<li><a href="https//01.org/jira/browse/VSM-245">VSM-245</a> error creating cluster</li>
<li><a href="https//01.org/jira/browse/VSM-231">VSM-231</a> VSM | Not possible to choose the machines during cluster creation</li>
<li><a href="https//01.org/jira/browse/VSM-229">VSM-229</a> Error state displayed on green color</li>
<li><a href="https//01.org/jira/browse/VSM-225">VSM-225</a> VSM Creates Very Small pg<em>num and pg.</em>num Size for EC Pool</li>
<li><a href="https//01.org/jira/browse/VSM-218">VSM-218</a> on centos 7, the web layout is messy</li>
<li><a href="https//01.org/jira/browse/VSM-195">VSM-195</a> if no cluster initialized, the UI shouldn’t knock at ‘manage servers’.</li>
<li><a href="https//01.org/jira/browse/VSM-194">VSM-194</a> User experience: OSD Status and Manage Devices.</li>
<li><a href="https//01.org/jira/browse/VSM-180">VSM-180</a> When a cluster is destroyed and recreated, VSM controller increments the cluster id (aka database rowid)</li>
<li><a href="https//01.org/jira/browse/VSM-153">VSM-153</a> after clicked vsm->settings->update,there is no successful tip</li>
<li><a href="https//01.org/jira/browse/VSM-68">VSM-68</a> Veriffy there are enough discrete servers and/or zones to support a VSM requested replication level</li>
<li><a href="https//01.org/jira/browse/VSM-5">VSM-5</a> KB used in "Pool status" panel not consistent with "ceph df" in backend</li>
</ul>
<h2>Known issues</h2>
<ul>
<li><a href="https//01.org/jira/browse/VSM-313">VSM-313</a> the logo is disappeared when running on IE 11</li>
</ul>
<h2>2.0.0 (build 123)</h2>
<h2>Special Notes</h2>
<ul>
<li>this is alpha 1 release for 2.0, which is not well verified yet, just for early preview.</li>
</ul>
<h2>1.1_1</h2>
<h2>Special Notes</h2>
<ul>
<li>this is a bugfix release for 1.1, which fixed the issues found in VSM-242 ("Allow user to modify ceph.conf outside VSM"). Also adding an new script uninstall.sh to help uninstall VSM in the case user expects to restart installation again.</li>
</ul>
<h2>New Features</h2>
<ul>
<li><a href="https://01.org/jira/browse/VSM-209">VSM-209</a> support multiple subnets</li>
</ul>
<h2>Resolved bugs</h2>
<ul>
<li><a href="https://01.org/jira/browse/VSM-260">VSM-260</a> the check<em>network in server</em>manifest will be wrong when it has a single network card</li>
</ul>
<h2>Known issues</h2>
<p>- </p>
<h2>1.1</h2>
<h2>Special Notes</h2>
<ul>
<li>starting from v1.1, the vsm dependencies are maintained on <a href="http://github.com/01org/vsm-dependencies">vsm-dependencies repository</a> for tracking and trouble shooting.</li>
<li>starting from v1.1, an automatic deployment tool is provided to deploy whole vsm controller and agents from one placement.</li>
</ul>
<h2>New Features</h2>
<ul>
<li><a href="https://01.org/jira/browse/VSM-156">VSM-156</a> add sanity check tool to help identify potential issues before or after deployment</li>
<li><a href="https://01.org/jira/browse/VSM-159">VSM-159</a> add issue reporting tool</li>
<li><a href="https://01.org/jira/browse/VSM-184">VSM-184</a> add automated script to help deploy VSM on multiple nodes</li>
<li><a href="https://01.org/jira/browse/VSM-242">VSM-242</a> Allow user to modify ceph.conf outside VSM</li>
</ul>
<h2>Resolved bugs</h2>
<ul>
<li><a href="https://01.org/jira/browse/VSM-4">VSM-4</a> Average Response Time" missing in dashboard Overview panel "VSM Status" section. </li>
<li><a href="https://01.org/jira/browse/VSM-15">VSM-15</a> VSM-backup prompt info not correct</li>
<li><a href="https://01.org/jira/browse/VSM-25">VSM-25</a> VSM Dashboard | Capacity of hard drives is wrong and percentage used capacity is not correct.</li>
<li><a href="https://01.org/jira/browse/VSM-26">VSM-26</a> [CDEK-1664] VSM | Not possible to replace node if ceph contain only 3 nodes.</li>
<li><a href="https://01.org/jira/browse/VSM-29">VSM-29</a> vsm-agent process causes high i/o on os disk</li>
<li><a href="https://01.org/jira/browse/VSM-33">VSM-33</a> negative update time in RBD list</li>
<li><a href="https://01.org/jira/browse/VSM-51">VSM-51</a> Install Fails for VSM 0.8.0 Engineering Build Release</li>
<li><a href="https://01.org/jira/browse/VSM-113">VSM-113</a> [CDEK-1835] VSM | /var/log/httpd/error_log - constantly ongoing messages [error] <Response [200]></li>
<li><a href="https://01.org/jira/browse/VSM-121">VSM-121</a> Storage node unable to connect to controller although network is OK and all setting correct</li>
<li><a href="https://01.org/jira/browse/VSM-123">VSM-123</a> Storage node will not be able to contact controller node to install if http proxy set</li>
<li><a href="https://01.org/jira/browse/VSM-124">VSM-124</a> [CDEK-1852] VSM | adding possibility to manipulate ceph values in cluster.manifest file</li>
<li><a href="https://01.org/jira/browse/VSM-166">VSM-166</a> cluster<em>manifest sanity check program gives incorrect advice for auth</em>keys</li>
<li><a href="https://01.org/jira/browse/VSM-168">VSM-168</a> [CDEK1800] VSM_CLI | remove mds - doesn't update vsm database</li>
<li><a href="https://01.org/jira/browse/VSM-171">VSM-171</a> [CDEK1672] VSM_CLI | list shows Admin network in Public IP section</li>
<li><a href="https://01.org/jira/browse/VSM-176">VSM-176</a> SSL certificate password is stored in a plain text file</li>
<li><a href="https://01.org/jira/browse/VSM-177">VSM-177</a> wrong /etc/fstab entry for osd device mount point</li>
<li><a href="https://01.org/jira/browse/VSM-179">VSM-179</a> keep ceph.conf up to date when executing "remove server" operations.</li>
<li><a href="https://01.org/jira/browse/VSM-193">VSM-193</a> hard-coded cluster id</li>
<li><a href="https://01.org/jira/browse/VSM-207">VSM-207</a> can't assume eth0 device name </li>
<li><a href="https://01.org/jira/browse/VSM-216">VSM-216</a> Add storage group requires at least 3 nodes</li>
<li><a href="https://01.org/jira/browse/VSM-217">VSM-217</a> Problem with replication size on "pool" created on newly added storage group.</li>
<li><a href="https://01.org/jira/browse/VSM-224">VSM-224</a> Controller node error in /var/log/httpd/error_log - constantly ongoing messages [error] <Response [200]></li>
<li><a href="https://01.org/jira/browse/VSM-230">VSM-230</a> when presenting pool to openstack, cache tiering pools should be listed. </li>
<li><a href="https://01.org/jira/browse/VSM-233">VSM-233</a> console blocks when running automatic installation procedure</li>
<li><a href="https://01.org/jira/browse/VSM-236">VSM-236</a> no way to check manifest correctness after editing them</li>
<li><a href="https://01.org/jira/browse/VSM-239">VSM-239</a> with automatic deployment, the execution is blocked at asking if start mysql service</li>
<li><a href="https://01.org/jira/browse/VSM-244">VSM-244</a> Internal server error when installing v1.1</li>
</ul>
<h2>Known issues</h2>
<p>- </p>
<h2>1.0</h2>
<p>Special Notes</p>
<pre><code>For installation, please check the INSTALL.md on current release branch instead of the one on master branch.
</code></pre>
<p>New Features</p>
<pre><code>Openstack Icehouse support
</code></pre>
<p>Fixed bugs</p>
<pre><code>VSM-187 GUI shows always replication 3 when replicated pool is other than "Same as Primary"
VSM-183 ct_target_max_mem_mb and ct_target_max_capacity_gb sets the same value in create cache tier
VSM-182 add osd_heartbeat_grace and osd_heartbeat_interval to cluster.manifest
VSM-173 Can select same storage group in create replicated pool -- which should not
</code></pre>
<p>Known issues</p>
<pre><code>VSM-191 VSM does not display the replica storage group.
VSM-192 force nonempty.
VSM-188 Missing column in manage pool page.
</code></pre>
</body>
</html>
<!-- This document was created with MarkdownPad, the Markdown editor for Windows (http://markdownpad.com) -->