Age | Commit message (Collapse) | Author | Files | Lines |
|
|
|
This hasn't been properly wired in for a while AFAICT, so it makes
sense to remove it, and introduce a value via parameter_defaults
which enables easier global selection of a particular transport
without passing the value down through all the nested stacks.
Change-Id: Icd830aea00768e65adc1df1287440fdab98058f9
|
|
We want to ensure this actually worked, or subsequent configuration
steps may fail.
Change-Id: Ia9ae12e70dd32dd3ae6c26cbfd3e3e2dba5d272f
|
|
We want to know this deployment succeeded, again the
ControllerAllNodesPostDeployment depends_on this, which implies
it should actually be done before doing the PostDeployment stuff,
which is impossible to determine with NO_SIGNAL.
Change-Id: I46d23bce8762ac414e4de82cf42193694aebb763
|
|
We need to be sure the boostrap node data has been propagated to the
cluster before proceeding with configuration, because
ControllerNodesPostDeployment consumes the data put in place by this
and depends_on for serialization, which is essentially meaningless when
combined with NO_SIGNAL.
Change-Id: I73a1e5a2cda4c79f457bfbd9ce2836dc5c1902cc
|
|
Change-Id: I5b6454d0e09eba79fc0376e963fd0e4c64105081
|
|
Currently we use NO_SIGNAL on both the NetworkConfig and subsequent config
deploying the data associated with the role. This means there is a risk that
should the NetworkConfig do anything interruptive (os-net-config can do
interface renaming based on discovery data for example) the role configuration
config could fail, and we'd never know until some later error occurs.
Additionally, we need to be sure that the heiradata deployed by each of the role
specicific configs is actually in-place before proceeding with any of the cluster
configuration - atm this works due to the inherent delays involved deploying to
bare-metal, but there's still a theoretical race if very fast deployment backends
(I'm thinking containers, e.g lxc backend to nova or something) were used instead.
Essentially, we should never be using NO_SIGNAL unless we want to ignore failure,
which AFAICT is not the case in this instance.
Change-Id: I0dbbcc87fb8df8e6bc4775c39fa616b0d0713464
|
|
|
|
As most of the OpenStack services are automatically bound
to the public virtual IP already we don't need to set
the default network for Horizon and Keystone to the 'external'
network. These should probably default to the internal_api
network like the rest of the OpenStack services...
Change-Id: I04cf64568c2fc7bb8a821b0de5ba56aa90158e2d
|
|
This patch adds VIPs for the internal_api, storage,
and storage management networks.
For puppet these are persisted into a local vip-config
hieradata file which is then used by puppet-tripleo's
loadbalancer module to apply per-service VIP settings.
Change-Id: I909c3bdc9d17a8e15351f4797287769e3f76c849
|
|
For VIP ports we set an explicit name on the ports. This
patch adds an optional PortName parameter to the ports
objects which can be used to specify a name.
Change-Id: Iad0f5e4cfc31a931dbb574d9e589570125e9465c
|
|
We probably don't need to split out separate networks
for Heat CFN and Cloudwatch. Just having a single network
for Heat API in the overcloud is probably fine.
Change-Id: I917b314e01227af72129645c9b72ad8e54f07865
|
|
This patch adds a new NetIpListMap abstraction which we can use
to make the all-nodes-config IP list network assignments
configurable. Ip address lists for all overcloud services
which require IPs were added to all-nodes-config so
that puppet manifests can be directly supplied the
correct network list for each service.
Change-Id: I209f2b4f97a4bb78648c54813dad8615770bcf1a
|
|
This patch makes ServiceNetMap a top level parameter.
This is helpful to tools like Tuskar which don't support Heat
environments that contain both a resource_registry and default_parameters.
ServiceNetMap will in fact be utilized at the top level in some of
the VIP related patches that follow.
Change-Id: I375063dacf5f3fc68e6df93e11c3e88f48aa3c3a
|
|
Change-Id: Ibd1581ebb87ed02f3840000e90025a2a371019aa
|
|
This patch adds 5 new role templates to help configure
a vlans on top for each of the overcloud roles. This
patch adds vlans on top of a single NIC attached to
the control plane network (already used for provisioning).
The patch also includes an environment file to
enable configuration of vlans by simply sourcing this file.
Change-Id: Ibc40e452dec9b372ff10442aab2bddaf382b0a2f
|
|
|
|
|
|
|
|
|
|
With current effort of creating isolated networks, the controller_host
hiera variable does not exist anymore. Hence we remove it else the
lookup will fail.
The hiera binding neutron::agents::ml2::ovs::local_ip has been written
in another review[1]
[1] I1dc11987b4ea3c37775b14fbdddb75588499e9bb
Change-Id: I12777c512d379210e5cddb5e683be4d79808fa2c
|
|
|
|
|
|
Change-Id: I1c8fc6beacc8352ad2aabe44ff20614ac52c1795
|
|
Change-Id: I1243b68506f37d6b78807c03948874ae100fef65
|
|
Constraints based on vncproxy are commented due to it not starting
with websockify < 0.6, see [1]
1. http://lists.openstack.org/pipermail/openstack-dev/2014-October/048535.html
Co-Authored-By: Jiri Stransky <jistr@redhat.com>
Change-Id: Ie51014bf563920d2e75c5e38942bc42ddc2a3939
|
|
Adds neutron-server, neutron-l3-agent, neutron-dhcp-agent,
neutron-openvswitch-agent and neutron-metadata-agent as
pacemaker resources.
Change-Id: I4dcc6f56db4c27a2a4f627fa8303cbeb2bd563d4
|
|
This change adds parameters to specify which networks the MySQL
service will use. If the internal_api network exists the MySQL
service will bind to the IP address on that network, otherwise
the services will default to the IP on the Undercloud 'ctlplane'
network.
This patch also drop the old 'controller_host' variable from
the puppet controller template since it is no longer in use.
Change-Id: I4fba2c957f7db47e916bc269fb4bd32ccc99bd4c
|
|
This patch updates the controller and compute roles
so that we use get_input in the software configuration
instead of calling get_attr/get_param there.
Change-Id: I1dc11987b4ea3c37775b14fbdddb75588499e9bb
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Specify the MariaDB package name to meet new requirement from
puppetlabs-mysql introduce but latest commit[1][2]
[1]
https://github.com/puppetlabs/puppetlabs-mysql/commit/4bab65edcb98f82f87a4414840fe90ab81b6cea3
[2]
https://github.com/puppetlabs/puppetlabs-mysql/commit/29788fb4c492865b5246daef6cbefe99c4aa067d
Change-Id: I1b855934a88ceb4995ca1a44394db6b7a20c038d
|
|
Fixes the colocation order between glance-api and glance-registry to
match the ref-arch[1]
[1]
https://github.com/beekhof/osp-ha-deploy/blob/master/pcmk/glance.scenario#L108
Change-Id: I40f35afedb3333d97c8b689538bb80a90a66afe8
|
|
Make sure the keystone service starts before the glance-registry one.
Change-Id: Ia81df13682bf556a39cc36520def48105ee3e27d
|
|
Make sure the keystone service starts before the cinder-api one.
Change-Id: I21549c066afcf051e52fc4bba4fae2f34ad2ba4b
|
|
The interface for pcmk_resource offers the parameter master_params to set
--master during the resource creation.
Change-Id: I6fa769f14a6248b371810af3ba6819a1f9ed9442
|
|
Depends-On: I7b992450176595a89dba9fe2eccf619af2645d6b
Change-Id: I30cebb6d3a8670f49587bedaf51af18a87a8d24c
|
|
|
|
|
|
This change adds parameters to select the networks for Horizon,
Redis, Rabbit MQ, and memcached services. Horizon is often used for
administration from outside the cloud, so if the external network
exists, Horizon will bind to that IP, otherwise it will default to
the Undercloud 'ctlplane' network. Redis, Rabbit MQ, and memcached
will bind to IPs on the internal_api network if it exists, else
they will default to the 'ctlplane' network as well. Any of these
network assignments can be overridden with an environment file.
Change-Id: Ie0aa46b4a3c00d3826866796b4ec3b14f71f987c
|