Chapter 2a: Server Issues: Platform Infrastructure

Platform infrastructure

Coordinator: In-grid (Katie)

Contributors: Winnie, Becky, Batool, Katie

Index TBC

Introduction

Why pi?

Pub/public spaces

Educational institutions

Inbetweens/travel

Workshop as space

CULTURAL/PUBLIC SPACES

DOMESTIC/PRIVATE SPACES

Introduction

Wiki4print, the raspberry pi which hosts https://wiki4print.servpub.net/ travels with us [1]. We have constructed our network of servers in such a way that we can keep it's hardware by our sides as we use it, teach and experiment with it and activate it with others. This chapter will consider the materiality of our particular network of nodes, our reasoning for arranging our infrastructure in the way we have and what it means to move through the world with these objects. By considering our movement from one place to another we can begin to understand how an ambulent server allows us to locate the boundaries of the software processes, the idiosyncrachies of hardware, the quirks of buildings and estates issues, and how we fit into larger networked infrastructures. How we manage departures, arrivals, and points of transcience, reveals boundaries of access, permission, visibility, precarity and luck.

In this chapter we will explain our decision to arrange our physical infrastructure in this way; mobile and in view. To do this we will map our collective experiences in a series of types of space. These spaces are reflective of our relative positions as artist*technologist*activist*academic (delete as appropriate):    

   * PUB / PUBLIC SPACES (maybe add this? e.g. 8M / the social origins/elements?)

   * EDUCATIONAL INSTITUTIONS (+history, eduroam,ctp,aarhus, cci, lsbu etc) (overview)

   * INBETWEENS: TRAVEL / suitcase as a space (hardware)

   * WORKSHOP AS A SPACE (workshopping as a methodolgy, a server runs on a computer)

   * CULTURAL/SEMI-PUBLIC SPACES (more on physical layer of the internet)

   * DOMESTIC/PRIVATE SPACES (hardware maintenance and care)

WHY PI? (As an overview, maybe this goes in Educational Institutions)

• By bringing the pi in person to teaching moments, it allowed us to discuss ideas around the physicality of and physical caring for a server. There is trust and intimacy in proximity.

• Why the pi and not another single board computer

• Why pre owned/borrowed hardware

• For clarity, when we refer to Wiki4Print[pi] * or another name we decide together

• Needs to move, because it's travelling for workshop

• Problems of plugging into network infrastructure at various institutions

• Legible at borders - recognisable by border patrol officers

• Problems of maintaining hardware

* PUB / PUBLIC SPACES (?)

maybe add this? e.g. 8M / the social elements? Again a space for origin stories?

* EDUCATIONAL INSTITUTIONS. /winnie

https://ctp.cc.au.dk/pad/p/winnie_servpub#L11 (still working on it...some might need to go somewhere, but moving towards to educational institutions)

The constraints of working within educational institutions (that use eduroam). The example of needing to set up or use mobile hotspots for the UAL and LSBU workshops.

see this link for writing: https://ctp.cc.au.dk/pad/p/winnie_servpub

**** could this be a moment to talk about the "origin" story of servpub, i.e. that the idea of getting around insitutional constraints of eduroam helped birth the project. So a place to talk about network issues? Review network...****** good idea...

What allows the pi to go walking:

Survey of the final set-up, brief overview of the parts of the infrastructure.  i.e. that starting from this problem of the constraints of the institution we set out to create a VPN which connected ambulant servers. Define how the Network Infrastructure chapter will deal with connecting to the wider web.

More on IP Addresses mapped to DNS / A Records / Tuxic ?

* INBETWEENS: TRAVEL / a suitcase as a space

***** Could this come next after institutional constraints? Just anecdotally the fact that they recognised the pi at the border, could serve as a nice way to talk about why pi and/or the other alternatives out there.  *****

The conditions of traveling with an ambulent server where movement is limited through border control, visa rules, and absurd transportation rules. Making a ambulent server for a constrictive space.

What it means to pack a server into a bag, cables and plugs and screens. What actually goes travelling. The pi unplugged, sans-electricity, sans-network. The physicality of a thing. A list of the things borrowed and stolen.

