1
Distributed Development Roadmap
Ralf Gronkowski Product Specialist
2
Perforce Today Current Solutions
3
13.1 Update
§ Filtered Replication § Task Streams § Unshelve to Branch § Submit Shelf
The Problem is…
4
§ Remote sites
§ Large teams
§ Automation
§ Git mirrors
Supporting
Versioning Service
Proxy
Proxy
Replication Service
6
Road Map New Solutions
7
“100X” Initiative
“100X”
Data Center
Dis
trib
uted
Today
8
100X Includes…
Failover Distributed optimization
Reduced
network load
Horizontal scaling
Concurrency
9
The Road to 100X
Proxy
Replicas
Filtered / Chained
Commit / Edge
Clustering
9
10
100X: Advanced Replication
DO NOT DISTRIBUTE 10
Filtered Replication
Chained Replicas
Git Replication
Available Now
11
100X: Remote Site Support
11
Eliminate WAN traffic for many
opera9ons
Reduce data transfer
Commit
Edge Edge
12
Reduced Activity on Commit Instance
12
Replica Master Edge Master
13
Remote Sites: Just Faster
56.6
8.7
61
9.8
0.9 0.7 1.8 0.2 0
10
20
30
40
50
60
70
Sync Revert Integrate Edit
COMMON OPERATIONS WITH 128MS LATENCY BETWEEN CLIENT AND P4D
Direct Edge
14
100X: 2014
Horizontal scaling (read ops) High availability (failover)
Concurrency
15
Nuts and Bolts Details, details, details…
16
100X
Failover Commit/edge
Chain replicas
Horizontal scaling
Concurrency
Filter replicas
17
Chaining Replicas
17
p4 configure set replicaSingapore#P4TARGET=master:1666 p4 configure set replicaHK#P4TARGET=replicaSingapore:1666
Configuration
Use common sense
Ask for help when necessary
Master Repository(California)
Read-Only Replica(Singapore)
Read-Only Replica(Hong Kong)
Read-Only Replica(Singapore)
Read-Only Replica(Singapore)
18
Filtering Replicas
Configure in server spec and pull commands
18
> p4 server repl ServerID: repl RevisionDataFilter: //gui/... > p4 configure set "repl#startup.1=pull -‐i 1 -‐P repl"
Singapore Replica
Estonia Replica
Toronto Replica 20 TB
500 GB
50 GB
Master Repository(US)
500 TB
19
Git Replication
19
Configuration • Set P4PORT in Git Fusion
configuration to proxy, broker, or replica
Access control • Set IP-based rules on Git Fusion
account
FAQ • Commits are identical across all Git
Fusion instances
Upgrading to commit / edge
DR Replica
Build Server Replica
Versioning Service
Small Remote Office
Large Remote Office
Proxy Service
Forwarding Replica Git Fusion
Main Office
Upgrading to commit / edge
DR Replica
Edge Server (for Build Farm)
Versioning Service
Small Remote Office
Large Remote Office
Proxy Service
Edge Server Git Fusion
Main Office
Edge Server (for Users)
22
2014: Horizontal Scaling of Read Operations
Write Node
Read Node
Read Node
Read Node
Journal Service
Coordinator
Read Node
23
Write Node
Read Node
Read Node
Read Node
Coordinator
Journal Service
2014: High Availability and Failover
24
2014: Improved Replication Throughput
Write Node
Read Node
Read Node
Read Node
Coordinator
Journal Service
Durable write
25
100X
Advanced replicaKon Remote Sites Scaling, failover,
and concurrency
Perforce
Git
26
Questions? See Git Fusion in the Demo Lounge
Follow us Randy DeFauw: [email protected], @rdefauw Charlie McLouth: [email protected]
P4Ideax Forums