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.