Share your experience using Flockport

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.

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.

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.

I have been working with Canonical LXD for one year.

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.

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.

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.

Positive

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.

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.

A system integrator was used for implementation.

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.

On-premises

Other

We are using Mirantis Container Cloud for production builds. It is integrated with Mirantis, and we use it in the insurance industry.

The most useful feature of Mirantis Container Cloud for our container management is Kubernetes. It provides a cluster, high availability, and a self-healing mechanism. Its multi-cluster management capability enhances our operational efficiency as it is easy to use, and every deployment is from the CI/CD, which automatically builds and deploys without human interference, reducing our deployment time to a few seconds.

Mirantis Container Cloud should have AI integration tools, which are not available right now. These tools should assist in app scalability and deployment error handling.

I have been working with Mirantis Container Cloud for three years.

The deployment time is only a few seconds.

I have had no complaints about the stability of the solution. I did not face any stability issues.

I find Mirantis Container Cloud to be scalable. On a scale of one to ten, I would rate its scalability a nine.

I have consulted Mirantis support for some issues, but the support quality is not good. I suffer from support delays due to timezone differences between India and USA.

Neutral

The initial setup of Mirantis Container Cloud is easy. On a scale of one to ten, I would rate the setup process an eight.

Regarding the cost, Mirantis Container Cloud is cheaper than other solutions like Red Hat. The license costs around 10,000 Indian rupees per year.

I compared it with Red Hat.

From a cost perspective, Mirantis Container Cloud is a reasonable choice compared to other solutions. However, for support, it might be better to go with Red Hat, which provides better support. Overall, I would rate Mirantis Container Cloud an eight out of ten.

On-premises