Yesterday, the Linux Foundation announced the newly formed Cloud Native Computing Foundation – a Linux foundation collaborative project backed by industry giants like AT&T, Box, Cisco, Docker and many more. In addition to this announcement, Google has also announced that it has donated it’s Kubernetes container technology to the foundation, just days after announcing its support for the OpenStack foundation for the sake of advancing container technology. As advocates and users of container based technology and cloud native applications, we at Cloud-A are really excited about this string of announcements and the affect it will have on the adoption of modern, container based, cloud aware technology.
With fear that Canada was lagging in the adoption of leading edge technology and missing out on major economic benefit as a result, Cloud-A was launched with the goal of promoting the use of modern cloud technology within Canada and accelerating innovation in both private and public sectors.
The true opportunity with modern Cloud infrastructure like Cloud-A is not necessarily with the migration of existing applications and platforms, but the developer greenfield that it provides.
Here are 3 ways that Cloud-A and modern Cloud Computing can help organizations Innovate.
There are now two ways to authenticate your Cloud-A Bulk Storage account to CloudBerry products based on your workflows and requirements. The first method is Keystone authentication, which is the legacy method. Authenticating this way. The Cloud-A, CloudBerry Lab partnership has been great for our clients, providing a tried and tested use-case for backups of on-premise or Cloud-A hosted Windows servers (and soon to be Linux!)
You will notice a few changes in the Cloud-A/CloudBerry relationship. First of all, most CloudBerry OpenStack products now have a branded connector for Cloud-A. No longer will you have to choose the generic OpenStack account.
There are now two ways to authenticate your Cloud-A Bulk Storage account to CloudBerry products based on your workflows and requirements. The first method is Keystone authentication, which is the legacy method. Authenticating this way will allow for read and write access to all of the Bulk Storage containers in your Cloud-A Account.
With the release of Bulk Storage container keys, users can now authenticate to specific containers, rather than all of the containers in your account. Authenticating this way is ideal for service providers who manage backups for multiple customers. Instead of authenticating to the service provider’s Bulk Storage account where you would have access to all of the account’s containers, you authenticate to a specific client’s container.
Cyberduck allows users to edit any file with your preferred editor. To edit files, a seamless integration with any external editor application makes it easy to change content quickly. Edit any text or binary file on the server in your preferred application.
We often get questions from prospective customers who aren’t familiar with the public cloud model on whether Cloud-A is better suited for test/dev environments or production environments. The answer is both. Cloud-A is built on the same enterprise class server and storage hardware that many enterprise organizations run internally, thus making it more than suitable for production environments. The utility billing model allows users to access their systems on the same enterprise class hardware, but only pay for it when they are using it, also making it an ideal and cost effective test/dev environment.
Here is a look at the benefits of using Cloud-A for testing, development and QA environments:
Technical disruptions are likely only a small hurdle to overcome when compared to the organizational change that is required for moving from legacy on-premises IT technology to the public cloud. Here are a few considerations for getting executive buy-in for your public cloud projects.
The Lift and Shift cloud migration technique includes migrating an existing application to a modern cloud platform as is, with very little modification to the architecture of the application. Because the architecture of the existing application was likely architected for its original host, the application might fail to take advantage of the features and benefits of the new cloud platform.
Minimal development work ($)
Missing the benefits of elastic cloud resources
Higher cost of management over time
2. Hybrid Partitioning
Hybrid partitioning includes partitioning the individual components of an application and spanning them across a combination of both private infrastructure and public cloud infrastructure. The idea is to limit the amount of dSimplify the Cloud with Cloud-A & Cloud 66 Webinarevelopment work required, by migrating the highly scalable, highly transactional components of an application to public cloud resources to take advantage of the elasticity and utility billing, but keeping the less scalable components (think Oracle databases) on their original host.
Best of both worlds (public and private cloud)
Components on the Public cloud resources can scale up and down on demand
Less development work than than totally refactoring an app
More development and testing work than Lift and Shift ($$)
Possible latency concerns
Not a fit for every application
Refactoring an application includes a complete rewrite of the code, so that the application becomes “cloud aware” and can take advantage of the benefits of elastic, scalable, API driven public cloud infrastructure. Since this strategy is essentially going back to the drawing board, the app can be re-written with modern application architecture best practices like decoupling components and utilizing distributed microservices for enhanced reliability and performance.
Scale resources on demand
Costs scale with demand
Increased application resiliency
Requires the most development and testing work ($$$)
It is no secret that Canadian enterprises are scrambling to determine their cloud strategy. Many organizations have catalogs of legacy applications and racks of legacy hardware, and determining whether private cloud, public cloud or both (hybrid cloud,) is the right fit is not always an easy decision to make. This whitepaper was written to help Canadian enterprises identify some of the considerations to make when adopting public cloud in their cloud strategy.