Canonical LXD is used as a technology for spinning containers for infrastructure requirements. Canonical LXD is deployed in my organization on an on-premise cloud and private cloud. It helps to maintain isolation and secure the workload due to the inherent security features offered by Canonical LXD container.
Container operations have become more efficient with reduced manual intervention and reliable performance
What is our primary use case?
What is most valuable?
Ease of administration is the feature of Canonical LXD that I have found the most valuable and useful so far.
It provides simplified operations for container management.
It helps to maintain isolation and secure the workload due to the inherent security features offered by Canonical LXD container.
What needs improvement?
Canonical LXD's snapshotting system is not being used.
The REST API in Canonical LXD is not being utilized. Direct management using the online interface is preferred because REST API integration is required for some application-level integration, and Canonical LXD is being used as an infrastructure component rather than requiring REST API communication. A standard interface is sufficient for administering Canonical LXD container.
Device pass-through has not been used.
Migration features of Canonical LXD are not being utilized.
Administration through a graphical user interface or graphical-based administration would definitely help for managing Canonical LXD. Currently, only command-line tool features are available, but if optical tools are introduced, that would also help.
More detailed documentation in terms of deployment and manageability of Canonical LXD container is needed.
For how long have I used the solution?
I have been working with Canonical LXD for one year.
What do I think about the stability of the solution?
Canonical LXD is a very stable solution. We have never faced any issues or errors post initial implementation, and very little manual intervention is required in terms of manageability of Canonical LXD.
What do I think about the scalability of the solution?
Canonical LXD is a pretty scalable solution. You can scale horizontally to n number of instances. There is no hard limit, so horizontal scaling is seamless for this solution.
How are customer service and support?
Cases and tickets are raised with Canonical when priority issues arise. These issues can range from bugs in the product or some severe issues with high severity.
How would you rate customer service and support?
Positive
Which solution did I use previously and why did I switch?
I have used several solutions before Canonical LXD, but they belong to the open source domain, not in the enterprise domain.
Primarily the cost and commercial aspects led me to decide to switch from the previous solution to Canonical LXD. It is a more cost-effective solution as compared to competitive products.
How was the initial setup?
Canonical LXD deployment is pretty straightforward if you are familiar with it. People who do not have a background with Canonical solutions may find it a little overwhelming, but people who are familiar with Canonical Infrastructure stack should be comfortable deploying it.
What about the implementation team?
A system integrator was used for implementation.
What other advice do I have?
Canonical LXD is not sold separately. It comes as part of the operating system license or a cloud solution license, so it is not an independent product. I would rate this product a 9 out of 10.
Which deployment model are you using for this solution?
On-premises
If public cloud, private cloud, or hybrid cloud, which cloud provider do you use?
Other
