|
|
@@ -58,10 +58,12 @@
|
|
|
</ul>
|
|
|
<aside class="notes">for keep humanity, safeguard the ambient, to know that there are stuffs without a price, </aside>
|
|
|
</section>
|
|
|
- <section>
|
|
|
+ <section data-background="./imgs/xm24_web.png">
|
|
|
<h2>Where?</h2>
|
|
|
+ <div class="fragment">
|
|
|
<p>In shared public space: square and squat VS supermarket</p>
|
|
|
<p>Campi Aperti was born in XM24 in Bolognina</p>
|
|
|
+ </div>
|
|
|
<aside class="notes">xm24 is a self-managed public space in bolognina, exist more than 17 year old, now is under treat of eviction because is out the logic of profit, is not a service, is a community that selfmanaged herself</aside>
|
|
|
</section>
|
|
|
<section>
|
|
|
@@ -76,9 +78,9 @@
|
|
|
</ul>
|
|
|
<aside class="notes">our time is gold, is circolar, is projects, is community, is story,normally when something is smart and quick, is not considering some variables... </aside>
|
|
|
</section>
|
|
|
- <section>
|
|
|
+ <section data-background-video="video.mp4,video.webm">
|
|
|
<h3>HOW</h3>
|
|
|
- <ul>
|
|
|
+ <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 gerarchical relationship</li>
|
|
|
@@ -86,12 +88,6 @@
|
|
|
<li>sense of limit, shared ideas and mutualism, understand the diversity, planned together</li>
|
|
|
<li>economy of relationship, based on knowledge and not competition</li>
|
|
|
</ul>
|
|
|
- <aside class="notes">il video, sennò nn ci crede nessuno. spiega garanzia partecipata</aside>
|
|
|
- </section>
|
|
|
-
|
|
|
- <section>
|
|
|
- <h3>Video</h3>
|
|
|
-
|
|
|
<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>
|
|
|
@@ -236,21 +232,7 @@
|
|
|
<li>PKI management</li>
|
|
|
<li>builtin services</li>
|
|
|
</ul>
|
|
|
- <aside class="notes">Autistici is a self managed server from the 2001, privacy oriented,this year changed the Infrastructure. We decide to try to copy theri resistent infrastructure and because we have common need. we decided to not use big software like kibernetes, because need that someone of us became too specilize in that, it's too much code to review and check, because the comunity behind is different from our. we need small stuff, 1thousen line of python is enought! docker give the possibility to test all in local.* *static service allocation* - the service scheduler does not move
|
|
|
- containers at runtime in response to host failures, all changes
|
|
|
- happen at "configuration time" when running Ansible.
|
|
|
-* *1:1 instance/host mapping* - the scheduler won't run more than one
|
|
|
- instance of a service on each host.
|
|
|
-* *manual port assignments* - you must manually pick a unique port for
|
|
|
- your services, there's no automatic allocation.
|
|
|
-* *service discovery protocol* - DNS based.
|
|
|
-* *PKI management* - all service-to-service communication can be
|
|
|
- encrypted and authenticated using a private PKI.
|
|
|
-* *builtin services* - the toolkit provides a number of built-in
|
|
|
- services, such as monitoring, alerting, log collection and analysis,
|
|
|
- thorough audit functionality, private networking. These services are
|
|
|
- automatically configured and managed (though they can be extended).
|
|
|
-</aside>
|
|
|
+ <aside class="notes">Autistici is a self managed server from the 2001, privacy oriented,this year changed the Infrastructure. We decide to try to copy theri resistent infrastructure and because we have common need. we decided to not use big software like kibernetes, because need that someone of us became too specilize in that, it's too much code to review and check, because the comunity behind is different from our. we need small stuff, 1thousen line of python is enought! docker give the possibility to test all in local. 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>
|
|
|
@@ -281,6 +263,7 @@
|
|
|
<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>
|
