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 14 h dpurdie /ManagerSuite/Deployment_Manager/trunk/web/ [JATS-397] Fixing resource leaks  
5513 3617 d 14 h dpurdie /ManagerSuite/Deployment_Manager/trunk/ Reorganized the directory structure  
5355 3679 d 13 h dpurdie /ManagerSuite/Deployment_Manager/trunk/ Add FavIcon support. With configuration via global.asa
Made page footer format the same as the rest of the Manager Suite		  
3947 4514 d 18 h dpurdie /ManagerSuite/Deployment_Manager/trunk/ ClearQuest interactions
Removed use of 4 ,unused and unavailable, ClearQuest databases
Release Notes
Migrated the storage of the Deployment Manager Release Notes from the (deprecated) MASS Wiki into the Deployment Manager tool itself.
Merged several features from Release Manager into Deployment Manager
The use of an internal Wiki Engine
Common header generation on all pages
Common header to highlight use on non-Production machines and databases
Tooltips
Authentication process
Use Authentication domain as provided by Access Manager
No password when used on Development Database
Account Details Pages
These have been enabled. Some changes have been imported from Release Manager. In particular the ability to display details on the users access permissions.		  
3911 4526 d 16 h dpurdie /ManagerSuite/Deployment_Manager/trunk/ Changes to generation of NodeSpec files
1) Email and Web NodeSpec files are now generated via the same code
2) Packages with VIX are treated in the same way as packages with erg_logo.gif
3) All Keys in the NodeSpec file are quoted		  
29 6397 d 4 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.		  
15 6719 d 9 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 9 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