Weave Code
Openstack Laravel Package
php-opencloud/openstack
PHP OpenStack SDK lets PHP developers connect to OpenStack APIs in a simple, idiomatic way. It supports multiple services and versions, installs via Composer, and requires PHP 7.2.5+ with ext-curl. Official docs and integration tests included.
php-opencloud/openstack is a PHP SDK that lets developers connect to OpenStack APIs in a simple, idiomatic way. Built specifically for OpenStack, it supports multiple services and service versions, requiring PHP >= 7.2.5 and ext-curl. Install it via composer require php-opencloud/openstack.
- Broad service coverage — compute, storage, networking, identity, and more
- Version-aware — supports multiple versions of each OpenStack service
- Semantic versioning — minor updates never break PHP code or configuration
- Well documented — full guides on Read the Docs
- Actively maintained — CI-tested unit and integration suites
Frequently asked questions about Openstack
- How do I install php-opencloud/openstack in a Laravel application?
- Install it with Composer using composer require php-opencloud/openstack:^3.16. The package is framework-agnostic, so you still need to bind a client factory and service adapters in Laravel’s service container. Keep credentials in config/openstack.php or a secrets manager rather than in controllers.
- Does php-opencloud/openstack support Laravel 11 and PHP 8.4?
- The SDK requires PHP 7.2.5 or newer with ext-curl, and recent releases explicitly added PHP 8.4 support. Current Laravel releases on PHP 8.0 through 8.4 are compatible in principle, but you should test Composer resolution against your app’s Guzzle constraints. The package is not Laravel-native, so Laravel version support depends on PHP and dependency compatibility.
- Which OpenStack services can I use with this PHP SDK?
- The SDK covers Compute (Nova), BlockStorage (Cinder), Identity (Keystone), Images (Glance), Networking (Neutron), ObjectStore (Swift), and Gnocchi metrics. Service and version coverage is documented in the repository’s COVERAGE.md, so verify your required OpenStack releases and microversions there. Not every OpenStack API or extension is necessarily supported.
- How do I authenticate to OpenStack from Laravel with php-opencloud/openstack?
- Authentication is Keystone-oriented and supports models such as Keystone v3 password, application credentials, token validation, and multi-tenant credential brokering. In Laravel, resolve credentials from config or a secrets manager and build the OpenStack client through a bound factory. Avoid exposing SDK identity models or tokens to controllers, jobs, or views.
- Can I run OpenStack provisioning operations in Laravel queues?
- Yes, long-running operations such as server creation, volume attachment, snapshots, and large object uploads should run in queued jobs rather than synchronous HTTP requests. The SDK does not build in async workflow behavior, idempotency, compensation, or orphan-resource cleanup, so your application must own those concerns. Use retries, status polling, and reconciliation carefully.
- What are the requirements for php-opencloud/openstack?
- The runtime requires PHP 7.2.5 or newer and the ext-curl extension. Installation is via Composer, and the SDK uses PSR-4 autoloading and Guzzle, which align with typical Laravel stacks. Check your PHP version, extensions, and Guzzle constraints before adopting it.
- Is php-opencloud/openstack actively maintained and safe for production?
- The package is active and follows semantic versioning, but it has a small maintainer base, community-only support, and limited Packagist dependent metadata. It can be production-appropriate when your Laravel app is already committed to OpenStack and you add guardrails around it. Validate upstream responsiveness, OpenStack upgrade testing, and your own support plan.
- How should I handle OpenStack API errors, retries, and idempotency in Laravel?
- Wrap SDK calls behind application-owned interfaces and map OpenStack exceptions into your Laravel error handling. Build retry policies, token caching, idempotency keys, compensation, and orphan-resource cleanup yourself because the SDK does not provide them. For queued operations, record state and reconcile partial failures explicitly.
- What are alternatives to php-opencloud/openstack for Laravel OpenStack integration?
- Alternatives include calling OpenStack APIs directly with Guzzle, using cloud provider SDKs, or building thin in-house adapters for the specific services you need. This package is OpenStack-specific and not a cloud-portability strategy; it is best when OpenStack is already the target platform. Compare maintenance burden, service coverage, and Laravel integration effort before choosing.
- Will php-opencloud/openstack conflict with Laravel’s Guzzle dependencies?
- Dependency conflicts with Laravel’s Guzzle constraints are possible, so test Composer resolution early in a branch. Recent SDK releases fixed uri-template and Guzzle promise compatibility issues that matter for Laravel dependency resolution. If constraints conflict, you may need to adjust versions or isolate the integration.
Weaver
How can I help you explore Laravel packages today?