a guide to choosing an apache subversion server for the enterprise

17
1 Copyright ©2014 CollabNet, Inc. All Rights Reserved. A Guide to Choosing an Apache Subversion Server for the Enterprise CollabNet

Upload: collabnet

Post on 18-Dec-2014

106 views

Category:

Technology


3 download

DESCRIPTION

Over 6 million developers have trusted CollabNet open source technologies and thousands of organizations use CollabNet’s enterprise solutions to manage their Git and Subversion servers more effectively. CollabNet’s Subversion Edge with TeamForge can help you identify and reign-in all those SVN repositories and manage them in one environment. Furthermore, TeamForge can help ensure all your Git and SVN servers are safe, secure and manageable under one environment. In this webinar Mark Phippard, Chief Architect at CollabNet, will help you understand the different Apache Subversion server products that CollabNet provides and which of them is right for you. Learn the advantages of both. Who Should attend: Enterprise architects, managers responsible for multiple SVN repositories, and organizations looking to manage a heterogeneous SCM environment

TRANSCRIPT

1 Copyright ©2014 CollabNet, Inc. All Rights Reserved.

A Guide to Choosing an Apache Subversion Server for the Enterprise

CollabNet

2 Copyright ©2014 CollabNet, Inc. All Rights Reserved.

Mark Phippard Chief Architect CollabNet

• Manage the Subversion and Version Control teams and products at CollabNet since 2007.

• Member Apache Software Foundation and Apache Subversion PMC

• Project Owner/Lead, Subclipse – Eclipse Integration for Subversion

About Me

3 Copyright ©2014 CollabNet, Inc. All Rights Reserved.

Provide an overview and understanding of the different Apache Subversion server products that CollabNet provides.

Help you understand which options are best for you.

Objective

4 Copyright ©2014 CollabNet, Inc. All Rights Reserved.

• What are you using today for SVN server?

– Subversion Edge

– TeamForge

– Subversion cloud hosting

– Plain SVN binaries

– Not using Subversion

– Other

Poll Question #1

5 Copyright ©2014 CollabNet, Inc. All Rights Reserved.

• “Plain” binaries – Provided for convenience and packaging

– Separate “client” and “server” packages

– “Qualified” before release

• Configuration was DIY and left up to user

• Upgrades sometimes challenging – httpd 2.0.x -> 2.2.x -> 2.4.x

• Today .. only makes sense for simple svnserve deployments – Included in “client” binary packages

– “server” packages maintained for legacy users

• Personal bias against svnserve – No logging or encryption

– Poor user management -- SASL not a real option for most

– Unclear scalability

– Suitable for smallest deployments only

In the beginning …

6 Copyright ©2014 CollabNet, Inc. All Rights Reserved.

• Started as internal project to provide “Edge appliance”

– Aimed at largest customers that wanted replication

• Still provides “plain” binaries

– … but also includes web application to configure the server

• Full managed “stack” – Apache httpd, Subversion, ViewVC

• Updates built into web app

– Upgrades can manage configuration changes

• Best practices built-in

– Log rotation and cleanup

– Easy SSL and “easier” LDAP authentication

– Simple backup options

… enter SVN Edge

7 Copyright ©2014 CollabNet, Inc. All Rights Reserved.

• Single server “appliance”

– Easy to install and get started

– Windows, Linux and Solaris

• Replace need to login to server and run commands

– Create repositories, add users, edit ACL files etc.

• Provides “some” separation of roles

– User(s) that manage the server vs. manage repositories/users

– Permissions are always “server-wide” if you can manage repositories, you can manage all repositories

• Provide smooth connectivity to TeamForge

– SVN Edge can be “latched in” to TeamForge

SVN Edge Goals

8 Copyright ©2014 CollabNet, Inc. All Rights Reserved.

• How many production Subversion servers exist in your organization?

– 0-1

– 2-4

– 5-10

– 10+

Poll Question #2

9 Copyright ©2014 CollabNet, Inc. All Rights Reserved.

• Still provides “plain” binaries – actually SVN Edge

– custom Apache authn/authz module – mod_auth_teamforge

TeamForge

10 Copyright ©2014 CollabNet, Inc. All Rights Reserved.

• Federated server management

– Manage multiple servers from single UI

– Can be SVN Edge servers or any supported TeamForge SCM server

TeamForge – Subversion Federation

11 Copyright ©2014 CollabNet, Inc. All Rights Reserved.

• Fine-grained permissions and delegation of responsibilities

– Site-admin / Project-admin / Users

– Custom roles (Developer, Stakeholder, QA etc.)

TeamForge – Central Management and RBAC

12 Copyright ©2014 CollabNet, Inc. All Rights Reserved.

• SVN Replication

– Centralize and secure assets and IP

– SVN Edge replica servers in remote locations

TeamForge – Subversion Replication

13 Copyright ©2014 CollabNet, Inc. All Rights Reserved.

• SVN wildcard path-based permissions

– /**/secure

– Simplifies branch/tag permission management

• Code search

– Included but optional to install

• Code review

– Included but optional to install

• Activity reporting

• Also supports Git and CVS

TeamForge continued

14 Copyright ©2014 CollabNet, Inc. All Rights Reserved.

• Multi-tenant cloud hosting

– Also supports Git and other dev tools (Trac, Bugzilla, WebDAV)

– TeamForge supported for tracker and document management

• Integrations

– Jira, Rally, Pivotal etc.

• Inexpensive plans

CloudForge

15 Copyright ©2014 CollabNet, Inc. All Rights Reserved.

• CloudForge – Let someone else manage your server

– Get started fast, grow easily

• Plain binaries – Only for svnserve – only for small installations

– Honestly, SVN Edge is always better option

• SVN Edge – Single server/single team installations

– No need for, or still willing to DIY integrations

– No need for Git or other tools

• TeamForge – Multiple teams

– Multiple servers

– Replication

– Need for additional tools

– Git

Which server to use?

16 Copyright ©2014 CollabNet, Inc. All Rights Reserved.

• Any existing Subversion server to SVN Edge

– Relatively easy … point SVN Edge at folder with your repositories

– Configure SVN Edge as desired (SSL, LDAP etc)

– Only http(s) protocol supported

– Only fsfs repository format supported

– Wiki: http://bit.ly/YSyd8L

• SVN Edge to TeamForge

– Simple wizard in SVN Edge to “connect” it to TeamForge

– Federated mode – full SVN server managed by TeamForge

– Replication mode – write-thru proxy for a TeamForge SVN server

Migrating from one to another

17 Copyright ©2014 CollabNet, Inc. All Rights Reserved.

• Subversion Edge info

http://www.collab.net/products/subversion

• TeamForge info

http://www.collab.net/products/teamforge

• CloudForge info

https://www.cloudforge.com

• Downloads

http://www.collab.net/downloads/subversion

• Archived Webinars

http://www.collab.net/resources/webinars

Questions and Links