User Tools

Site Tools


genesis:requirements_examples

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision
Previous revision
genesis:requirements_examples [2015/07/27 17:51]
Frank Brockners
genesis:requirements_examples [2015/07/31 17:26] (current)
David Duffey [!!!DRAFT!!!]
Line 1: Line 1:
-======Example requirements to help kick-off the Genesis work======+======!!!DRAFT!!!====== 
 +[[https://​docs.google.com/​document/​d/​1-WH2hS-Kt5IaQ_epe79q4Hb_kzb1TO7r43r5HMEblj4/​edit?​usp=sharing|Google Doc Version]] 
 + 
 +======Genesis sandbox: Example requirements====== 
 + 
 +Example requirements to help kick-off the Genesis work
 + 
 +Requirements fall into several categories:​ 
 + 
 +  * Target system requirements:​ Hardware components of the installed system 
 +  * Target system requirements:​ Software components of the installed system 
 +  * Common software artifacts and scripts used across all installers 
 +  * Requirements for a common user experience
  
 ====Target system requirements:​ Hardware components===== ====Target system requirements:​ Hardware components=====
  
-  * Deploy on a "​Pharos-compliant"​ lab+  * Deploy on a "​Pharos-compliant"​ lab (details to be added)
   * Deploy on a single node with nested virtualization   * Deploy on a single node with nested virtualization
  
Line 70: Line 82:
     * ...     * ...
  
-====Common ​user-experience ​requirements====+====Requirements for a common ​user experience====
  
 === HA === === HA ===
Line 97: Line 109:
  
   * Configure boot-order of servers for automated (re-)provisioning   * Configure boot-order of servers for automated (re-)provisioning
-  * Configure RAID on boot drives, so that the OS can be installed on redundant drives+  * Configure RAID (for local storage resiliancy) ​on boot drives, so that the OS can be installed on redundant drives. RAID to be configured in the earliest phase of bare metal install and without user interaction.
   * Enable SELinux by default   * Enable SELinux by default
   * Install ssh keys on servers so that key-based login can be used for administration   * Install ssh keys on servers so that key-based login can be used for administration
-  * Configure NTP servers on the server for clock synchronization +  * Configure NTP servers on the server for clock synchronization. Configured as early as possible to avoid later skew. Configured to support multiple pools. 
-  * Format non-boot drives on compute servers, so that they can be used as CEPH OSDs. +  * Format non-boot drives on compute servers, so that they can be used as CEPH Object Storage Devices (OSDs)
-  * Specify the VIC in my servers to use, so that I can deploy servers with more than one VIC.+  * Specify the VIC in the servers to use, so that I can deploy servers with more than one VIC.
   * Unique kickstart file per platform/​role,​ so that OS can be customized for hardware and role.   * Unique kickstart file per platform/​role,​ so that OS can be customized for hardware and role.
   * Option to provide a set of ssh user keys to be installed on all servers (for administration)   * Option to provide a set of ssh user keys to be installed on all servers (for administration)
Line 112: Line 124:
 === Security === === Security ===
  
- * Protect passwords, keys, credentials:​ Allow for mandatory access control, method for chaning passwords.+  ​* Protect passwords, keys, credentials:​ Allow for mandatory access control, method for chaning passwords.
  
 === Testing === === Testing ===
Line 137: Line 149:
   * Deployment using binaries from 3rd-party repos (vendor specific distro)   * Deployment using binaries from 3rd-party repos (vendor specific distro)
   * Deployment using OPNFV created binaries from upstream (for "build from source"​ option) ​   * Deployment using OPNFV created binaries from upstream (for "build from source"​ option) ​
- 
- 
- 
- 
genesis/requirements_examples.1438019519.txt.gz · Last modified: 2015/07/27 17:51 by Frank Brockners