kcli-provider-development

Guide implementing kcli virtualization providers for cloud platforms and hypervisors.

649|170|Updated Sep 2, 2016
One-click install
npx skills add https://github.com/karmab/kcli --skill kcli-provider-development
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: kcli-provider-development
Source: https://github.com/karmab/kcli/tree/main/.claude/skills/kcli-provider-development
Command: npx skills add https://github.com/karmab/kcli --skill kcli-provider-development

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Guides implementing new virtualization providers for kcli, enabling support for additional cloud platforms and hypervisors.

Core Features & Use Cases

  • Provider architecture and directory layout
  • Required implementation steps and standardized interfaces
  • Integration with kcli config for provider registration

Quick Start

Create a new provider directory under kvirt/providers/, implement the provider class, and register it in the config to enable managing the new platform.

Frequently Asked Questions about kcli-provider-development

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I add support for a new hypervisor or cloud platform to kcli?

To add a new hypervisor or cloud platform to kcli, create a provider directory under kvirt/providers/, implement the provider class with required virtualization methods, and register it in the kcli config.

What virtualization methods are required when building a kcli provider?

Building a kcli provider requires implementing core VM lifecycle methods, along with storage, networking, and images handling, using a standardized return structure to ensure consistent integration across platforms.

How do I register a new infrastructure provider in kcli config?

You register a new infrastructure provider in kcli config by completing the provider class implementation and adding it to the configuration registration system, enabling kcli to manage the new platform.

What is the directory structure for developing kcli virtualization providers?

The directory structure for kcli provider development requires placing your new provider implementation directly under the kvirt/providers/ directory to ensure proper architecture and config integration.

Can I include optional components when integrating a new cloud platform with kcli?

Yes, kcli provider development covers optional components alongside core VM lifecycle methods and standardized return structures, allowing flexible integration when adding support for new cloud or virtualization platforms.

Does kcli provider development work for both cloud platforms and on-premise hypervisors?

Yes, kcli provider development guides implementing new virtualization providers applicable across both cloud platforms and hypervisors, covering provider architecture, required methods, and integration steps for both environments.