fuel 9.0 openstack mitaka
- disk qos
- network qos
- cpu qos
- memory qos
- ...
Refrence:
[OpenStack Orchestration In Depth]
https://developer.rackspace.com/blog/openstack-orchestration-in-depth-part-1-introduction-to-heat/
[Heat Orchestration Template]
http://docs.openstack.org/developer/heat/template_guide/hot_spec.html
#!/bin/bash | |
# Following the guide found at this page | |
# http://programmingarehard.com/2014/03/17/behat-and-selenium-in-vagrant.html | |
echo "\r\nUpdating system ...\r\n" | |
sudo apt-get update | |
# Create folder to place selenium in |
######################################## | |
# Required changes to nova.conf # | |
######################################## | |
# notification_driver=nova.openstack.common.notifier.rpc_notifier | |
# notification_topics = notifications | |
# notify_on_state_change = vm_and_task_state | |
# instance_usage_audit_period = hour | |
# instance_usage_audit = True | |
# default_notification_level = INFO | |
# notify_api_faults = true |
The .0, .1 files are datafiles. Each datafile is preallocated to a particular size. (This is done to prevent file system fragmentation, among other reasons.) The first filename for a database is .0, then .1, etc. .0 will be 64MB, .1 128MB, et cetera, up to 2GB. Once the files reach 2GB in size, each successive file is also 2GB. Information regarding datafiles can be found here:
The ".ns" files are namespace files. Each collection and index would count as a namespace. Each namespace is 628 bytes, the .ns file is 16MB by default.
>Thus if every collection had one index, we can create up to 12,000 collections. The --nssize parameter allows you to increase this limit.
root@node-3:~# cat /var/lib/neutron/lbaas/v2/c9646493-cc1e-4bfc-baba-1c235bbf3053/haproxy.conf | |
# Configuration for lb-80 | |
global | |
daemon | |
user nobody | |
group haproxy | |
log /dev/log local0 | |
log /dev/log local1 notice | |
stats socket /var/lib/neutron/lbaas/v2/c9646493-cc1e-4bfc-baba-1c235bbf3053/haproxy_stats.sock mode 0666 level user |