We’ve finally jumped the CoreOS ship over to Flatcar Container Linux by Kinvolk, an OSS fork of the original project. Everything has been faithfully copied over and is once again running smoothly.
Thanks to Kinvolk for keeping the Container Linux legacy alive!
It’s been quite a move for Laboratory B! Our new location at 12-22 North has come with plenty of perks, but at the same time, it’s placed new constraints on things like space, parking and electricity use. As Matt Cropp mentioned in the previous post, the new space has a cap on free electricity use – so as part of the move, we’ve had to temporarily suspend our on-site server hosting policy.
Unfortunately, that conflicts with one of the priorities we formulated during the move – that we should consider migrating away from the locked-down services (offered by Google, Amazon and their ilk), and instead look towards self-hosted, open-source infrastructure to run our day-to-day Lab activities. (After all, free and open-source software is practically in our mission statement.)
So, how could we reduce our power footprint but still run servers? One suggestion was to use virtual private servers (VPS) – but the monthly cost of hosting was potentially prohibitive, and relying on webhosting would bring us further from truly controlling our own infrastructure. The nail in the coffin, though, was probably that we still had a surplus in our budget of renewable electricity – and some napkin math showed it might be enough to run servers with, if only we use the right kind of hardware. Napkin math devolved into discussion about Intel “Avoton” Atom processors and triple-digit-core ARM boards – but discussion matured into dejection when the price tags came up. The Lab did not have loose cash.
Around the same time, I had set up a Dockerized GitLab server on an old Mac Pro at home, to help organize our projects and handle support tickets from AJ, our landlord at 12-22 North. (Context: As a component of our lease, we are granted a rent discount in exchange for rendering IT support, in a sort of skill-share scheme.) I soon discovered, however, that the Mac Pro doubled as a space heater, drawing over 200W at near idle. I needed a solution that wouldn’t cook me alive when the summer came around – and one night, as I aimlessly browsed Youtube, the solution presented itself.
Laptop are plentiful, use cheap RAM, idle at low wattage, have an integrated UPS (the battery, duh!) and KVM – all things a server could use! Plus, if you don’t mind going without one or two of those things, you can find some absurdly cheap hardware – and find I did, in two dirt-cheap X230 motherboards. Long story short, for $100 a pop, I was able to cobble together two machines (i5-3320M + 16GiB DDR3), each of which could rival the Mac Pro, but which consumed a whopping nine watts at near-idle – 5% of what the Mac Pro was drawing.
I christen thee Bones Mk1!
As hacky as it is, having a server solution that can be hosted at the Lab means we can house new open-source platforms – Etherpad / Etherdraw, Mattermost, Funkwhale, Mastodon, Matrix … for just now, the GitLab is the lone tenant, but our only limit is how many laptop skeletons we can fit in our server closet.
As we settle into our new space on North Street, one project Lab B members have been working on is an updated membership agreement and code of conduct. Members are the core of Lab B: they govern our organization democratically, expenses are funded primarily by their dues, and, as an all-volunteer non-profit, their work is what makes things happen.
Thus, to clearly communicate what is expected of Laboratory B members, the following was passed by a vote of the membership this month:
As a member of Laboratory B, I, _______________________, agree to the following, as well as to terms in any future version of this agreement as amended by the organization’s membership:
Financial Accountability
The Lab maintains our autonomy and flexibility through the core of our funding coming from member dues. Therefore I will…
…make every effort to pay dues on time.
…make a good faith effort to pay the appropriate dues on the sliding scale relative to my income and wealth, and will reassess my dues level relative to my means regularly.
…remain in open and responsive communication with the Treasurer to make arrangements if dues become outstanding.
…contribute to supporting the terms of our lease.
Operational Accountability
The Lab is an all-volunteer organization that requires active member participation to function. Therefore I will…
…make good-faith effort to attend the monthly member meetings, to participate in asynchronous decision-making on Loomio, and to keep up on operational conversations on Slack.
…make every effort to maintain the cleanliness of the Lab and common spaces.
…be responsible about the use of shared space and leaving project spaces clear when I leave the space.
…be responsible for the actions of any invited guests.
…be willing to share efforts in running Lab activities, such as hosting regular public hours, offering skill-shares, volunteering at community outreach events, etc.
…shut off lights, lock doors, turn off power strips, and follow shutdown procedures when leaving the building.
Social Accountability
To maintain a healthy community, Lab members take accountability for their behavior towards both their fellow members and the community at large. Therefore I will…
…advance and exemplify our mission and vision.
…maintain the active sponsorship of a Lab member for issues of mediation and dispute resolution.
…contribute to a goal of restorative justice. I will participate in good faith in a restorative justice process if asked to by the Lab community.
…maintain confidentiality about information and conversations if asked to by a fellow Lab member, and about topics designated confidential by the membership as a whole.
…abide by the Lab Code of Conduct with the following elements, and as may be amended in the future by the Lab membership:
Generally: Be excellent to each other!
Curiosity: Cultivate a culture of curiosity and exploration. Don’t discourage enthusiasm and exploration of a topic by others because it does not interest you.
Respect: Treat fellow Lab members & visiting community members with respect.
Disagreement: The Lab encourages the free exchange of ideas, while respecting others’ experiences and perspectives. We agree to work together to cultivate an environment that creates space for approachability and for resolving disagreements safely and productively.
Boundaries: Respect the boundaries of others, and be clear and explicit in the communication of your boundaries if you feel uncomfortable. If you have trouble communicating your boundaries, seek assistance from your sponsor or another trusted Lab member. An ounce of awkward conversation is worth a pound of festering resentment.
Reputation: Do not sully the good name of the Lab. Operate with respect and conscientiousness in the community in public-facing contexts, and be cognizant of the Lab’s social clout and the ramifications of that identity out in the wider world. Agree to report ASAP any personal or observed actions that might reflect poorly on the Lab community to the Lab President (or another Board member).
Humility: As a member, I agree to admit that there will be times that I am wrong. The Lab is full of sharp folks, but intelligence is not an excuse for arrogance.
After a heroic move-out effort by Lab members and volunteers, and a month of being a “virtual Lab” operating out of a storage locker, Loomio group, and pop-up event spaces (thanks, Bytes.co!) we’re pleased to announce that Laboratory B once again has a space!
After considering several possibilities, our membership voted to move into a room on the second floor of 12-22 North Street in the Old North End. In addition to our new HQ space, where we’ll be holding public hours, meetings, co-working sessions and small workshops, the lease also gives us access to a number of shared spaces we can use after business hours, including a dedicated electronics lab, a sizeable class/event space on the first floor, and basement storage.
Many things about the Lab will stay the same, but a sampling some of the changes the move offers that our members are excited about include:
Handicapped Accessibility for Many Events: In the Soda Plant, all of our space was up a set of steep stairs, limiting accessibility of workshops and other events for folks with mobility challenges. While the Lab’s dedicated room is similarly only stair-accessible, our ability to reserve the large downstairs space means that many of our public-facing workshops and events, such as mobile security night and LAN parties, will take place in accessible spaces.
Direct Access to Our Space In Off Hours: In the Soda Plant, the outside door was usually locked after 5pm, so public event attendees needed to ring a doorbell and be guided through a labyrinth to access the space. So, we’re every excited that our new space has a door opening directly to the outside.
Some members in the new Lab B (after hauling up the first load of chairs and a table)
Environmental Impact: In the Soda Plant (and the Hood Plant before it), we were occupying the decaying remains of industrial infrastructure, and it definitely showed in the winter time with heat loss through single-pane windows, etc. By contrast, 12-22 North Street is an optimized energy-efficiency machine: it was built by a worker co-op in the 1980s with a passive solar design, has significant installed solar electric capability (including wiring for DC lighting), and is run by a landlord who works on IoT sustainability and environmental impact monitoring. The fact that we have a monthly kWh cap in our lease has sparked our thinking on how to sip rather than chug energy (no more using out-of-date servers and crypto miners as de facto space heaters in the winter). Whether this transition means our aesthetic center-of-gravity will shift from cyberpunk to solarpunk remains to be seen…
Space that is more fully “ours”: At the soda plant, we were subletting from Brandthropology, who were incredibly accommodating partners, but pretty much all of our space was at least somewhat shared, in they needed to walk through our main room to get to the shared Couch Room and kitchen. We now fully control our core space, while also having access to additional shared spaces and resources in the building.
We’ll be spending the next few weeks moving in and setting up, and are planning to host a “Lab Warming Party” for our initial Thursday public hours on February 21 from 7-9pm. For more details, check the Facebook event, and, as always, keep an eye on our calendar for upcoming Lab B happenings!
After several years in residence on the top floor of the Soda Plant on Pine Street, Laboratory B has officially left the building as of 1/1/2019. Many thanks to the members who put in lots of hours, leg, and back-work over the past month to prep to space for our move, and also great appreciation to the friends of the Lab who showed up on the 30th to help with the big move day!
Half-way into filling the storage locker…
The move has been a great opportunity to assess and discard a good deal of superfluous stuff, while our core materials are safely ensconced in a Champlain Housing Trust storage locker, ready to be deployed at our next space….
We’re already in talks with a few possible new sites for the Lab, but are being deliberate about the process so we can land on the best spot for our community’s needs. We’re in search of a space with a maximum all-inclusive cost of $700/month; it can have shared spaces, be a sublet arrangement, etc., but needs at least one room that Lab members will have exclusive access to. So, if you have a lead for the next venue for Burlington’s member-run and -governed hackerspace, please get in touch by shooting an email to [email protected]!
In the meantime, Lab-sponsored events will be popping up in various locations around town, and we’ll be using the spare capacity derived from not having weekly public hours to do some internal work to position us for success in our 5th (!) location since the Lab was founded in 2009. If you want to keep in the loop, follow our shared calendar and Facebook page, where events and announcements will be posted, and we’ll post to this blog when your new space is finalized.
Happy New Year, and we look forward to sharing the next iteration of Laboratory B with the Burlington community in the coming months!
Ever wondered exactly what those black helicopters are up to? Thanks to a federal law called the Freedom of Information Act (FOIA), you can find out!
At the FOIA party, we’ll get together, brainstorm ideas, teach the basics, and discuss techniques for getting the information you’re after. Bring your most burning government questions (local, state, or federal), and we’ll make sure everyone leaves with at least one request under their belt.
The “Intro to FOIA” presentation by Brian Waters will start at 7:15 and run approximately 30 minutes, including Q&A.
Following the presentation, there will be a workshop session in which attendees will file their first FOIA requests, so, if you are interested in doing so, bring along a laptop!
We’re excited to add a new event to the Lab’s roster: the BTV Hacker Book Club! The group will be meeting monthly to discuss a book drawn from a list built by Lab members, with members voting on which book from the list to read each month. While Lab members pick the books, all who have read the book are welcome to the discussions, and attendees are welcome to bring munchies and beverages to share.
Our first pick is A Hacker Manifesto by media theorist McKenzie Wark, and we’ll be gathering for the discussion on Thursday, 8/17 at 6pm in the Couch Room. For more details and updates, RSVP to the Facebook event.
We’ll be discussing setting a recurring monthly date at the August meeting, and Lab members are presently voting on the September book pick. Cyberpunk classic Neuromancer by William Gibson currently holds a narrow lead, but there are a few more days for members to weigh in…
Want to carry around a world of important data, like Wikipedia, and health guides?
Need a way to share a bunch of files with some folks?
Come learn how to make a PirateBox a tool for sharing information in a secure offline manner!
PirateBox is a DIY anonymous offline file-sharing and communications system built with free software and inexpensive off-the-shelf hardware. Perfect for public spaces as a means of sharing interesting data and having offline discussions.During this quick 4 hour class students will learn how to build a Pirate Box. This class will guide students through the process of converting a plain TP-Link MR3020 and USB thumb drive into a Pirate Box.
$50 lab fee covers purchase of Pirate Box and all necessary materials (MR3020 & USB Drive).
A few Lab members recently asked me “how do you survive power outages?”
Here’s how, and it’s all available at your website or department store of choice (cough cough Amazon, Wal-Mart)
One (1) marine deep cycle battery, as large as you can afford
and/or can carry (approx $80) (must buy in store)
One (1) 12 volt trickle charger (approx $30)
One (1) 12 volt to 120 volt inverter, sized according to your needs. 200 watts will power a few devices for around $40; do yourself a favor and get a 600 watt Tripp Lite or similar, around $90
Optional: One or more 12V accessory plugs, to wire into battery (approx $10/ea)
My current “Power Box”, pictured below, is currently out on an off-grid island staged and waiting to run some Civic Wireless customer premises equipment. The box will run network gear on a small inverter for weeks on a full charge.
Part 2: Exploring solar trickle charging.
Questions? Email: help [at] civicwireless.org
–Chad
With some inspiration from the potential snow storm last week, I endeavored to test my emergency preparedness for heating my apartment when the power is out. I never did lose power, but the test was successful and I am happy to know that if I did lose power in the winter, I can keep warm at home.
I attached an inverter to a marine battery, then plugged in my Rinnai heater and it ran just fine. The Rinnai does buzz a bit loudly, but that’s because the inverter does not produce a “true-sine-wave” signal. I tested the setup with a box-fan attached to the inverter as well and it worked fine.
With the fan and the heater both running on LOW the draw was 115W. Some quick and super dirty math approximations tell me that the battery (if fully charged) will run this about 11 hours. This would be longer if the box-fan isn’t running (less power would be used).
105 Amp hours (sticker value, full charge)
105 Amp hours x 12v = 1260 watt hours (approximate average voltage)
1260 watt hours / 115 watts = ~11 hours
Of course, the inverter can be run from any 12V source. My Honda Civic has an alternator with a faceplate rating of 70Amps. Some quick math tells me how much power this can potentially provide.
70 Amps x 12 Vdc = 840 Wattsdc
I believe the inverter is well within the ability for the alternator to run. So the car could potentially run the inverter as a generator as long as there is gasoline in the tank.
Check out the rest of the info and pictures at my blog.
Inverter attached to batteryRinnai heater on extension cord w/ box-fan
During this quick 4 hour class students will learn how to build a Pirate Box. This class will guide students through the process of converting a plain TP-Link MR3020 and USB thumb drive into a Pirate Box.
attery (approx $10/ea)
