barnyard.github.io/index.html at master · barnyard/barnyard.github.io · GitHub

1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
<!doctype html>
<html>
  <head>
    <meta charset="utf-8">
    <meta http-equiv="X-UA-Compatible" content="chrome=1">
    <title>Pi</title>

    <link rel="stylesheet" href="stylesheets/styles.css">
    <link rel="stylesheet" href="stylesheets/pygment_trac.css">
    <meta name="viewport" content="width=device-width, initial-scale=1, user-scalable=no">
    <!--[if lt IE 9]>
    <script src="//html5shiv.googlecode.com/svn/trunk/html5.js"></script>
    <![endif]-->
  </head>
  <body>
    <div class="wrapper">
      <header>
        <h1>Pi</h1>
        <p>Distributed Decentralised App Substrate</p>

        <p class="view"><a href="/">Home</a></p>
		<p class="view"><a href="about.html">About</a></p>
		<p class="view"><a href="code.html">Code</a></p>
      </header>
      <section>
		<h2>The Story of Pi</h2>
		<p>
			Pi is a software platform for the rapid development and deployment of massively
			scalable and resilient infrastructure software services. It was the result of
			strategic ambitions of a major telco to explore new, game-changing ways of
			delivering combined software, infrastructure and network services in the cloud.
		</p>
		<p>
			The Pi software - the focus of this site - was a major piece of a bigger,
			holistic puzzle, the heart of a 'cloud operating system' running atop containerised
			data centre hardware, connected by software driven networks. Started by a small core
			group spanning  software, systems, network and infrastructure architecture and
			engineering, over two years the entire effort evolved from the initial exploration
			phase to deliver the full hardware and software stack, offering a fully-featured,
			Amazon EC2 and S3 compatible set of compute and storage services across many hundreds
			of machines and three geographic locations.
		</p>
		<p>
			By early 2011, Pi was in regular and rapidly growing use across the organisation,
			transforming the server provisioning and management lifecycle, in turn fuelling
			a fundamental shift in what small, lean teams could accomplish, rapidly and cheaply.
			It had just officially become the Most Innovative Software Product company-wide,
			largely on the back of unsolicited nominations and praise from its growing user base.
			It was drawing favourable comparisons from technology leaders acquainted with
			the IaaS startup landscape at the time.
		</p>
		<p>
			Over the next few months, the tide turned as strategic realignment and organisational
			seismics put a stop to the development effort in favour of a commitment to the more
			traditional and less ambitious vendor path. Although Pi has remained in use through
			2013, it is very much on life support.
		</p>
		<p>
			The Pi codebase was open-sourced in 2012 in an effort to extend its lifespan.
			However without a large pool of machines to control, and with the evolution of
			alternatives such as OpenStack and CloudStack, it has lacked a sufficiently
			captivating end goal to motivate further active development and evolution.
		</p>

		<h2>About This Site</h2>
		<p>
			This site presents the entire open-sourced Pi codebase, a description of
			the design of the Pi software stack, and a summary of the challenges and learnings
			derived in the course of developing the platform.
		</p>
		<p>
			Its aim is to capture and preserve the experience from successfully meeting a demanding
			set of infrequently encountered design goals, and thus encourage further contributions.
		</p>
	</section>
	<footer>
		<p><small>Hosted on GitHub Pages &mdash; Theme by <a href="https://github.com/orderedlist">orderedlist</a></small></p>
	</footer>
    </div>
    <script src="javascripts/scale.fix.js"></script>
  </body>
</html>