|
|
|
|
|
|
by akg_67
4504 days ago
|
|
|
Like your concept. I am very interested in OpenStack myself, more look at it as a building block for private cloud. Sounds like you are trying to create a NOVA pool for virtual instanced from excess available CPU/memory capacity of the participant users. Not sure you really need to have OpenStack to achieve this. What will happen to all the virtual instances running on a NOVA node if a participant user turns off their NOVA node? Also, how are you going to handle shared storage side of OpenStack? About 12 years ago, I was trying to do something similar pooling together excess storage capacity and tried to position as solution for SMB and consumer market (big mistake). A positioning and solution focusing on Disaster Recovery and enterprise most probably would have been more successful. |
|
|
Each provider (a user) installs their own OpenStack cluster, which includes a nova controller. That cluster runs a virtual appliance who's job is to watch a given Bitcoin address for payments. If it sees a payment it either starts an instance or resets a counter to keep an instance running. Payments by users are taken by the pool operator. The pool then starts micro drips to the instance, in most cases half a cent or so.
The pool I'm going to run will be at stackmonkey.com. If a provider shuts off their controller, something crashes, or there's a rig failure, only a small percentage of the total number of instances will be affected. Payments won't matter because the instance costs are so low, and the drip can be turned off when the appliance stops responding to the pool controller.
OpenStack makes this handy because it handles all the heavy lifting for starting and stoping instances, doing network setup, images, instance sizes, etc.
Initial audience for this low trust pool will be hackers, developers, testers, tor nodes, individuals, etc. Very low cost, highly ephemeral instances.
There's a video here: https://vimeo.com/86717476