specs
Sellable box with gig branded Mountaintop, OpenvStorage and a management layer in Mothership1, managed by At Your Service.
Git repository: https://git.aydo.com/0-complexity/openvcloud
Even though in this version "Billing" does not make much sense, having an overview of the consumption is still nice. As such, most of the current billing visualization and the payment flows have to be removed.
- Internally, set the price of all items (space, machines, disks) to 0
On the billing page:
- Change "Billing" menu item to "Consumption"
- Remove "Balance & Usage" Block
- Remove paypal payment api
- Remove "History" title
- Remove "Amount, credit and status colums"
On the usage report page:
- Remove the costs on accountlevel, spacelevel and machinelevel
On the Knowledge Base:
- Remove the entire billing section
On the Quick Tutorial
- Remove the billing explanation on the cloudspace tab
-
Remove from the Home page
-
Remove from the Right Menu
-
Remove from the Quick Tutorial
- Remove application Deck from the Knowledge base
- Remove application Deck from the right menu
- Remove application Deck from the home page
- Remove application Deck from the quick tutorial
No S3 will installed on the OpenvCloud box. As such this functionality needs to be removed both from the UI and from the rest API.
- Remove the Storage rest API
- Remove the link to the Storage API documentation
- Remove the Storage Deck from the menu
- Remove the Storage Deck from Getting Started
On the knowledge base:
- Remove the Storage Deck menu item
- Remove the S3 windows client item in technical questions
In a private context, no self sign up is desired.
User management can be done through the admin portal, no need for user administration pages in mountaintop UI itself.
Not only the UI for the signup should be removed, this functionality should also be removed from the rest api.
Remove MS1 logo and dark background, change to http://www.greenitglobe.com style
Replace with Mountaintop background like https://extranet-gig.aydo.com
Change to "OpenvCloud"
Proposition: replace with #345E79;
Search in the CSS for the MS1 blue, and replace it all (Titles, menubar, table headers)
Currently the mountaintop software stack uses qcow2 files as volumes for virtual machines. Instead of these qcow2 files, the openvstorage volumes should be used.
Concept:
- Our current images are converted to openvstorage volumes.
- At vm creation, instead of creating a new qcow file pointing to the master image, a new openvstorage volume is created pointing to the master volume (should be done through the api).
- KVM is started to work with raw files (=the openvstorage volume just created)
- Snapshots are created using the openvstorage api.
- Templates are snapshots on openvstorage of existing volumes
Even though openvstorage does not rely on the volumes being created on the same node as where the hypervisor runs, this does benefit initial performance. This means the current implementation that executes the creation of the volume on the same node as the hypervisor that is going to run the vm should stay in place.
Documentation: http://doc.openvstorage.com
According to Stefaan, the api is probably not sufficient and the python libs can be used: http://epydocs.openvstorage.com/stable/lib/
In order to convert our current machine templates, a procedure is needed to convert them to base images on the openvstorage system.
Open questions:
- DNS
- Replication
- SSL certificate: custom or wildcard
Fork the current MS1 implementation to https://git.aydo.com/0-complexity/openvcloud