The Cloudify operations guides are based on the experience of our field support engineers in real customer situations and verified by our R&D engineers for accuracy. You can use the guides to see the flow of Cloudify deployment and troubleshooting operations.
Overview Snapshots provide a way for the state of Cloudify HA cluster. A cloudify snapshot should be done on a daily basis (suggest in an off peak time) and can be automated using the REST API as an alternative to an operator manually running the snapshot as shown here in this user guide. Backing up the virtual machine that the cloudify managers run on should be done at regular intervals, this would be dictated by a backup policies and would likely involve daily, weekly, monthly and yearly backups as required.
Cloudify Console for Service Orchestration The Cloudify Console provides a graphical user interface for orchestration that lets the operator: Upload blueprints into the Cloudify Managers Deploy and install/uninstall new services Monitor the status and performance of services View service logs and events All of the things that can be done in the Cloudify Console can also be done using the CLI and the REST API. Logging into the Console To login to the Cloudify Console you need to use a browser on your laptop or PC and enter in the URL of the Cloudify manager IP address or hostname, for example https://192.
Overview These instructions explain how to upgrade a Cloudify High Availablity (HA) cluster from version 4.x to version 4.3. Upgrade on new hosts This is the recommended method. If something happen in upgrade process, you still have the old manager, working and functioning. The key elements of upgrading a Cloudify HA cluster on new hosts are: Create and download snapshot. Save agent ssh keys. Install new version for master manager on new host.
Environment Hardware prerequisite Cloudify HA cluster usually builds on three Cloudify managers. Each Cloudify manager requires at least next hardware resources: Minimum Recommended vCPU 2 8 RAM 4GB 16GB Storage 5GB 64GB The minimum requirements are enough for small deployments that only manage a few compute instances. Managers that manage more deployments or large deployments need at least the recommended resources.
The purpose of this document is to provide detailed information for: Identifying Cloudify Manager’s processes Defining how these processes should be tracked for monitoring and alerting Defining locations of Cloudify Manager log files Cloudify System Processes In a Cloudify Manager environment, the following system processes exist: User Command Description cfyuser nginx: master process /usr/sbin/nginx -c /etc/nginx/nginx.conf Nginx web server (REST API) root process nginx nginx: worker process Nginx web server (REST API) child process stage_u+ /opt/nodejs/bin/node /opt/cloudify-stage/backend/server.
This troubleshooting guide provides a list of frequently asked questions that point to common troubleshooting techniques or external cloudify documents where necessary. Deleting a deployment fails with the error message: Deployment still has active nodes First uninstall the deployment (i.e. run the “uninstall” workflow on the deployment) and then run the delete on the deployment again. A deployment install failed, how do I find out what went wrong? By searching through the Cloudify logs and events you should be able to ascertain what went wrong with the install.