Page History
Add_workflow_for_techpubs | ||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|
|
OpenStack Requirements
Multiexcerpt | ||
---|---|---|
| ||
The SBC SWe supports the following OpenStack environments:
|
Server Hardware Requirements
Multiexcerpt | ||||||||||||||||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| ||||||||||||||||||||||||||||||||||||
|
S-SBC SWe Requirements
Multiexcerpt | |||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| |||||||||||||||
The system hosting the SBC SWe must meet the following requirements to achieve the performance targets listed:
|
M-SBC SWe Requirements
Multiexcerpt | |||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| |||||||||||||||
|
OAM Node Requirements
Multiexcerpt | ||||||||||
---|---|---|---|---|---|---|---|---|---|---|
| ||||||||||
|
I-SBC SWe Requirements
Info | ||
---|---|---|
| ||
Ribbon is retiring the 2 vCPU for the SBC SWe private cloud as of the 12.0 release. |
Multiexcerpt | ||||||||||
---|---|---|---|---|---|---|---|---|---|---|
| ||||||||||
|
Info | ||
---|---|---|
| ||
For deployments that require it, you can instantiate the SBC SWe in smaller-sized configurations that use limited memory and vCPU resources. However, the limited resources place some restrictions on capacity and capabilities. Refer to Small SBC SWe Deployment Characteristics and Small SBC SWe Configuration Performance Metrics for more information. |
Recommended Host Settings: Setting disk cache mode to "writethrough"
In order to prevent the SBC from crashing when the compute host power cycle is reset, it is recommended to set the cache mode for the disk type "file
" to "writethrough
". Execute the following steps on the compute host:
Retrieve the current disk cache modes in the nova configuration on the compute host by executing the following command:
Code Block title Command crudini --get /var/lib/config-data/puppet-generated/nova_libvirt/etc/nova/nova.conf libvirt disk_cachemodes
Code Block title Sample Output file=none,block=writeback,network=writeback
Info title Note Note that "
file=none
" in the sample output above. Continue to Step 2 to set "file=writethrough
".Set the disk type "
file
" to "writethrough
" by executing the following command:Code Block title Command crudini --set /var/lib/config-data/puppet-generated/nova_libvirt/etc/nova/nova.conf libvirt disk_cachemodes 'file=writethrough,block=writeback,network=writeback'
Info title Note The cache mode for the two other disk types "
block
" and "network
" are determined by the customer. The available cache modes are "writethrough
", "writeback
", and "none
".Restart all nova containers by executing the following command:
Code Block title Command docker restart $(docker ps|grep nova|sed -r 's/^([^ ]+).*/\1/')
Info title Note The container restart procedure may vary depending on the container management tool. When in doubt, reboot the compute host.
Verify in the nova configuration that the cache mode "
file
" is set to "writethrough
" by executing the following command:Code Block title Command crudini --get /var/lib/config-data/puppet-generated/nova_libvirt/etc/nova/nova.conf libvirt disk_cachemodes
Code Block title Sample Output file=writethrough,block=writeback,network=writeback
If any VMs/instances exist on the compute host, verify in libvertd that "
cache='writethrough'
" for the disk type "file
" by executing the following command:Code Block title Command virsh dumpxml <instance_name> | grep -A 1 "disk type='file'"
Info title Note In the command above, replace
<instance_name>
with the actual name of the instance.Code Block title Sample Output <disk type='file' device='disk'> <driver name='qemu' type='qcow2' cache='writethrough'/>