7 best practices for operating containers proposed by Google. These can serve as blueprint for ensuring resilient solutions.
Below are some of the best practices for operating containers proposed by Google. These can serve as blueprint for ensuring resilient solutions.
- Use native logging mechanisms or containers
- JSON logs
- Log aggregator sidecar pattern
- Ensure that containers are stateless and immutable
- Avoid privileged containers
- Make application easy to monitor
- Metrics HTTP endpoint
- Sidecar pattern for monitoring
- Expose the health of your application
- Liveness probe
- Readiness probe
- Avoid running as root
- Carefully choose image version
For full details of each line item check this link:
This chart displays very clearly the types of cloud services and highlights what’s managed by cloud provider vs customer.
Ref: Design a Compute Strategy for Microsoft Azure by John Savill
This post will provide the steps to rename an Azure subscription.
Why is this needed?
When managing several Azure subscriptions, keeping the default name may not be very desirable because you would like to quickly identify the customer, website, or any other association you have when managing resources and billing.
I recently ran into this issue myself, where I had to create a new subscription for managing the resources and billing for a production website separately from my own development and testing. When creating the subscription, I chose the Pay-As-You-Go type, and I wanted to rename it with the website name. So my naming convention is:”<websitename> Pay-As-You-Go”. This way, I’ll be able to get the exact billing for each production website in my account, and I could even decide to use different credit cards for each one.
The option for renaming a subscription is not available from the Azure portal. This is available from the windows azure account page. I’d be interested to know why Microsoft hasn’t decided to unify this and allow the action from the portal itself, at least for service administrators.
Renaming an Azure Subscription
- Navigate to the Windows Azure account page at: https://account.windowsazure.com and click on SUBSCRIPTIONS on top
- Select the subscription you want to rename, and click “Edit Subscription Details” from the right menu
- Enter the new name and save it
- Navigate back to the Azure portal and you should see the new name reflected under your subscriptions
This article describes what an Azure subscription is and how to create one. It also touches on some of the best practices for managing multiple subscriptions.
What is an Azure Subscription?
An Azure subscription allows you to get access to the Azure cloud services through the Windows Azure Platform Management Portal. It is mostly used for recording resource usage and billing services.
How to create an Azure subscription?
If you are new to Azure, the easiest way to get started is to navigate to http://azure.microsoft.com and click “Start free” button. This will walk you through the process of creating a free trial account with some free credit (as of 08/13/2016 they are offering $200 free credits that expire after a month), and you can continue to purchase credits or use their free services.
If you are already registered in the Azure portal and would like to create additional subscriptions, you can navigate to this link . Similarly, if you are logged into the portal, you can click on the account name on the top right corner and select “View My Bill” from the menu. Here you should be able to manage your existing subscriptions and add new ones.
Some best practices
- It is possible for an organization to have several Azure accounts, each one with one subscription. However, it is generally a better approach to have one Azure account with multiple subscriptions, in order to reduce the management complexity.
- Use separate subscriptions for different departments, to keep track of usage, spending, and to be able to use different payment methods (very useful for managing cost centers).
- Assign different co-admins to each subscriptions to be able to delegate management and billing operations. Ensure granular security and use minimal access strategy.
- It is a good idea to create separate subscriptions for DEV/TEST and Production environments. This will allow you to monitor billing and usage for each of this environment separately. Also, you can leverage free services while in DEV/TEST.
Create Windows Azure Subscriptions – Arun Rakwal
How Azure subscriptions are associated with Azure Active Directory – Curtis Love