$@MID@$: 233 Date: Wed, 22 Sep 2010 10:31:28 -0500 Type: Meeting notes Meeting: Template: Subject: Code management backup and recovery meeting Attendees: Lynn Garren Keywords: Code Attachment: Encoding: HTML ======================================== 
o  From Aug 4 meeting to discuss migration of services and code distribution
   archive from cdfcode, and associated backup procedures:
Service on cdfcode Current backup schem New location of service New backup scheme   
tarfiles for 
release distribution

 encp_bin (only
release/bin area)

New ftp server
(the new 'cdfkits')

Files copied from 
fcdfbld* machines 
during release
build procedure

Nightly 
'cvs update Distribution'
needed to get current
distribution scripts

TIBS
[Does TIBS have a maximum
size restriction on area
to be backed up?]
  
development build
 
Not backed up
 
Distributed across
fcdfbld* machines

Not backed up
   
cdfkits server 
(upd server for products 
+ current distribution
scripts)

encp_cdfkits
(products)
+
encp_rel
(release/lib,
         shlib,
         tmp,
+ NULL tarballs,
etc.) 

upd server moved to
fnkits

Serving distribution
scripts moved to new
ftp server

'cdfkits' alias moved
to new ftp server

CD responsibility

NOTE:  need to have
~cdfsoft/products/upsdb 
backed up on all fcdfbld*
machines and on 
/cdf/code
  
Code browser

Code in cvs
 
New web server + db
machine for postgres DB

[How to index new releases
+ nightly developement
update?]

TIBS (?) + code in cvs
  
Code management scripts
usually run from ~cdfsoft
(eg, Init_package, updadd)

Code in cvs 

All general code 
management procedures
and scripts to be run
from fcdfbld5 

Code in cvs

                       
         
             
Log files (under
~cdfsoft/maint)


            		
            
            
Weekly crno job to
create rotating 
backup archive on 
disk


            		
            
            
Log areas migrate with
the services (always
in local area) 


            		
            
            
Not backed up??


            		
             
        

        

            
            
Work areas

            		
            
            
Weekly cron job to 
create rotating
backup archive on
disk

            		
            
            
Move to *bld* machines

            		
            
            
Not backed up??


            		
             
        

        

            
            
Archive to Enstore
scripts (not in cvs!!!)


            		
            
            
Weekly cron job to 
create rotating
backup archive on 
disk


            		
             
             
             
        

        

            
            
Everything else under
~cdfsoft


            		
            
            
Weekly cron job to
create rotating
backup archive on
disk


            		
            
            
Move to *bld* machines 


            		
            
            
Not backed up


            
Need to back-up
~cdfsoft/products/upsdb
area on all machines
and on /cdf/code


            		
             
        

        

             
             
             
             
             
        

        

             
             
             
             
             
        

    



o  Archive to Enstore scripts

   encp_dbstats:  not our problem, let the DB people handle it in the future
   encp_cdfcvs:  not needed since cdfcvs migration to cdcvs
   endp_iso:  (CD images of offline releases) not needed




o  Lynn and I agreed that release distribution tarballs can 
   live in a disk archive with rotating backups provided by 
   TIBS.

   Would need to isolate actively distributed releases
   from those that are archived, but not being 
   distributed. Just put them into an "OBSOLETE"
   area.

   This will require that we write scripts to 
   move releases into and back out of the 'obsolete'
   area. Would need to be driven off DistLog files
   since those have the mapping of which releases
   use which versions of various packages. 

   The DistLog files *all* need to be in the active 
   release area, and be backed up.

o  Spoke to Stephan (happened to wander by meeting)
   Requested that we back up everything under all 
   ~cdfsoft home area except dist and products.

   He said he would look into it.
   We noted that we need to have the 
   ~cdfsoft/products/upsdb area backed
   up since that is local configuration 
   that cannot be restored from fnkits.

   This is needed for both the fcdfbld* machines and
   for /cdf/code 

o  One conclusion from the above is that we can retire
   all the encp_* scripts, so that line becomes moot.