CNM Cloud requirements

CNM Cloud requirements is a set of detailed requirements for CNM Cloud. This document has been drafted to assist cloud developers to come up with detailed implementation of enterprise private cloud with an objective to host BigBlueButton, Moodle, MediaWiki, Odoo, and Redmine end-user software applications. Each of these application shall serve more than 100 users with a peak load capacity of 20 simultaneous users. The requirements have been drafted keeping in mind that users of above applications would require an uninterrupted very high availability.

The target audience for this document is cloud architects, DevOps engineers and system administrators.

Block storage

Block Storage Objectives

1. Capacity requirement of 2T
2. A peak speed of 110Mbps of data transfer
3. A peak speed of 15-20Mbps of data transfer rate with about 20 parallel transfers
4. 3x Data redundancy
5. Super scalability
6. Uniform load distribution
7. Shall be consumed by VMs and Containers
8. Shall be consumed by applications
9. Shall be consumed by OpenStack
10. An acceptable latency

Storage Requirements

1. Distributed striped GlusterFS volume shall be implemented for data redundancy, load balancing and scalability
2. GlusterFS shall be implemented for serving block storage
3. System should be implemented with at least three or more stripes.
4. A minimum of three bare metal servers shall be used to implement GlusterFS.
5. Each of the node shall have at least 3 SSD drives each with capacity of 1TBx2 terabytes and 125GBx1.
6. Hardware configuration for each node shall be, a minimum of 4GB RAM, 2 or more CPU Cores, 1+ GBE x 2 Network adapters.

Object storage

Object Storage Objectives

1. Capacity requirement of 3T
2. A peak speed of 110Mbps of data transfer
3. A peak speed of 15-20Mbps of data transfer rate with about 20 parallel transfers
4. 2x data redundancy
5. Super scalability
6. Shall host Storage images, Data backups and System snapshots
7. Shall host Docker Registry

Object Storage Requirements

1. Distributed OpenStack swift object volume shall be implemented for data redundancy, load balancing and scalability
2. Swift object shall be implemented for serving Block storage
3. A minimum of three bare metal servers shall be used to implement Swift.
4. Each of the node shall have at least 3 SATA/SCSI drives each with capacity of 1TBx2 terabytes and 125GBx1.
5. Hardware configuration for each node shall be, a minimum of 4GB RAM, 2 or more CPU Cores, 1+ GBE x 2 Network adapters.
6. The management network shall be separate from data for replications
7. The OpenStack controller cluster shall be used to authenticate and authorise the usage of object storage.
8. Possibility of using data and management network separate

BigBlueButton

BigBlueButton Specific Objectives

1. This cluster should be built using bare metals.
2. The streaming data that comes in and goes out should directly terminate on this application
3. A minimum bandwidth of 80Mbps internet data streaming capacity is required.

BigBlueButton Requirements

1. A two node cluster shall be implemented to host BigBlueButton
2. Hardware configuration for each node shall be, a minimum of 8GB RAM, 4 or more CPU Cores, 1+ GBE x 2 Network adapters.
3. Big blue button should be specifically implemented on Ubuntu 16.04 64-bit OS
4. $A minimum of 500G of GlusterFS storage shall be made available to the cluster
5. 80Mbps symmetrical data transfer rate shall be made available to the cluster.

Container/Magnum Cluster Requirements

1. A two node cluster shall be implemented to host Dockers
2. Hardware configuration for each node shall be, a minimum of 32GB RAM, 4 or more CPU Cores, 1+ GBE x 2 Network adapters.
3. A best possible OS shall be chosen to implement this cluster, to accommodate maximum number of applications.
4. At a minimum of ten applications shall run simultaneously.
5. A minimum of 300G of GlusterFS storage shall be reserved for use by Containers
6. A minimum of 300G of Swift object storage shall be reserved for use by docker registry
7. All applications other than BigBlueButton shall be hosted using these Containers

OpenStack Objectives

1. Should be able to act as single point infrastructure management console.
2. A single authentication, authorisation agent for all the applications in the cloud.
3. Should be able to make all the cluster and nodes in concert.

Controller Cluster

1. A two node cluster shall be implemented to host OpenStack controller.
2. Hardware configuration for each node shall be, a minimum of 8GB RAM, 2 or more CPU Cores, 1+ GBE x 2 Network adapters.
3. A local storage of 256 GB SSD shall be used for OS and logs
4. This cluster shall host OpenStack dashboard, neutron and authentication agent and any other dependencies.

Compute Cluster

1. A two node cluster shall be implemented to host OpenStack Nova.
2. Hardware configuration for each node shall be, a minimum of 32GB RAM, 4 or more CPU Cores, 1+ GBE x 2 Network adapters.
3. A local storage of 256 GB SSD shall be used for OS and logs
4. This cluster shall host OpenStack Nova and Ironic (Bitfrost ??) services along with any other necessary dependencies.

Cinder Cluster

1. A two node cluster shall be implemented to host OpenStack Cinder.
2. Hardware configuration for each node shall be, a minimum of 4GB RAM, 2 or more CPU Cores, 1+ GBE x 2 Network adapters.
3. A local storage of 256 GB SSD shall be used for OS and logs
4. This cluster shall host OpenStack Cinder and any other necessary dependencies.

Senlin Cluster

1. TBD

Security Requirements

1. TBD

Internet and Floating IPs

1. At a minimum pack of 10-12 real IPv4 would be required
2. Each application interfacing user shall use 1-2 IP addresses as per application and design requirements.

Networking Requirements

1. GlusterFS and Swift cluster shall have two separate networks
2. VLAN tagging if necessary
3. Number of networking
4. TBD

Monitoring and trouble Requirements

1. What monitoring tools
2. Where to install
3. TBD

New drafts

The Cloud shall:

• Enable:
  1. More than one language support. Depending on the local language preference of the main user.
  2. Frequent updating as need arises and/or new versions of utilized software are available.
  3. Copying of data from one page to another.
  4. Data backup by allowing automatic update as one works as well as creating copies offsite where it will be safe from theft or malfunction.
  5. Information sharing with in the team by sharing effortlessly.
  6. Growth planning as it is scalable and self managed by apps.
• Provide file storage especially for large heavy files.
• Allow integration of existing and new systems.

See also

• Cloud lexicon, a listing of links about computer terms