Subversion Repositories DevTools

Rev

Show changed files | Details | Compare with Previous | Blame | RSS feed

Filtering Options

Rev Age Author Path Log message Diff
5958 3414 d 17 h dpurdie /ManagerSuite/Deployment_Manager/trunk/web/ [JATS-397] Fixing resource leaks  
5513 3617 d 17 h dpurdie /ManagerSuite/Deployment_Manager/trunk/ Reorganized the directory structure  
21 6719 d 12 h rsolanki /ManagerSuite/Deployment_Manager/trunk/ DevTools/ManagerSuite/Deployment_Manager: Checkin by Svn Import
There are changes in Release Manager and Deployment Manager so that the generation of node spec files is automated and the business
processes involved made efficient and less time-consuming. This involves the introduction of a mechanism that would enable users to add/import
processes to package versions in Release Manager and to the platforms in a given node in a BOM (Bills Of Materials) in Deployment Manager.
In general, the mechanism can be described in the following steps:

1. Insert processes/instances of processes in a given package version in Release Manager.
2. Import the processes/instances of processes to the platforms in a given node in Deployment Manager.
3. Generate the NodeSpecFiles from Deployment Manager to be used.


<b>Release Date:</b> 19-May-2006		  
19 6719 d 12 h rsolanki /ManagerSuite/Deployment_Manager/trunk/ DevTools/ManagerSuite/Deployment_Manager: Checkin by Svn Import
<b>Support to Add Patch Electronic Name</b>
This functionality has been added to support the generation of patch names in the XML BOMs.

<b>NodeSpec File Generation</b>
The process change in the nodespec files generation is:
1. Emailing of the nodespec files to the user.
2. Generating of the nodespec files under releases in auperaunx26.
(NB: Nodespec filenames should be existing for these to take place)

<b>Message Board Added</b>
Important messages or tasks can be scheduled and posted on the message board.

<b>BOM Diff and Merge Manager re-located</b>
These have been moved under the "Tools" section on the top-right menu bar. This is where useful tools would be placed so as to assist the business process.

<b>All Process Fields Editable</b>
Pkg_health_tag and package/product fields for a process in a given OS in a node can now be changed upon user request.


<b>Release Date:</b> 12-May-2006		  
15 6719 d 12 h rsolanki /ManagerSuite/Deployment_Manager/trunk/ DevTools/ManagerSuite/Deployment_Manager: Checkin by Svn Import
<b>New Functionality Under Additional Tools</b>
The functionality to merge and diff two given SBOMs have now been split into two so that the user can get more detailed information regarding the differences between the SBOMs.
The SBOM Merge Manager would display the changes as per node, operating systems applied to the node and the product versions existing.
The SBOM Version Difference Report would display the changes as per the product versions existing in the SBOMs.

<b>History Tab</b>
History tabs have been added to most of the sections in Deployment Manager so as to track and record the action logs of Deployment Manager users.

<b>NOT_XML functionality</b>
Each operating system would now have an option whether to display or not to display in the XMLs generated for CFengines.

<b>Is_Interface Edit Option</b>
There is now support to edit the "is_interface" value for given processes.

<b>Support for Windows E-name</b>
Package names would now support both SunOS and WIN electronic names for CFengines.

<b>Products In the Node Spec File</b>
Deployment Manager can now support the ability to add several products in the node spec file.

<b>Bom Difference Report</b>
The difference report that gets emailed as per the user's request has been modified so that now it would be able to display the product/package versions that exist between the two versions employed in the BOMs.

<b>XML files for CFEngines</b>
The XML files being generated for CFengines would now be zipped and emailed to the user instead of having Deployment Manager displaying the path to access the files previously.


<b>Release Date:</b> 13-Mar-2006