1 / 9

Collaborative Web Development

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. Hardware/OS Sparc Based

renee-frye
Download Presentation

Collaborative Web Development

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Collaborative Web Development Designing and Building a Collaborative Web Infrastructure Andrew Gehring - NREL

  2. Overview • Previous Architecture & Processes • Requirements & Objectives • New Architecture • Hardware • Software • New Processes • Challenges • Future

  3. History • 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 • Architecture • Process • Development Cycle • Version Control • Major “Issues”

  4. Objectives • Implement revision control system • Implement “Test” into Development Cycle • Encourage “Best Practices” • SDLC, SOA, Security, … • Collaboration Tools • Migration toward Green IT Requirements • Ease of Use • “No Change” for Internal Users • Improve remote Contractor access / Controls

  5. New Architecture • Hardware • Software • “Tools” • Standards • 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”

  6. New Processes • Coding Environment • Test / Production Environment • Test / Production Deployment Process • 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)

  7. Challenges • Social • Users (developers) are reluctant to change • Political • Previous investment in tools • Security • Unfamiliarity with new tools • Subversion • TRAC

  8. Future • Work for Others • Code Sharing (public subversion server) • Collaboration • ticketing, WIKIs (TRAC) • The “Cloud” • Better development processes

  9. Questions / Discussion

More Related