Subversion Repositories DevTools

Rev

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

Filtering Options

Rev Age Author Path Log message Diff
25 6719 d 22 h rsolanki /ManagerSuite/Deployment_Manager/trunk/ DevTools/ManagerSuite/Deployment_Manager: Checkin by Svn Import
<b>Escrow Report - Paul Blain Request</b>
Added the functionality to generate the escrow report.

<b>BOM Base Configuration Products</b>
Added a new tab that would show the Base Configurations for a given BOM

<b>Find Product In BOM</b>
This has been added under the Tools > Advanced Search section.

<b>BOM NOTE Functionality - George Christidis Request</b>
All BOMs should display the BOM Notes regardless of the state of the BOM.


<b>Release Date:</b> 13-October-2006		  
21 6719 d 22 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		  
17 6719 d 22 h rsolanki /ManagerSuite/Deployment_Manager/trunk/ DevTools/ManagerSuite/Deployment_Manager: Checkin by Svn Import
<b>BOM History Report</b>
This tool has been added under the new "Reports" link on the header menu on the home page.
Select the "BOM History Tracker" from the "Bom History" as this is the initial report functionality that has been officially released. This would help users in identifying the Bom, Node, OS changes that occur in an SBOM between certain periods:

<b>Bom Difference Report</b>
The difference report that gets emailed as per the user's request has been extended once again, so that now it would be able to display the patches that have been added to the new BOM selected compared to the old BOM.


<b>Release Date:</b> 04-Apr-2006		  
15 6719 d 22 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		  
13 6719 d 22 h rsolanki /ManagerSuite/Deployment_Manager/trunk/ DevTools/ManagerSuite/Deployment_Manager: Checkin by Svn Import
SBOM Difference Report

XML Bom Generation Path Modified


DEVI-021016: Need deployment manager support for managing what patch goes to which node
Stephen,
As per your suggestions, I have written 2 scripts to support this. One has been implemented in the Deployment Manager GUI.
The other can be run from the server to extract data required by you for the patches without the HTML contents.
(For example, run_patch.asp?project=SYDNEY (SYD)&release=SITS Legacy&sbom=1.4.2&node=Central System Off-line Server(OFS)&OS=Solaris))

Regards,
Rupesh


<b>Release Date:</b> 31-Jan-2006