History: Orchestrator
Preview of version: 18
WikiSuite Orchestrator
WikiSuite Orchestrator is to deploy, manage, monitor, aggregate data from and handle billing for a large number of WikiSuite instances. Each instance is an autonomous virtual machine, and can be moved to a different physical server.
Status: planning phase
Who is this for?
| Who | Benefit / use case |
| Business incubators | Offer a platform to all your members, so they don't waste time / money on this, and focus on their differentiator |
| Enterprise and governments | Large organizations may want to have autonomous entities, either as a subdomain or a different domain name |
| Universities | Offer your professors and researchers secure collaboration spaces |
| Hosting companies | Offer usable and integrated software instead of just hosting |
| Specialized SaaS service provider | Ex.: a firm specialized in a vertical market like ISO compliance could deploy very focused WikiSuite instances for each project. To be combined with Tiki Profiles |
| Consultants | Quickly set up a Tiki instance for a client project |
| FLOSS / digital autonomy promotion associations (ex.: Framasoft, FACIL, etc.) | Promote FLOSS in a more integrated fashion than the current Framasoft setup |
High-level features
Deploy
Manage
Monitor
Aggregate
Billing
The billing will typically be per instance, and per ressources used (CPU, Disk space), regardless of the number of users
Tiki instance to manage
- Project / customer list
- Domain name (use own or a provided sub-domain)
- Access (passwords, public keys)
- Payment
- Monitoring? (probably better to handle from another system)
- Registration
- Launch request for services
Development
- Do we start on https://github.com/wikisuite/ ?
Priorities
- Let's start with ClearOS (perhaps unregistered), Tiki and Openfire
- Then, the others