{"id":1340,"date":"2019-02-17T09:30:43","date_gmt":"2019-02-17T09:30:43","guid":{"rendered":"https:\/\/www.appservgrid.com\/paw93\/?p=1340"},"modified":"2019-03-07T17:16:28","modified_gmt":"2019-03-07T17:16:28","slug":"magento-and-docker-magento-deployment","status":"publish","type":"post","link":"https:\/\/www.appservgrid.com\/paw93\/index.php\/2019\/02\/17\/magento-and-docker-magento-deployment\/","title":{"rendered":"Magento and Docker | Magento Deployment"},"content":{"rendered":"

\"magento-logo2\"<\/a>A
\nlittle over a month ago I wrote
\nabout<\/a>
\nsetting up a Magento cluster on Docker using Rancher. At the I
\nidentified some short comings of Rancher such as its lack of support fot
\nload-balancing. Rancher released support for load
\nbalancing<\/a> and docker
\nmachine<\/a> with
\n0.16, and I would like to revisit our Magento deployment to cover the
\nuse of load balancers for scalability as well as availability.
\nFurthermore, I would also like to cover how the docker machine
\nintegration makes it easier to launch Rancher compute nodes directly
\nfrom the Rancher UI.<\/p>\n

Amazon Setup<\/h3>\n

As before we will be running our cluster on top of AWS hence if you have
\nnot already done so follow the steps outlined in the Amazon Environment
\nSetup<\/em> section of the earlier tutorial to setup an ssh key pair and a
\nsecurity group. However, unlike earlier we will be using the Rancher UI
\nto launch compute nodes and will require an Access Key ID<\/em> and Secret
\nAccess Key<\/em>. To create your key and secret click through to the IAM<\/em>
\nservice and select Users<\/em> from the menu on the left. Click the Create
\nUser<\/em> button and specify rancher<\/em> as the user name in the subsequent
\nscreen and click Create<\/em>. You will be given the Access Key ID and
\nSecret Access Key in the dialogue shown below, keep the information safe
\nas there is no way to recover the secret and you will need this later.<\/p>\n

\"iam-key\"<\/a>Once
\nyou have created the IAM user you will also need to give it permissions
\nto create Amazon Ec2 Instances. To do so select rancher from the user
\nlist and click Attach Policy<\/em> in the Managed Policies<\/em> section.<\/em> Add
\nthe AmazonEC2FullAccess<\/em> policy to the Rancher user so that we are able
\nto create the required resources from the Rancher UI when creating
\ncompute nodes. Full access is a little more permissive tan required
\nhowever, for the sake of brevity we are not creating custom policy.<\/p>\n

\"Screen<\/a><\/p>\n

Rancher Setup<\/h3>\n

After setting up the AWS environment, follow the steps outlined in the
\nRancher Server Launch<\/em> section of the earlier Magento
\ntutorial<\/a>
\nto bring up your Rancher server and browse to
\nhttp:\/\/RANCHER_SERVER_IP:8080\/<\/a>. *Be sure you are using a version of
\nRancher after 0.16.* Load the Hosts<\/em> tab using the respective option
\nin the left-side menu and click + Add Host<\/em> to add rancher compute
\nnodes. The first time you launch a compute node you will be prompted to
\nconfirm the IP address at which Rancher server is available to your
\ncompute nodes. Specify the Private IP address of the Amazon node on
\nwhich Rancher server is running and hit save.<\/p>\n

\"Screen-Shot-2015-04-27-at-9.30.14-PM\"<\/a><\/p>\n

In the Add Host<\/em> screen select the Amzon EC2 Icon and specify the
\nrequired information in order to launch a compute node. The required
\ninformation is shown below. Enter the access key and secret key that you
\ncreated earlier for the rancher IAM user. We are using a t2.micro
\ninstance for our tutorial however you would probably use a larger
\ninstance for your nodes. Select the same VPC as your Rancher server
\ninstance and specify Rancher<\/em> as the security group to match the
\nsecurity group that you created earlier in the Environment Setup
\nsection. The compute nodes must be launched in a different availability
\nzone from the rancher server hence we select Zone c (Our Rancher Server
\nwas in Zone a) . This requirement is due to the fact that Docker Machine
\nuses the Public IP of compute agents to ssh into them from the Server.
\nHowever, a nodes public IP is not addressable from within its own
\nsubnet.<\/p>\n

\"machine\"<\/a><\/p>\n

Repeat the steps above to launch five compute nodes; one for the MySQL
\ndatabase, two for the load-balanced Magento nodes and two for the load
\nbalancers themselves. I have labeled the nodes as DataNode, Magento1,
\nMagento2, LB1 and LB2. When all nodes come up you should be able to see
\nthem in the Rancher Server UI as shown below.<\/p>\n

\"Screen-Shot-2015-04-27-at-10.45.09-PM\"<\/a><\/p>\n

Magento Container Setup<\/h3>\n

Now that we have our Rancher deployment launched we can setup our
\nMagento containers. However before we launch our Magento containers we
\nmust first launch a MySQL container to serve as our database and
\nMemcached containers for caching. Let\u2019s launch our MySQL container first
\non one of the compute nodes. We do this by clicking the + Add
\nContainer<\/em> on the DataNode host. In the pop up menu we need to specify a
\nname for our container and mysql<\/em> as the source image. Select Advanced
\nOptions > Command<\/em> > Environment Vars +<\/em> to add the four required
\nvariables: mysql root password, mysql user, mysql password, and mysql
\ndatabase. You may choose any values for these the root password and user
\npassword, however, the mysql user and database must be magento. After
\nadding all of these environment variables, hit create to create the
\ncontainer. Note that mysql is official Docker mysql image and details
\nof what is inside this container can be found on
\nits dockerhub<\/a> page.<\/p>\n

\"envvars.png\"<\/a><\/p>\n

Next we will create the Memcached containers on the two magento compute
\nnodes, one on each of the Magento nodes. We again give the containers a
\nname (memcached1 and memcached2) and specify their source images
\nas memcached.<\/em> The Memcached containers do not require any further
\nconfiguration and therefore we can just click create to setup the
\ncontainers. Details of the memcached official container we use can be
\nfound on
\nits dockerhub<\/a> page.<\/p>\n

Now we are ready to create the magento containers, On the Magento1 host
\ncreate a container named magento1<\/em> using the image
\nusman\/magento:multinode<\/a>.
\nYou need to specify the MYSQL_HOST<\/em> and MEMCACHED_HOST<\/em> environment
\nvariables using the container IPs that are listed in the Rancher UI.
\nNote that for Magento1 you should specify the IP of Memcached1.
\nSimilarly launch a second container called magento2 on the Magento2 host
\nand specify the mysql host and memcached host environment variables. In
\na few moments both your magento hosts should be up and ready. Note that
\nunlike before we did not have to link the mysql and memcached containers
\nto our magento containers. This is because Rancher now gives all
\ncontainers access to each other over a Virtual Private Network (VPN)
\nwithout the need for exposing ports or linking containers. Furthermore
\nwe will not need to expose ports on the Magento containers as we will
\nuse the same VPN to allow the load balancers to communicate with our
\nnodes.<\/p>\n

Load balancer Setup<\/h3>\n

Now that your containers are up we can setup load balancers to split
\ntraffic onto the Magento containers. Select the Balancing<\/em> tab in the
\nleft side menu then click Balancers<\/em> and + Add Load Balancer<\/em>. In the
\nsubsequent screen you can specify a name and description for your load
\nbalancer. Next you can select the hosts on which to run balancer
\ncontainers run. in our case we can select both LB1 and LB2. We then need
\nto select the two Magento containers as targets. In the Listening
\nPorts<\/em> section we need to specify that our Magento containers are
\nlistening for HTTP traffic on port 80 and that we want load balancers to
\nalso listen to http traffic on port 80.<\/p>\n

\"Screen<\/a><\/h3>\n

Lastly, click on the Health Check<\/em> tab and specify that the load
\nbalancers should send a GET<\/em> request to the root URI every 2000 ms to
\ncheck that the container is still healthy. If three consecutive health
\nchecks fail then the container will be marked as unhealthy and no
\nfurther traffic will be routed to it until it can respond successfully
\nto two consecutive health checks. In a few moments your load balancers
\nwill be ready and you can load Magento on the public IP of either load
\nbalancer host. You will need to look for the IP in the Amazon EC2
\nconsole as the Rancher UI only shows the private IP of the nodes. Once
\nyou load the Magento UI follow the steps outlined in the previous
\ntutorial to setup your connection the MySQL and to setup a magento
\naccount.<\/p>\n

\"Screen<\/a><\/p>\n

###<\/p>\n

DNS Round-robin Setup using Amazon Route 53<\/h3>\n

Now that we have our load balancers up and running we can split traffic
\nonto our two Magento contianers but we still must send our requests to
\none balancer or the other. To enable routing to both load balancers
\ntransparently we need to setup DNS round-robin. For this you may use any
\nDNS provider of your choice but since we are using Amazon EC2 we will
\nuse Amazon\u2019s Route 53 service. Use the Top menu to select the Route
\n53<\/em> service and select Hosted Zones<\/em> from the left menu. If you don\u2019t
\nalready have a registered domain and hosted zone you may have to create
\none. We are using the rancher-magento.com<\/em> domain and hosted zone. In
\nyour hosted zone click the Create Record Set<\/em> button and specify a
\nsubdomain such as lb.rancher-magento.com<\/em> in the form which loads to
\nthe right of the screen*. S*elect type A – IPv4 address<\/em> and specify
\nthe public IP address of one of your load balancer hosts. In the
\nRouting Policy<\/em> section select Weighted<\/em>, and enter 10 as the weight.
\nEnter 1 as the Set ID and click Save Record Set.<\/em> Repeat exactly the
\nsame process once more but use the public IP of the second load-balancer
\nhost. This pair of DNS entries is specifying that we want to route
\nclients who ask for lb.rancher-magento.com<\/em> to the two specified IPs.
\nSince the IPs records have the same weight the traffic will be split
\nevenly between the two load balancers. We can now load up our Magento UI
\nusing http:\/\/lb.rancher-magento.com<\/em> instead of having to specify the
\nIP.<\/p>\n

\"Screen<\/a><\/p>\n

Wrapping up<\/h3>\n

\"rancher-machine\"<\/a><\/h3>\n

Putting it all together we get a cluster setup as shown above. Using the
\nDNS entries our web browsers are directed to one of the load balancers
\nLB1, or LB2. By having two load balancers we have split traffic and
\nhence reduced the load on each of our load balancer instances. The load
\nbalancers will then proxy traffic to either Magento1 or Magento2. This
\nagain allows us to spread the load to the separate containers running on
\ntheir own hosts. We have setup only two Magento containers but your
\ncould setup as many as you need. Furthermore, the health check setup
\nensures that if one of the Magento containers fails the traffic will
\nquickly be diverted to the remaining container without human
\nintervention. Each of the Magento containers has a Memcached server
\nrunning on its own host to provide fast access to frequently used data.
\nHowever, both magento containers use the same MySQL container to ensure
\nconsistency between the two containers. By using Rancher\u2019s docker
\nmachine support we were able to launch all hosts (other than Rancher
\nServer) directly from the Rancher UI. In addition, due to Rancher\u2019s VPN
\nwe did not have to expose ports on any of our containers nor did we have
\nto link containers. This greatly simplifies the Magento container setup
\nlogic. With support for load balancers and machine (as well as docker
\ncompose coming soon), Rancher is becoming a much more viable option for
\nrunning large scale user facing deployments.<\/p>\n

To learn more about Rancher, please join us for one of our monthly
\nonline meetups. You can register for an upcoming meetup by following the
\nlink below.<\/p>\n

Source<\/a><\/p>\n","protected":false},"excerpt":{"rendered":"

A little over a month ago I wrote about setting up a Magento cluster on Docker using Rancher. At the I identified some short comings of Rancher such as its lack of support fot load-balancing. Rancher released support for load balancing and docker machine with 0.16, and I would like to revisit our Magento deployment … <\/p>\n

Continue reading “Magento and Docker | Magento Deployment”<\/span><\/a><\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[3],"tags":[],"class_list":["post-1340","post","type-post","status-publish","format-standard","hentry","category-kubernetes"],"_links":{"self":[{"href":"https:\/\/www.appservgrid.com\/paw93\/index.php\/wp-json\/wp\/v2\/posts\/1340","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.appservgrid.com\/paw93\/index.php\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.appservgrid.com\/paw93\/index.php\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.appservgrid.com\/paw93\/index.php\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/www.appservgrid.com\/paw93\/index.php\/wp-json\/wp\/v2\/comments?post=1340"}],"version-history":[{"count":1,"href":"https:\/\/www.appservgrid.com\/paw93\/index.php\/wp-json\/wp\/v2\/posts\/1340\/revisions"}],"predecessor-version":[{"id":1411,"href":"https:\/\/www.appservgrid.com\/paw93\/index.php\/wp-json\/wp\/v2\/posts\/1340\/revisions\/1411"}],"wp:attachment":[{"href":"https:\/\/www.appservgrid.com\/paw93\/index.php\/wp-json\/wp\/v2\/media?parent=1340"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.appservgrid.com\/paw93\/index.php\/wp-json\/wp\/v2\/categories?post=1340"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.appservgrid.com\/paw93\/index.php\/wp-json\/wp\/v2\/tags?post=1340"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}