Subversion Repositories DevTools

Rev

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

Filtering Options

Rev Age Author Path Log message Diff
3938 4515 d 16 h dpurdie /ManagerSuite/Deployment_Manager/branches/dpurdie/ Use common header for all pages
Header highlights development web server and database.
Used updated code from Release Manager to:
* Display User Account Information
* Display tipster.js
* Handle login processing		  
1283 4908 d 13 h dpurdie /ManagerSuite/Deployment_Manager/branches/dpurdie/  
29 6397 d 7 h jtweddle /ManagerSuite/Deployment_Manager/trunk/ DevTools/ManagerSuite/Deployment_Manager: Checkin by Svn Import
* Fixed a bug in BOM comparison that caused products that had been updated to also be shown as having been removed.
* Fixed a bug that caused server error pages when removing an OS from a node, or a product from an OS.		  
19 6719 d 11 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		  
17 6719 d 11 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 11 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