Loading...
 

History: Orchestrator

Preview of version: 30

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 basic IT needs, and instead focus on their market 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 -> White-label SaaS platform
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.

Manage

Monitor

Aggregate

WikiSuite Orchestrator will permit to deploy hundreds of WikiSuite instances. But what if we want to benefit from network effects?

Use cases

  • Gather logs
    • For security purpose (ex.: attack logs)
      • These security logs can be agregated and when bad behavior is detected for some of the instances, mitigation measures can be implemented for all instances.
      • This is closely related to the FusionCenter project
  • Marketing
    • Usage logs
  • Community


Billing

The billing will typically be per instance, and per resources 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

Priorities

  • Let's start with ClearOS (perhaps unregistered), Tiki 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 Gateway Antiphishing n/a
Client devices n/a VPN MDM


https://en.wikipedia.org/wiki/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