zeyev
/
presentazione
forked from campiaperti/infra


			
				
					
						
						
							123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109110111112113114115116117118119120121122123124125126127128129130131132133134135136137138139140141142143144145146147148149150151152153154155156157158159160161162163164165166167168169170171172173174175176177178179180181182183184185186187188189190191192193194195196197198199200201202203204205206207208209210211212213214215216217218219220221222223224225226227228229230231232233234235236237238239240241242243244245246247248249250251252253254255256257258259260261262263264265266267268269270271272273274275276277278279280281282283284285286287288289290291292293294295296297298299300301302303304305306307308309310311312313314315316317318
							<!doctype html>
<html>

<head>
	<meta charset="utf-8">
	<meta name="viewport" content="width=device-width, initial-scale=1.0, maximum-scale=1.0, user-scalable=no">

	<title>Talk on infra CA</title>

	<link rel="stylesheet" href="css/reset.css">
	<link rel="stylesheet" href="css/reveal.css">
	<link rel="stylesheet" href="css/theme/black.css">

	<!-- Theme used for syntax highlighting of code -->
	<link rel="stylesheet" href="lib/css/monokai.css">

	<!-- Printing and PDF exports -->
	<script>
		var link = document.createElement('link');
		link.rel = 'stylesheet';
		link.type = 'text/css';
		link.href = window.location.search.match(/print-pdf/gi) ? 'css/print/pdf.css' : 'css/print/paper.css';
		document.getElementsByTagName('head')[0].appendChild(link);
	</script>
	<style>
	.reveal h2 {
    font-size: 1.6em;
    background: rgba(6,6,6,0.8);
}
div.fragment, ul.fragment{background: rgba(6,6,6,0.8);}
	</style>
</head>

<body>
	<div class="reveal">
		<div class="slides">
			<section>
				<h2>Infrastructures in a horizontal farmers community</h2>
				Human agreements, comunication infrastructures<br/> Campi Aperti - Bologna - Italy
			</section>
			<!--
			<section>
				<h2>title</h2>
				<p>subtitle</p>
				<ul>
					<li></li>
					<li></li>
					<li></li>
					<li></li>
					<li></li>
					<li></li>
				</ul>
				<aside class="notes"> </aside>
			</section>
		-->
			<section>
				<h2>CAMPI APERTI</h2>
				<p>our food autonomy</p>
				<ul>
					<li>why: to know what we eat, to know how the environment is changing</li>
					<li>who: farmers, food processors (only in relation to producers), consumers = co-producers</li>
					<li>from: Via Campesina, 1999 no global movement, radical anticapitalist background</li>
					<!--li>how: agroecology, principle of equality, economy based on relationships, sense of limit</li>
					<li>where: near! In shared public spaces</li-->
				</ul>
				<aside class="notes">to keep humanity, safeguard the environment, to know that some things do not have a price, </aside>
			</section>
			<section data-background="./imgs/xm24_web.png">
				<h2 class="fragment">Where?</h2>
				<div class="fragment">
				<p>In shared public space: </br/>
					squares and squats VS supermarkets and car-parkings</p>
				<p>Campi Aperti was born in XM24 in Bolognina</p>
				<p>www.ecn.org/xm24</p>
			</div>
				<aside class="notes">xm24 is a self-managed public space in bolognina, more than 17 years old: now is under threat of eviction because it is out the logic of profit, because it is not a service, because it is a self-managed community</aside>
			</section>
			<section>
				<h2>WHEN? </h2>
				<p> a diffente idea of time!</p>
				<ul>
					<li>time does not depend from us, it is not human-centric</li>
					<li>farmers know this really well, they are used to plan</li>
					<li>ciclically</li>
					<li>emergencies can't exist, you have to be prepared</li>
					<li>everything change, slowly</li>
				</ul>
				<aside class="notes">our time is gold, is circular, is projects, is community, is story. Usually when something is smart and quick, is not considering some variables...  </aside>
			</section>
			<section data-background-video="video.mp4,video.webm">
				<h3>HOW</h3>
				<ul class="fragment">
					<li>food autonomy (those who live in the area decide what to grow, eat and produce)</li>
					<li>agroecology, recognizing an ecosystem to be safeguarded</li>
					<li>consensus method, not hierarchical relationship</li>
					<li>shared warranty: participatory BIO certification!= centralized BIO certification</li>
					<li>sense of limit, shared ideas and mutualism, understand the diversity, planned together</li>
					<li>economy of relationship, based on knowledge and not on competition</li>
				</ul>
				<aside class="notes"><li>food autonomy (those who live in the area decide what to grow, eat and produce)</li>
				<li>agroecology, recognizing an ecosystem to be safeguarded</li>
				<li>consensus method, not gerarchical relationship</li>
				<li>shared warranty: participatory BIO certification!= centralized BIO certification</li>
				<li>is like a web of trust: every farmers at every market checks the product of the other.. is easier than it looks, because we live in the valleys.. you see if a product comes from the big distribution and not from a nearby field</li>
				<li>sense of limit, shared ideas and mutualism, understand the diversity, planned together</li>
				<li>economy of relationship, based on knowledge and not on competition</li></aside>
			</section>
			<section>
				<h3>Consensus method</h3>
				is a non-monopolistic method, based on trust and on the richness given by the diversity of points of view.
				it is a negotiation between content and relationship, between trust and technical agreement.
				It does not mean unanimity (which makes it difficult to express doubts), it means CONSENSUS, trust, understanding,
				Leave the possibility to CHANGE. Don't hide the problems.
				We use a formal consensus method, there are many small assemblies with reports and plenary assemblies with
				parallelizations.
				<aside class="notes">Img con diagramma trust and law. Always be in transformation and do not take definitive decision. no meta discussion. critical thinking </aside>
			</section>
			<section>
				<h1> diagrams</h1>
			</section>
			<section>
				<h2>Orientation</h2>
				<p>never say: "do we all agree?", but rather: "do someone have more doubts?"</p>
				<ul>
					<li>active consent</li>
					<li>consent and doubt</li>
					<li>active dissent</li>
				</ul>
				<aside class="notes"> active dissent, means that the path we are taking is against some principles</aside>
			</section>

			<section>
				<h2>Our Shared agreements</h2>
				<ul>
					<li>reports </li>
					<li>time keeper</li>
					<li>right to listen/ to be listened</li>
					<li>everyone talks for herself (no meta discussion)</li>
				</ul>
				<aside class="notes"> </aside>
			</section>
			<section data-background="./imgs/Ca_web.png">
				<h2 class="fragment">Early Communication tools</h2>
				<ul class="fragment">
					<li>2003: markets in public squares</li>
					<li>2003: mailing list: a lot of different self-managed servers</li>
					<li>2004: web site: autistici/inventati server</li>
				</ul>
				<p>the possibility to reduce distances is really important in the countryside</p>
				<aside class="notes">AI is an antifascist/antisexist/antiracist server, more than 12 ml, many different comunications tools, also commercial; we are 143 farmers, probably a bit more than 1000 thousand people</aside>
			</section>
			<section>
				<h2>Mesh network</h2>
				<ul>
					<li>ninux.org</li>
					<li>Starting in March 2017</li>
					<li>8 nodes</li>
					<li>software: libremesh.org</li>
					<ul>					<li>based on openwrt</li>
