ABCDEFGHIJKLMNOPQRSTUVWXYZ
1
2
3
Project NameKnown Upgrade StepsExisting Config File Changes?Needed work
4
odlparentNo steps are required.N/A
5
yangtoolsNo steps are required.N/A
6
md-salUnknown
7
controller1) cluster configuration files
8
netconf1) changes to netconf mounts from config subsystem to RESTYes, several
Should we provide a migration utility?
9
AAA1) AAA has not made any changes to existing config subsystem files in the Beryllium release, but has added a few. These will naturally get loaded upon feature install. 2) AAA uses file-based database to store IdM credentials @ $KARAF_HOME/idmlight.db.mv.db. This schema was changed to include a domain field and a salt field during the Beryllium timeframe. There is no upgrade logic in place; the recommended upgrade procedure is to delete the existing database (rm idmlight.db.mv.db) then start fresh in Beryllium.No, just new ones
Should we provide a migration utility to migrate the idm store to the new format?
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