Pike. swift-ringbuilder.yaml
Hello folks,
on pike we are trying to run the swift-ringbuilder.yaml during the initial deploying of the overcloud.
but it failed without useful error message.
below the yaml file. is copied from template.
is the anything else to do or to adapt before running this file?
any idea how i can troubleshoot what exactly is going wrong?
thanks for your answers
br
Niko
[stack@srvhost1 services]$ more swift-ringbuilder.yaml
heat_template_version: pike
description: >
OpenStack Swift Ringbuilder
parameters:
DockerSwiftConfigImage:
description: The container image to use for the swift config_volume
type: string
DockerSwiftRingbuilderConfigImage:
description: Fake parameter to bypass config_volume yaml validation
type: string
default: ''
ServiceData:
default: {}
description: Dictionary packing service data
type: json
ServiceNetMap:
default: {}
description: Mapping of service_name -> network name. Typically set
via parameter_defaults in the resource registry. This
mapping overrides those in ServiceNetMapDefaults.
type: json
DefaultPasswords:
default: {}
type: json
RoleName:
default: ''
description: Role name on which the service is applied
type: string
RoleParameters:
default: {}
description: Parameters specific to the role
type: json
EndpointMap:
default: {}
description: Mapping of service endpoint -> protocol. Typically set
via parameter_defaults in the resource registry.
type: json
SwiftMinPartHours:
type: number
default: 1
description: The minimum time (in hours) before a partition in a ring can be moved following a rebalance.
SwiftPartPower:
default: 9
description: Partition Power to use when building Swift rings
type: number
SwiftRingBuild:
default: true
description: Whether to manage Swift rings or not
type: boolean
SwiftReplicas:
type: number
default: 2
description: How many replicas to use in the swift rings.
SwiftRawDisks:
default: {}
description: 'A hash of additional raw devices to use as Swift backend (eg. {sdb: {}})'
type: json
SwiftUseLocalDir:
default: true
description: 'Use a local directory for Swift storage services when building rings'
type: boolean
SwiftRingGetTempurl:
default: ''
description: A temporary Swift URL to download rings from.
type: string
SwiftRingPutTempurl:
default: ''
description: A temporary Swift URL to upload rings to.
type: string
resources:
SwiftRingbuilderBase:
type: ../../puppet/services/swift-ringbuilder.yaml
properties:
EndpointMap: {get_param: EndpointMap}
ServiceData: {get_param: ServiceData}
ServiceNetMap: {get_param: ServiceNetMap}
DefaultPasswords: {get_param: DefaultPasswords}
RoleName: {get_param: RoleName}
RoleParameters: {get_param: RoleParameters}
outputs:
role_data:
description: Role data for Swift Ringbuilder configuration in containers.
value:
service_name: {get_attr: [SwiftRingbuilderBase, role_data, service_name]}
config_settings:
map_merge:
- {get_attr: [SwiftRingbuilderBase, role_data, config_settings]}
- tripleo::profile::base::swift::ringbuilder:skip_consistency_check: true
logging_source: {get_attr: [SwiftRingbuilderBase, role_data, logging_source]}
logging_groups: {get_attr: [SwiftRingbuilderBase, role_data, logging_groups]}
step_config: &step_config
get_attr: [SwiftRingbuilderBase, role_data, step_config]
service_config_settings: {get_attr: [SwiftRingbuilderBase, role_data, service_config_settings]}
# BEGIN DOCKER SETTINGS
puppet_config:
config_volume: 'swift_ringbuilder'
puppet_tags: exec,fetch_swift_ring_tarball,extract_swift_ring_tarball,ring_object_device,swift::ringbuilder::create,tripleo::profile::base::swift::add_devices,swift::ringbuilder::rebalance,create_swift
_ring_tarball,upload_swift_ring_tarball
step_config: *step_config
config_image: &swift_ringbuilder_image {get_param: DockerSwiftConfigImage}
kolla_config: {}
docker_config:
step_3:
swift_copy_rings:
image: *swift_ringbuilder_image
user: root
detach: false
command:
# Use bash to run the cp command so that wildcards can be used
- '/bin/bash'
- '-c'
- 'cp -v -a -t /etc/swift /swift_ringbuilder/etc/swift/*.gz /swift_ringbuilder/etc/swift/*.builder /swift_ringbuilder/etc/swift/backups'
volumes:
- /var/lib/config-data/puppet-generated/swift/etc/swift:/etc/swift:rw
- /var/lib/config-data/swift_ringbuilder:/swift_ringbuilder:ro
Responses
Red Hat
Expert
1065 points
So this looks like the default containerized service template for swift-ringerbuilder. There shouldn't be any modifications required to the template to get it working.
How do you know that it's the swift-ringbuilder? Is the docker container in a failed state? Did the other containers start successfully (for example, the HA services)?
Red Hat
Expert
1065 points
Sorry, I mistyped. I meant there shouldn't be any modifications required.
I think there might be some confusion here. The "openstack container list" is for something different (not docker containers). What I'm trying to find out is how you know the swift-ringbuilder failed, as per your original message:
on pike we are trying to run the swift-ringbuilder.yaml during the initial deploying of the overcloud. but it failed without useful error message.
How do you know it was specifically the swift-ringbuilder that failed?
Red Hat
Expert
1065 points
So the ringbuilder isn't so much a service. It's a container that performs some initial configuration to define the swift rings. Rings essentially map data in the swift cluster. So if you run docker ps on its own, nothing relating to the swift-ringbuilder will appear because the container finished its operation during deployment. However, you should be able to see the container that ran the ringbuilder using:
$ sudo docker ps --all --filter name=swift_copy_rings
Welcome! Check out the Getting Started with Red Hat page for quick tours and guides for common tasks.