NCP‐MCA_19 - itnett/FTD02H-N GitHub Wiki
To create a concise, to-the-point version of the key insights and answers from the Nutanix NCP-MCA 6.5 cheat sheet for use with a GitHub Wiki markdown page and Edge text-to-speech, here's a streamlined version formatted to be clear, direct, and optimized for audio output.
Nutanix NCP-MCA 6.5 Cheat Sheet
Calm Blueprint
- Pre-create Task: Executes tasks before main provisioning, like setting up prerequisites. Example: Installing software dependencies before VM deployment.
- Post-delete Task: Executes tasks after a resource is decommissioned. Example: Cleaning up temporary files after VM deletion.
- Service Dependencies: Ensures services start in the correct order. Example: Database starts before application server.
- Substrate Task: Defines the base VM configuration (OS, disk size, network settings). Example: Setting up a new VM with specified resources.
- Macros: Dynamically assigns values during deployment. Example:
@@{address}@@
for IP addresses.
Calm Playbooks
- Triggers: Automates tasks based on specific triggers, such as manual or alert-based. Example: Restart a service when CPU usage is high.
- HTTP Task: Executes HTTP requests to external APIs for third-party integrations. Example: Request a static IP address from an IPAM solution.
- Alert-based Automation: Executes actions automatically based on alerts. Example: Send notification when a security event is detected.
Self-Service Portal
- End-User Provisioning: Allows users to provision and manage resources without admin intervention. Example: Users can deploy VMs autonomously.
- Approval Policies: Defines who can approve specific changes or deployments. Example: Requiring manager approval before deploying production workloads.
- Role-Based Access Control (RBAC): Manages user permissions for accessing Blueprints, applications, and the portal. Example: Restrict certain users from accessing sensitive applications.
Automation Techniques
- Scaling Policies: Automates scaling based on resource usage. Example: Scale out VMs when CPU usage exceeds 80%.
- Task Automation: Automates repetitive tasks to reduce manual workload. Example: Scheduling daily backups and snapshots.
Governance and Compliance
- Granular RBAC: Defines specific access permissions for different users. Example: Allow only specific roles to deploy sensitive workloads.
- Approval Policies: Ensures changes or deployments are approved by designated personnel. Example: Require approval for deploying critical applications.
Monitoring and Validation
- Audit Tab: Provides logs for tracking and troubleshooting deployments. Example: Reviewing deployment logs to identify the cause of failure.
- Built-in Validation Tool: Checks Blueprint configurations for errors before deployment. Example: Validating a Blueprint to ensure correct network settings.
Network and Storage Management
- Dynamic IP Assignment: Uses macros or IPAM integration for dynamic IP allocation. Example: Assign unique IPs to VMs during deployment.
- Storage Monitoring: Monitors storage performance (IOPS, latency, throughput). Example: Check for high latency in storage I/O.
- Resource Usage Alerts: Alerts when resource usage exceeds thresholds. Example: Notify admin when a VM's CPU usage stays above 80% for 5 minutes.
Integration and Compatibility
- Multi-Cloud Deployment: Supports deployment across multiple cloud environments (AHV, AWS, Azure, VMware). Example: Deploying applications in a hybrid cloud setup.
- Third-Party Integration: Integrates with external services via HTTP tasks and APIs. Example: Connecting to external monitoring tools using REST APIs.
Security and Compliance
- Automated Security Responses: Uses Playbooks to automatically respond to security alerts. Example: Isolate a compromised VM based on alert triggers.
- Policy-Driven Governance: Enforces policies through Approval Policies, RBAC, and automation. Example: Require approvals for all production deployments.
Troubleshooting
- Common Causes of Deployment Failures: Includes incorrect credentials, network misconfigurations, and insufficient permissions. Example: Resolve "check login" error by updating credentials.
- Task Failure Troubleshooting: Review task logs and error messages to identify and correct issues. Example: Diagnose failed script execution due to missing network adapter.
Nutanix NCP-MCA 6.5 Cheat Sheet - Audio Cram Page 2
Blueprint Validation and Deployment
- Blueprint Best Practices: Follow best practices for efficient and error-free blueprint creation. Example: Use versioning and reuse common components through the Task Library.
- Error Handling in Blueprints: Implement error handling to capture and log errors during deployments. Example: Use try/catch blocks in scripts to log errors and exit gracefully.
- Blueprint Versioning: Manage changes in Blueprints by tracking versions to ensure consistency. Example: Use version control to maintain different versions of a production Blueprint.
- Common Blueprint Errors: Typical errors include invalid configurations, missing dependencies, and incorrect macro usage. Example: Double-check macro syntax and validate Blueprint settings.
Event-Driven Playbooks
- Event Types in Calm: Types of events that can trigger Playbooks include system alerts, manual triggers, and API calls. Example: Automatically scale out infrastructure when CPU usage exceeds a threshold.
- Conditional Actions in Playbooks: Actions within a Playbook can be conditional, allowing different paths based on the state or input. Example: Use conditions to decide whether to reboot a server or send an alert.
Category Management
- Creating and Using Categories: Categories are used to organize and apply policies or settings to specific objects. Example: Categorizing VMs by environment type, like production or development.
- Policy Application Based on Categories: Policies can be enforced based on assigned categories to manage resources effectively. Example: Applying backup policies only to VMs in the 'Production' category.
Project Management
- Creating Projects: Projects help organize resources, assign quotas, and manage permissions for specific teams. Example: Creating a project for the development team with limited VM quotas.
- Assigning Infrastructure to Projects: Specify which infrastructure resources are available for a particular project. Example: Allocating specific clusters or storage resources to a project.
- Resource Quotas for Projects: Define limits for resource consumption within a project to avoid overuse. Example: Setting a project limit of 100 CPUs and 500 GB of storage.
Runbooks and Task Automation
- Common Runbook Features: Runbooks automate sequences of actions across multiple VMs or applications. Example: Automating software patching across all production VMs.
- Runbook Execution Methods: Runbooks can be triggered manually, on a schedule, or by specific events. Example: Running a maintenance script on all servers every Sunday at midnight.
- Task Dependencies in Runbooks: Define task dependencies to control execution order and handle prerequisites. Example: Ensuring database backup completes before starting the VM upgrade task.
Self-Service Managed Infrastructure
- Scaling In and Out: Self-service options allow dynamic scaling of infrastructure to meet changing demands. Example: Users can request additional VMs as needed or decommission unused ones.
- Retiring Managed Applications: Procedures for retiring and cleaning up resources associated with managed applications. Example: Automatically deleting databases and storage when an application is retired.
Configuration Settings for Self-Service
- Provider Configuration for Calm: Properly configure provider settings for supported platforms like AHV, AWS, Azure, VMware. Example: Configuring credentials, network, and storage settings for each provider.
- Defining Marketplace Capabilities: Marketplace items should have clear descriptions, version control, and appropriate RBAC settings. Example: Publishing a new version of a multi-tier application in the Marketplace.
- Endpoint Configuration: Properly configure endpoints to ensure seamless communication with external systems. Example: Setting up an endpoint to connect Calm with an external monitoring tool.
Governance Features in Nutanix Calm
- Scheduler and Approval Policies: Schedulers automate routine tasks; approval policies ensure proper authorization. Example: Scheduling routine backups and requiring management approval for deletions.
- Common Governance Features: Approval workflows, RBAC policies, and audit logging are key governance tools. Example: Ensuring only authorized users can make critical changes in production.
Monitoring and Logging
- Collecting Logs and Troubleshooting Data: Use Calm’s logging capabilities to collect and analyze data for troubleshooting. Example: Accessing logs from failed deployments to identify root causes.
- Integrating with External Logging Systems: Configure Calm to send logs to external systems like Splunk or ElasticSearch for central monitoring. Example: Sending all alert logs to an external SIEM for security monitoring.
Calm Security Best Practices
- Enforcing Security Policies: Use RBAC, approval workflows, and automated Playbooks to enforce security policies. Example: Automatically isolating a VM when unauthorized access is detected.
- Isolating Compromised Resources: Utilize Calm automation to isolate or quarantine compromised VMs or applications. Example: Using a Playbook to automatically disconnect a compromised VM from the network.
Tips for Efficient Study and Recall
- Use Categories to Organize: Apply categories dynamically to enforce policies across environments.
- Blueprint, Playbook, Runbook: Remember, Blueprints define deployments, Playbooks automate event-driven tasks, and Runbooks handle sequenced actions.
- Validate Before Deployment: Always validate configurations to prevent runtime errors.
- RBAC for Security: Leverage RBAC to control access and ensure compliance.
By focusing on these core concepts, you'll be well-prepared for the Nutanix NCP-MCA 6.5 exam.