Downloaded 12 times
![master:~$export TOKEN=$(docker run --rm swarm create)master:~$docker run -d -p 3375:2375 swarm manage token://$TOKENmaster:~$docker run -d swarm join --addr=<node_1_private_ip:2375> token://$TOKEN node-0:~$docker run -d swarm join --addr=<node_2_private_ip:2375> token://$TOKENstaging$ sudo systemctl enable docker-tcp.socketstaging$ sudo systemctl enable docker.socketstaging$ sudo systemctl stop dockerstaging$ sudo systemctl start docker-tcp.socketstaging$ sudo systemctl start dockerzmaster$ docker -H tcp://0.0.0.0:3375 infostaging$ sudo vi /etc/systemd/system/docker-tcp.socket [Unit]Description=Docker Socket for theAPI [Socket]ListenStream=2375BindIPv6Only=bothService=docker.service[Install]WantedBy=sockets.target/etc/systemd/system/docker-tcp.socket](/image.pl?url=https%3a%2f%2fimage.slidesharecdn.com%2fcontainermicroservices-151127105546-lva1-app6891%2f75%2fContainer-microservices-33-2048.jpg&f=jpg&w=240)
![[DI01] 窓は開かれた! SQL Server on Linux で拡がる可能性](/image.pl?url=https%3a%2f%2fcdn.slidesharecdn.com%2fss_thumbnails%2fdi01-170605023800-thumbnail.jpg%3fwidth%3d640%26amp%3bheight%3d640%26amp%3bfit%3dbounds&f=jpg&w=240)
![[SC02] シチュエーション別 Active Directory デザインパターン](/image.pl?url=https%3a%2f%2fcdn.slidesharecdn.com%2fss_thumbnails%2fsc02-170614044138-thumbnail.jpg%3fwidth%3d640%26amp%3bheight%3d640%26amp%3bfit%3dbounds&f=jpg&w=240)
![[AC07] 米国マイクロソフト本社で体験したノウハウを伝授！マイクロサービス実行基盤Azure Service Fabricの勘所](/image.pl?url=https%3a%2f%2fcdn.slidesharecdn.com%2fss_thumbnails%2fac07-170602093741-thumbnail.jpg%3fwidth%3d640%26amp%3bheight%3d640%26amp%3bfit%3dbounds&f=jpg&w=240)
![[TL04] .NET 15 周年の今こそ考えるクラウドネイティブ アプリケーションと .NET の活用](/image.pl?url=https%3a%2f%2fcdn.slidesharecdn.com%2fss_thumbnails%2ftl04-170614050632-thumbnail.jpg%3fwidth%3d640%26amp%3bheight%3d640%26amp%3bfit%3dbounds&f=jpg&w=240)
![[DO09] 獲れたて OSS x DevOps！自動化三昧を満喫セヨ](/image.pl?url=https%3a%2f%2fcdn.slidesharecdn.com%2fss_thumbnails%2fdo09-170616021522-thumbnail.jpg%3fwidth%3d640%26amp%3bheight%3d640%26amp%3bfit%3dbounds&f=jpg&w=240)
![[TL02] "Shift Left" で問題の早期発見を実現する、最新 Visual Studio の品質チェック・テスト機能の使い方](/image.pl?url=https%3a%2f%2fcdn.slidesharecdn.com%2fss_thumbnails%2ftl02-170614050626-thumbnail.jpg%3fwidth%3d640%26amp%3bheight%3d640%26amp%3bfit%3dbounds&f=jpg&w=240)
![[MW06] PaaS を活用した、ハイコストパフォーマンスなウェブサイト構築・運用・メンテナンス](/image.pl?url=https%3a%2f%2fcdn.slidesharecdn.com%2fss_thumbnails%2fmw06-170614050053-thumbnail.jpg%3fwidth%3d640%26amp%3bheight%3d640%26amp%3bfit%3dbounds&f=jpg&w=240)
Container microservices
- 4.
- 5.BrowserLoadbalancerDatabasehttp://www.slideshare.net/chris.e.richardson/developing-apps-with-a-microservice-architecture-svforum-microservices-meetupDeveloping applications witha microservice architecture / Chris RichardsonStoreFrontUIProductServiceRecommendationServiceReviewServiceOrderService
- 6.BrowserAPIGatewayhttp://www.slideshare.net/chris.e.richardson/developing-apps-with-a-microservice-architecture-svforum-microservices-meetupDeveloping applications witha microservice architecture / Chris RichardsonRESTProductServiceRecommendationServiceReviewServiceOrderServiceRESTRESTRESTWebapplicationDBDBDBDB
- 9.Development Development DevelopmentDevelopment
- 10.Development Development DevelopmentDevelopment
- 11.Development Development DevelopmentDevelopmentOPS
- 12.
- 13.
- 14.
- 17.
- 18.http://blogs.technet.com/b/livedevopsinjapan/archive/2015/11/13/devops-enterprise-2015-2.aspx【DevOps Enterprise 2015参加レポート】第 2 回 – DockerによるDevOpsソフトウェアサプライチェーンの改善
- 20.Docker Machine, CLIfor Windows etc… Docker Engine For Windows
- 22.
- 23.https://azure.microsoft.com/en-us/documentation/articles/xplat-cli-install/https://www.docker.com/docker-toolbox$ git clonehttps://github.com/TsuyoshiUshio/aservice.git$ openssl req -x509 -nodes -days 365 -newkey rsa:1024 -keyout mycert.pem -outmycert.pem $ openssl pkcs12 -export -out mycert.pfx -in mycert.pem -name "MyCertificate”$ openssl x509 -inform pem -in mycert.pem -outform der -out mycert.cer
- 25.$ docker build–t {your DockerHub repository name}/{image name}$ docker run -d hello-world$ docker run –p 80:80 tsuyoshiushio/aservice$ docker login$ docker pushdocker-machine create -d azure --azure-subscription-id=”{Your subscription id}" --azure-subscription-cert=”/path/to/mycert.pem" {prefered-machine-name}
- 28.本番への適用 End toEndセキュリティ
- 30.
- 33.master:~$export TOKEN=$(docker run--rm swarm create)master:~$docker run -d -p 3375:2375 swarm manage token://$TOKENmaster:~$docker run -d swarm join --addr=<node_1_private_ip:2375> token://$TOKEN node-0:~$docker run -d swarm join --addr=<node_2_private_ip:2375> token://$TOKENstaging$ sudo systemctl enable docker-tcp.socketstaging$ sudo systemctl enable docker.socketstaging$ sudo systemctl stop dockerstaging$ sudo systemctl start docker-tcp.socketstaging$ sudo systemctl start dockerzmaster$ docker -H tcp://0.0.0.0:3375 infostaging$ sudo vi /etc/systemd/system/docker-tcp.socket [Unit]Description=Docker Socket for theAPI [Socket]ListenStream=2375BindIPv6Only=bothService=docker.service[Install]WantedBy=sockets.target/etc/systemd/system/docker-tcp.socket
- 34.http://qiita.com/TsuyoshiUshio@github/items/33be6b54a741c5834253Docker Orchestration Toolsのチュートリアル(詳細の手順が書かれています）master $ docker-compose -f production.docker-compose.yml -p dockchat_production pullmaster $ docker-compose -f production.docker-compose.yml -p dockchat_production up -ddocker-compose -f production.docker-compose.yml -p dockchat_production scale web=10dockchat.com/haproxy?statsdockchat.com
- 35.# Mongo DBdb:image:mongoexpose:- 27017command: --smallfilesenvironment:- "constraint:environment==production”# Python Appweb:image: nicolaka/dockchat:v1ports:- "5000”links:- db:dbenvironment:- “constraint:environment==production- INTERLOCK_DATA={"hostname":"dockchat.com","domain":"dockchat.com”}interlock:image: ehazlett/interlock:latestports:- "80:80”volumes:- /var/lib/docker:/etc/dockerenvironment:- "constraint:environment==production”command: "--swarm-url tcp://$DOCKER_HOST --debug --plugin haproxystart"https://github.com/docker/dceu_tutorials/blob/master/2-orchestration.md
- 40.
- 42.
- 43.
- 49.
- 50.
- 51.
- 52.オープン ソース活用でもっと Azureを使い切ろう!https://channel9.msdn.com/Events/FEST/2015/CLD-331https://docs.com/microsoftjapan-/6056/cld-331-azure
- 57.エバンジェリスト牛尾の Live DevOps!(Movie) https://channel9.msdn.com/Blogs/livedevopsinjapanLive DevOps in Japan! (Blog) http://blogs.technet.com/b/livedevopsinjapan/
- 58.DevOpsのマインドセットをマイクロソスフトのエバンジェリストとハッカソンで学ぶ２日間Nov 28th –29th with JJUG CCCDec 9th – 10th @Shibuya dots.Jan 23rd – 24th @OsakaMicrosoft corporationSenior Technical Evangelist forDevOpsMicrosoft 月次イベントDev：http://aka.ms/dx1128-dev Ops：http://aka.ms/dx1128-it
Editor's Notes
- #3 Agenda
- #22 · We've been working with containers for a long time · Out story is an open one · Community defined APIs and tools · We are in the communities contributing to this ecosystem · Linux first as that's what customers want today
- #42 · We've been working with containers for a long time · Out story is an open one · Community defined APIs and tools · We are in the communities contributing to this ecosystem · Linux first as that's what customers want today
- #43 Operations Management Suite is a software-as-a-service offering that allows you to manage Linux and Windows computers in any cloud – AWS, Azure, OpenStack, or VMWare. It has services for log analytics, performance metrics, automation, backup and recovery, and security and compliance. As of a week ago, it now supports Docker containers as well (private preview).
- #44 These are quotes from users we talked with during our research who were using containers in production, about what some of their biggest pain points were. No grand surprise here, but these are what we built – visibility into where your containers and hosts are, including sorting by images and how many containers of specific images are running, as well as tag and versioning information. Log collection, so logs are centralized and searchable, and a slew of perf metrics –memory, cpu, network usage, storage, and many more. Everything is searchable so it’s highly flexible and query-able.
- #45 Please call out the email for people to write us at – it’s mostly because we need to expose the workspace to their free trial, and not everyone can see it.