May 13 2016

Cloud Beta | VM Controller – DIY CloudPanel Prototype update

As mentioned in the original release announcement of the Early Beta, , I’ve updated the framework and functionality to have a better glimpse of what’s to come. Check out the new update and use the “Trial” function which only requires using your API Key to see the system in action:

As you can see, I used the official 1&1 CloudPanel as my inspiration for design and functionality but will look to change things up as functionality becomes more complete. For now, it’s more to just limit the learning curve.

The endgoal will be to create a system that you can host on your own, sell servers to your clients, and the hope will be that your clients will never have to know or worry about whom your vendor is. Currently that vendor will be 1&1, but as time goes on, I’ll create a modular design to allow you to choose between the different companies like DigitalOcean, Linode, and AWS. Unfortunately, most providers don’t provide the same features that 1&1 provides like Firewalls and Load Balancers.

Business logic proposal

Currently 1&1 shows all servers to every API users, but allows ACL control to limit who can create/delete. For this reason, our users =/= API users, as we don’t want our users to be able to see other users’ servers.

In the future, you would assign our CloudController to have a number of API Keys for provisioning, each API key relates to a different 1&1 Cloud Contract which has a 99Server limit. We can then set up rules about how many users can be assign to each Provisioning server, and how many servers each user can have. From there, it’s simply like having Shared Hosting accounts, but each user owns their own server, and the “Host” is our Provisioning contract

Say we have 3 “Tiers” we sell:

  • Small: 5 server limit per user
  • Medium: 10 server limit
  • Large: 20 server limit

Small limitations

  • 18-9 users per Small Provisioning Contract
  • 5-10 servers reserved for shared MySQL DB servers, a DHCP server, exceptions

Medium limitations

  • 9 users per Small Provisioning Contract
  • <10 servers reserved for shared MySQL DB servers, a DHCP server, exceptions

Large limitations

  • 4 users per Small Provisioning Contract
  • <10 servers reserved for shared MySQL DB servers, a DHCP server, exceptions

Overall Limitations

  • Once they’re placed on a contract, they can’t be taken off. There’s no way to move a VM between contracts at the moment with 1&1
  • To overcome, you must price the tiers accordingly. Customers who know they won’t need more than 5 will choose Small Tier for the price, while others will get the Large because they know they’ll need it. (In Theory)

Copyright 2020. All rights reserved.

Posted May 13, 2016 by Timothy G in category "1&1 Internet", "Admin Tools


  1. By linux interview questions on

    Amazing things here. I am very satisfied to peer your article.
    Thanks so much and I’m taking a look forward to contact you.
    Will you kindly drop me a mail?


Leave a Reply

Your email address will not be published. Required fields are marked *

This site uses Akismet to reduce spam. Learn how your comment data is processed.