da Agency

Docker Birthday #4: Thank you Docker Community!

Pақмет сізге, tak, धन्यवाद, cảm ơn bạn, شكرا, mulțumesc, gracias, merci, danke, obrigado, ευχαριστώ, köszönöm, thank you #Docker community! From Des Moines to Santiago de Cuba, Budapest to Tel Aviv and Sydney to Cairo, it was so awesome to see the energy from the community coming together to celebrate and learn about Docker!

We originally planned for 50 Docker Birthday #4 celebrations worldwide with 2,500 attendees. But over 9,000 people registered to attend one of the 152 celebrations across 5 continents! A huge thank you to all the Docker meetup organizers who worked hard to make these celebrations happen and offered Docker beginners the  opportunity to participate in hands on Docker labs.
Join in on the fun!
In case you missed it last week, check out the pics from all of the #DockerBday celebrations including the awesome birthday cakes! Check out the Facebook photo album too! Up for a little more reading? Check out these blog posts from Docker Captains Jonas Rosland and Alex Ellis about their experience mentoring at their local event.
None of this would have been possible without the support (and expertise!) of the 500+ advanced Docker users who signed up as mentors to help attendees learn about Docker by working through the labs we have available.
Here are some of our favorite tweets from the meetups:
 

Huge turnout at @docker #Seattle dockerbday bash! Docker #DockerSeattle pic.twitter.com/cEgGcak2ZR
— Kaslin Fields (@kaslinfields) March 24, 2017

 

Learning and celebrating with @docker 4th Anniversary. We . dockerbday #NScommunity pic.twitter.com/tDoxGnEKCQ
— Nearsoft Jobs (@NearsoftJobs) March 18, 2017

Learn Docker
In case you weren’t able to attend a local event, all the labs are now available to everyone online here: http://birthday.play-with-docker.com/
About play-with-docker
Play-with-docker (PWD) is a site made by Docker captains Marcos Nils and Jonathan Leibiusky. PWD is a Docker playground which allows you to run Docker commands in a matter of seconds. It gives you the experience of having a free Alpine Linux Virtual Machine in your browser, where you can build and run Docker containers and even create clusters in Docker Swarm Mode. Under the hood DIND or Docker-in-Docker is used to give the effect of multiple VMs/PCs.
Share Your Experience
If you were able to attend a local event, please take a moment to let us know how it went. Here is the participant survey and the mentor survey.
Contribute to Docker Labs
The material used for the Bday 4 meetups was pulled from https://github.com/docker/labs and contains Docker labs and tutorials authored by Docker, and by members of the community. We welcome contributions and want that repo to grow. If you have a tutorial to submit, or contributions to existing tutorials, please check out the guide to submitting your own tutorial.
Get involved with the Docker Community:

Sign up for the Docker Community Directory and Slack
Join your local Docker Meetup group
Join the Docker Online Meetup group

The DockerBday labs are now available online! #learndockerClick To Tweet

The post Docker Birthday 4: Thank you Docker Community! appeared first on Docker Blog.
Quelle: https://blog.docker.com/feed/

da Agency

Do You Rinse Your Lemons?

It has recently come to my attention that some people do a completely absurd thing: They rinse lemons before using them. Not just if they’re going to put a slice in a drink, but even if they’re just going to use little juice for say, a salad dressing.

A quick poll of friends and coworkers revealed that people are bitterly divided on this issue. Those who rinse think it’s disgusting that people wouldn’t rinse, and the non-rinsers think it’s a big waste of time.

Well, when life hands me a debate about lemons, I make some phone calls and fix myself a tall glass of sweet, refreshing journalism lemonade.

First, I spoke to Jaydee Hanson, senior policy analyst for the Center for Food Safety, an organization that advocates a variety of agricultural issues, like trying to keep genetically modified apples out of supermarkets and encouraging popcorn producers to use bee-friendly pesticides.

“Yes, lemons definitely should be washed,” Hanson told me. His reasoning was that the rind is chock-full of pesticides that could transfer to the lemon while cutting, or transfer onto your hands while you touch the rind. “In addition to having pesticides on them, they also have antibiotics on them,” Hanson continued. “Most people don’t realize this. The EPA granted emergency use of antibiotics on citrus crops to prevent citrus greening.” Citrus greening is a bacterial disease passed along by bugs that has been plaguing U.S. citrus crops in the last few years.

