Root server sharing under supervision of Ecobytes?

This post is intentionally a wiki post. Use the power.

Dear @auli, @ArneBo, @aporia @gualter, @asdx and @elfpavlik .

As OuiShare need quick solutions and Ecobasa have about two months to converge plus Edgeryders and unMonastery kind of agreed already, we can already lay out the framework of our cooperation. Fortunately, Ecobytes is offering very flexible services in this case.

Needs

The needs of the different organizations that I can overview are presented seperately below.

TransforLab

further for TransforMap

  • Ethermap
  • uMap
  • OSM Tasking Manager
  • GeoCouch

plus several smaller services like the Taxonomy Editor.

OuiShare

possibly

  • OwnCloud
  • Etherpad
  • Mailing Lists?
    • Discourse
    • GroupServer
    • Sympa
    • Mailman
  • Multiple environments
    • PHP (WordPress, MediaWiki, drupal)
    • Ruby

Edgeryders

  • Testdrives
  • Possible migration when neccessary

unMonastery

  • Blogs Ghost
  • Websites Node
  • Mail

Current State

We are actively working on deploying additional VMs and get new mail services running. Internal networking and hardening are still a bit at stakes, but progressing well.

With the additional IPs that have been acquired for TransforMap, we will soon be able to offer GroupServer Web Mailing Lists, GitLab for private repositories of version controlled files and Dokku Alternative for a flexible PaaS/IaaS hybrid hosting, which will allow us to serve virtually every hosting need. See their websites for details.

If that works out nicely, we’re only close to offering a wide range of excellent stuff like

  • Loomio
  • Discourse
  • GitLab
  • Sentry
  • Uptime
  • Taiga
  • CI ( Travis, GitLab CI, Jenkins )
  • Huginn or
  • Bip.io and

which will only be the first services to come. If we can quickly spin up complex infrastructures, our social resilience increases exponentially (t.b.p.).

Actually it makes sense for Ecobytes to rent a new root server for the new guests, as some legacy services are still going to be migrated to the already existing hosts. Finally we need to apply IPv4 subnets to the hypervisors instead of individual IPs, so supporting partners can receive reliably seperated environments.

An example calculation can be found in an Etherpad.
But of course we can also just go on updating the existing infrastructure constantly.

Outreach

The infrastructure can be further scaled on a roadmap similiar to Panamax + IndieHosters > OpenStack + OpenShift > Mesosphere.

@gualter Can we acquire the last additional IPv4 address of the respective machine for the d:space experiment now, so it doesn’t need to wait until we figure out more complicated internal routes?

Conforming with the Etherpad, we’re also trying to get in touch with

to find out if they would be willing to further extend the network of independently and fair hosted IT services. I am inviting some of them as marked above using the button below.

If we get this running, I can transfer two currently external VMs to that setup and provide another ~100 € from my private funds in the name of allmende.io to the pool.

Then we could also start thinking of using geographically spread locations for quick worldwide reachability, esp. if we imagine of scaling up to organizations like Shareable, i.e. by providing mapping services, and so forth.