Ticket #376 (new task)
Better Change Control mechanism required
Reported by: | selatham | Owned by: | jdoughty |
---|---|---|---|
Priority: | required | Milestone: | NDG3 |
Component: | roadmap | Version: | |
Keywords: | DiscoveryService | Cc: |
Description
Implement change control now that we have 'live' services. So that changes to NDG production machine superglue (and possibly glue too?) are done in a controlled, predicted manner. Sue & Phil had some ideas of how to do this effectively.
Change History
comment:1 Changed 15 years ago by selatham
- Priority changed from desirable to required
- Milestone changed from PostAlpha_review to SystemIntegrationOctober2006
comment:3 Changed 14 years ago by selatham
- Milestone changed from BETA to Reporting and Futures
Operational procedures for live services.
comment:4 Changed 13 years ago by pjkersha
- Status changed from assigned to closed
- Resolution set to wontfix
Use of eggs has helped with this issue a little.
comment:5 Changed 13 years ago by selatham
- Status changed from closed to reopened
- Resolution wontfix deleted
- Component changed from strategy to DiscoveryService
- Milestone changed from Reporting to Replace Metadata Gateway
I'm re-opening as we should make sure we know who is supporting the live NERC-DDS and how changes will be implemented. We should document a procedure when handing over to CEDA.
comment:6 Changed 13 years ago by selatham
- Status changed from reopened to new
- Owner changed from pjkersha to selatham
comment:7 Changed 12 years ago by lawrence
- Keywords DiscoveryService added
- Component changed from DiscoveryService to discovery
Moved from DiscoveryService? component to discovery as part of NDG2 cleanup
Note: See
TracTickets for help on using
tickets.
The un-scheduled changes to apache just prior to the last Project Board highlighted the need for this step towards 'maturity' in system administration. Related to ticket #491 'Move trac off glue'