Hanson admits that the amount of pesticides on a lemon aren’t exactly deadly. “Are you going to die from it? Not unless you’re allergic to the antibiotics.”

Hmm. I know plenty of people who are allergic to antibiotics, and I’ve never heard of anyone ever having a reaction from eating fruit. If this sounds perhaps a little alarmist, you’re not the only one thinking that.

Lemons at the grocery store, touched by who knows how many germy hands.

Katie Notopoulos / BuzzFeed News

Jim Adaskaveg is a professor of plant pathology at University of California, Riverside, who specifically studies post-harvest fruit problems and sanitizing fruit. His career is basically dedicated to whether or not you should rinse a lemon.

To understand if you should rinse a lemon, you first have to understand what rinsing would actually accomplish. Are you really washing off those pesticides and antibiotics? Nope! “Most lemons in a supermarket are processed and treated and ready to be consumed,” Adaskaveg explained. Fruit is washed at a processing plant between the field and the supermarket. After it’s washed, they’re treated with a wax and a safe fungicide to keep them from getting moldy.

And the wax means that any trace amount of pesticide residue is not really getting washed off anyway – at least not be a few seconds of rinsing.

However, Askaveg still is in favor of rinsing. The reason? Germs from whoever touched them at the grocery store: the manager who set up the display, or a customer who test-squeezed a few. Or even you when you touched them before washing your hands. “The pesticides aren’t really dangerous, even though people think they are,” he said. “The risk of any poisoning is astronomically low compared to germs from handling.”

So there you go. Whether you believe the food safety guy or the fruit packing professor about the dangers of potential pesticide residue, they still agree that a rinse is worth it. Most of all, this is terrible news for me, since it means my husband was right. Goddammit.

Quelle: <a href="Do You Rinse Your Lemons?“>BuzzFeed

da Agency

One-click disaster recovery of applications using Azure Site Recovery

Disaster recovery is not only about replicating your virtual machines but also about end to end application recovery that is tested multiple times, error free, and stress free when disaster strikes, which are the Azure Site Recovery promises. If you have never seen your application run in Microsoft Azure, chances are that when a real disaster happens, the virtual machines may just boot, but your business may remain down. The importance and complexity involved in recovering applications was described in the previous blog of this series – Disaster recovery for applications, not just virtual machines using Azure Site Recovery. This blog covers how you can use the Azure Site Recovery construct of recovery plans to failover or migrate applications to Microsoft Azure in the most tested and deterministic way, using an example of recovering a real-world application to the public cloud.  

Why use Azure Site Recovery “recovery plans”?

Recovery plans help you plan for a systematic recovery process by creating small independent units that you can manage. These units will typically represent an application in your environment. Recovery plan not only allows you to define the sequence in which the virtual machines start, but also helps you automate common tasks during recovery.

Essentially, one way to check that you are prepared for disaster recovery is by ensuring that every application of yours is part of a recovery plan and each of the recovery plans is tested for recovery to Microsoft Azure. With this preparedness, you can confidently migrate or failover your complete datacenter to Microsoft Azure.
 
Let us look at the three key value propositions of a recovery plan:

Model an application to capture dependencies
Automate most recovery tasks to reduce RTO
Test failover to be ready for a disaster

Model an application to capture dependencies

A recovery plan is a group of virtual machines generally comprising an application that failover together. Using the recovery plan constructs, you can enhance this group to capture your application-specific properties.
 
Let us take the example of a typical three tier application with

one SQL backend
one middleware
one web frontend

The recovery plan can be customized to ensure that the virtual machines come up in the right order post a failover. The SQL backend should come up first, the middleware should come up next, and the web frontend should come up last. This order makes certain that the application is working by the time the last virtual machine comes up. For example, when the middleware comes up, it will try to connect to the SQL tier, and the recovery plan has ensured that the SQL tier is already running. Frontend servers coming up last also ensures that end users do not connect to the application URL by mistake until all the components are up are running and the application is ready to accept requests. To build these dependencies, you can customize the recovery plan to add groups. Then select a virtual machine and change its group to move it between groups.

 

