This appendix provides tables summarizing the usage of new commands provided with this release of the N1 Service Provisioning System.
Table A–1 bdb.b.la – Lists All Bundle Templates|
Argument/Result |
Class |
Description |
|
|---|---|---|---|
|
result |
Bundle |
The Bundle template instances |
The bdb.b.lo command displays the details of a bundle template. Summary formatter is the default formatter. The summary formatter displays the same information as that in the bdb.b.la command, but for a single bundle template. Details could be retrieved with a -o detail argument.
Table A–2 bdb.b.lo – Displays Details of a Bundle Template|
Argument/Result |
Class |
Description |
|
|---|---|---|---|
|
ID |
[R] |
BundleID |
The ID of the bundle template to view |
|
result |
Bundle |
The bundle template details, the contained search criteria, a generated list of entities corresponding to these criteria, if any |
Table A–3 bdb.b.add – Adds a New Bundle Template
|
Argument/Result |
Class |
Description |
|
|---|---|---|---|
|
name |
[R] |
String |
The name of the bundle template |
|
desc |
[O] |
String |
The description of the bundle template |
|
criteria |
[O] |
SearchCriteriaArray |
Search criteria for entities to be included in the bundle template. Criteria start with either F:(folder) HT:(hostType) HR:(hostSearch) HS:(hostSet) C:(component) CT:(componentType) SS:(systemServices) P:(plan), followed by comma seperated attribute=value pairs. Separate multiple such criteria by ';'. Attributes can be a combination of: name, desc, vis (visibility), path (folder path),ver (version), ct (extendsType), lab (label). Attributes depend the entity type. |
|
result |
BundleID |
ID of the newly created bundle template |
The bdb.b.mod command modifies the contents of a bundle template. Criteria that you specified with the bdb.b.mod replace existing criteria for the entity type. Criteria specified on the command line replace the pre-existing ones for that entity.
Table A–4 bdb.b.mod – Modifies a Bundle Template|
Argument/Result |
Class |
Description |
|
|---|---|---|---|
|
ID |
[R] |
BundleID |
The ID of the bundle template to modify |
|
desc |
[O] |
String |
The description of the bundle template |
|
criteria |
[O] |
SearchCriteriaArray |
Search criteria for entities to be included in the bundle template. Criteria specified through this command overwrite any existing criteria the bundle template had. The syntax of usage is the same as for bdb.d.add |
|
result |
BundleID |
ID of the modified bundle template |
For the bdb.b.add and bdb.b.mod command, the order in which the entities are exported or imported is by default decided by the order of their search criteria in the bundle template. Pattern strings that contain ',' , ';' & '=' characters can be included by using '\' as an escape character. Backslash itself can be specified as '\\' in the pattern.
|
Argument/Result |
Class |
Description |
|
|---|---|---|---|
|
ID |
[R] |
BundleID |
The ID of the bundle template to delete |
Table A–6 bdb.b.exp – Exports a Bundle Template
|
Argument/Result |
Class |
Description |
|
|---|---|---|---|
|
ID |
[R] |
BundleID |
The ID of the bundle template to export |
|
path |
[R] |
String |
The path of the file system in which to save bundle jar that is created by the export |
Table A–7 bdb.b.imp – Imports a Bundle Jar
|
Argument/Result |
Class |
Description |
|
|---|---|---|---|
|
path |
[R] |
String |
The path to the file system from which to import the bundle jar |
|
owner |
[R] |
GroupID |
The group that will be owner of folders created by the import |
|
v |
[O] |
boolean |
True if you want only to validate an import, without actually executing one. Default value is false. |
|
result |
BundleSessionInfo |
Summary of the number and types of entities imported |