<li>routing protocols: batman adv and babeld</li>
					</ul>
					<li>hardware: tplink, ubiquiti, librerouter.org</li>
				</ul>
				<aside class="notes"> </aside>
			</section>
			<section>
				<h3>Deploying a feminist perspective</h3>
				<p>technology is a balance between skill and dependence</p>
				<ul>
					<li>do not do things alone</li>
					<li>testing environment</li>
					<li>document everything and explain the choice of algorithms</li>
					<li>give yourself the time to study</li>
					<li>share knowledge</li>
					<li>don't be too much specialized</li>
					<li>mix proficients with newbies</li>
				</ul>
				<aside class="notes">
					<ul>
						<li>do not do things alone [resilience, knowing that a single person should not be so important],</li>
						<li>consider the possibility of making mistakes [testing environment!]</li>
						<li>document everything to be able to redo it and explain the choice of algorithms [documentation!],
						</li>
						<li>give yourself time to study, encourage to get your hands on,
						</li>
						<li>share knowledge [sometimes with facilitation approaches]
						</li>
						<li>do not be too much specialized [to feel stronger and less alienated and to not burn-out]
							to have an overview of things and not being just a mechanism, a piece in an assembly line
						</li>
						<li>mix proficients in a skill with newbies in that skill [everyone can learn new stuff!]
							everyone is a newby in somethng.
						</li>
					</ul>
					<p>the technology that incorporates algorithms is NOT politically
						NEUTRAL. They are not like a hammer, algorithms have a political
						design.</p>
				</aside>
			</section>
			<section>
				<h2>Infrastructure</h2>
				<ul>
					<li>human agreement</li>
					<li>from 2003: markets</li>
					<li>from 2003: mailing list</li>
					<li>from 2004: website</li>
					<li>2017: starting the mesh network</li>
					<li>2019: starting our server</li>
				</ul>
				<aside class="notes"> </aside>
			</section>
			<section data-background="./imgs/gcsardo.jpg"  data-background-size="550px">
				<h2>starting from our needs</h2>
				<p>we started to speak about the cloud in 2016</p>
			<p>during Genuino Clandestino in Sardinia</p>
				<aside class="notes"> is about the cards of shared warranty, where to host them? Genuino Clandestino is the human network of farmers in our peninsula and near islands, </aside>
			</section>
			<section>
				<h2>cloud</h2>
				<p>the problem of our intimacies</p>
				<ul>
					<li>find the server: tetaneutral.net (FFDN)</li>
					<li>find the sysadmins</li>
					<li>nextcloud</li>
					<li>docker</li>
					<li>ansible</li>
					<li>1 year of testing</li>
					<li>to grow or not to grow?</li>
				</ul>
				<aside class="notes">1 year of testing, 3 months to find the people: an herbalist, a technician, an astrophysicist. Tetaneutral supports net neutrality and internet access, inside the Federate France data Network, something that started near 20 years ago; with a budget based on donations with a trasparent money report. We turn on the cloud in march and now we are using it only to distribute administrative tasks. We are still in time to change software and infrastructure, we have to evaluate, but we have to think how to grow and make plans accordingly</aside>
			</section>

			<section data-background="./imgs/float.png">
				<h2 class="fragment">Float</h2>
				<div class="fragment">
				<p>a minimalistic container orchestrator by autistici.org</p>
				<p>git.autistici.org/ai3/float</p>
				<ul>
					<li>static service allocation</li>
					<li>1:1 instance/host mapping</li>
					<li>manual port assignments</li>
					<li>service discovery protocol</li>
					<li>PKI management</li>
					<li>builtin services</li>
				</ul>
			</div>
				<aside class="notes">Autistici is a self-managed and privacy oriented server active since 2001. This year it changed the Infrastructure. We decided to copy their resistent infrastructure because we have common needs. we decided to not use large software projects like kibernetes, because some of us would have to become too specialized in that, it's too much code to review and check, because the community behind it is different from ours. we need small stuff, 1thousand lines of python are enough! docker gives the possibility to test everything locally. the service scheduler does not move  containers at runtime in response to host failures, all changes happen at "configuration time" when running Ansible. the scheduler won't run more than one instance of a service on each host. there's no automatic allocation of ports. service discovery protocol DNS based. all service-to-service communication can be encrypted and authenticated using a private PKI. the toolkit provides a number of built-in monitoring services</aside>
			</section>
			<section>
				<h2>Interesting features for us</h2>
				<ul>
					<li>move on bare metal</li>
					<li>have a testing infrastructure</li>
					<li>we trust the group and share their value</li>
					<li>UTF</li>
					<li>services go down when something fails</li>
					<li>integrated monitoring</li>
					<li>versioning everything</li>
				</ul>
				<aside class="notes">we have different needs than companies, speaking with other sysadmins in the last 10 years the stuff became more and more sophisticated, layers over layers, wrapper inside other wrapper.. being a sysadmin is becoming similar to a production-line job, you miss the overview and you start to be afraid of the interdependencies. this infrastructure gives you the possibility to be modular but specific, being able to seclude software but also not managing the machines like in a industry. the aim is to do the best with less , not to do the minimum with a lot of resources. we don't want to have machines that are numbers, we have machines with names, like pets :) I think that float is the best compromise that we could find with the complexity of managing a comunication infrastructure and knowing that we are not alone, using also the help of another community, because in the freesoftware an important thing is to not be alone and to make alliances with those sharing the same objectives.</aside>
			</section>
			<section>
				<h2>thanks</h2>
				<p>questions?</p>
				<small>CC 4 - by-nc-sa ; slide in reveal.js</small>
				<aside class="notes"> </aside>
			</section>
			<section>
				<h2>thanks to</h2>
				<ul>
					<li>campiaperti.org</li>
					<li>autistici.org</li>
					<li>libremesh.org</li>
					<li>librerouter.org</li>
					<li>tetaneutral.net</li>
					<li>genuinoclandestino.it</li>
					<li>hackmeeting.org</li>
					<li>ninux.org</li>
					<li>eclectictechcarnival.org</li>
				</ul>				<aside class="notes"> </aside>
			</section>
		</div>
	</div>

	<script src="js/reveal.js"></script>

	<script>
		// More info about config & dependencies:
		// - https://github.com/hakimel/reveal.js#configuration
		// - https://github.com/hakimel/reveal.js#dependencies
		Reveal.initialize({
			controls: true,
			progress: true,
			center: true,
			hash: true,

			transition: 'slide', // none/fade/slide/convex/concave/zoom

			dependencies: [{
					src: 'plugin/markdown/marked.js'
				},
				{
					src: 'plugin/markdown/markdown.js'
				},
				{
					src: 'plugin/notes/notes.js',
					async: true
				},
				{
					src: 'plugin/highlight/highlight.js',
					async: true
				}
			]
		});
	</script>
</body>

</html>