Once you complete the customization, you can visualize the exact steps of the recovery. Here is the order of steps executed during the failover of a recovery plan:

First there is a shutdown step that attempts to turn off the virtual machines on-premises (except in test failover where the primary site needs to continue to be running)
Next it triggers failover of all the virtual machines of the recovery plan in parallel. The failover step prepares the virtual machines’ disks from replicated data.
Finally the startup groups execute in their order, starting the virtual machines in each group – Group 1 first, then Group 2, and finally Group 3. If there are more than one virtual machines in any group (for example, a load-balanced web frontend) all of them are booted up in parallel.

Sequencing across groups ensures that dependencies between various application tiers are honored and parallelism where appropriate improves the RTO of application recovery.

Automate most recovery tasks to reduce RTO

Recovering large applications can be a complex task. It is also difficult to remember the exact customization steps post failover. Sometimes, it is not you, but someone else who is unaware of the application intricacies, who needs to trigger the failover. Remembering too many manual steps in times of chaos is difficult and error prone. A recovery plan gives you a way to automate the required actions you need to take at every step, by using Microsoft Azure Automation runbooks. With runbooks, you can automate common recovery tasks like the examples given below. For those tasks that cannot be automated, recovery plans also provide you the ability to insert manual actions.

Tasks on the Azure virtual machine post failover – these are required typically so that you can connect to the virtual machine, for example:

Create a public IP on the virtual machine post failover
Assign an NSG to the failed over virtual machine’s NIC
Add a load balancer to an availability set

Tasks inside the virtual machine post failover – these reconfigure the application so that it continues to work correctly in the new environment, for example:

Modify the database connection string inside the virtual machine
Change web server configuration/rules

For many common tasks, you can use a single runbook and pass parameters to it for each recovery plan so that one runbook can serve all your applications. To deploy these scripts yourself and try them out, click the button below and import popular scripts into your Microsoft Azure Automation account.

 
With a complete recovery plan that automates the post recovery tasks using automation runbooks, you can achieve one-click failover and optimize the RTO. 

Test failover to be ready for a disaster

A recovery plan can be used to trigger both a failover or a test failover. You should always complete a test failover on the application before doing a failover. Test failover helps you to check whether the application will come up on the recovery site.  If you have missed something, you can easily trigger cleanup and redo the test failover. Do the test failover multiple times until you know with certainty that the application recovers smoothly.

 

Each application is different and you need to build recovery plans that are customized for each. Also, in this dynamic datacenter world, the applications and their dependencies keep changing. Test failover your applications once a quarter to check that the recovery plan is current.

Real-world example – WordPress disaster recovery solution

Watch a quick video of a two-tier WordPress application failover to Microsoft Azure and see the recovery plan with automation scripts, and its test failover in action using Azure Site Recovery.

The WordPress deployment consists of one MySQL virtual machine and one frontend virtual machine with Apache web server, listening on port 80.
WordPress deployed on the Apache web server is configured to communicate with MySQL via the IP address 10.150.1.40.
Upon test failover, the WordPress configuration needs to be changed to communicate with MySQL on the failover IP address 10.1.6.4. To ensure that MySQL acquires the same IP address every time on failover, we will configure the virtual machine properties to have a preferred IP address set to 10.1.6.4.

With relentless focus on ensuring that you succeed with full application recovery, Azure Site Recovery is the one-stop shop for all your disaster recovery needs. Our mission is to democratize disaster recovery with the power of Microsoft Azure, to enable not just the elite tier-1 applications to have a business continuity plan, but offer a compelling solution that empowers you to set up a working end to end disaster recovery plan for 100% of your organization&#039;s IT applications.

You can check out additional product information and start replicating your workloads to Microsoft Azure using Azure Site Recovery today. You can use the powerful replication capabilities of Azure Site Recovery for 31 days at no charge for every new physical server or virtual machine that you replicate, whether it is running on VMware or Hyper-V. To learn more about Azure Site Recovery, check out our How-To Videos. Visit the Azure Site Recovery forum on MSDN for additional information and to engage with other customers, or use the Azure Site Recovery User Voice to let us know what features you want us to enable next.
Quelle: Azure