Loading...
 

History: Orchestrator

Preview of version: 47

WikiSuite Orchestrator

WikiSuite Orchestrator helps manage a large number of WikiSuite instances.

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


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 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)
https://gitlab.com/wikisuite/virtualmin-installer/
https://doc.tiki.org/Tiki-Manager-Web-UI

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 Gateway Antiphishing n/a
Client devices n/a VPN MDM like Flyve MDM


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

alias

History

Advanced
Information Version
Marc Laporte 55
View
Marc Laporte 54
View
Marc Laporte 53
View
Marc Laporte 52
View
Marc Laporte 51
View
Marc Laporte 50
View
Marc Laporte 49
View
Marc Laporte 48
View
Marc Laporte 47
View
Marc Laporte 46
View
Marc Laporte 45
View
Marc Laporte 44
View
Marc Laporte Vaporware 43
View
Marc Laporte 42
View
Marc Laporte 41
View
Marc Laporte Mist deserves its own page 40
View
Marc Laporte 39
View
Marc Laporte 38
View
Marc Laporte 37
View
Marc Laporte 36
View
Marc Laporte 35
View
Marc Laporte 34
View
Marc Laporte 33
View
Marc Laporte 32
View
Marc Laporte 31
View
Marc Laporte 30
View
Marc Laporte 29
View
Marc Laporte 28
View
Marc Laporte 27
View
Marc Laporte add an alias 26
View
Marc Laporte 25
View
Marc Laporte 24
View
Marc Laporte 23
View
Marc Laporte 22
View
Marc Laporte 21
View
Xavier de Pedro 20
View
Marc Laporte 19
View
Marc Laporte 18
View
Marc Laporte 17
View
Marc Laporte 16
View
Marc Laporte 15
View
Marc Laporte 14
View
Marc Laporte 13
View
Marc Laporte 12
View
Marc Laporte 11
View
Marc Laporte 10
View
Marc Laporte 9
View
Marc Laporte 8
View
Marc Laporte 7
View
Marc Laporte 6
View
  • «
  • 1 (current)
  • 2