Open Source Cloud Platform
Cloud platform developed and designed according to the Open Infrastructure principles
Fluctus is based on the most recent and stable version of OpenStack. It can be expanded with additional resources and functionality based on need.
Create your cloud based on real needs: to obtain a local private cloud infrastructure or one distributed across third party structures for a remote private cloud within your datacenter
In both cases, Fluctus can be connected to the most widely used public cloud providers to plan a multicloud distributed infrastructure.
With Fluctus as the basis for a true open infrastructure, you won’t have to worry about hardware or software constraints. Our Open Source Cloud Platform is a solution without lock-ins, including from the point of view of functionalities and services: each of them can be activated and deactivated easily to radically change the scope and shape of the infrastructure. This is something that can be defined as true infrastructure-as-code.
FREE No vendor, software, hardware, provider or service type lock-in. Simply because the best choice for your infrastructure today may not be the one most suited to tomorrow’s needs. Those who manage cloud infrastructure must be able to change strategy both quickly and rapidly.
SECURE The private cloud enables users to personalize their security policies based on their own needs. This enables organizations to protect intellectual property and sensitive data in a more efficient manner compared to a public cloud
REDUCED COST Fluctus permits a significant reduction of two of the main line items in the maintenance of a cloud infrastructure. It reduces the cost of manual operations thanks to the degree of automation and permits the discontinuation of commercial products, replacing them with open source alternatives
EXPANDABLE Selecting OpenStack, your cloud platform can be built exactly as you need it. The good news is that, being open source, you can add extra functionality at any time. It is thus a very flexible software product
Discover the advantages
Fluctus: available layouts
The logical architecture of Fluctus offers 3 possible formats: Hyperconverged, Converged and Distributed. These are available in predefined sizes in increasing resource quantities.
The Hyperconverged layout envisions that each of the physical nodes (from 3 to 5) which make up the farm E4 Cloud Platform has all the software tools on board to cover every logical role of the farm itself. In case of farms which are particularly reduced in size or if you wish to use all the resources of the nodes for the Compute portion, the Hyperconverged farm can be connected to an external storage device from which it can use the disco component.
The Converged layout on the other hand envisions the presence of nodes dedicated to governance (1 Admin node and a variable number of 3-5 Control nodes ) and the workers nodes will issue the Compute and Storage software defined roles. This layout has the advantage of having all the workers nodes balanced and permits a change of node use destination which is much more flexible in that it is already equipped to do both compute and storage.
Finally, the Distributed layout uses a verticalization of the nodes on a single Compute or Storage functionality which will also be different on a hardware level, favoring a greater presence of CPU or disk space.
Multiregion and Edge are among the more significant additional functionalities which can be activated for each of the formats, as explained below.
- Infrastructure as a Service with OpenStack
- Universal Software Defined Storage with Ceph: (Object Storage, Block Storage and Network Filesystems)
- Distributed Software Defined Networking: with Open vSwitch
- Hypervisor: with KVM
- Core Components of OpenStack: includes Authentication and Authorization (Keystone), Computing (Nova), Software Defined Networking (Neutron), Cloud Orchestration (Heat), Secret Management (Barbican), Dashboard and GUI (Horizon), Image Management (Glance backed by Ceph), Volume Storage (Cinder backed by Ceph) and Object Storage (Swift backed by Ceph)
- Exposed Components: includes Authentication and Network Services (FreeIPA), Infrastructure metrics (Grafana, InfluxDB and Fluentd), Data and Logging Centralization (ElasticSearch, Fluentd and Kibana) and Repository Manager (Nexus)
- Background Components: Multimaster Database Cluster (MariaDB and Galera), Message Bus (RabbitMQ) and Load Balancing plus High Availability (HAProxy and Keepalived)
On demand features
- Infrastructure as Code: includes Code Review (Gerrit), Continuous Integration (Zuul) and ITS (OpenProject)
- Application Lifecycle; (available as an add-on to Infrastructure as Code): includes Container Orchestration Engine (Kubernetes, available both as a vanilla installation and as an E4 Kaptain) and Continuous Delivery (Spinnaker)
- Advanced Management: includes Telemetry (Ceilometer), Monitoring (Monasca) and Workflow (Mistral)
- Platform-as-a-Service: includes Container Orchestration Engine (Magnum which can manage Mesos or Kubernetes)
- DataBase-as-a-Service: includes Database Deploy (Trove which can manage MySQL, MariaDB, PostgreSQL, MongoDB)
- Advanced Orchestration: (available as an add-on to Advanced Management): includes Billing (CloudKitty), DNS (Designate) and Resource Optimization (Watcher)
- Network Function Virtualization: includes NFV (Tacker)
- Baremetal management: (Ironic)
- Multiregion: the configuration for distributed infrastructures is activated on 2 or more Active-Active locations. Each of the sites involved (generally balanced and equivalent to each other in terms of available resources) contributes to the providing of cloud services. The management and monitoring console remains a single unit providing an overall view. The workload can be allocated in a transparent manner on each of the included sites.
- Edge: the edge configuration permits centralized management even in situations with a high geographic distribution. Edge sites include an arbitrary number of nodes, even 1 single node, but Edge is deployed on secondary sites to ensure greater proximity with respect to data sources or the users of the service. The Edge configuration also permits optimization and reduction of network traffic to the primary sites to a minimum since a part of the processing is performed by the edge nodes themselves.