mysql_virtual_ip.
* mysql_clu_member_addrs: the IP addresses (as a space-separated
list) internal to the cluster that pacemaker communicates on. So,
if you are going to have a cluster of 3 members, the three IP
addresses of the cluster members are listed here. NOTE: these IP's
must already be configured and active on the cluster-hosts-to-be
before they are added to this Host Group (i.e., this Host Group
does not set up these IP's for you).
* mysql_resource_group_name: the name of the resource group. This
Host Group adds a virtual IP, filesystem and mysql resource to the
resource group named here. The default is fine.
* mysql_shared_storage_type: e.g., nfs or ext3. The type of
filesystem that pacemaker is responsible for mounting to
/var/lib/mysql.
* mysql_shared_storage_device: the path to the storage device.
E.g. if mysql_shared_storage_type, the nfs mount point.
* mysql_virtual_ip: the virtual IP address that pacemaker will
manage and the IP address that clients will use to connect to
MySQL.
* mysql_virt_ip_nic: the interface (e.g., eth2) that pacemaker
will attempt to bring up the virtual IP on. Note that this may be
empty if the host already has an IP address active on the same
subnet that the virtual IP will be brought up on.
* mysql_virt_ip_cidr_mask: the subnet mask mysql_virtual_ip lives
on (e.g., 16 or 24).
BZ #104 9 6 33
With this update, two new parameters needed by puppet-neutron for
ovs agent/plugin support for vxlan have been included. Thus,
adding the ability to configure VXLAN for OpenStack Networking.
This update also opens the UDP port on the firewall on the
OpenStack Networking and Compute nodes.
BZ #1056 055
The default behavior most customers expect for small to medium
installations is to run cinder-volume on the controller node.
Packstack does this but a Foreman deployment only allows a
dedicated storage backend backed by iSCSI or Red Hat Storage.
With this update, you can deploy cinder-volume on the Compute or
OpenStack Networking controller node, if cinder_backend_gluster is
set to false. It will detect a volume group named cinder-volumes
(backed by a loopback device) and share it via the target deamon
(tgtd). You must manually create the volume group, which is also
the case with the cinder_backend_iscsi parameter for the LVM
backend storage group.
Comentários a estes Manuais