- Hardware (why pi)

• - Why Raspberry Pi

• - Why the pi and not another single board computer

• - Why pre owned/borrowed hardware - CCI

* WORKSHOP AS A SPACE

Pull out: Workshop as space

• Creating a space in a workshop, creating

• need to be with it to work - proximity to it to fix it

A server runs on a computer. By bringing the pi in person to teaching moments, it allows us to discuss ideas around the physicality of a server and caring for a server. There is trust and intimacy in proximity. This allows us to demystify network infrastructure.

CCI workshop / earlier workshops?

LSBU workshop content before joining the pi to the VPN. Demystifying the browser. Serving up files over a LAN. Accessing a file system, navigating around a file system on the command line.

Plugging it in:

• - Start with the impact of physicality, being in the same room as the hardware, being able to point to it in the corner of a room. Understanding the distinction between software and hardware. Setting up Hardware, what is an operating system Linux (why Linux):

• https://wiki4print.servpub.net/index.php?title=Docs:01.1_Hardware_and_OS

• + further links to Raspberry Pi

• - Local Area Network

• - Physical layer of network infrastructure?

• - Routers / Wi-fi / ethernet / MAC addresses ?

• - Software / Internet Protocol layer

• - TCP / UDP / ports / IP Address  ?

• - Protocols:

