Tripleo

Once Overcloud is deployed, few things cloud operator can do e.g. backup, restore, scaling etc. Lets us check one by one: 1. TripleO backup and restore a) Backing up the Undercloud: we can run a full MySQL backup with additional paths as: $ openstack undercloud backup –add-path /etc/ \ –add-path /var/log/ \ –add-path /root/ \ […]

TripleO offers a default network topology when deploying with network isolation enabled, and this is reflected {tripleo_repo}/network-data-samples/default-network-isolation.yaml file in tripleo-heat-templates. These default networks are as follows: External – External network traffic (disabled by default for Compute/Storage nodes) InternalApi – Internal API traffic, most intra-service traffic uses this network by default Storage – Storage traffic StorageMgmt

In TripleO overcloud deployment, various storage options like Volume, Shared File system, Object storage can be provided with various ways. Check below some options: 1. Adding custom backend to Cinder (Volume Service) Each backend is represented in cinder.conf with a stanza and a reference to it from the enabled_backends key. The keys valid in the

To prepare baremetal environment following things needs to consider: 1. Hardware configuration To deploy a minimal TripleO cloud with TripleO you need the following baremetal machines: Undercloud Overcloud Controller Overcloud Compute For each additional Overcloud role, such as Block Storage or Object Storage, you need an additional baremetal machine.The baremetal machines must meet the following