DEV Community: Bunnyshell

Creating Ephemeral Environments for CI/CD (GitOps) Pipelines with Kubernetes

Bunnyshell — Wed, 28 Sep 2022 21:50:01 +0000

🌐 [Upcoming Webinar] Testing your application in a production-like environment can help you catch bugs early in the development life cycle and increase the overall quality of the shipped product. However, setting up your CI/CD pipeline in a way that allows you to set up ephemeral production-like environments is not a trivial undertaking.

But... Kubernetes can help. Join Sorin Dumitrescu, VP of Engineering, and Cristian Blanaru, SRE team lead as they explore 🔍:

☑️ How to use Kubernetes to create cost-effective, ephemeral environments that look like production
☑️ How to easily integrate GitLab and GitHub pipeline testing with Bunnyshell using ephemeral environments
☑️ How to run tests automatically for every PR to accelerate code quality and see all changes in real-time before each merge

development #testing #engineering #kubernetes #environment

https://hubs.la/Q01n8VXN0

How Slack Uses Remote Development to Improve Dev Experience & Productivity

Bunnyshell — Wed, 07 Sep 2022 20:23:20 +0000

[YOU'RE INVITED👇]

⏰ Wed, Sep 14, 2022, || 10:00 AM PST.⏰

REMOTE DEVELOPMENT capabilities give the developers the POWER to develop locally while full-stack is running in the cloud, which makes changes visible to all team members (including QAs and Product teams) without any need to rebuild.

https://www.linkedin.com/video/event/urn:li:ugcPost:6962637599597355008/

Benefits of Ephemeral Environments in the Dev Cycle

Bunnyshell — Fri, 12 Nov 2021 10:45:15 +0000

The main reason organizations adopt ephemeral environments is because they accelerate the software development cycle; developers can review changes visually and also share their work with non-technical team members (such as designers, for example) using a link to the proposed revision.

Other benefits of ephemeral environments include:

removing the staging / QA bottleneck:
traditionally, organizations use a staging or QA environment to merge and test all code before pushing it into production. The problem is, they only have one or very few of these environments, so, as the organization grows, this becomes a bottleneck that slows down the development cycle. Enter ephemeral environments - now you have a limitless supply of environments you can use for testing. As every code branch is contained in its own isolated environment, it becomes its own integration environment, so you no longer need a single testing and integration environment to merge all code before pushing it into production.

allowing early and often feedback:
the earlier in the development cycle you identify quality issues, the more you can reduce rework and improve development velocity. Ephemeral environments help minimize rework by enabling all stakeholders to become part of the development process. For example, QAs, designers, product managers, or even customers no longer have to wait until a developer finishes coding to see changes, they can offer feedback as the feature is being built.

limiting rework, thus increasing development velocity:
Continuous Integration (CI) focuses on the idea that you should continuously test your code as it’s being pushed. The problem is, most CI systems only perform unit tests (they test small units of code, not the entire system), while Integration and Smoke tests (which test the system as a whole) are left until the code is merged to the main branch in the staging environment. If any issues are found at that stage, it’s already too late; you’ll need rework to get them fixed. Even more, if there’s only one staging environment available, this will create bottlenecks. Ephemeral environments allow Integration and Smoke tests to be run right after the environment is created, thus ensuring they’re performed as frequently as unit tests and allowing you to find issues early in the development process.

allowing for experimentation with infrastructure:
infrastructure changes are costly both in terms of money and time, and they can slow down your team’s velocity. But with ephemeral environments, testing the new infrastructure can be done in isolation, so it doesn’t affect other developers.

they enable Agile / Scrum: today, many organizations follow Agile / Scrum practices, but their infrastructure and technology are not always adapted to iterative software development. These workflows focus on early and frequent feedback, and ephemeral environments are the perfect tool to enable that.

Storing Files In Today’s Cloud: What Is Object Storage

Bunnyshell — Thu, 26 Nov 2020 09:00:37 +0000

Simply put, object storage, or object-based storage, is a data storage architecture that manages data as distinct units called objects. Each object includes the data itself, a variable amount of metadata, and a globally unique identifier.

Further, object storage devices can be aggregated into larger storage pools, and these pools can be distributed across multiple locations. This enables not only unlimited scale but also data resiliency and disaster recovery.

Because of this, object storage is used to retain and manage massive amounts of unstructured data, such as Facebook photos, Spotify songs, or Dropbox files.

How object storage works

Let’s suppose you want to store all the books in the world in a very large library system on a single platform. There are two things you need to store:

the contents of the books (data)
and the associated information like author, publisher, publication date, etc. (metadata).

Traditionally, you would do this using a relational database, organized in folders under a hierarchy of directories and subdirectories. But because we’re talking about a vast amount of books, the search and retrieval process becomes cumbersome and time-consuming when you want to access a specific book.

Instead, object storage is a better choice because the data is static or fixed (neither the contents of the books or the associated information will change).

In this case, the objects (data, metadata, and ID) will be stored as “packages” in a flat structure that’s easily located and retrieved with a single API call. In the future, as the number of books will grow, you can aggregate storage devices into larger storage pools and distribute these storage pools for unlimited scale.

Object storage use cases

Besides the storage of unstructured data, object storage can be used for:

storage of backup files, database dumps, and log files;
large data sets;
archiving files in place of local take drives.

Object storage vs. block storage vs. file storage

There are fundamental differences between file storage and object storage. File storage organizes data hierarchically inside directories, sub-directories, and files. It works great when the number of files is not very large and you know exactly where they’re stored.

Object storage, on the other hand, typically presents itself via a RESTful API – there’s no concept of a file system. Instead, applications save objects (files + additional metadata such as the file name, the date it was created, and the date it was last modified) to the object store using the PUT or POST API, and the object storage saves the object somewhere in the system.

Then, the application receives a unique key (think of it like the number you receive when you leave your coat in the cloakroom) for that object from the object storage platform which will be saved in the application database. If an application wants to fetch that object, all they would need to do is give the key as part of the GET API and the object would be fetched by the object storage.

Some good examples of object storage APIs are those used by Amazon S3 (the default standard for object storage access), OpenStack Swift, and Azure Blob Service REST API.

Because objects are stored in a flat address space, this makes it easier to locate and retrieve data across regions. This is why object storage has become the preferred solution for data archiving and backup.

Files in a filesystem have a broader set of functions that can be applied to them, including appending data and updating data in place. The programming model is more complex than an object store and is, nowadays at least, almost always accessed programmatically via a “POSIX” style of interface. Generally, the use of CPU and memory is very efficient and there’s a mindset that the filesystem is a private local resource.

Although NFS and SMB do allow for a filesystem to be made available as a multi-tenanted resource, developers usually avoid them because, sometimes, there are subtle differences in how they react compared to “local” filesystems despite their full support for POSIX semantics.

Another big difference between file storage and object storage is that file systems are designed with consistency in mind, and are usually accessed over low to moderate latency (50 microseconds – 50 milliseconds) networks. In contrast, object stores are distributed over a shared infrastructure, connected together over low-bandwidth high-latency wide area networks, and their time to first byte can sometimes be measured in multiples of whole seconds. Performing lots of small (4K – 16K) random reads from an object store is likely to cause frustration and performance problems.

Last but not least, maybe the biggest advantage object storage has is that you can be reasonably sure that anything you put in an object store will remain there until you ask for it again, and that it will never run out of space as long as you pay for what you use. These resources generally run at large scale with built-in replication, version control, automated recovery, etc., and only natural disasters will make the data disappear (but even then, you have easy options to make another copy in another location).

When it comes to filesystems, especially those you’re expecting you or your local team to manage, you can only hope that everything is getting backed up and that it doesn’t fill up accidentally and cause everything to melt down when you can’t update your data anymore.

Block storage is an alternative to file storage. It takes a file apart into equally-sized data blocks and then stores these blocks as separate pieces of data. Each piece of data has a different address, so they don’t need to be stored in a file structure. To access a file, the operating system uses the unique addresses to reassemble it.

Want to find out more about the benefits of Object Storage? Check out our blog!

Top Issues Stemming From Multi-Cloud Adoption

Bunnyshell — Wed, 04 Nov 2020 16:16:08 +0000

Whether to optimize the costs associated with running and managing their own infrastructure or to enable development teams to build more efficient apps, most businesses today are interested in adopting a cloud infrastructure.

This is why now we have quite a few cloud solutions on the market, from public clouds such as Amazon Web Services, Microsoft Azure, and DigitalOcean, to private clouds such as Azure Stack, VMWare, or HPE.

In the early days, cloud adoption was about using a new approach to building applications. Today, however, implementing the cloud model is about the ability to embrace a multi-cloud architecture. Each of the solutions available appeals to different types of businesses and business needs. They can even be combined to create hybrid clouds.

And this is exactly where the problems start to appear. In their race towards creating the best cloud architecture for their organizational needs, companies sacrifice visibility.

Because their infrastructure is spread across multiple platforms and vendors, it’s almost impossible to have a clear overview. This lack of visibility leads to issues such as time-consuming infrastructure management and even the impossibility of scaling.

Find out more about the drawbacks of multi-cloud adoption on our blog.

6 Online Magento Events You Can Attend From Home This Fall

Bunnyshell — Mon, 26 Oct 2020 07:21:17 +0000

2020 was a year like no other, and among the many things that we had to get accustomed to was the lack of offline events. If you’re a professional who likes to connect with the local community or attend conferences and learn from the best in your industry, we’re sure this was a bitter pill to swallow.

Luckily, most organizers didn’t cancel their events; they simply moved them online. And from this, new opportunities emerged, as we’re now able to attend events we’d otherwise not be able to.

Below we’ve compiled a list of all the Magento events happening in the next months, from local meetups to webinars and international conferences. Which ones are you most eager to attend?

Magento Events Calendar

1. Meet Magento Poland 2020

Meet Magento Poland is the biggest event in Middle-Eastern Europe dedicated to the business community circled around big eCommerce projects. It’s the place to be if you want to form lasting business relationships, work on mutual projects, and expand your network.

The agenda for this 9th edition is split into two parts – business and technology, and will address subjects like Polish implementations, integration with Polish eCommerce service suppliers, and the development of global and Polish markets.

When: Tuesday, October 27, 2020
Where: Online event
Type: Conference
Details: https://meetmagento.pl/en

Find out more online Magento events on our blog.

How to set up Laravel in Ubuntu

Bunnyshell — Thu, 10 Sep 2020 08:24:44 +0000

Laravel is a very popular open-source PHP framework aimed at easy development of applications. If you are looking for a new PHP framework, you should give Laravel a try.

Summary

The following steps will show you how to install and run Laravel on an Ubuntu 18.04 LTS based Apache server. This tutorial works for Ubuntu 17.x as well. But for servers, you should prefer to use an Ubuntu LTS release like the current Ubuntu 18.04 LTS. Learn how to set up Laravel in Ubuntu.

After showing you how to set up this PHP framework in Ubuntu, we’ll be showing you what it takes to set up your Laravel Application using the Bunnyshell Platform.

How to set up Laravel in Ubuntu

Pre-Requisites

We will assume that you have a basic server based on Ubuntu running.

Before proceeding with the installation, it’s always a good idea to make sure your sources and existing software are updated.

sudo apt-get update

sudo apt-get upgrade

Before Laravel, we need to install other components that are essential.

Installing Apache and PHP 7.2

Next step is to install PHP along with several extra packages that would prove useful if you are going to work with Laravel.

sudo add-apt-repository ppa:ondrej/php

sudo apt-get update

sudo apt-get install apache2 libapache2-mod-php7.2 php7.2 php7.2-xml php7.2-gd

php7.2-opcache php7.2-mbstring

Even though Ubuntu’s own repository has PHP, it’s better to add a 3rd party repository here because it gets more frequently updated. You can skip that step and stick to Ubuntu’s version if that’s what you prefer.

Installing Laravel

Before we finally delve into it, we also need Git version control to be installed. If you have it installed, you can skip the following step.

Download and install Git for Linux:

sudo apt-get install git
Once the installation has successfully completed, the next thing to do is to set up the configuration details of the GitHub user.

git config --global user.name "user_name"

git config --global user.email "email_id"
To install Laravel, we need to install Composer first. It is a tool for dependency management in PHP that allows you to package all the required libraries associated with a package as one. To install Laravel and all its dependencies, Composer is required.

cd /tmp

curl -sS https://getcomposer.org/installer | php

sudo mv composer.phar /usr/local/bin/composer

The curl command downloads composer.phar package to your /tmp directory. But we would want composer to run globally hence we need to move it to /usr/local/bin/ directory under the name ‘composer’. Now we can run composer from anywhere.

To install Laravel, move to the public html directory on your system. Since we are on Ubuntu and using Apache, we will install it in the /var/www/html directory.

cd /var/www/html

sudo composer create-project laravel/laravel your-project --prefer-dist

The above command will create a “your-project” directory with Laravel installation in it. Composer uses Git to download and install all the packages and modules that Laravel requires for functioning.

Configuring Apache

Now that we have installed Laravel, we move onto the step of configuring Apache webserver.

Give proper permissions to the project directory:

sudo chgrp -R www-data /var/www/html/your-project

sudo chmod -R 775 /var/www/html/your-project/storage
Go to the /etc/apache2/sites-available directory and use the following command to create a configuration file for our Laravel install:

cd /etc/apache2/sites-available

sudo nano laravel.conf

Add the following content to the file and close it after saving. Replace yourdomain.tld with the domain name of your website inside the file:

ServerName yourdomain.tld

ServerAdmin webmaster@localhost

DocumentRoot /var/www/html/your-project/public

<Directory /var/www/html/your-project>

    AllowOverride All

</Directory>

ErrorLog ${APACHE_LOG_DIR}/error.log

CustomLog ${APACHE_LOG_DIR}/access.log combined

We have to enable this newly created .conf file and disable the default .conf file that is installed with the default Apache install. Also, we need to enable mod_rewrite so that permalinks can function properly:

sudo a2dissite 000-default.conf

sudo a2ensite laravel.conf

sudo a2enmod rewrite

sudo service apache2 restart

Your Laravel installation is now complete. Visit the IP address or domain name of your server with a web browser.

Looking for an easier way? Check the full tutorial to see how to set up Laravel using Bunnyshell.

Introduction To Cloud Optimization

Bunnyshell — Wed, 08 Jul 2020 13:30:33 +0000

With the ever-increasing amount of data being shared, used, and processed, web app performance is more important than ever.

At the same time, users expect applications to run seamlessly, and a bad experience can potentially damage business productivity.

Slow and unreliable web applications also mean higher resource consumption, which can lead to higher costs, diminished profits, and even serious damage to the company’s image.

However, all these shortcomings can easily be avoided through cloud optimization. Specifically, through the continuous optimization of web applications at each critical level.

This article is part of a Cloud Optimization Series where we discuss how you can configure your cloud environment to achieve the best results.

What is cloud optimization?

Every web app is unique, and so are its infrastructure requirements. Plus, these requirements change over time.

Cloud optimization refers to the process of balancing these requirements and allocating the right resources so that an application can run efficiently.

Some of these optimizations can also be automated through AI/ML, with little to no developer intervention. This means fewer resources to manage and a more streamlined infrastructure.

Why should you care about cloud optimization?

There are 3 main reasons why you should care about cloud optimization:

1. Site performance & speed

Web app optimization isn’t just nice to do, but a necessity. 47% of internet users expect websites to load in 2 seconds or less, and 40% will abandon a page that takes 3 or more seconds to load.

An Aberdeen study also found that a 1-second delay in page load time equals 11% fewer page views, a 16% decrease in customer satisfaction, and 7% loss in conversions.

2. Site ranking & SEO

Your website’s SEO ranking is closely related to its loading speed. There are many factors that contribute to how high or low Google ranks a page (like how much time users spend on it and whether they find what they’re looking for), but among them, page speed is one of the most important.

3. Cost optimization

On one hand, Financial Departments want to keep cloud spend in check. On the other hand, developers want to make sure their apps are always working at 100%, so simply reducing the allocated resources is not an option.

The more complex your web app is, the more resources it will need, and they don’t come cheap. The efficient use of the tools and resources you have at your disposal can translate into savings and overall better management of your IT budget.

The five levels of cloud optimization

Cloud optimization techniques can be applied at each level of the cloud environment. We can, therefore, talk about 5 levels of cloud optimization, one at every level. If you want to dive into each of them, read the full article here.

How to deploy Discourse in Cloud

Bunnyshell — Thu, 07 May 2020 11:03:25 +0000

As an open-source community forum platform, Discourse proposes an out of the box approach. It is developed as a social interaction method looking to empower the community mindset. It uses an automatic trust system that encourages the members of the community to vote out trolls and spammers.

In this step by step tutorial, we are going to show you how to deploy Discourse in Cloud by using Bunnyshell, the easiest tool to manage your technology stack on multiple clouds. Since it is the same interface, the commands are similar on different clouds, including Azure and Digital Ocean, AWS.

Step 1: Log in your Bunnyshell account (cloud.bunnyshell.com) and open the Dashboard.

On the left side of the page you will see the main menu where you can find environments (you can see the environment as projects in your business e.g tracking, production), package bundles (a package contains apps that are already configured and ready to use), and one-click apps (apps like Jorani, Jenkins, WordPress a which are ready to deploy).

Step 2: Go to RESOURCES and select One Click Apps

Step 3: Here you will find a variety of apps that you can deploy on your cloud. If you can’t find the app you are looking for, you can use the search bar located on top of the apps. When you found the app you need, click on it.

Step 4: Press “Launch in Cloud” button:

Step 5: Give the app a name, and choose: the location of the server, a virtual network, and the server size.

Step 6: Next, you need to look at the bottom of the page. There you will find the application secrets that you have to complete.

Step 7: Once you are done, all you have to do is to click on DEPLOY. Then you will be redirected to a page where you can see that Discourse is deploying. You can click on View logs to see how the app is deployed.

Your job here is done. You can now focus on creating the best forum for your visitor. Give yourself some time to learn how to use all of the functionalities of Discourse.

See? You can easily deploy Discourse in Cloud with Bunnyshell!

How to use Docker with Bunnyshell

Bunnyshell — Thu, 07 May 2020 10:50:29 +0000

Docker is the most popular file format for Linux-based container development and deployments. If you’re using containers, you’re most likely familiar with the container-specific toolset of Docker tools, that enable you to create and deploy container images to a cloud-based container hosting environment.

This can work great for brand-new environments, but it can be a challenge to mix container tooling with the systems and tools you need to manage your traditional IT environments. And, if you’re deploying your containers locally, you still need to manage the underlying infrastructure and environment.

Bunnyshell allows you to automate Docker in your environment, enabling you to operationalize your Docker container build and deployment process in ways that you’re likely doing manually today, or not doing at all.

Using the provisioning configuration, Docker can be installed and configured as needed. First, let’s dive into provisioning for a moment, to better understand how it works with Bunnyshell.

Provisioning refers to bringing a server in a desired state. Some resources handled by provisioning are:

Packages that should be installed and configured in a certain manner
Services that should be running and enabled at boot
Users and Groups
Crons and Log rotates
File system components

The provisioning can be done using two mechanisms:

1. Use supported Bunnyshell packages

The advantage of using these packages is that configuration and updates are easy to handle, with one-click install.

2. Use Bunnyconfig

This method can be used for all other provisioning resources which are not natively supported in Bunnyshell.

In order to provision your servers with Docker, you would do that through Bunnyconfig.

Next, let’s see how you can deploy a Docker image. Before, let’s take a look at how deployments work in Bunnyshell.

Bunnyshell supports multiple applications on a single server each application having its own:

Source
Secrets
Deploy steps

Source

The application source can be from Git or archives. You can also use the deploy steps described below to get the application source. Furthermore, an application can have no source and contain only deploy step configurations.

Secrets

Application secrets are sensitive data which needs to be accessible by the application. We store these secrets in an encryption service and allow the application to get its own secrets at deployment time.

Deploy steps

There are three steps which are being executed when initiating a deployment action:

Exec-Once – Action which is executed only for the first deploy or at demand. This may include:

Global application configuration
Install/Configure application dependencies

Build Actions – Actions which are being executed every time before the application version switch. This may include:

Building, compiling, warmup, etc
Passing application secrets in required locations: config file, web server configs
Creating symlinks to other application components

Post Deploy Actions – Actions which are being executed after the application version switch. This may include:

Restarting a service for example a web server

Using Docker

Bunnyshell can be adapted to easily deploy docker application.

Using the provisioning configuration, Docker can be installed and configured as needed.

For deploying the application you can do this in a number of ways.

The way you construct/maintain infrastructure depends on the application business logic and on project constraints. For example:

All containers run a different application which has to be maintained
All containers run the same application, same configuration
A batch of containers runs the same application, others don’t
Container configuration must be changed or not on application deploy
Application deploy in parallel on all containers or not (in case all containers contain the same application, same configuration)

Assuming Docker is installed on one server and on that server will run all containers (created with docker-compose for example), being on one server you can only make all at once deployment for any defined environment application.

Docker & Bunnyshell usecases:

Docker-compose + 2 containers + same application/configuration on all containers

Let’s take this example. First steps will be to create a new environment of type single (only one server needed to run docker)

Go to Environments -> New Environment

Next step is to create docker configuration on a server.

To do this, we use the concept of Application. An application is an entity which can be installed on a server. The Application can contain source code (can import from git/gitlab existing repository) or can be empty.

When can the application be empty? Well, the reason we are discussing this is because an application means more than just a source code, it means commands which can be executed and configured using Bunnyconfig. Imagine you just need some commands to update server configuration, for this you don’t need any source code, just a way to run some commands.

Go to Environment -> Application -> New Application. Create a new one:

Note

Also, the application can have a git source where the “docker compose” file is versioned.

Use Bunnyconfig Build Actions to build the images. At this step you can also add application secrets to the configuration file in order to include them in the image.

Use Bunnyconfig Build Actions to run the new image.

You will be redirect to application page, go to Deploy Actions

All commands which have to run only once (on first deploy action of the application) should be configured with Bunnyconfig on Exec-Once Actions. Here you can add docker specific boot commands like:

Get Docker image from registry
Create docker-compose file on server
Run “docker-compose up -d” to start containers

All commands which have to run each time a deploy action is triggered should be configured in Bunnyconfig on Build Actions. You can use this section to stop docker before build by implementing command “docker-compose stop”, for example.

All commands which have to run on Post Deploy Event, should be configured in Bunnyconfig on Post Deploy Actions. You use this section to start docker after deploy by implementing command “docker-compose up -d”.
Now, let’s presume you have created an environment with an application used to manage Docker.

How can we maintain the code executed into containers?

The applications installed on all containers should have a hard/soft file system link on main server (path to the application). For simplicity we’ll consider 2 docker containers with two different applications.

Container 1 will run application 1, Container 2 will run application 2.

Application 1 has a path /var/www/app_1, Application 2 has path /var/www/app_2.

Go to Environment -> Applications -> New Application and create new application (git type). Do this for application 1 and application 2.

After all applications were created, configure deploy steps (exec once, build actions, post build actions) for both applications.

Go to Environment -> Applications -> Application 1 to deploy application 1.

Go to Environment -> Applications -> Application 2 to deploy application 2.

Container 1 will run application 1, Container 2 will run application 1.

In this case, both containers runs the same application. You can use a shared folder between containers to update the same source code for both of them using one application configured.

Wrap up

In conclusion, regardless of your scenario, whether you have a simple architecture or a complex one (with load balancers, clusters or hundreds of servers, docker, etc), Bunnyshell helps you create and maintain your entire devops pipeline: from creating servers, provisioning, application deployments, monitoring or ops management.

#DevsTogether – How devs are working to help fight COVID-19

Bunnyshell — Mon, 27 Apr 2020 10:41:50 +0000

These last few weeks, it seems like the physical world has been replaced by the virtual.

As more and more changes take place in how people live and work around the world, the Cloud is a mighty force against the coronavirus pandemic.

Over time more companies have given their employees the right to work from home. That’s led to an increase in demand and usage of Cloud services and collaboration tools. It’s also led these companies to put out freemium offers meant to attract even more users.

Take Microsoft for example, who’s offering its Office 365 free for 6 months, following an announcement of a 775% increase in demand for its cloud services in regions enforcing social distancing and/or shelter-in place.

The unprecedented demand has also led to outages. Just this month a Google Cloud outage caused failures at Gmail, Snapchat and the smart home company Nest, among other services.

From the fast adaptation to working from home to businesses that have found themselves needing to migrate to Cloud overnight, these daily life changes are showing up in patterns of Cloud use around the world. Luckily, its most faithful developers have stepped up to the challenge.

We’ve put together a list of some of the most impactful initiatives where devs have contributed in the fight against COVID-19.

Are you a dev looking to make your own contribution? We’ve also made sure to include a few freemium resources at the end for you that can get you started in the fight against COVID-19.

  ## Table Of Contents

    * How devs are helping in the fight against COVID-19

    * Freemium Dev Resources to fight COVID-19

    * How has the Coronavirus pandemic impacted the Cloud?

    * How Cloud Automation can help

How devs are helping in the fight against COVID-19

Bunnyshell offers free migration to Cloud

Bunnyshell, a SaaS platform that simplifies the usage of Cloud infrastructure, is migrating companies affected by COVID-19 to cloud for free.

The platform helps companies by automating repetitive cloud tasks, from coding to production to maximize applications performance, speed and uptime with essential auto-scaling functions.

For all the SME that have been economically affected by the virus and for the Medical, NGOs and Educational companies that are active in finding a solution to the COVID-19 virus bunnyshell aid their recovery and evolution with free cloud migration.

IBM’s 2020 Call for Code

The tech giant has expanded the 2020 Call for Code Global Challenge to take on COVID-19. Developers and problem solvers are encouraged to submit their open source solutions by April 27th for early deployment and to make an immediate and lasting impact.

AWS initiative

A global initiative to accelerate COVID-19 diagnostics, research, and testing with Amazon Web Services committing $20 million for customers working on diagnostics solutions.

Apple & Google tracking tool

Apple and Google’s engineering teams have banded together to create a decentralized contact tracing tool that will help individuals determine whether they have been exposed to someone with COVID-19.

Codevid-19 – Dev Hackaton against COVID-19

The world’s first pandemic hackathon. Projects compete in four problem areas:

Supporting Crisis Response
Understanding The Pandemic
Social Distancing & Isolation
Scarcity & The Economy

U.S. Digital Response

A volunteer tech industry veteran run initiative that’s helping governments find technology, communications, and operations volunteers.

Synology offers VPN Plus Licenses for Free

Starting from April 6, Synology VPN Plus licenses will become free to purchase until September 30, 2020.

HPE Aruba provides network help to floating hospital in Italy

Aruba, a Hewlett Packard Enterprise company, has installed network infrastructure on the GNV Splendid, a passenger ferry that has been turned into a floating hospital to help fight the COVID-19 pandemic.

COVID-19 Open-Source Help Desk

Expert users, developers, maintainers and community leaders of major open source scientific computing software packages used across scientific fields offering virologists, epidemiologists, or researchers working on a cure that make use of open-source scientific computing software to help them use their time most effectively.

FOSS Responders

A community looking to help those that COVID-19 is impacting, in the open source industry. Help may come in many forms such as advice on how to cancel and negotiate your event contracts, how to manage digital events, and individual or organizational financial support.

Open GitHub collaboration on COVID-19

Devs collaborating on some of the most impactful open source projects for tracking, understanding, and responding to COVID-19.

The COVID Tracking Project

A project launched out of The Atlantic to fill a major gap in publicly available COVID-19 testing data, that collects and publishes the most complete testing data available for US states and territories.

COVID-19 Italia – Monitoraggio situazione

Italians have open sourced their COVID-19 data, providing a dashboard that tracks infections in real-time.

CoronaTracker

The app for iOS & macOS includes maps and charts, using the latest data available. It updates automatically to reflect current changes and provides two levels of detail for tracking countries or the state of individual cities.

Folding@Home

Devs are lending their computing power to the cause. Folding@Home provides software that runs on the computer in the background. It is available for Windows, macOS, and 64bit and 32bit Linux. All data is then made available to the public.

CORD-19 Search

Verizon Media (formerly Yahoo) is giving its new Vespa search engine a chance to show what it can do against CORD-19, the collection of scholarly articles about COVID-19. The company is inviting the public to try using Vespa against the data set.

Freemium Dev Resources to fight COVID-19

GitHub – Free for COVID

A collection of tools and software provided for free for those contributing to alleviating the COVID-19 pandemic.

GitHub – Remote Work & Study Resources

Free products/services and premium services that offer free plans for schools, companies and individuals affected by the pandemic.

ArcGIS for Developers

A suite of no-cost location services and SDKs that devs developing coronavirus disease COVID-19 apps can use in their solutions.

How has the Coronavirus pandemic impacted the Cloud?

The ways this epidemic has impacted the Cloud and how devs have stood up against COVID-19 offers a clue into what the future might bring. So what does the new normal in Cloud Infrastructure look like?

Migration & Portability – For organizations playing catchup on cloud migration, that are recognizing the unquestionable value that the Cloud delivers.
Resource Consolidation – for infrastructure operators struggling to maintain SRE programs and keep services running under increased load.
Team Productivity – a shift towards automation, which can mask the complexity of infrastructure and empower app developers to create, deploy and manage apps without the headache of dealing with infrastructure.
Increased Agility – the search for an agile framework that not only supports deployment of new services and quickly pivots to new economic and market realities.
Horizontal Scaling – as more and more individuals start working from home and using tools that are cloud native, the need for better apps on faster, more numerous servers has left some businesses looking for scaling solutions.

How Cloud Automation can help

Companies that rely on cloud infrastructure to keep up with their needs have found that the effort to maintain operations during the COVID-19 pandemic puts cloud computing at center stage.

This means facing a “what if” scenario made real that shows the worth of being able to scale up at a moment’s notice with the cloud.

Those running their own infrastructure may hit limits on what they can provide and possibly be forced to turn away customers or see some service degradation. Businesses that have automated scaling solutions in place are more likely to deliver, which is a key value proposition.

Perhaps the most valuable thing about cloud automation is the flexible options it provides in this time of crisis, when companies need solutions they can implement and test quickly.

A vast, never-ending network of cloud-based systems enabled to stay up and running throughout this pandemic, to maintain service thanks to layers of planning and redundancies through automation.

The post #DevsTogether – How devs are working to help fight COVID-19 appeared first on bunnyshell.com

Article source