Loading...
 

Orchestrator

WikiSuite Orchestrator

WikiSuite Orchestrator will help manage a large number of WikiSuite instances.

  • Deploy and manage software
  • Deploy data and configuration
  • Monitor
  • Aggregate data
  • Handle billing
  • etc.


Status: planning phase for big picture, while some components are mature. Ex.: Tiki Manager

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 basic IT needs, and instead focus on their market differentiator
Enterprise and governments Large organizations have thousands of systems and a lot of complexity. Diverse projects/systems can be made with WikiSuite (mostly with TikiTrackers.org). So needs are addressed with a consistent platform. projectABC.example.com, projectXYZ.example.com, etc.
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 -> SaaS platform template
Consultants and digital agencies Quickly set up an 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

  • On-demand deployment of virtual machines with WikiSuite fully configured.


Current code (to be built on) and brainstorming

Manage

Monitor

Aggregate

WikiSuite Orchestrator will permit to deploy hundreds of WikiSuite instances. But what if we want to benefit from network effects? We need to think of the "creep factor".

Use cases

Billing

WikiSuite is Open Source and users are encouraged to self-host.

However, a portion of the community prefers a SaaS without vendor lock-in.

Thus, we need to be able to track usage and bill accordingly. Formulae have yet to be determined. Some options include

  • Resources used (CPU, Disk space)
  • Users in various groups (groips with more features have higher fee)
  • Action (views, edits
  • Data (number of pages, items, etc.)

Backups

Automatic, Incremental, off-site and with some sort of test / alerting if something's not right (ex.: disk full)

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

Priorities

  • Let's start with Virtualmin, Tiki, Syncthing, Elasticsearch and Openfire.
  • Then, the others

Brainstorming for the future

What / where Marketing Security Management
WikiSuite instances Web Analytics IDS data aggregation ALM
Open Web Media Intelligence and Competitive intelligence Email Antiphishing n/a
Client devices n/a VPN MDM like Flyve MDM


https://en.wikipedia.org/wiki/Machine_learning is now in Tiki: Machine Learning

alias