3.5 KiB
Configuration
Copy the sample configuration file config.yaml.sample
to
config.yaml
and adjust the file accordingly.
Networking
Bridges
bridge_internal: tap0
bridge_external: tap1
Addresses
netmask_internal: 255.255.0.0
address:
controller: 10.100.50.10
network: 10.100.50.30
storage: 10.100.50.40
compute:
- 10.100.50.20
- 10.100.50.21
To increase the number of compute nodes add more addresses to the
compute
list.
L2 agent
network_agent: openvswitch
Tenant networks
network_type: gre
Clock synchronization (NTP)
Accurate clocks on every node are very important. Default is the the usage of the NTP Pool Project.
ntp:
- 0.pool.ntp.org
- 1.pool.ntp.org
- 2.pool.ntp.org
- 3.pool.ntp.org
Resources
Default resources defined in ~/.vagrant.d/Vagrantfile
or
the Vagrantfile
provided by the base box will be
overwritten. Resources assigned to the controller node will be
multiplied by two and additional block storage devices will be attached
to the controller and NFS nodes.
resources:
memory: 4096
vcpus: 2
storage: 65536
Development version
To use the development version (master
) of Packstack set
development: true
.
Vagrant base box
In theory (not tested) it is possible to use RHEL or Fedora instead
of CentOS. Default is b1-systems/centos-packstack
, a
customized Vagrantbox based on boxcutter/centos70.
The sources of the used Packer template
is available on Github and the
box iself on Atlas.
To change the used Vagrant base box modify the value of
box
. A list of public available Vagrant boxes is available
on Atlas.
Depending on the used base box you have to set the used storage
controller (normally IDE Controller
or
SATA Controller
). The storage controller of the base box
must support at least three ports.
Storage backend
At the moment NFS is the only supported storage backend. Support for Ceph will be added in the future (at the moment Ceph is not supported as a storage backend in Packstack).
Timezone
At the moment it is not possible to configure the timezone with Packstack.
Caching / Proxying
To speed up the provisioning the Vagrant plugin vagrant-proxyconf
configures a HTTP proxy to be used by yum
.
$ vagrant plugin install vagrant-proxyconf
When the plugin is installed caching/proxying is enabled by default and the HTTP proxy Squid will be installed on the controller node.
proxy:
use: true
address: 'http://proxy.company.site:3128'
install: true
To explicitly disable caching/proxying when
vagrant-proxyconf
is installed set use
to
false
.
To skip the installation of Squid on the controller node set
install
to false
. address
has to
point to an existing HTTP proxy server (e.g.
http://proxy.company.site:3128
) when Squid is not
installed. address
has not to be set when installing Squid
on the controller node.