Production planning
When you are planning a production deployment, you should consider the aspects that you want to customise for best results. This topic covers the most common and important requirements when you are planning to move your Anbox Cloud deployment to production. While there could be other specifically tailored needs, this topic helps you identify your basic requirements and deployment strategy.
Compute resource requirements
Depending on your workload and the type of deployment you choose, hardware or cloud resource requirements can differ. See requirements to get an idea about the kind of resources that are required to run a full Anbox Cloud deployment with the streaming stack or a minimal core version of the deployment without the streaming stack.
You should pay special attention to the hardware requirements of applications that are used but not maintained by Anbox Cloud.
Software requirements
Anbox Cloud deployments require the Ubuntu operating system. You should consider the Ubuntu OS, LXD, and Juju versions supported by Anbox Cloud for a production deployment. See requirements to see compatible software versions.
Networking requirements
Consider the following questions to decide your networking requirements:
- In your deployment, how should your network structure and topology look like?
- Do you need subnets? If yes, what is the range of the subnets that you want to define?
- Do you require a virtual network and plan Juju spaces on top of it?
- Where is your Anbox Application Registry (AAR) deployed? How will the AMS in other clusters connect to AAR? Define any peering requirements that you may have, based on the number of clusters you have and where AAR is deployed. To know more about AAR, see the following links:
Storage requirements
Based on your safety protocols, think about where you would want to host your storage. Also, refer to the following links that will help you plan and calculate your storage needs:
Scalability, High availability, and redundancy
With Anbox Cloud, you can scale your deployment to as many clusters and subclusters as you require. It is a good idea to define how many Anbox clusters you want to deploy and how many subclusters per cluster.
You should also assess the number of instances that you require for each model/service. For example, think about the number of Juju controller instances that you need. See Make a controller highly available for more information.
Anbox Cloud comes with support for High Availability (HA) for both Core and the Streaming Stack.You can define HA by adding new Juju units. See How to enable High availability? to plan your HA requirements.
Security
Secure communication
Communication between the Anbox Cloud components uses TLS encryption and authentication. Access is controlled through secure authentication tokens or temporary passwords. Secure communication is achieved using TLS and public-key encryption with a chain of trust up to a shared root Certificate Authority (CA). However, when the cluster is being brought up or a new unit is being added, the chain of trust and certificates required must be bootstrapped into the machines.
See About Security for more information.
Patching
You should keep your Anbox deployment updated to the latest available stable version. You should also update the other applications which make up Anbox. Keeping up to date ensures you have the latest fixes and security patches for smooth operation of your cluster.
For details about the Anbox Cloud release roadmap, see Release roadmap.
Data backup
Consider how frequently you want your data backed up and where you want to host your backed up data.
Load balancing
Load balancing solutions can differ based on your deployment model. You should assess the load balancing solution that you want to use and the number of load balancers that is ideal for your deployment model.
Monitoring and metrics
Although Anbox Cloud does not offer its own observability solution, Anbox Cloud gathers various performance metrics that you can access through API endpoints to create a monitoring solution.
You can decide if you want to use Canonical’s monitoring system or a customised version. See How to monitor Anbox Cloud? and Prometheus metrics for a detailed understanding of monitoring and metrics to assess your monitoring needs for the production deployment. To help you in your assessment, you can refer to these example implementations: Example: Collect metrics and Example: Monitor status.
Licensing and Support
You need the Ubuntu Pro subscription to use Anbox Cloud. Depending on the type of subscription you choose, your support model differs. You can refer to the Ubuntu Pro website to learn and compare the different types of subscriptions.
Upgrade
When you consider a production deployment, it is important to assess your upgrade roadmap. For more information about upgrading Anbox Cloud and the prerequisites required for the upgrade process, see How to upgrade Anbox Cloud.
You can also choose to subscribe to the announcements about Anbox Cloud releases on discourse. For insights into the Anbox Cloud release roadmap, see Release roadmap.
Last updated 23 days ago.