AHA gets its own bandwidth. We get a little server rack and throw some
servers in there. With these servers, we can:
* Host cool services of our own, that members can use, such as:
Email
Diaspora
Status.net
* Host AHA's website and such.
* Give AHAers VMs to do development on.
And, when the wireless mesh network is up, we can host all these services
on the inside of the network. So when the Revolution comes, and we're cut
off of facebook, twitter, and google+, we can still organize :)
ANYWAY.
I've been yammering about this stuff. Word on the street is that, if
we're going to host services out of AHA, we should buy our own bandwidth.
Xander had a brilliant idea, though: Rather than pay for this out of the
general funds we have, what if we sold hosting to people like us, to make
this bandwidth cost-neutral for AHA?
I know that many of us already pay for hosting in some datacenter in
chicago or what-have-you. Who would be willing to move your hosting to
AHA?
My plan is that we see who would be interested in moving their hosting to
AHA. We have a meeting to discuss what kind of service and reliability we
need. What is your estimated bandwidth usage? Do you need to have a
failover net connection? That sort of thing. What are you currently
paying for service, and how much would you be willing to pay at the new
AHA colo?
Once we know our needs and our monies, we go about contracting some
internet service, getting a rack, ups what? offsite backup what?
I loves me some system administration. I could volunteer to set up
services for AHA, and to set up some VM stuff for AHA folks to develop on.
Also, I can move my hosting to AHA. And Xander said he could as well.
Fun times? Who wants in on this AHA colo? Tell me who is in and we'll
have a little meeting over on the couches sometime.
Sincerely,
Ryan "Galaxor Nebulon" Hughes
--Jon
> Spam detection software, running on the system "dedicated37.virtbiz.com",
> has
> identified this incoming email as possible spam. The original message
> has been attached to this so you can view it (if it isn't spam) or label
> similar future email. If you have any questions, see
> the administrator of that system for details.
>
> Content preview: Okay, I have a Vision: AHA gets its own bandwidth. We get
> a little server rack and throw some servers in there. With these servers,
> we can: * Host cool services of our own, that members can use, such as:
> Email
> Diaspora Status.net [...]
>
> Content analysis details: (14.2 points, 5.0 required)
>
> pts rule name description
> ---- ----------------------
> --------------------------------------------------
> 1.8 FSL_HELO_NON_FQDN_1 FSL_HELO_NON_FQDN_1
> -1.5 BAYES_00 BODY: Bayes spam probability is 0 to 1%
> [score: 0.0000]
> 1.7 RDNS_DYNAMIC Delivered to internal network by host with
> dynamic-looking rDNS
> 2.6 HELO_NO_DOMAIN Relay reports its domain incorrectly
> 4.3 TO_NO_BRKTS_DIRECT To: misformatted and direct-to-MX
> 2.7 TO_NO_BRKTS_DYNIP To: misformatted and dynamic rDNS
> 2.6 TO_NO_BRKTS_NOTLIST To: misformatted and not a mailing list
>
>
>
>
> Spam detection software, running on the system "dedicated37.virtbiz.com", has
> identified this incoming email as possible spam. The original message
> has been attached to this so you can view it (if it isn't spam) or label
> similar future email. If you have any questions, see
> the administrator of that system for details.
>
> Content preview: Okay, I have a Vision: AHA gets its own bandwidth. We get
> a little server rack and throw some servers in there. With these servers,
> we can: * Host cool services of our own, that members can use, such as: Email
Steve
It sounds like we could all benefit from getting on one larger slice together, despite charger a colo works out. Also, I still have a blade in the server room that anyone isa welcome to try restoring
It sounds like we could all benefit from getting on one larger slice together, despite charger a colo works out. Also, I still have a blade in the server room that anyone isa welcome to try restoring
On Jul 29, 2011 7:26 AM, "Kelly Johnston" <lisette....@gmail.com> wrote:
Hm. Where are they physically?
Would they be amenable to being on the inside of the mesh network (once
it's up?)
--Ryan