Collaborative Web Development info协同网络开发信息.ornl.gov.ppt

Collaborative Web Development Designing and Building a Collaborative Web Infrastructure Andrew Gehring - NREL Overview Previous Architecture Processes Requirements Objectives New Architecture Hardware Software New Processes Challenges Future History Architecture Process Development Cycle Version Control Major “Issues” Objectives Implement revision control system Implement “Test” into Development Cycle Encourage “Best Practices” SDLC, SOA, Security, … Collaboration Tools Migration toward Green IT New Architecture Hardware Software “Tools” Standards New Processes Coding Environment Test / Production Environment Test / Production Deployment Process Challenges Social Users (developers) are reluctant to change Political Previous investment in tools Security Unfamiliarity with new tools Subversion TRAC Future Work for Others Code Sharing (public subversion server) Collaboration ticketing, WIKIs (TRAC) The “Cloud” Better development processes Questions / Discussion * * Hardware/OS Sparc Based Solaris (8 9) Software Custom Apache Shared Binary NFS Process Development NFS / CiFS Prod Dev Same appliance External Contractors FTP Transfer Freeze CTP Copy to Production Network Appliance .snap 1 revision Issues Silos Upgrades Outage No “Test” Environment Halt work Production vs. Dev folder Requirements Ease of Use “No Change” for Internal Users Improve remote Contractor access / Controls Hardware SUN X86 Servers (x4600) Sparc Servers (T2000) SAN iSCSI Fibre NFS Clustered Appliances Software VMWare ESX Ubuntu LTS Solaris 10 Zones Containers “Official” Software Supported Tools Subversion “Hooks” TRAC Tickets PM Custom Test Production Standards Authentication Active Directory Management BCFG2 OS Config Single Purpose Multi “Homed” Desktop NFS / CiFS Checkout/in Remote Checkout/in Hooks Hooks Authorized Tags Autonomous Reduced dependencies Centrally Managed BCFG2 SVN (Config) Patch Management Aggressive (D/T) *