{"push_id":675396522,"size":1,"distinct_size":1,"ref":"refs/heads/master","head":"7418a32a73277d258ceeb06b329973d61aceed7c","before":"7587446c6e1030bb85a019b13ef3a757b4d5fb79","commits":[{"sha":"7418a32a73277d258ceeb06b329973d61aceed7c","author":{"email":"62cccc0004df0a8e3c343b26b69e434f6aa9711c@redhat.com","name":"Dan Prince"},"message":"Add isolated network ports to controller roles\n\nThis patch updates the controller roles so that\nthey can optionally make use of isolated network\nports on each of 5 available overcloud networks.\n\n -Multiple networks are created based upon settings in the heat\n  resource registry. These nets will either use the noop network (the\n  control plane pass-thru default) or create a custom Neutron port on\n  each of the configured networks.\n\n -The ipaddress/subnet of each network is passed passed into the\n  NetworkConfig resource which drives os-net-config. This allows the\n  deployer to define a custom network template for static IPs, etc\n  on each of the networks.\n\n -The ipaddress is exposed as an output parameter. By exposing\n  the individual addresses as outputs we allow Heat to construct\n  collections of ports for various services.\n\nChange-Id: I9bbd6c8f5b9697ab605bcdb5f84280bed74a8d66","distinct":true,"url":"https://api.github.com/repos/openstack/tripleo-heat-templates/commits/7418a32a73277d258ceeb06b329973d61aceed7c"}]}