summaryrefslogtreecommitdiffstats
path: root/swift-source.yaml
AgeCommit message (Collapse)AuthorFilesLines
2014-05-21Merge "Adding Swift proxy-server memcache metadata"Jenkins1-0/+1
2014-05-02Specify group os-apply-config for config resourcesSteve Baker1-0/+1
This will indicate to os-collect-config that this config resource represents os-apply-config configuration data, so it can only write out top-level config files for os-apply-config data (or Heat::Ungrouped for backwards compatibility). Change-Id: I3552fdd6df8106ab83cfd17d5f4b137cf33fbc36 Related-Bug: #1299109
2014-04-17Adding Swift proxy-server memcache metadataEamonn O'Toole1-0/+1
Swift proxy-servers use memcache to store and share metadata. This change adds swift.proxy-memcache metadata to the swift-source and swift-storage-source yaml templates modelled on the existing swift.devices metadata. This metadata will be consumed by the swift-proxy/os-config-applier/etc/swift/proxy-server.conf element if the metadata exists. Change-Id: If0b5724f69e7ec1c98e4dbdbeb9f08c4a18151b6
2014-04-16Switch overcloud to software-configClint Byrum1-51/+15
This migrates the overcloud to using OS::Heat::StructuredConfig and OS::Heat::StructuredDeployment. With those tools, we can decouple servers from software configuration and begin to deprecate features in tripleo_heat_merge. Change-Id: Ice85f0711e90d0fabf1d1bc4698201c4d6758508
2014-04-09Stop using notCompute in favor of controllerDan Prince1-2/+2
Updates all references for notCompute and notcompute to use 'controller' instead. Change-Id: I70ef83f35064ab388bdc7e1a6da62b6585580010 Partial-bug: #1300324
2014-03-10Swift storage heat templatesRichard Su1-9/+26
Updated the existing swift-source template to properly list all swift devices. Created a new swift-storage-source template to add additional swift-storage only nodes. The default SWIFTSTORAGESCALE is 0. Change this number to add additional swift storage nodes. Change-Id: Ia05f4ad44593316430d60541106d23b032c3e760
2014-01-31Prep work for a scalable control plane.Robert Collins1-2/+2
This is complete as far as it goes but it isn't enough to make running a scaled out control plane actually work. Specifically, the constructs to point at API hosts based on looking up a network address aren't suirtable for scaled out - we need to be using the virtual IP or DNS round robin or other such resilient configurations, but that is largely / entirely orthogonal to making the template be ready for scaling. Change-Id: Ib9e6db5e7d5db84e4746afdabea046d2b8702bbb
2013-11-26Fix case of OpenStack in templates.Dan Prince1-1/+1
merge.py seems to look for OpenStack::ImageBuilder::Elements But we use Openstack::ImageBuilder::Elements in our templates. Change-Id: I94ee367cf77c3f2929ee23d2dcdd28622849c89e
2013-11-18Add metadata to configure swiftDerek Higgins1-0/+35
o Adds the required swift metadata (in swift-source.yaml). o Sets up glance to use the swift backend on the overcloud. o Sets up glance to use the file backend on the undercloud and seed, i.e. maintain the Status quo. Change-Id: I4a70ffbf9c51f1fea5cfc84d8718d3d30d36b3f2