Revision history [back]

In FIWARE Lab we have 2 kind of cloud users: Trial users and Community users. Trial users are supposed to be users who are allowed to test FIWARE Technology using FIWARE Lab Cloud deployment for 15 days. After 15 days they will be removed. Community "long term" users which have asked the FIWARE Team to hace a community account and a reason to have that kind of account. This basically means that they are building a project based on FIWARE.

End-user and customer are basically the same.

If you are going to have a private instance of FIWARE Lab, you will have some kinds of "organizations" called Tenants of Projects. This means a group of users working together in the same project(s) and sharing the resources of the project.

You can set your own network requirements and set the quality you want to deliver your customers in your openstack installation. The one shown there is a good one which has shown to be performant enough for the typical requirements of a development process of many people at the same time.

The allocation of resources based on Openstack can be found in Openstack documentation: https://docs.openstack.org/arch-design/design-compute/design-compute-overcommit.html * 1 core ~ 16vCPU * 1 Gb RAM ~ 1.5 Gb of vRAM * 1 Gb HD ~ 1 Gb of HD

So, 1 physical host with 8 cores and 32Gb of RAM (28Gb just to let the Operating system room enough) should be able to host more than 20VMs 2Gb of RAM and 20Gb HD each, if it has 500Gb of free disk space --- This hosts running Virtual Machines are called Compute Nodes.

22 Gb for images it is for the whole Openstack installation in order to have all the FIWARE images. Although you could think that people would need to make their own snapshots and you could need another 100Gb per project. You might need even more disk space in order to let your users create their own persistent disks, and if you allow them to use object storage, you might need even more disk space. You can decide your quota per project (how much disk space you want to let your users in a project have).

An idea is to have 2 physical host for "openstack controllers" in order to install the Openstack Services with HA (one might be enough wihtout HA). and some more hosts for your customer Virtual Hosts (Compute Nodes). You can add new compute nodes later.

Your users will need a public IP to access their VMs so their services could be reached from outside your network.