From 47019361d3a5e876c70dae27186159c54db680b6 Mon Sep 17 00:00:00 2001 From: Roger Berlind Date: Tue, 11 Apr 2017 16:46:16 -0400 Subject: [PATCH 1/4] Added extra copy of apcera.md since first not linked --- deployment/apcera.md | 20 +++--- microservices-demo/deployment/apcera.md | 90 +++++++++++++++++++++++++ 2 files changed, 100 insertions(+), 10 deletions(-) create mode 100644 microservices-demo/deployment/apcera.md diff --git a/deployment/apcera.md b/deployment/apcera.md index f1a260c..cf18762 100644 --- a/deployment/apcera.md +++ b/deployment/apcera.md @@ -3,15 +3,15 @@ layout: default deployDoc: true --- -## Socks Shop on Apcera +## Sock Shop on Apcera -These instructions will help you deploy and run the Socks Shop application on the [Apcera Platform](https://www.apcera.com/platform), an enterprise-grade container management platform for cloud-native and legacy applications. Apcera is secure by default, only permitting things explicitly authorized by policy, and supports multi-cloud deployments. +These instructions will help you deploy and run the Sock Shop application on the [Apcera Platform](https://www.apcera.com/platform), an enterprise-grade container management platform for cloud-native and legacy applications. Apcera is secure by default, only permitting things explicitly authorized by policy, and supports multi-cloud deployments. -Apcera has tested Socks Shop on the Apcera Community Edition running single-cloud clusters in Amazon AWS, Google Cloud Platform, Microsoft Azure, and VMware. We have also tested Socks Shop on the Apcera Enterprise Edition running a multi-cloud cluster that spanned across AWS, GCP, and VMware. +Apcera has tested Sock Shop on the Apcera Community Edition running single-cloud clusters in Amazon AWS, Google Cloud Platform, Microsoft Azure, and VMware. We have also tested Sock Shop on the Apcera Enterprise Edition running a multi-cloud cluster that spanned across AWS, GCP, and VMware. ### Packaging -The Socks Shop application is packaged and configured for Apcera using a [Multi-Resource Manifest file](https://docs.apcera.com/jobs/multi-resource-manifests/) called socksshop-docker.json which is similar to a Docker Compose file. Scripts are provided to make it easy to deploy all the services and a network from the manifest, to start and stop the services, and to delete everything that was deployed. +The Sock Shop application is packaged and configured for Apcera using a [Multi-Resource Manifest file](https://docs.apcera.com/jobs/multi-resource-manifests/) called socksshop-docker.json which is similar to a Docker Compose file. Scripts are provided to make it easy to deploy all the services and a network from the manifest, to start and stop the services, and to delete everything that was deployed. ### Pre-requisites @@ -23,7 +23,7 @@ The Socks Shop application is packaged and configured for Apcera using a [Multi- git clone https://github.com/microservices-demo/microservices-demo cd microservices-demo/deploy/apcera ``` -- *(Optional)* If you are not an admin user in your Apcera cluster, you might need an Apcera administrator to import a [policy](https://docs.apcera.com/policy/introduction/) file to give you permission to create the Socks Shop services and network in your sandbox. +- *(Optional)* If you are not an admin user in your Apcera cluster, you might need an Apcera administrator to import a [policy](https://docs.apcera.com/policy/introduction/) file to give you permission to create the Sock Shop services and network in your sandbox. ``` apc import policy socksShop.pol @@ -31,11 +31,11 @@ apc import policy socksShop.pol ### Networking and Security -In this demo scenario, we create a single [virtual network](https://docs.apcera.com/jobs/virtual-networks/) to which all the services except *zipkin* and *user-sim* are added. Services inside the virtual network can all talk to each other. Apcera [job links](https://docs.apcera.com/jobs/job-links/) are used to let the *user-sim* load testing service send requests to the *front-end* service and to let the main Socks Shop services send traces to the *zipkin* service. Using job links in this fashion simulates how real, cloud-based load testing and APM solutions can be integrated into applications running on Apcera without sacrificing security. +In this demo scenario, we create a single [virtual network](https://docs.apcera.com/jobs/virtual-networks/) to which all the services except *zipkin* and *user-sim* are added. Services inside the virtual network can all talk to each other. Apcera [job links](https://docs.apcera.com/jobs/job-links/) are used to let the *user-sim* load testing service send requests to the *front-end* service and to let the main Sock Shop services send traces to the *zipkin* service. Using job links in this fashion simulates how real, cloud-based load testing and APM solutions can be integrated into applications running on Apcera without sacrificing security. ### Deployment -All of the Socks Shop services and the network are deployed to Apcera with a single script. However, you first need to target your cluster and login to it with APC. After that, just run the deploySocksShop.sh script. +All of the Sock Shop services and the network are deployed to Apcera with a single script. However, you first need to target your cluster and login to it with APC. After that, just run the deploySocksShop.sh script. diff --git a/microservices-demo/deployment/apcera.md b/microservices-demo/deployment/apcera.md new file mode 100644 index 0000000..cf18762 --- /dev/null +++ b/microservices-demo/deployment/apcera.md @@ -0,0 +1,90 @@ +--- +layout: default +deployDoc: true +--- + +## Sock Shop on Apcera + +These instructions will help you deploy and run the Sock Shop application on the [Apcera Platform](https://www.apcera.com/platform), an enterprise-grade container management platform for cloud-native and legacy applications. Apcera is secure by default, only permitting things explicitly authorized by policy, and supports multi-cloud deployments. + +Apcera has tested Sock Shop on the Apcera Community Edition running single-cloud clusters in Amazon AWS, Google Cloud Platform, Microsoft Azure, and VMware. We have also tested Sock Shop on the Apcera Enterprise Edition running a multi-cloud cluster that spanned across AWS, GCP, and VMware. + +### Packaging + +The Sock Shop application is packaged and configured for Apcera using a [Multi-Resource Manifest file](https://docs.apcera.com/jobs/multi-resource-manifests/) called socksshop-docker.json which is similar to a Docker Compose file. Scripts are provided to make it easy to deploy all the services and a network from the manifest, to start and stop the services, and to delete everything that was deployed. + +### Pre-requisites + +- Set up your preferred private or public cloud environment, preferably AWS, Google, Azure, or VMware. +- Install [Apcera Community Edition (CE)](https://docs.apcera.com/setup/apcera-setup/) in your cloud or use the Apcera Enterprise Edition (EE) if you own it. +- Download the Apcera command line tool [APC](https://docs.apcera.com/quickstart/installing-apc/) from the Apcera [Web Console](https://docs.apcera.com/quickstart/using_console/) and install it. + +``` +git clone https://github.com/microservices-demo/microservices-demo +cd microservices-demo/deploy/apcera +``` +- *(Optional)* If you are not an admin user in your Apcera cluster, you might need an Apcera administrator to import a [policy](https://docs.apcera.com/policy/introduction/) file to give you permission to create the Sock Shop services and network in your sandbox. + +``` +apc import policy socksShop.pol +``` + +### Networking and Security + +In this demo scenario, we create a single [virtual network](https://docs.apcera.com/jobs/virtual-networks/) to which all the services except *zipkin* and *user-sim* are added. Services inside the virtual network can all talk to each other. Apcera [job links](https://docs.apcera.com/jobs/job-links/) are used to let the *user-sim* load testing service send requests to the *front-end* service and to let the main Sock Shop services send traces to the *zipkin* service. Using job links in this fashion simulates how real, cloud-based load testing and APM solutions can be integrated into applications running on Apcera without sacrificing security. + +### Deployment + +All of the Sock Shop services and the network are deployed to Apcera with a single script. However, you first need to target your cluster and login to it with APC. After that, just run the deploySocksShop.sh script. + + + +``` +apc target +apc login +``` + + + ./deploySocksShop.sh + + + +After determining your targeted cluster and default namespace, this script does the following: + +- It sets your current namespace to \/socksshop. +- It runs the "apc manifest deploy" command against the socksshop-docker.json manifest to create the services and the socksshop-network virtual network. +- It creates [job affinity tags](https://docs.apcera.com/jobs/job-affinity/) to make sure that each service that uses a database is deployed to the same Apcera instance manager as the database. +- It then runs the startSocksShop.sh script to start all of the Sock Shop services. + +Altogether, the script should take under two minutes to run. + +### Using + +- You can access the Sock Shop front-end service in a browser with the URL: + - http://front-end.\ +- Note that the *edge-router* service is not used since Apcera provides its own router. +- You can view logs for the services in the Apcera Web Console or by using the "apc app logs" command. + +### Testing + +A load testing service, *user-sim*, is provided in the socksshop-docker.json manifest file. It will run when the manifest is deployed after a delay of 60 seconds. This is a load test provided to simulate user traffic to the application. You can view the results of the test in the *user-sim* log. + +### Tracing +[Zipkin](http://zipkin.io/) has been written into some of the services. While the system is up you can view the traces at http://zipkin.\. Currently *orders* provides the most comprehensive traces. + +### Starting and Stopping + +You can use the startSocksShop.sh and stopSocksShop.sh scripts to start and stop all the services. + +### Cleaning up + +Run the deleteSocksShop.sh script to delete the Sock Shop services and network. + + + + ./deleteSocksShop.sh + + From 4e7046bc4ac2a2eaf5c2762902f8f159ab8dbeed Mon Sep 17 00:00:00 2001 From: Roger Berlind Date: Thu, 13 Apr 2017 12:15:23 -0400 Subject: [PATCH 2/4] changed Socks Shop to Sock Shop --- deployment/apcera.md | 22 +++++++++++----------- 1 file changed, 11 insertions(+), 11 deletions(-) diff --git a/deployment/apcera.md b/deployment/apcera.md index cf18762..ace0f96 100644 --- a/deployment/apcera.md +++ b/deployment/apcera.md @@ -11,7 +11,7 @@ Apcera has tested Sock Shop on the Apcera Community Edition running single-cloud ### Packaging -The Sock Shop application is packaged and configured for Apcera using a [Multi-Resource Manifest file](https://docs.apcera.com/jobs/multi-resource-manifests/) called socksshop-docker.json which is similar to a Docker Compose file. Scripts are provided to make it easy to deploy all the services and a network from the manifest, to start and stop the services, and to delete everything that was deployed. +The Sock Shop application is packaged and configured for Apcera using a [Multi-Resource Manifest file](https://docs.apcera.com/jobs/multi-resource-manifests/) called sockshop-docker.json which is similar to a Docker Compose file. Scripts are provided to make it easy to deploy all the services and a network from the manifest, to start and stop the services, and to delete everything that was deployed. ### Pre-requisites @@ -26,7 +26,7 @@ cd microservices-demo/deploy/apcera - *(Optional)* If you are not an admin user in your Apcera cluster, you might need an Apcera administrator to import a [policy](https://docs.apcera.com/policy/introduction/) file to give you permission to create the Sock Shop services and network in your sandbox. ``` -apc import policy socksShop.pol +apc import policy sockShop.pol ``` ### Networking and Security @@ -35,7 +35,7 @@ In this demo scenario, we create a single [virtual network](https://docs.apcera. ### Deployment -All of the Sock Shop services and the network are deployed to Apcera with a single script. However, you first need to target your cluster and login to it with APC. After that, just run the deploySocksShop.sh script. +All of the Sock Shop services and the network are deployed to Apcera with a single script. However, you first need to target your cluster and login to it with APC. After that, just run the deploySockShop.sh script. - ./deploySocksShop.sh + ./deploySockShop.sh After determining your targeted cluster and default namespace, this script does the following: -- It sets your current namespace to \/socksshop. -- It runs the "apc manifest deploy" command against the socksshop-docker.json manifest to create the services and the socksshop-network virtual network. +- It sets your current namespace to \/sockshop. +- It runs the "apc manifest deploy" command against the sockshop-docker.json manifest to create the services and the sockshop-network virtual network. - It creates [job affinity tags](https://docs.apcera.com/jobs/job-affinity/) to make sure that each service that uses a database is deployed to the same Apcera instance manager as the database. -- It then runs the startSocksShop.sh script to start all of the Sock Shop services. +- It then runs the startSockShop.sh script to start all of the Sock Shop services. Altogether, the script should take under two minutes to run. @@ -70,21 +70,21 @@ Altogether, the script should take under two minutes to run. ### Testing -A load testing service, *user-sim*, is provided in the socksshop-docker.json manifest file. It will run when the manifest is deployed after a delay of 60 seconds. This is a load test provided to simulate user traffic to the application. You can view the results of the test in the *user-sim* log. +A load testing service, *user-sim*, is provided in the sockshop-docker.json manifest file. It will run when the manifest is deployed after a delay of 60 seconds. This is a load test provided to simulate user traffic to the application. You can view the results of the test in the *user-sim* log. ### Tracing [Zipkin](http://zipkin.io/) has been written into some of the services. While the system is up you can view the traces at http://zipkin.\. Currently *orders* provides the most comprehensive traces. ### Starting and Stopping -You can use the startSocksShop.sh and stopSocksShop.sh scripts to start and stop all the services. +You can use the startSockShop.sh and stopSockShop.sh scripts to start and stop all the services. ### Cleaning up -Run the deleteSocksShop.sh script to delete the Sock Shop services and network. +Run the deleteSockShop.sh script to delete the Sock Shop services and network. - ./deleteSocksShop.sh + ./deleteSockShop.sh From ab5cffaed16849d4b1d4c78f2751dad96be0cd72 Mon Sep 17 00:00:00 2001 From: Roger Berlind Date: Thu, 13 Apr 2017 13:10:07 -0400 Subject: [PATCH 3/4] Delete extra copy of apcera.md Not needed --- microservices-demo/deployment/apcera.md | 90 ------------------------- 1 file changed, 90 deletions(-) delete mode 100644 microservices-demo/deployment/apcera.md diff --git a/microservices-demo/deployment/apcera.md b/microservices-demo/deployment/apcera.md deleted file mode 100644 index cf18762..0000000 --- a/microservices-demo/deployment/apcera.md +++ /dev/null @@ -1,90 +0,0 @@ ---- -layout: default -deployDoc: true ---- - -## Sock Shop on Apcera - -These instructions will help you deploy and run the Sock Shop application on the [Apcera Platform](https://www.apcera.com/platform), an enterprise-grade container management platform for cloud-native and legacy applications. Apcera is secure by default, only permitting things explicitly authorized by policy, and supports multi-cloud deployments. - -Apcera has tested Sock Shop on the Apcera Community Edition running single-cloud clusters in Amazon AWS, Google Cloud Platform, Microsoft Azure, and VMware. We have also tested Sock Shop on the Apcera Enterprise Edition running a multi-cloud cluster that spanned across AWS, GCP, and VMware. - -### Packaging - -The Sock Shop application is packaged and configured for Apcera using a [Multi-Resource Manifest file](https://docs.apcera.com/jobs/multi-resource-manifests/) called socksshop-docker.json which is similar to a Docker Compose file. Scripts are provided to make it easy to deploy all the services and a network from the manifest, to start and stop the services, and to delete everything that was deployed. - -### Pre-requisites - -- Set up your preferred private or public cloud environment, preferably AWS, Google, Azure, or VMware. -- Install [Apcera Community Edition (CE)](https://docs.apcera.com/setup/apcera-setup/) in your cloud or use the Apcera Enterprise Edition (EE) if you own it. -- Download the Apcera command line tool [APC](https://docs.apcera.com/quickstart/installing-apc/) from the Apcera [Web Console](https://docs.apcera.com/quickstart/using_console/) and install it. - -``` -git clone https://github.com/microservices-demo/microservices-demo -cd microservices-demo/deploy/apcera -``` -- *(Optional)* If you are not an admin user in your Apcera cluster, you might need an Apcera administrator to import a [policy](https://docs.apcera.com/policy/introduction/) file to give you permission to create the Sock Shop services and network in your sandbox. - -``` -apc import policy socksShop.pol -``` - -### Networking and Security - -In this demo scenario, we create a single [virtual network](https://docs.apcera.com/jobs/virtual-networks/) to which all the services except *zipkin* and *user-sim* are added. Services inside the virtual network can all talk to each other. Apcera [job links](https://docs.apcera.com/jobs/job-links/) are used to let the *user-sim* load testing service send requests to the *front-end* service and to let the main Sock Shop services send traces to the *zipkin* service. Using job links in this fashion simulates how real, cloud-based load testing and APM solutions can be integrated into applications running on Apcera without sacrificing security. - -### Deployment - -All of the Sock Shop services and the network are deployed to Apcera with a single script. However, you first need to target your cluster and login to it with APC. After that, just run the deploySocksShop.sh script. - - - -``` -apc target -apc login -``` - - - ./deploySocksShop.sh - - - -After determining your targeted cluster and default namespace, this script does the following: - -- It sets your current namespace to \/socksshop. -- It runs the "apc manifest deploy" command against the socksshop-docker.json manifest to create the services and the socksshop-network virtual network. -- It creates [job affinity tags](https://docs.apcera.com/jobs/job-affinity/) to make sure that each service that uses a database is deployed to the same Apcera instance manager as the database. -- It then runs the startSocksShop.sh script to start all of the Sock Shop services. - -Altogether, the script should take under two minutes to run. - -### Using - -- You can access the Sock Shop front-end service in a browser with the URL: - - http://front-end.\ -- Note that the *edge-router* service is not used since Apcera provides its own router. -- You can view logs for the services in the Apcera Web Console or by using the "apc app logs" command. - -### Testing - -A load testing service, *user-sim*, is provided in the socksshop-docker.json manifest file. It will run when the manifest is deployed after a delay of 60 seconds. This is a load test provided to simulate user traffic to the application. You can view the results of the test in the *user-sim* log. - -### Tracing -[Zipkin](http://zipkin.io/) has been written into some of the services. While the system is up you can view the traces at http://zipkin.\. Currently *orders* provides the most comprehensive traces. - -### Starting and Stopping - -You can use the startSocksShop.sh and stopSocksShop.sh scripts to start and stop all the services. - -### Cleaning up - -Run the deleteSocksShop.sh script to delete the Sock Shop services and network. - - - - ./deleteSocksShop.sh - - From 12b135bb6a68813091d4620ae159aba1dc9888cd Mon Sep 17 00:00:00 2001 From: Roger Berlind Date: Thu, 13 Apr 2017 13:11:15 -0400 Subject: [PATCH 4/4] removed extra copy of apcera.md --- microservices-demo/deployment/apcera.md | 90 ------------------------- 1 file changed, 90 deletions(-) delete mode 100644 microservices-demo/deployment/apcera.md diff --git a/microservices-demo/deployment/apcera.md b/microservices-demo/deployment/apcera.md deleted file mode 100644 index cf18762..0000000 --- a/microservices-demo/deployment/apcera.md +++ /dev/null @@ -1,90 +0,0 @@ ---- -layout: default -deployDoc: true ---- - -## Sock Shop on Apcera - -These instructions will help you deploy and run the Sock Shop application on the [Apcera Platform](https://www.apcera.com/platform), an enterprise-grade container management platform for cloud-native and legacy applications. Apcera is secure by default, only permitting things explicitly authorized by policy, and supports multi-cloud deployments. - -Apcera has tested Sock Shop on the Apcera Community Edition running single-cloud clusters in Amazon AWS, Google Cloud Platform, Microsoft Azure, and VMware. We have also tested Sock Shop on the Apcera Enterprise Edition running a multi-cloud cluster that spanned across AWS, GCP, and VMware. - -### Packaging - -The Sock Shop application is packaged and configured for Apcera using a [Multi-Resource Manifest file](https://docs.apcera.com/jobs/multi-resource-manifests/) called socksshop-docker.json which is similar to a Docker Compose file. Scripts are provided to make it easy to deploy all the services and a network from the manifest, to start and stop the services, and to delete everything that was deployed. - -### Pre-requisites - -- Set up your preferred private or public cloud environment, preferably AWS, Google, Azure, or VMware. -- Install [Apcera Community Edition (CE)](https://docs.apcera.com/setup/apcera-setup/) in your cloud or use the Apcera Enterprise Edition (EE) if you own it. -- Download the Apcera command line tool [APC](https://docs.apcera.com/quickstart/installing-apc/) from the Apcera [Web Console](https://docs.apcera.com/quickstart/using_console/) and install it. - -``` -git clone https://github.com/microservices-demo/microservices-demo -cd microservices-demo/deploy/apcera -``` -- *(Optional)* If you are not an admin user in your Apcera cluster, you might need an Apcera administrator to import a [policy](https://docs.apcera.com/policy/introduction/) file to give you permission to create the Sock Shop services and network in your sandbox. - -``` -apc import policy socksShop.pol -``` - -### Networking and Security - -In this demo scenario, we create a single [virtual network](https://docs.apcera.com/jobs/virtual-networks/) to which all the services except *zipkin* and *user-sim* are added. Services inside the virtual network can all talk to each other. Apcera [job links](https://docs.apcera.com/jobs/job-links/) are used to let the *user-sim* load testing service send requests to the *front-end* service and to let the main Sock Shop services send traces to the *zipkin* service. Using job links in this fashion simulates how real, cloud-based load testing and APM solutions can be integrated into applications running on Apcera without sacrificing security. - -### Deployment - -All of the Sock Shop services and the network are deployed to Apcera with a single script. However, you first need to target your cluster and login to it with APC. After that, just run the deploySocksShop.sh script. - - - -``` -apc target -apc login -``` - - - ./deploySocksShop.sh - - - -After determining your targeted cluster and default namespace, this script does the following: - -- It sets your current namespace to \/socksshop. -- It runs the "apc manifest deploy" command against the socksshop-docker.json manifest to create the services and the socksshop-network virtual network. -- It creates [job affinity tags](https://docs.apcera.com/jobs/job-affinity/) to make sure that each service that uses a database is deployed to the same Apcera instance manager as the database. -- It then runs the startSocksShop.sh script to start all of the Sock Shop services. - -Altogether, the script should take under two minutes to run. - -### Using - -- You can access the Sock Shop front-end service in a browser with the URL: - - http://front-end.\ -- Note that the *edge-router* service is not used since Apcera provides its own router. -- You can view logs for the services in the Apcera Web Console or by using the "apc app logs" command. - -### Testing - -A load testing service, *user-sim*, is provided in the socksshop-docker.json manifest file. It will run when the manifest is deployed after a delay of 60 seconds. This is a load test provided to simulate user traffic to the application. You can view the results of the test in the *user-sim* log. - -### Tracing -[Zipkin](http://zipkin.io/) has been written into some of the services. While the system is up you can view the traces at http://zipkin.\. Currently *orders* provides the most comprehensive traces. - -### Starting and Stopping - -You can use the startSocksShop.sh and stopSocksShop.sh scripts to start and stop all the services. - -### Cleaning up - -Run the deleteSocksShop.sh script to delete the Sock Shop services and network. - - - - ./deleteSocksShop.sh - -