• - SSH (to enable networked/remote collaboration, I'm not sure going into collaboration here is the right thing to do, maybe more for praxis doubling?)

• https://www.raspberrypi.com/documentation/computers/remote-access.html#ssh

• https://wiki4print.servpub.net/index.php?title=Docs:01.3_SSH

• - Default Password Access. Basics of SSH + command line: navigating around a computer, installing software etc.

• - Setting up SSH keys per User ?

• https://wiki4print.servpub.net/index.php?title=Docs:01.2_Creating_Users

• https://wiki4print.servpub.net/index.php?title=Docs:01.3_SSH

• - TMUX ?

• - HTTP

• - Default set up on a pi?

• - Setting up a server with Nginx

• https://wiki4print.servpub.net/index.php?title=Docs:02_Local_Server_Setup_with_Ngin

• - the browser: accessing a website on the LAN

* SSH/User creation (maybe just do the basics of SSH not user creation)

Servpub as a platform could be understood as a series of interconnected nodes or small board computers connected together to create a network. At the time of writing we have two nodes: wiki4print, and the servpub pi.

[DIAGRAM OF THE NETWORK]

Through much of this project many of us are working (coding, writing) in a collaborative space on one or more of our networked nodes. When setting up a node which will be accessed, maintained or changed by several people we need to first consider how it is we configure those spaces. This is both a series of social questions (how we organise and document labour, how we decide who has access and to what extent) and technical considerations. Fundementally, at some point in developing the collaborative environment, we must should discuss and choose a user and access structure. Whatever structure is decided upon, we should then decide how to communicate between sysadmins, how to keep records and how to handover work.

As we mentioned in the section about why we want to be mobile our servers are shared and also mobile. In order for us to be able to have a functioning collaborative space that space needs to be accessable regardless of where is is in the world, or who is currently it's physical caretaker. In order to access the nodes remotely, we therefore need to call upon a protocol which allows us to enter the common space created on the pis remotely. Secure Shell (SSH) is a network protocol that lets users securely access and manage servers and computers (like our pi) from another device as long as it has internet access and the correct credentials. It functionally allows an individual to 'log-in' one device from another. If you have ever used a remote desktop, the idea is very similar, only you have access to that devices folder structure using a command line/text-based interface, rather than having the ability to access that devices desktop.

* Note: if you are interested in the steps it takes to use this protocol we have an installation/configuration guide as part of our documentation here.

This is all well and good, but you cant use ssh to access a remote device unless you have the correct credentials to do so: a user profile on the remote device in question and a pair of keys which encrypt and decrypt messages between the devices. SSH uses Client-sever architecture, which means that it divides tasks between clients and servers. The client is the device that requests information from a device, the sever is the device that provides that information.

In our case our Pi is our Server, and our personal laptop or device we want to use to access the pi, is the client. We talk about the nuances of these terms and how we feel about them in chapter x praxis doubling.

SSH is generally considered more secure due to its reliance on strong encryption and public/private key authentication.

**** Mention that this is where you'd then need to connect it to the VPN, which is not covered in this chapter? Reference Network Infrastructure chapter? *****

* CULTURAL/PUBLIC SPACESSECTION DRAFTING [Cultural spaces] /katie

Once connected to the VPN, problematics and politics of:

• - Accessing the wider internet from different spaces

• - Physical layer of network infrastructure

• - Routers / Wi-fi / ethernet / MAC addresses ?

Up to the point of writing, Wiki4Print[pi] has been a physical presence at several public workshops and events/interventions. Although in many (if not all) cases, it would be more practical and less effort to leave the hardware at home, we opt to bring it with us, for the reasons outlined above. By dint of our artist*sysadmin*academic situations, the pi has visited several of what we are defining as cultural spaces. We are using this term to describe spaces which primarily support or present the work of creative practicioners: museums, galleries, artist studios, libraries. This definition is not perfect, and obscures a lot of factors which we feel are pertinent to this discussion. We are conflating publicly funded institutions with privately rented spaces, spaces that are free to enter with others that have partial barriers like membership. However, we feel that for our purposes here, these comparisons, although imperfect allow us to see common issues. As with our entrances and exits from institutional spaces (universities), domestic locations and moments traveling we need to spend some time feeling out the material conditions of the space, and the customy practice in, and idiosyncracies of, that space. Not all two cultural spaces are built the same, as no two homes are the same.

We'll tell you about two spaces to explain what we mean.

1. An arts space run space run by a charity, based in a meanwhile use [2] building. The building contains rented studios which are used by individual artists and small businesses, a cafe and performance space, and gallery space open to the public. The space is based in the UK.

precarious

2. A center for contemporary arts, publicly funded by the federal government. The space hosts art exhibitions, theater and performance, films, and academic conferences. It also contains cafes and shops, and is generally open to the public, with some ticketed events. It is in Germany.

For now I will refer them the two spaces as [name1] [name2]

* Estates issues: (broken?)ethernet ports, working plugs, access to extensions, locked doors, opening hours, previous bookings, cleaning regimens, central heating (or lack there of), security (theft), furniture.

* Shitty wifi, privacy

Above mostly talking about entering/negotiating 'cultural spaces'

Using movements from places, arrivals in spaces as a comparitive narrative. We need to feel out the location every time, dependant on local situation i.e. internet speed and access. Negotiating being in the same space in different networks i.e. eduroam, things that surpass our protocols, gatekeepers - negotiation of being portable but who has the permissions.

Transmediale the connectivity not working when we arrived, as an example.

Within instituitions, the need to use mobile hotspots to bypass the institutional barriers. Refer to the constraints of educational spaces.

Internet of the building going down - precarious spaces (studio space in SET)

"parasitic" -- negotiatiing with different networks (power dynamic / security)

• - Public institution/cultural spaces (museum/HKW at TM/SET), EASST

https://ci.servpub.net/in-grid/collective-infrastructures

Rosa

* DOMESTIC/PRIVATE SPACES / Becky

- a way to talk about hardware of the pi? e.g. heatsinks and the limitations of a pi

- hardware maintenance as a practice

- extending storage with a USB

- backups

The wiki4print pi has ended up living in a house of an In-grid member in South London. How it came to be there was a result of the needs of caring for a temperamental Raspberry pi in a temperamental meanwhile space (SET studios). However, its particular journey through London and where it has landed was as much to do with the material constraints of internet access as it was to do with the needs of working in a collective. Passing hardware from hand to hand across London became a force that determined the material shape of the network: last minute plans, emergencies, the demands of work schedules, holidays, illness and commute times all played a part in the movement of the hardware.

wiki4print was originally at SET Studios in Woolwhich. The building was originally (what?) then it was an HMRC building (insert full history), it is now maintained by the Arts Charity SET which emerged out of squatter culture in London. The use of meanwhile space (definition?) within the arts sector in London is closely tied into wider property development crises, where more and more artists are reliable on institutions that exist in the margins <ref>https://www.artmonthly.co.uk/magazine/site/article/high-streets-for-all-by-matthew-noel-tod-may-2021</ref>. The reality of having a studio within a meanwhile space is that much of the infrastructure is crumbling. When In-grid first set up the Raspberry pis the hope was to host them in an art studio at SET, but it quickly became apparent that it was not viable, the ethernet ports in the room were not functional, the wi-fi was not reliable and the team maintaining the building are primarily artists themselves rather than corporate service providers. In the lead up to the Content/Form Transmediale workshop the pi kept crashing and going offline. We moved it to avoid these issues in the middle of a co-working session with multiple collectives so as to stick to the timeline. Batool raced to Becky's so that we could go ahead with the session. Why Becky's? Batool was not traveling to Germany for the workshop and Becky's house was the closest to the studio and on the way to where Batool was travelling for work.

We thought the pi kept going offline becasue the SET wi-fi was bad, but this was a red herring. While the pi was at Becky's it temporarily lived under a bed so the ethernet cable could reach it. Through the process of being able to debug at any hour (lying on the floor beside a bed) we were able to discover that problems with accessing the pi online were due to the Raspberry pi overheating, freezing and shutting down processes which would take it offline. We bought a heat sink and fan for the pi, and from then on it worked reliably in all locations. Maintaining server hardware in a domestic space or outside the context of a server farm (small or large) becomes an act of providing care at odd hours.

Maintaining the network becomes an act of inviting the rhythms and bodies of others into the material realities of the network. Cleaning the cat hair out of the fan of the raspberry pi or plugging in the pi because a guest did some hoovering and didn't realise what they were unplugging.

Footnotes? ----

[1] Link to intro? to a part explaining writing on wiki4print?

[2] Define meanwhile use?

------------------

Glossary -> Can we make a glossary for the technical terms...

Technical Writing / Structure for what to potentially include in this chapter

- Hardware (why pi)

• - Why Raspberry Pi

• - Setting up Hardware:

• https://wiki4print.servpub.net/index.php?title=Docs:01.1_Hardware_and_OS

• + further links to Raspberry Pi

- Remote Access to Hardware over a local network (workshop)

• - What constitutes a local area network LA

• - Physical layer of network infrastructure?

• - Routers / Wi-fi / ethernet / MAC addresses ?

• - Software / Internet Protocol layer

• - TCP / UDP / ports / IP Address  ?

• https://wiki4print.servpub.net/index.php?title=Docs:00.1_Network_terminology

• (Network Infrastructure chapter has some detail about lan/wan/van already + history and politics of IP Addresses IPv4 and IPv6, they touch on Static IP addresses) https://wiki4print.servpub.net/index.php?title=Chapter_2b:_Server_Issues:_Networked_Infrastructure

• What Protocol stack or internet infrastructure model do we want to use and what are the politics of that? Not sure what protocol stack is in Network Infrastructure Chapter (image of the hourglass). OSI or Internet Protocol Suite (TCP/IP) or is there something else?

• https://en.wikipedia.org/wiki/Internet_protocol_suite

• https://en.wikipedia.org/wiki/OSI_model

• - Protocols:

• - SSH (why pi / to enable networked/remote collaboration)

• https://www.raspberrypi.com/documentation/computers/remote-access.html#ssh

• https://wiki4print.servpub.net/index.php?title=Docs:01.3_SSH

• - Default Password Access

• - Setting up SSH keys per User

• https://wiki4print.servpub.net/index.php?title=Docs:01.2_Creating_Users

• https://wiki4print.servpub.net/index.php?title=Docs:01.3_SSH

• - TMUX ?

• - HTTP

• - Default set up on a pi?

• - Setting up a server with Nginx

• https://wiki4print.servpub.net/index.php?title=Docs:02_Local_Server_Setup_with_Nginx

- IP Addresses mapped to DNS / A Records / Tuxic

- Hand over to Syster Server Chapter? VPNs, Tinc, Reverse Proxy servers / routing traffic?

index.php?title=Category:ServPub