d9a4ea36e1
The networking setup was inappropriate for non-seed clouds - it depended on two network interfaces, forced NAT that we don't need and could not be turned off. Additionally there wasn't much clarity between idempotent machine config and non-idempotent service config. Key changes in this patch: * No longer write persistent device files, instead update idempotently. * NAT rules are now setup idempotently on each o-r-c run. * New definitions for the meaning of various config keys to suit working with different cloud layers. Change-Id: Ie86be0fc884b4c4f655d73da345bdee45fcde473 |
||
|---|---|---|
| .. | ||
| install.d | ||
| os-apply-config/var/opt/seed-stack | ||
| os-refresh-config/post-configure.d | ||
| config.json | ||
| element-deps | ||
| README.md | ||
Provide configuration for seed clouds
Seed clouds are booted without any cloud infrastructure. The seed-stack-config element stubs out enough infrastructure to permit the rest of boot-stack to work either when booted by a cloud, or booted without.
In particular, it sets up resolv.conf, a hosts file, and delivers a Heat metadata file with static data into the image (rather than that being delivered at boot-time by Heat itself).
Usage
Edit config.json to customise it for your deployment environment. The default is configured for nova-baremetal operation in a seed VM. The configuration options are documented in the actual elements that use the configuration - e.g. nova, quantum etc.
Configuration keys
bootstack: public_interface_ip: 192.0.2.1/24 - What IP address to place on the ovs public interface. Only intended for use when the interface will not be otherwise configured. masquerade_networks: [192.0.2.0] - What networks, if any, to masquerade. When set, all traffic being output from each network to other networks is masqueraded. Traffic to 192.168.122.1 is never masqueraded.