aboutsummaryrefslogtreecommitdiffstats
path: root/network/external.yaml
AgeCommit message (Collapse)AuthorFilesLines
2016-06-14Add gateway_ip in OS::Neutron::SubnetDimitri Savineau1-0/+5
This patch allows to : - disable the gateway ip for non routable network - use the first ip in the subnet - set the correct gateway on the external network Change-Id: Idc816c782856e93ecd339b3aca2a7f53c1564b1d Closes-bug: #1588379 Depends-On: I8ea6733fe46902e1baeff4ccfbcd42ecc5a1825f
2015-11-24Update typosSwapnil Kulkarni (coolsvap)1-1/+1
Change-Id: Id63c1bcfc34058eb7285698ba9bf86d1cf2025a6
2015-09-08Set NetValueSpecs parameter types to JsonDan Prince1-1/+1
The latest Heat API is a bit more strict in validating the datatypes for the OS::Neutron::Net value_specs. This patch converts the default parameter types for these from string to json. Change-Id: Iaad6ee6417d3ae55c52ffe2f4e6ed79124161923 Closes-bug: #1493502
2015-06-16Fix allocation pool in external.yamlDan Sneddon1-1/+1
The file network/external.yaml has a typo in the last commit. It should have been a get_param instead of a get_resource. This change fixes that line in that file. Change-Id: Ibc0db0510e9b5dae3c4669a620c642357906cbc2
2015-06-12Flexible IP allocations for isolated netsDan Prince1-1/+5
This patch adds new '<net name>AllocationPool' parameters to all of the isolated network nested stacks so that users can easily control the allocation ranges on these networks. Change-Id: I44b564831446c62e3489a69d992e0fb1f642b085
2015-05-20Overcloud: bump HOT version to 2015-04-30Dan Prince1-1/+1
This patch bumps the HOT version for the overcloud to Kilo 2015-04-30. We should have already done this since we are making use of OS::stack_id (a kilo feature) in some of the nested stacks. Also, this will give us access to the new repeat function as well. Change-Id: Ic534e5aeb03bd53296dc4d98c2ac5971464d7fe4
2015-05-06Create split out neutron networks via Heat.Dan Prince1-0/+58
This patch adds a new abstraction for network creation within Heat. This (optional) set of templates may be disabled if you wish to create Neutron networks for the undercloud via Heat templates... instead of using os-cloud-config JSON to do so. Creating networks with Heat has the benefit of being parameter driven so that users can quickly enable networks using the resource registry and parameters. There are 5 networks to start with which are roughly modeled around networks an Overcloud user might want to use to isolate their traffic. The intent is to make these opt-in and configurable for end users. The networks.yaml template can be used to create all of the networks using parameters in the resource registry. Change-Id: I5f2b3356378eb263d90d428cc83c7f5b141957e1