This is radosgw lab steps I try. I used virtualbox and setup RHEL7 as guestOS.
PS: before you start, please make sure you have all the required ceph repo under your /etc/yum.repo.d/
=================================
Install Ceph Object Gateway
=================================
To run a Ceph Object Storage service, you must install Apache and Ceph Object Gateway daemon on the host that is going to provide the gateway service, i.e, the gateway host.
install apache
=========================
#sudo yum install httpd
configure apache
=========================
1. Open the httpd.conf file:
#sudo vim /etc/httpd/conf/httpd.conf
2. Uncomment #ServerName in the file and add the name of your server. Provide the fully qualified domain name of the server machine (e.g., hostname -f):
ServerName {fqdn}
ServerName ceph-vm13
3. Edit the line Listen 80 in /etc/httpd/conf/httpd.conf with the public IP address of the host that you are configuring as a gateway server. Write Listen {IP ADDRESS}:80 in place of Listen 80.
Listen localhost:80
4. Start httpd service
#sudo service httpd start
Or:
#sudo systemctl start http
install ceph
=========================
#sudo yum install ceph-radosgw
PS:
ceph auth list
make sure keyring name in [] and path is same in ceph.conf
=================================
Configuring Ceph Object Gateway
=================================
Configuring a Ceph Object Gateway requires a running Ceph Storage Cluster, and an Apache web server with the FastCGI module.
The Ceph Object Gateway is a client of the Ceph Storage Cluster. As a
Ceph Storage Cluster client, it requires:
Assumy my hostname is ceph-vm13
Create a User and Keyring
=========================
1. Create a keyring for the gateway. ::
#sudo ceph-authtool --create-keyring /etc/ceph/ceph.client.radosgw.keyring
#sudo chmod +r /etc/ceph/ceph.client.radosgw.keyring
2. Generate a Ceph Object Gateway user name and key for each instance. For exemplary purposes, we will use the name ``gateway`` after ``client.radosgw``::
#sudo ceph-authtool /etc/ceph/ceph.client.radosgw.keyring -n client.radosgw.gateway --gen-key
3 Add capabilities to the key. See `Configuration Reference - Pools`_ for details on the effect of write permissions for the monitor and creating pools. ::
#sudo ceph-authtool -n client.radosgw.gateway --cap osd 'allow rwx' --cap mon 'allow rwx' /etc/ceph/ceph.client.radosgw.keyring
4. Once you have created a keyring and key to enable the Ceph Object Gateway with access to the Ceph Storage Cluster, add the key to your Ceph Storage Cluster.
For example::
#sudo ceph -k /etc/ceph/ceph.client.admin.keyring auth add client.radosgw.gateway -i /etc/ceph/ceph.client.radosgw.keyring
5. Distribute the keyring to the node with the gateway instance. ::
#sudo scp /etc/ceph/ceph.client.radosgw.keyring root@ceph-vm13:/home/cephdeploy
#ssh ceph-vm13
#sudo mv ceph.client.radosgw.keyring /etc/ceph/ceph.client.radosgw.keyring
Create Pools
============
Ceph Object Gateways require Ceph Storage Cluster pools to store specific
gateway data. If the user you created has permissions, the gateway will create the pools automatically. However, you should ensure that you have
set an appropriate default number of placement groups per pool into your Ceph configuration file.
.. note:: Ceph Object Gateways have multiple pools, so don't make the number of PGs too high considering all of the pools assigned to the same CRUSH hierarchy, or performance may suffer.
if you don't you can use this command to create pool, if you did before when you test osd you can skip here
#ceph osd pool create {poolname} {pg-num} {pgp-num} {replicated | erasure} [{erasure-code-profile}] {ruleset-name} {ruleset-number}
Double check your pool
#sudo rados lspools
Add a Gateway Configuration to Ceph
===================================
Add the Ceph Object Gateway configuration to your Ceph Configuration file. The Ceph Object Gateway configuration requires you to identify the Ceph Object Gateway instance. Then, you must specify the host name where you installed the Ceph Object Gateway daemon, a keyring (for use with cephx), the socket path for FastCGI and a log file. For example::
[client.radosgw.{instance-name}]
host = {host-name}
keyring = /etc/ceph/ceph.client.radosgw.keyring
rgw socket path = /var/run/ceph/ceph.radosgw.{instance-name}.fastcgi.sock
log file = /var/log/radosgw/client.radosgw.{instance-name}.log
The ``[client.radosgw.*]`` portion of the gateway instance identifies this portion of the Ceph configuration file as configuring a Ceph Storage Cluster client where the client type is a Ceph Object Gateway (i.e., ``radosgw``). The instance name follows. For example::
[client.radosgw.gateway]
host = ceph-vm13
keyring = /etc/ceph/ceph.client.radosgw.keyring
rgw socket path = /var/run/ceph/ceph.radosgw.gateway.fastcgi.sock
log file = /var/log/radosgw/client.radosgw.gateway.log
.. note:: The ``host`` must be your machine hostname, not the FQDN. Make sure that the name you use for the FastCGI socket is not the same as the one used for the object gateway, which is ``ceph-client.radosgw. instance-name}.asok`` by default. You must use the same name in your S3 FastCGI file too. See `Add a Ceph Object Gateway Script`_ for details.
Redeploy Ceph Configuration
---------------------------
To use ``ceph-deploy`` to push a new copy of the configuration file to the hosts in your cluster, execute the following::
1 ceph-deploy config push {host-name [host-name]...}
#sudo ceph-deploy --overwrite-conf config pull ceph-vm13
#sudo ceph-deploy --overwrite-conf config push ceph-vm13
Add a Ceph Object Gateway Script
================================
Add a ``s3gw.fcgi`` file (use the same name referenced in the first line of ``rgw.conf``). For Debian/Ubuntu distributions, save the file to the ``/var/www`` directory. For CentOS/RHEL distributions, save the file to the``/var/www/html`` directory. Assuming a cluster named ``ceph`` (default), and the user created in previous steps, the contents of the file should include::
#sudo vim /var/www/html/s3gw.fcgi
#!/bin/sh
exec /usr/bin/radosgw -c /etc/ceph/ceph.conf -n client.radosgw.gateway
Ensure that you apply execute permissions to ``s3gw.fcgi``. ::
#sudo chmod +x /var/www/html/s3gw.fcgi
On some distributions, you must also change the ownership to ``apache``. ::
#sudo chown apache:apache /var/www/html/s3gw.fcgi
Create Data Directory
=====================
#sudo mkdir -p /var/lib/ceph/radosgw/ceph-radosgw.gateway
Create a Gateway Configuration
==============================
On the host where you installed the Ceph Object Gateway, create an ``rgw.conf`` file.
For CentOS/RHEL systems, place the
file in the ``/etc/httpd/conf.d`` directory.
------------------------------
sudo vim /etc/httpd/conf.d/rgw.conf
###add###
FastCgiWrapper off
<VirtualHost *:80>
ServerName ceph-vm13
DocumentRoot /var/www/html
ErrorLog /var/log/httpd/rgw_error.log
CustomLog /var/log/httpd/rgw_access.log combined
# LogLevel debug
RewriteEngine On
RewriteRule .* - [E=HTTP_AUTHORIZATION:%{HTTP:Authorization},L]
SetEnv proxy-nokeepalive 1
ProxyPass / fcgi://localhost:9000/
</VirtualHost>
-------------------------------
Adjust Path Ownership/Permissions
=================================
#sudo getenforce
Enforcing
#sudo setenforce 0
#sudo getenforce
Permissive
#sudo chown apache:apache /var/log/httpd
#sudo chown apache:apache /var/run/ceph
#sudo chown apache:apache /etc/httpd/conf.d
Restart Services and Start the Gateway
======================================
On CentOS/RHEL systems, use ``httpd``. For example::
#sudo systemctl restart httpd
Start the Gateway
-----------------
On CentOS/RHEL systems, use ``ceph-radosgw``. For example::
#sudo /etc/init.d/ceph-radosgw start
Thursday, April 9, 2015
Tuesday, April 7, 2015
Storage Performance Evaluation - General Concept
Since my research is kinds of lean on Storage, thus storage performance is always most important topic for me. Most of the storage research, either invent new storage media or H/W or redesign the algorithm to refine the way how data store to fulfill specific purpose.
No matter what's kinds of storage / memory research, the ultimate goal in general is reduce IOPs, response time ( latency ) and improve throughput. Of course there has other measurement from other angles such as power consumption, CPU cycle time ... etc, but as long as we are talking about the storage, can't get rid of below three major measurement indicators.
No matter what's kinds of storage / memory research, the ultimate goal in general is reduce IOPs, response time ( latency ) and improve throughput. Of course there has other measurement from other angles such as power consumption, CPU cycle time ... etc, but as long as we are talking about the storage, can't get rid of below three major measurement indicators.
Before we jump into to explain more detail about these indicators, I would like to give general concept about the disk architecture here. There has three of major as below.
Disk Drive Architecture
1. JBOD ( just a bunch of disks )
2. RAID ( Redundant Array of Inexpensive/Independence Disks )
3. SPAN ( Spanning drive : combine multiple drives into 1 single volume )
All the explanation as below is pretty much against JBOD.
Section 1: Definition
First of all, let's give a general definition of these three indicators.
1. Throughput = data volume / second
The throughput is usually used to describe the max theoretical limit of data transfer, while throughput is used to describe a real-world measurement. For me, throughput is common understandable for general people since it gives in units of size over units of time.
2. IOPs = I/O per second = Input / Output / second
The IOPs usually can be used to figure such as the amount of I/O created by DB, or you might use it when defining the max performance of storage system in AB test.
3. Latency ( response time ) = Seconds per I/O = Seconds / ( Input / Output )
Latency appears in conversion magnetic disk regarding the disk header seek time and rotation latency. The basics: every time you need to access a block on a disk drive, the disk actuator arm has to move the head to the correct track (the seek time), then the disk platter has to rotate to locate the correct sector (the rotational latency).
Section 2: Relationship
Second, let's talk about the relationship between these indicators.
a. Throughput = IOPs * I/O size (average block size)
This is my personal interpret and feel free to share your comment with me. Like we described above , throughput = data volume / second and IOPs is (I/O: input / ouput) / second, plus we know the average block size, thus we can get throughput = IOPs * average block size. eg: IOPs = 1000 and Average Block Size = 4K then throughput = 4000K.
b. IOPs = Per Second ( 1 second ) / Latency ( head seek time + rotation latency )
In conversion disk, latency is a common indicator for performance measurement. That I/O per second which usually includes the seek time and rotational latency. eg: the average rotation latency of a 15k RPM disk is 4ms(15,000 rotations per minute = 250 rotations per second, which means one rotation is 1/250th of a second or 4ms). and we can assume 1ms latency form disk header seeking time and total is 4+1 = 5ms. The physical limit of this disk on each spindle per second is 1/(5/1000) = 200 IOPs.
Section 3: Penalty
Follow up with latency, I would say it would be like penalty in conversion disk nowadays especially when random transaction (read / write) vs sequential happen.
Let me use the most common question people ask : Why IOPs is costy on convention HDD ? It's because sequential vs random. In the real world, Magnetic Disk ( Convention HDD ) cost when do the random read/write since the head seek and rotation latency but in sequential read/read, disk head move basically free, doesn't cost head seek time and limit disk rotation because the data section is right behind each I/O.
Let's say if HDD RPM is 7200, random read/write slow down the performance since disk header and sector spin move a lot. Thus, IOPs is costy when you are on Convention HDD. Another example is when you read/write large file the latency cost less since they are one after one in sequential rather than small fraction files might cost more latency in that has higher IOPs since disk need to move a lot.
In sum, if that next block is somewhere else on the disk, you will need to incur the same penalties of seek time and rotational latency. We call this type of operation a random I/O. But if the next block happened to be located directly after the previous one on the same track, the disk head would encounter it immediately afterwards, incurring no wait time (i.e. no latency). This, of course, is a sequential I/O.
That I/O results in a certain amount of latency, as described earlier on (the seek time and rotational latency).
Section 4: Flash Offers Another Way
The idea of sequential I/O doesn't exist with flash memory, because there is no physical concept of blocks being adjacent or contiguous. Logically, two blocks may have consecutive block addresses, but this has no bearing on where the actual information is electronically stored. "You might therefore say that all flash I/O is random, but in truth the principles of random I/O versus sequential I/O are disk concepts so don't really apply". And since the latency of flash is sub-millisecond, it should be possible to see that, even for a single-threaded process, a much larger number of IOPs is possible. When we start considering "concurrent operations things" or "in-line deduplication" get even more interesting… but that topic is for another day.
This sector (Flash Offer Another Way) is most reference by (http://www.violin-memory.com/blog/understanding-io-random-vs-sequential/)
Section 5: Tools
There has lots of storage performance tools on market either it's open or needs licensing. Here I would like to introduce three of major that I am familiar with. Hopefully it helps you jump into storage domain quick and get through above indicators easier.
Linux DD
Linux DD is a default and common tool which is used for storage performance testing. dd can be used for simplified copying of data at the low level. In doing this, device files are often access directly. Since additional queries do not arrive while the device is being accessed, erroneous usage of dd can quickly lead to data loss. I absolutely recommend performing the steps described below on test systems. If dd is used incorrectly, data loss will be the result.
fio
fio is an I/O tool meant to be used both for benchmark and stress/hardware verification. It has support for 19 different types of I/O engines (sync, mmap, libaio, posixaio, SG v3, splice, null, network, syslet, guasi, solarisaio, and more), I/O priorities (for newer Linux kernels), rate I/O, forked or threaded jobs, and much more. It can work on block devices as well as files. fio accepts job descriptions in a simple-to-understand text format. Several example job files are included. fio displays all sorts of I/O performance information, including complete IO latencies and percentiles. fio is in wide use in many places, for both benchmarking, QA, and verification purposes. It supports Linux, FreeBSD, NetBSD, OpenBSD, OS X, OpenSolaris, AIX, HP-UX, Android, and Windows.
vdbench
Vdbench is a command line utility specifically created to help engineers and customers generate disk I/O workloads to be used for validating storage performance and storage data integrity. Vdbench execution parameters may also specified via an input text file. It's a intersting tool and get rid of lots of setup but require to read through the guide since all the configuration is exist in parmfile. It can be combined with Oracle swat, however as my understanding the swat is in oracle licensing and not open.
In sum, I would like to demo how to install and use these tools, however I would think it might need another posting. If you are interesting in, stay tune, I will put it on my blog later.
Reference:
Movie Quote:
A smile doesn't always show that you're happy; sometimes, it shows that you are strong.
- (Jerry Maguire), 1996
Sunday, February 8, 2015
Docker POC Lab Ubuntu 14.04 via VirtualBox
I heard about Docker when I was in Puppet Conf 2014. There has a session to talk about Docker and Puppet corporation. I know there has application visualization when I was doing VM image deduplication but was surprise it came out to the market early and turns out very popular. I would like to share the Docker Proof of Concept Lab I built base Ubuntu VM via VirtualBox. It actually shows how easy to make DevOps adopt CI/CI concept. Here, I list the major sections for my blog and hope you would enjoy it.
Outline
- 1. What's Docker.
- 2. Installation
- 3. Permission
- 4. Docker Commands
- 5. More Run Commands
- 6. Build Docker Image
1. What's Docker
Docker is an open-source that makes creating and managing Linux containers. Here is standard statement from Docker - Docker is an open platform for developers and sysadmins to build, ship, and run distributed applications. Consisting of Docker Engine, a portable, lightweight runtime and packaging tool, and Docker Hub, a cloud service for sharing applications and automating workflows, Docker enables apps to be quickly assembled from components and eliminates the friction between development, QA, and production environments. As a result, IT can ship faster and run the same app, unchanged, on laptops, data center VMs, and any cloud. I reference the docker explanation for the people has familiar VM already. I think it's easier to get you get the point !.
What's linux container ?
Containers are like extremely lightweight VM(Virtual Machines)s - they allow code to run in isolation from other containers but safely share the machine resources, all without the overhead of a hypervisor.
Linux Containers (LXC)
LXC combines "cgroups" and "namespace" support to provide an isolated environment for applications. Docker can also use LXC as one of its execution drivers, enabling image management and providing deployment services.
Docker Registry
DOCKER REGISTRY - REPOSITORIES OF DOCKER IMAGES - We need to have a disk image to make the virtualization work. The disk image represents the system we're running on. Docker registry is a registry of already existing images that we can use to run and create containerized applications.
Why setup via Ubuntu first ?
Ubuntu Trusty comes with a 3.13.0 Linux kernel, and a docker.io package which installs Docker 0.9.1 and all its prerequisites from Ubuntu's repository.
Ubuntu (and Debian) contain a much older KDE3/GNOME2 package called docker, so the package and the executable are called docker.io.
2. Installation
Generally, the way I try is follow the instruction (https://docs.docker.com/installation/ubuntulinux/), it downloads the package lists from the repositories and "updates" them to get information on the newest versions of packages and their dependencies by synchronizing the package index files fetched from /etc/apt/sources.list.
preparation
#sudo apt-get update
#sudo apt-get install docker.io
To make the shell easier to use, we need to create a soft link since /usr/local/bin is for normal user programs not managed by the distribution package manager. The following command overwrites the link (/usr/local/bin/docker):
#sudo ln -sf /usr/bin/docker.io /usr/local/bin/docker
To enable tab-completion of Docker commands in BASH, either restart BASH or:
#source /etc/bash_completion.d/docker.io
check docker process and docker version
#ps aux | grep docker
#docker -v
#sudo docker.io version
install the latest version
To install the latest version, we need to add the Docker repository key to our local keychain:
#sudo apt-key adv --keyserver hkp://keyserver.ubuntu.com:80 --recv-keys 36A1D7869245C8950F966E92D8576A8BA88D21E9
Add the Docker repository to our apt sources list:
#sudo sh -c "echo deb http://get.docker.io/ubuntu docker main > /etc/apt/sources.list.d/docker.list"
check
#cat /etc/apt/sources.list.d/docker.list
Then, update and install the lxc-docker package:
#sudo apt-get update
install
#sudo apt-get install lxc-docker
check docker version and info again, now you see it is 1.4.1
#sudo docker -v
#sudo docker info
To verify that everything has worked as expected, we can check if Docker downloads the ubuntu image, and then start bash in a container:
#sudo docker run -i -t ubuntu /bin/bash
or
#sudo docker run -it ubuntu /bin/bash
you will find you login docker latest image via root
log out
#exit
We were able to start bash in a container. And we can check if the image for ubuntu is there:
#sudo docker images
3. Permission
permission or you actually can't find docker with error message.
check docker group first
#cat /etc/group
add user to docker group
#sudo gpasswd -a devdocker docker
Restart the Docker daemon:
#sudo service docker restart
log out and log in
#exit
***PS docker need to run root w/o required sudo cli***
4. Docker Commands
If you are starter, you can just type docker and it will list all the commands for you, or you can go docker site to study those commands. (https://docs.docker.com/reference/commandline/cli/)
#docker
docker search
#docker search --help
#docker search -s 10 jenkins
We got too many outputs, so we need to filter it out items with more than 10 stars:
#docker search -s 10 tomcat
docker pull
The pull command will go up to the web site and grab the image and download it to our local machine.
#docker pull --help
#docker pull ubuntu
docker images
Check what Docker images are available on our machine, we use docker images:
#docker images
Try download centOS
#docker pull centos:latest
check again
#docker images
docker rmi ( remove images )
remove image from our local machine via image id
#docker rmi 4986bf8c1536
remove all images
#docker rmi $(docker images -q)
PS: force remove images
[root@xxx ~]# docker images
REPOSITORY TAG IMAGE ID CREATED VIRTUAL SIZE
hello-world latest 0a6ba66e537a 5 months ago 960 B
localhost:5000/myfirstimage latest 0a6ba66e537a 5 months ago 960 B
[root@xxx ~]# docker rmi -f 0a6ba66e537a
Untagged: hello-world:latest
Untagged: localhost:5000/myfirstimage:latest
Deleted: 0a6ba66e537a53a5ea94f7c6a99c534c6adb12e3ed09326d4bf3b38f7c3ba4e7
Deleted: b901d36b6f2fd759c362819c595301ca981622654e7ea8a1aac893fbd2740b4c
docker run
#docker run --help
check current local machine os
#cat /etc/issue
docker run centos - This will create container based upon the image and execute the bin/bash command. Then it will take us into a shell on that machine that can continue to do things:
#docker run -it centos:latest /bin/bash
now you are in the centos bash, log out from your centos
#exit
try busybox - "stripped-down Unix tools in a single executable file" - very tiny linux distribution, it runs in a variety of POSIX environments such as Linux, Android, FreeBSD, etc.
#docker run -it busybox sh
***can't do changing the command that's been executed***
for example echo Johnny Wang via docker run -it
#docker run -it echo 'Johnny Wang'
docker just run echo shell and exit, you see the status via docker ps -a
even you restart it and try to attach it, it will fail since it terminate after run echo command.
***ps if you run -it with the image local doesn't have, it will download image directly***
docker list container - ps
#docker ps
show running container
#docker ps -a
docker restart
we can restart the container via container id
#docker restart 6edc94951379 (container id)
docker attach
we can attach to a running container
#docker attach 6edc94951379 (container id)
docker remove
#docker rm 6edc94951379 (container id)
remove all container
#docker rm $(docker ps -aq)
remove container after run every time run -it --rm ( one time execution )
#docker run -it --rm busybox sh
#docker run -it --rm busybox echo "I will not staying around forever"
PS:don't have any container. By passing in --rm, the container is automatically deleted once the container exited.
docker kill
when you try to run an unstoppable container via docker run -t
#docker run -t busybox sh
you can attach but nothing there, now you would like to stop it.
#docker kill fd18db6a9223 (container id)
5. More Run Command
run -v for share file with local under root
binding a folder in our local machine (/home/k/myDocker) with the folder in Docker container (k) so that they can share files: ***-v /home/k/myDocker:/k busybox***
#docker run -it --rm -v /home/k/myDocker:/k busybox sh
run -p for attach file to run under port
Mapping host with port, using port 80 for nginx via auto assign.
#docker run -d -p 80 nginx
You can check the auto-mapping port via docker with ps -a command.
Then check the web app via browser.
run under specific port by request
#docker run -p 8099:80 -d nginx
Check web app via specific ports
run -e for run with environment variant
run -e DOCK_VAR=devdocker
#docker run -it --rm -e DOCK_VAR=devdocker busybox sh
5. Build Docker Images - mangoDB demo
There has two basic way to build your own Docker image. One is download image from docker forge and run image as container, then you can do the customization regarding your container then either you upload back to docker forge or you store it in your repository. The demo above has show the download and run container.
Another one is using dockerfile as scripting to customize your docker image automatically.
docker run build
Each Dockerfile is a script, composed of various commands (instructions) and arguments listed successively to automatically perform actions on a base image in order to create (or form) a new one. Dockerfiles begin with defining an image FROM which the build process starts. Here is the basic command.
#vim Dockerfile
#cat Dockerfile
FROM ubuntu
#docker build -t (Dockerfile) .
***watch out "." at the end.***
For me, Dockerfile is more like scripting for build an image, it is similar concept like some DSL. There are various other methods, commands and arguments (or conditions), in return, provide a new image which is to be used for creating docker containers. The scripting detail you can find in this link. (https://docs.docker.com/reference/builder/)
Here I would like to show a demo to use dockerfile to build a mangoDB automatically. I actually follow the steps on this site to simulate the process. (https://www.digitalocean.com/community/tutorials/docker-explained-using-dockerfiles-to-automate-building-of-images)
First of all, you need to prepare a Dockerfile for mangoDB. The copy you can find from above link.
#sudo vim Dockerfile
#docker build -t my_mongodb .
#docker run -name my_first_mdb_instance -i -t my_mongodb
if you would like to re-use the image, you can restart the image again and assign another container name for it.
Check image id
#docker ps -a
Restart image
#docker restart 46fd9933236d
Run another container
#docker run -name my_second_mdb_instance -i -t my_mongodb
PS: Even Docker fully leverage linux container, however Docker can still be running on Windows as long as leverage VM. Here has link from standard docker doc site (https://docs.docker.com/installation/windows/)
Last, I must share this funny pic with you. This is the best picture to describe what's Docker can do. Look the last one, Leo's face is so confusing !
Why use docker ( container )
Application-centric management:
Raises the level of abstraction from running an OS on virtual hardware to running an application on a virtual OS
The simplicity of PaaS with the flexibility of IaaS
Dev and Ops separation of concerns:
Provides separation of build and deployment
Decoupling applications from infrastructure
Agile application creation and deployment:
Increased ease and efficiency of container image creation compared to VM image use
Continuous development, integration, and deployment:
Facilitates reliable/frequent container image build/deployment with quick and easy rollbacks
Image immutability
Loosely coupled, distributed, elastic, liberated micro-services:
Applications are broken into smaller, independent pieces
Can be deployed and managed dynamically
Not a fat monolithic stack running on one big single-purpose machine
Environmental consistency across development, testing, and production: Runs the same on a laptop as it does in the cloud
Cloud and OS distribution portability:
Distros: Ubuntu, RHEL, SUSE, …
Clouds: AWS, Google Container Engine, Azure, Rackspace, …
Resource isolation:
Predictable application performance
Efficient resource utilization:
High efficiency and density
Movie Quote:
No body know where will we go, just follow the your instinct.
Cobb: You're waiting for a train. A train that'll take you far away. You know where you hope this train will take you. But you can't know for sure. Yet it doesn't matter. Now, tell me why?Mal: Because you'll be together! - (Inception) 2010
You dream always awaits you. It's up to you to decide when you'll go for it. - (Chef), 2014
Subscribe to:
Posts (Atom)

































