aboutsummaryrefslogtreecommitdiffstats
path: root/mcp/reclass/classes/cluster/mcp-pike-common-ha/openstack_telemetry.yml
AgeCommit message (Collapse)AuthorFilesLines
2018-05-21[ha] Bring in gnocchi/panko servicesMichael Polenchuk1-8/+62
JIRA: FUEL-372 Change-Id: I9083898f0179649d855750d48f3f9bc79caba50c Signed-off-by: Michael Polenchuk <mpolenchuk@mirantis.com>
2018-05-18[ha] Align package repositories on all the nodesMichael Polenchuk1-1/+1
Change-Id: Idd09d28677b109b4c0c5a4c232dcfb7c4f24dbd7 Signed-off-by: Michael Polenchuk <mpolenchuk@mirantis.com>
2018-02-20[reclass] Update copyright yearAlexandru Avadanii1-1/+1
Change-Id: Id1ca66938531e1d24ec0d44194f8b09643062944 Signed-off-by: Alexandru Avadanii <Alexandru.Avadanii@enea.com>
2018-02-05[baremetal] Rename all to drop baremetal prefixAlexandru Avadanii1-0/+33
A few things differ between baremetal and virtual nodes: - provisioning method; - network setup; Since now we support completely dynamic network config based on PDF + IDF, as well as dynamic provisioning of VMs on jumpserver (as virtual cluster nodes), respectively MaaS-driven baremetal provisioning, let's drop the 'baremetal-' prefix from cluster model names and prepare for unified scenarios. Note that some limitations still apply, e.g. virtual nodes are spawned only on jumpserver (localhost) for now. JIRA: FUEL-310 Change-Id: If20077ac37c6f15961468abc58db7e16f2c29260 Signed-off-by: Alexandru Avadanii <Alexandru.Avadanii@enea.com>