On Monday, March 03, 2014 12:31:51 Justin Herman wrote: > My question is why no other options viable for hosting?
It isn't just about hosting our website. SYNHAK.org is a playground for people who want to build a hackerspace's online infrastructure. If you're against that, I'd be happy to ramp up my efforts to protect our culture of exploration and inventiveness that supports the hacker community. > > Why MUST we use AWS? Why do we need 99.99 availability for 6 servers? Why > could we not hybrid the design (like Craig said) and use some local hosting > and some AWS? I'll produce a report that shows why AWS is the best option for fulfilling our goals. Hint: 99.99% availability isn't the primary reason. > > Hardware is cheap and easy to come by. Hosting our own allows us to have a > TON more CPU and RAM and storage. It something like spiff/wiki/fileserver > due to hardware failure, upgrade needs, network connection... we could > always but a static page for our contact info so it doesn't seem like we > fell off the face of the internet. Whats your solution to physical security against someone who accidentally fires a javelin through a server? Or flooding in the basement? Or pouring beer on a switch? > > If we want to have a class on AWS by all means fire up a demo site. That > has nothing to do with our production infrastructure. Saying "production" implies that we're sometimes not flying by the seat of our pants or actively hacking on things while they're being used. Is this the wrong time to mention that I deleted a web server from the face of the 'net using my phone while en route to Annabell's Saturday night to prove that our setup is in fact incredibly fault tolerant? > > I know we all want more internet and lots of people SAY TWC is unreliable > but I haven't seen anything saying HOW unreliable at the 48 Summit space it > is. Are we down or frequent outages? Not getting promised service <BW>? > Excessive packet loss? Are we taking metrics? I'll try and find the data I produced back when they were screwing us over at 21 W. North. Essentially, we were getting maybe 20% of what we were paying for. There also is no QOS contract. There also is nothing stopping a hacker from ripping out the modem and leaving us without internet for a few days while a replacement is sourced. Or even worse, city maintenance severing a physical line underground. > > And if TWC is that bad WHY was it chosen to use them? You're joking, right? What other options are there? They've got a monopoly. Starting a municipal ISP wasn't just an idea we threw out there for fun. > > On Mon, Mar 3, 2014 at 12:05 PM, Craig Bergdorf <mm1...@gmail.com> wrote: > > or, if it's $200 and you know for a fact the space needs it right now, > > just grudgingly buy it and hold mild anger towards those that said it > > wasn't needed (sorry, in a mood). Unless (crosses fingers) this is meant > > as a way to test a new, functional system for the space approving > > purchases, if so: > > > > Is there a budget for the space that includes consumables like toilet > > paper that any member is allowed to see / comment on? What percentage of > > the remainder of that does this $200 represent? > > > > As I mentioned before, I think this is a great idea, and the lower price > > tag just makes it better. I also have mentioned we should be paying more > > for internet so we can supplement our real host with some old fashioned > > house file servers (and a webcam/open sign/phone that doesn't require so > > much maintenance). > > > > If a call for comments is up, my only concern is one of not knowing if the > > amount we have for monthly improvements has included all the consumables I > > would think higher priority (such as toilet paper). I am also surprised > > that there is a penny left in this fund after 2 months of building. > > > > On Mon, Mar 3, 2014 at 11:45 AM, Torrie Fischer <tdfisc...@hackerbots.net>wrote: > >> On Monday, March 03, 2014 11:35:51 Justin Herman wrote: > >> > I agree with Andrew, > >> > > >> > I hold several concerns about this proposal and think we need to > >> > >> evaluate > >> > >> > the needs of the infrastructure. > >> > >> If you've got "several concerns", what are those concerns? I too can > >> claim to > >> be "concerned" about something and not actually say why. > >> > >> Instead of doing any useful synhak work today or tomorrow, I'll be > >> producing a > >> technical report that shows why this investment will benefit the hacker > >> community we aim to support. > >> > >> > On Mon, Mar 3, 2014 at 11:33 AM, Andrew Buczko > >> > >> <a4s...@dsprototyping.com>wrote: > >> > > WAT? > >> > > > >> > > first you said it was $1.60 > >> > > Then $16.40 > >> > > Now it's $123.10 > >> > > > >> > > ? > >> > > > >> > > On Mon, Mar 3, 2014 at 11:09 AM, Torrie Fischer > >> > >> <tdfisc...@hackerbots.net>wrote: > >> > >> Previous thread: > >> > >> > >> > >> https://synhak.org/pipermail/discuss/2014-February/003393.html > >> > >> > >> > >> I'd like to propose that we spend $200 to reserve the two t1.micro > >> > >> instances > >> > >> in that proposal for the purpose of web servers. > >> > >> > >> > >> Our current AWS expenditure is still ~$80/mo. Spending $200 up front > >> > >> will > >> > >> > >> reduce that bill by $16.40/mo and keep our infrastructure expenses > >> > >> low > >> > >> > >> for the > >> > >> next three years. Thats an extra $16.40 we can invest elsewhere with > >> > >> a > >> > >> > >> break > >> > >> even point of 12 months. > >> > >> _______________________________________________ > >> > >> Discuss mailing list > >> > >> Discuss@synhak.org > >> > >> https://synhak.org/mailman/listinfo/discuss > >> > > > >> > > _______________________________________________ > >> > > Discuss mailing list > >> > > Discuss@synhak.org > >> > > https://synhak.org/mailman/listinfo/discuss > >> > >> _______________________________________________ > >> Discuss mailing list > >> Discuss@synhak.org > >> https://synhak.org/mailman/listinfo/discuss > > > > _______________________________________________ > > Discuss mailing list > > Discuss@synhak.org > > https://synhak.org/mailman/listinfo/discuss _______________________________________________ Discuss mailing list Discuss@synhak.org https://synhak.org/mailman/listinfo/discuss
