Learn and Be Curious

c:\dev>bx login -u jesang.myung@gmail.com

API 엔드포인트: https://api.ng.bluemix.net


Password>

인증 중...

확인


계정 선택(또는 Enter를 눌러 건너뜀):

1. Jesang Myung's Account (4b87bafe5a89360c26fb9f022d408739)

2. SAMSUNG SDS (060163dc8cc9cb11351ccc7a9caa316a)

3. Ana Giordano's Account (cd08bd765f10d2430af4808a49380a2e)

4. KYU MIN JEONG's Account (cc2b9c223ffb550f64d4c83d3ca4efa7)

번호 입력> 2

대상 지정된 계정 SAMSUNG SDS (060163dc8cc9cb11351ccc7a9caa316a)


대상 지정된 조직 SDS_Bluemix_Workshop


대상 지정된 영역 Workshop




API 엔드포인트:   https://api.ng.bluemix.net(API 버전: 2.75.0)

지역:             us-south

사용자:           jesang.myung@gmail.com

계정:             SAMSUNG SDS (060163dc8cc9cb11351ccc7a9caa316a)

조직:             SDS_Bluemix_Workshop

영역:             Workshop



c:\dev>git clone https://github.com/pfgeiger/RedbookLibrary
Cloning into 'RedbookLibrary'...
remote: Counting objects: 285, done.
remote: Total 285 (delta 0), reused 0 (delta 0), pack-reused 285
Receiving objects: 100% (285/285), 5.80 MiB | 2.27 MiB/s, done.
Resolving deltas: 100% (109/109), done.

c:\dev>bx cf create-service dashdb Entry library_db
'cf create-service dashdb Entry library_db' 호출 중...

Creating service instance library_db in org SDS_Bluemix_Workshop / space Workshop as jesang.myung@gmail.com...
OK

Attention: The plan `Entry` of service `dashdb` is not free.  The instance `library_db` will incur a cost.  Contact your administrator if you think this is in error.


c:\dev>bx cf create-service SessionCache starter SessionCache-abc
'cf create-service SessionCache starter SessionCache-abc' 호출 중...

Creating service instance SessionCache-abc in org SDS_Bluemix_Workshop / space Workshop as jesang.myung@gmail.com...
OK

Attention: The plan `starter` of service `SessionCache` is not free.  The instance `SessionCache-abc` will incur a cost.  Contact your administrator if you think this is in error.


c:\dev>cd RedbookLibrary





c:\dev\RedbookLibrary>bx app push
'cf push' 호출 중...

Using manifest file c:\dev\RedbookLibrary\manifest.yml

Creating app sds-redbooklibrary in org SDS_Bluemix_Workshop / space Workshop as jesang.myung@gmail.com...
OK

Creating route sds-redbook-library.mybluemix.net...
OK

Binding sds-redbook-library.mybluemix.net to sds-redbooklibrary...
OK

Uploading sds-redbooklibrary...
Uploading app files from: C:\Users\MYUNG-~1\AppData\Local\Temp\unzipped-app473540899
Uploading 53.3K, 46 files
Done uploading
OK
Binding service library_db to app sds-redbooklibrary in org SDS_Bluemix_Workshop / space Workshop as jesang.myung@gmail.com...
OK
Binding service SessionCache-abc to app sds-redbooklibrary in org SDS_Bluemix_Workshop / space Workshop as jesang.myung@gmail.com...
OK

Starting app sds-redbooklibrary in org SDS_Bluemix_Workshop / space Workshop as jesang.myung@gmail.com...
Downloading liberty-for-java...
Downloaded liberty-for-java
Creating container
Downloading app package...
Successfully created container
Downloaded app package (2.8M)
Staging...
-----> Liberty Buildpack Version: v3.10-20170525-1107
-----> Retrieving IBM 1.8.0_20170215 JRE (ibm-java-jre-8.0-4.1-pxa6480sr4fp1-20170215_01-cloud.tgz) ... (0.0s)
-----> Retrieving App Management 1.26.0_20170522-1438 (app-mgmt_v1.26-20170522-1438.zip) ... (0.0s)
         Expanding JRE to .java ... (1.3s)
         Expanding App Management to .app-management (0.1s)
-----> Retrieving com.ibm.ws.liberty-17.0.0.2-201705251107.tar.gz ... (0.0s)
         Installing archive ... (1.2s)
-----> Retrieving com.ibm.ws.liberty.ext-17.0.0.2-201705251107.tar.gz ... (0.0s)
         Installing archive ... (1.0s)
-----> Retrieving wxsclient-wlp_8.6.0.8-Pcf81712.22162916.esa ... (0.0s).
         Installing feature ... (9.4s).
-----> Retrieving and installing client jar(s) from com.ibm.ws.icap.clientJars.db2.zip (0.0s)
-----> Warning: Liberty feature set is not specified. Using the default feature set: ["beanValidation-1.1", "cdi-1.2", "ejbLite-3.2", "el-3.0", "jaxrs-2.0", "jdbc-4.1", "jndi-1.0", "jpa-2.1", "jsf-2.2", "jsonp-1.0", "jsp-2.3", "managedBeans-1.0", "servlet-3.1", "websocket-1.1"]. For the best results, explicitly set the features via the JBP_CONFIG_LIBERTY environment variable or deploy the application as a server directory or packaged server with a custom server.xml file.
-----> Auto-configuration is creating config for service instance 'SessionCache-abc' of type 'SessionCache'
-----> Auto-configuration is creating config for service instance 'library_db' of type 'AnalyticsWarehouse'
-----> Liberty buildpack is done creating the droplet
Exit status 0
Staging complete
Uploading droplet, build artifacts cache...
Uploading build artifacts cache...
Uploading droplet...
Uploaded build artifacts cache (108B)
Uploaded droplet (219.8M)
Uploading complete
Destroying container
Successfully destroyed container

0 of 1 instances running, 1 starting
0 of 1 instances running, 1 starting
0 of 1 instances running, 1 starting
0 of 1 instances running, 1 starting
0 of 1 instances running, 1 starting
1 of 1 instances running

App started


OK

App sds-redbooklibrary was started using this command `.liberty/initial_startup.rb`

Showing health and status for app sds-redbooklibrary in org SDS_Bluemix_Workshop / space Workshop as jesang.myung@gmail.com...
OK

requested state: started
instances: 1/1
usage: 512M x 1 instances
urls: sds-redbook-library.mybluemix.net
last uploaded: Mon Jul 10 11:55:45 UTC 2017
stack: cflinuxfs2
buildpack: liberty-for-java

     state     since                    cpu      memory           disk           details
#0   running   2017-07-10 08:57:47 PM   320.5%   166.4M of 512M   293.4M of 1G


c:\dev\RedbookLibrary>bx cf apps
'cf apps' 호출 중...

Getting apps in org SDS_Bluemix_Workshop / space Workshop as jesang.myung@gmail.com...
OK

name                                          requested state   instances   memory   disk   urls
sds-redbooklibrary                            started           1/1         512M     1G     sds-redbook-library.mybluemix.net







c:\dev\RedbookLibrary>bx app scale sds-redbooklibrary -i 2
'cf scale sds-redbooklibrary -i 2' 호출 중...

Scaling app sds-redbooklibrary in org SDS_Bluemix_Workshop / space Workshop as jesang.myung@gmail.com...
OK




c:\dev\RedbookLibrary>bx cf apps
'cf apps' 호출 중...

Getting apps in org SDS_Bluemix_Workshop / space Workshop as jesang.myung@gmail.com...
OK

name                                          requested state   instances   memory   disk   urls
sds-redbooklibrary                            started           2/2         512M     1G     sds-redbook-library.mybluemix.net




c:\dev\RedbookLibrary>bx cf apps
'cf apps' 호출 중...

Getting apps in org SDS_Bluemix_Workshop / space Workshop as jesang.myung@gmail.com...
OK

name                                          requested state   instances   memory   disk   urls
sds-redbooklibrary                            started           2/2         512M     1G     sds-redbook-library.mybluemix.net
sds-test-app3                                 started           1/1         1G       1G     sds-test-app3.mybluemix.net
second-test2                                  stopped           0/1         512M     1G     second-test2.mybluemix.net
meetingroom-reservation-with-hkt              stopped           0/1         256M     1G     meetingroom-reservation-with-hkt.mybluemix.net
simple-rbs-hktbart-1425                       stopped           0/1         512M     1G     simple-rbs-hktbart-1425.mybluemix.net
hkt-iot-test2                                 stopped           0/1         512M     1G     hkt-iot-test2.mybluemix.net
orders-api-toolchain-demo-20170612010518521   stopped           0/1         96M      1G     orders-api-toolchain-demo-20170612010518521.mybluemix.net
orders-api-toolchain-demo-20170611154355788   stopped           0/1         96M      1G     orders-api-toolchain-demo-20170611154355788.mybluemix.net

c:\dev\RedbookLibrary>bx app scale sds-redbooklibrary -i 1
'cf scale sds-redbooklibrary -i 1' 호출 중...

Scaling app sds-redbooklibrary in org SDS_Bluemix_Workshop / space Workshop as jesang.myung@gmail.com...
OK






'Cloud > Bluemix' 카테고리의 다른 글

Cloud-Native Application Development  (0) 2017.07.10
Cloud Foundry difference between Pivotal and IBM  (0) 2017.07.10
Bluemix 총정리  (0) 2017.04.20
OpenWhisk  (0) 2017.04.20
Royal Bank of Canada's Journey  (0) 2017.04.20

c:\dev>bluemix api https://api.ng.bluemix.net
API 엔드포인트를 https://api.ng.bluemix.net(으)로 설정 중...
확인

API endpoint: https://api.ng.bluemix.net (CF API version: 2.75.0)

c:\dev>bluemix login -u jesang.myung@gmail.com
API 엔드포인트: https://api.ng.bluemix.net

Password>
인증 중...
확인

계정 선택(또는 Enter를 눌러 건너뜀):
1. Jesang Myung's Account (4b87bafe5a89360c26fb9f022d408739)
2. SAMSUNG SDS (060163dc8cc9cb11351ccc7a9caa316a)
3. Ana Giordano's Account (cd08bd765f10d2430af4808a49380a2e)
4. KYU MIN JEONG's Account (cc2b9c223ffb550f64d4c83d3ca4efa7)
번호 입력> 2
대상 지정된 계정 SAMSUNG SDS (060163dc8cc9cb11351ccc7a9caa316a)

대상 지정된 조직 SDS_Bluemix_Workshop

대상 지정된 영역 Workshop



API 엔드포인트:   https://api.ng.bluemix.net(API 버전: 2.75.0)
지역:             us-south
사용자:           jesang.myung@gmail.com
계정:             SAMSUNG SDS (060163dc8cc9cb11351ccc7a9caa316a)
조직:             SDS_Bluemix_Workshop
영역:             Workshop



c:\dev>git clone https://hub.jazz.net/git/osowski/bluemix-libertycache
Cloning into 'bluemix-libertycache'...
Receiving objects:  96% (150/156), 24.68 MiB | 1.93 MiB/s
Receiving objects: 100% (156/156), 25.41 MiB | 2.12 MiB/s, done.
Resolving deltas: 100% (4/4), done.



c:\dev>cd bluemix-libertycache



c:\dev\bluemix-libertycache>bx app push sds-test-app -p cacheSampleJavaNativeAPIs.war --no-manifest
'cf push sds-test-app -p cacheSampleJavaNativeAPIs.war --no-manifest' 호출 중...

Creating app sds-test-app in org SDS_Bluemix_Workshop / space Workshop as jesang.myung@gmail.com...
OK

Creating route sds-test-app.mybluemix.net...
OK

Binding sds-test-app.mybluemix.net to sds-test-app...
OK

Uploading sds-test-app...
Uploading app files from: C:\Users\MYUNG-~1\AppData\Local\Temp\unzipped-app960286279
Uploading 42.9K, 21 files
Done uploading
OK

Starting app sds-test-app in org SDS_Bluemix_Workshop / space Workshop as jesang.myung@gmail.com...
Downloading liberty-for-java_v3_9-20170419-1403...
Downloading xpages_buildpack...
Downloading python_buildpack...
Downloading liberty-for-java...
Downloaded liberty-for-java_v3_9-20170419-1403
Downloading java_buildpack...
Downloading go_buildpack...
Downloading sdk-for-nodejs...
Downloaded go_buildpack
Downloaded python_buildpack
Downloading dotnet-core...
Downloading swift_buildpack...
Downloaded liberty-for-java
Downloading noop-buildpack...
Downloaded xpages_buildpack
Downloaded sdk-for-nodejs
Downloading ruby_buildpack...
Downloaded swift_buildpack
Downloading nodejs_buildpack...
Downloaded dotnet-core
Downloading liberty-for-java_v3_7-20170118-2046...
Downloaded noop-buildpack
Downloading php_buildpack...
Downloaded java_buildpack
Downloaded nodejs_buildpack
Downloading staticfile_buildpack...
Downloading binary_buildpack...
Downloaded ruby_buildpack
Downloading swift_buildpack_v2_0_5-20170406-2317...
Downloaded liberty-for-java_v3_7-20170118-2046
Downloading liberty-for-java_v3_8-20170308-1507...
Downloaded php_buildpack
Downloading sdk-for-nodejs_v3_11-20170303-1144...
Downloaded staticfile_buildpack
Downloading dotnet-core_v1_0_13-20170330-1023...
Downloaded liberty-for-java_v3_8-20170308-1507
Downloaded binary_buildpack
Downloaded swift_buildpack_v2_0_5-20170406-2317
Downloaded sdk-for-nodejs_v3_11-20170303-1144
Downloaded dotnet-core_v1_0_13-20170330-1023
Creating container
Successfully created container
Downloading app package...
Staging...
Downloaded app package (6.1M)
-----> Liberty Buildpack Version: v3.10-20170525-1107
-----> Retrieving IBM 1.8.0_20170215 JRE (ibm-java-jre-8.0-4.1-pxa6480sr4fp1-20170215_01-cloud.tgz) ... (0.0s)
         Expanding JRE to .java ... (1.2s)
-----> Retrieving App Management 1.26.0_20170522-1438 (app-mgmt_v1.26-20170522-1438.zip) ... (0.0s)
         Expanding App Management to .app-management (0.1s)
-----> Retrieving com.ibm.ws.liberty-17.0.0.2-201705251107.tar.gz ... (0.0s)
         Installing archive ... (1.3s)
-----> Liberty buildpack is done creating the droplet
-----> Warning: Liberty feature set is not specified. Using the default feature set: ["beanValidation-1.1", "cdi-1.2", "ejbLite-3.2", "el-3.0", "jaxrs-2.0", "jdbc-4.1", "jndi-1.0", "jpa-2.1", "jsf-2.2", "jsonp-1.0", "jsp-2.3", "managedBeans-1.0", "servlet-3.1", "websocket-1.1"]. For the best results, explicitly set the features via the JBP_CONFIG_LIBERTY environment variable or deploy the application as a server directory or packaged server with a custom server.xml file.
Exit status 0
Staging complete
Uploading droplet, build artifacts cache...
Uploading build artifacts cache...
Uploading droplet...
Uploaded build artifacts cache (108B)
Uploaded droplet (138.4M)
Uploading complete
Destroying container
Successfully destroyed container

0 of 1 instances running, 1 starting
0 of 1 instances running, 1 starting
0 of 1 instances running, 1 starting
0 of 1 instances running, 1 starting
0 of 1 instances running, 1 starting
0 of 1 instances running, 1 starting
1 of 1 instances running

App started


OK

App sds-test-app was started using this command `.liberty/initial_startup.rb`

Showing health and status for app sds-test-app in org SDS_Bluemix_Workshop / space Workshop as jesang.myung@gmail.com...
OK

requested state: started
instances: 1/1
usage: 1G x 1 instances
urls: sds-test-app.mybluemix.net
last uploaded: Mon Jul 10 08:40:10 UTC 2017
stack: cflinuxfs2
buildpack: Liberty for Java(TM) (WAR, liberty-17.0.0_2, buildpack-v3.10-20170525-1107, ibmjdk-1.8.0_20170215, env)

     state     since                    cpu     memory         disk         details
#0   running   2017-07-10 05:41:48 PM   85.4%   129.9M of 1G   196M of 1G



------------------------------------------------------------------------------------------------------------------------------------------


c:\dev\bluemix-libertycache>bx app push sds-test-app2 -p cacheSampleJavaNativeAPIs.war -b java_buildpack --no-manifest
'cf push sds-test-app2 -p cacheSampleJavaNativeAPIs.war -b java_buildpack --no-manifest' 호출 중...

Creating app sds-test-app2 in org SDS_Bluemix_Workshop / space Workshop as jesang.myung@gmail.com...
OK

Creating route sds-test-app2.mybluemix.net...
OK

Binding sds-test-app2.mybluemix.net to sds-test-app2...
OK

Uploading sds-test-app2...
Uploading app files from: C:\Users\MYUNG-~1\AppData\Local\Temp\unzipped-app450300315
Uploading 42.9K, 21 files
Done uploading
OK

Starting app sds-test-app2 in org SDS_Bluemix_Workshop / space Workshop as jesang.myung@gmail.com...
Downloading java_buildpack...
Downloaded java_buildpack
Creating container
Successfully created container
Downloading app package...
Downloaded app package (6.1M)
Staging...
-----> Java Buildpack Version: v3.13 | https://github.com/cloudfoundry/java-buildpack.git#03b493f
-----> Downloading Open Jdk JRE 1.8.0_121 from https://java-buildpack.cloudfoundry.org/openjdk/trusty/x86_64/openjdk-1.8.0_121.tar.gz (0.5s)
       Expanding Open Jdk JRE to .java-buildpack/open_jdk_jre (1.4s)
-----> Downloading Open JDK Like Memory Calculator 2.0.2_RELEASE from https://java-buildpack.cloudfoundry.org/memory-calculator/trusty/x86_64/memory-calculator-2.0.2_RELEASE.tar.gz (0.0s)
       Memory Settings: -XX:MetaspaceSize=104857K -Xss349K -Xmx681574K -XX:MaxMetaspaceSize=104857K -Xms681574K
-----> Downloading Container Certificate Trust Store 2.1.0_RELEASE from https://java-buildpack.cloudfoundry.org/container-certificate-trust-store/container-certificate-trust-store-2.1.0_RELEASE.jar (0.0s)
       Adding certificates to .java-buildpack/container_certificate_trust_store/truststore.jks (0.6s)
-----> Downloading Tomcat Instance 8.0.45 from https://java-buildpack.cloudfoundry.org/tomcat/tomcat-8.0.45.tar.gz (0.1s)
       Expanding Tomcat Instance to .java-buildpack/tomcat (0.1s)
-----> Downloading Tomcat Lifecycle Support 2.5.0_RELEASE from https://java-buildpack.cloudfoundry.org/tomcat-lifecycle-support/tomcat-lifecycle-support-2.5.0_RELEASE.jar (0.0s)
-----> Downloading Tomcat Logging Support 2.5.0_RELEASE from https://java-buildpack.cloudfoundry.org/tomcat-logging-support/tomcat-logging-support-2.5.0_RELEASE.jar (0.0s)
-----> Downloading Tomcat Access Logging Support 2.5.0_RELEASE from https://java-buildpack.cloudfoundry.org/tomcat-access-logging-support/tomcat-access-logging-support-2.5.0_RELEASE.jar (0.0s)
Staging complete
Uploading droplet...
Exit status 0
Uploading droplet, build artifacts cache...
Uploading build artifacts cache...
Uploaded build artifacts cache (52.7M)
Uploaded droplet (57.9M)
Uploading complete
Destroying container
Successfully destroyed container

0 of 1 instances running, 1 starting
0 of 1 instances running, 1 starting
0 of 1 instances running, 1 starting
0 of 1 instances running, 1 crashed
FAILED
Error restarting application: Start unsuccessful

TIP: use 'cf logs sds-test-app2 --recent' for more information
















'Cloud > Bluemix' 카테고리의 다른 글

Adding a Session Cache service to an application  (0) 2017.07.10
Cloud Foundry difference between Pivotal and IBM  (0) 2017.07.10
Bluemix 총정리  (0) 2017.04.20
OpenWhisk  (0) 2017.04.20
Royal Bank of Canada's Journey  (0) 2017.04.20

Cloud Foundry difference between Pivotal and IBM

1. One key aspect of the differentiation is the diversity and capabilities of the services available on the platform. You can compare and contrast the services .
2. BlueMix provides an Mobile Application Development Platform whereas Pivotal CF does not provide mobile backend services today.
3. BlueMix provides an integrated developer experience in the cloud via integration with JazzHub. This enables various devops scenarios and the push from src model
4. In terms of runtimes for the applications, BlueMix supports running web applications and server packages for java, node on IBM-Node.js runtimes and ruby with the ruby on rails and Ruby Sinatra apps. The java runtime provisioned by the Liberty buildpack is very different from the open source java buildpack in terms of feature, function and philosophy.


* IBM Bluemix was originally based off Cloud Foundry's open technology. It is a cloud computing platform as a service that supports the full lifecycle, from initial development, through all testing stages, to deployment.
* Cloud Foundry has a CLI program called cf which is the primary tool to interact with Bluemix (or Bluemix provides a web GUI for this).
* Cloud Foundry introduces the concepts of Organizations that contain Spaces which you can think of as workspaces. Different spaces typically correspond to different lifecycle stages for an application.
* Cloud Foundry introduces the concepts of Services and Applications. A Cloud Foundry service usually performs a particular function (like a database service), and an application usually has services and their keys bound to it.


Pivotal과 IBM 간의 Cloud Foundry 차이

1. 차별화의 핵심 요소 중 하나는 플랫폼에서 사용할 수있는 서비스의 다양성과 기능입니다. 당신은 서비스를 비교하고 대조 할 수 있습니다. 2. BlueMix는 모바일 응용 프로그램 개발 플랫폼을 제공하지만 Pivotal CF는 현재 모바일 백엔드 서비스를 제공하지 않습니다. 3. BlueMix는 JazzHub와의 통합을 통해 클라우드에서 통합 된 개발자 경험을 제공합니다. 이것은 다양한 devop 시나리오와 src 모델로부터의 push를 가능하게합니다. 4. 응용 프로그램의 런타임 측면에서 BlueMix는 Java 용 웹 응용 프로그램 및 서버 패키지, IBM-Node.js 런타임의 노드 및 루비 온 레일 및 Ruby Sinatra 응용 프로그램과 함께 루비 실행을 지원합니다. Liberty buildpack이 제공하는 Java 런타임은 기능, 기능 및 철학 측면에서 오픈 소스 Java 빌드 팩과 매우 다릅니다. * IBM Bluemix는 원래 Cloud Foundry의 개방형 기술을 기반으로했습니다. 초기 개발부터 모든 테스트 단계, 배포까지 전체 라이프 사이클을 지원하는 클라우드 컴퓨팅 플랫폼입니다. * Cloud Foundry에는 Bluemix와 상호 작용할 수있는 기본 도구 인 cf라는 CLI 프로그램이 있습니다 (또는 Bluemix는이를위한 웹 GUI를 제공함). * Cloud Foundry는 작업 공간이라고 생각할 수있는 공간이 포함 된 조직의 개념을 소개합니다. 서로 다른 공간은 일반적으로 응용 프로그램의 다른 라이프 사이클 단계에 해당합니다. * Cloud Foundry는 서비스 및 응용 프로그램의 개념을 소개합니다. Cloud Foundry 서비스는 일반적으로 데이터베이스 서비스와 같은 특정 기능을 수행하며 응용 프로그램은 일반적으로 서비스와 해당 키가 바인딩되어 있습니다.


'Cloud > Bluemix' 카테고리의 다른 글

Adding a Session Cache service to an application  (0) 2017.07.10
Cloud-Native Application Development  (0) 2017.07.10
Bluemix 총정리  (0) 2017.04.20
OpenWhisk  (0) 2017.04.20
Royal Bank of Canada's Journey  (0) 2017.04.20

Bluemix 총정리

Cloud/Bluemix2017. 4. 20. 20:31

Starter - A starter is a template that includes predefined services and application

code that is configured with a particular buildpack. There are two types of starters:

boilerplates and runtimes.


Boilerplate - A boilerplate is a container for an application and its associated

runtime environment and predefined services for a particular domain.


Runtime - A runtime is the set of resources that is used to run an application.

Bluemix provides runtime environments as containers for different types of

applications. The runtime environments are integrated as buildpacks into Bluemix,

are automatically configured for use, and require little to no maintenance.



Buildpack - A buildpack is a collection of scripts that prepare your code for

execution on the target PaaS. A buildpack gathers the runtime and framework

dependencies of an application. Then, it packages them with the application into a

droplet that can be deployed to the cloud.


Service - A service is a cloud extension that is hosted by Bluemix. The service

provides functionality that is ready-for-use by the app's running code. The predefined

services that are provided by Bluemix include database, messaging, push

notifications for mobile apps, and elastic caching for web apps.



Managed services are listed in the IBM Bluemix PaaS catalog. A Managed Service integrates with Bluemix/Cloud Foundry via a service broker that implements the Service Broker API. The service broker advertises a catalog of service offerings and service plans to Bluemix/Cloud Foundry and receives calls from Cloud Foundry for four functions: create, delete, bind, and unbind.


User-provided services can be used by developers to programmatically define services outside of IBM Bluemix PaaS. This gives a mechanism to provide credentials to applications for service instances which have been pre-provisioned outside of Bluemix/Cloud Foundry.









[IBM Containers on Bluemix]


Docker Engine

Fully managed, scalable hosted container service built on open source Docker technology. Security compliance insight, logging, and monitoring and Container groups with fully qualified domain names, load balancer, auto-recovery, and auto-scaling.


Networking support

Privately network your containers by using real IP addresses, configured for each in a single step.


Vulnerability advisor (취약성)

Discover vulnerabilities and compliance problems in Docker images. Also, regardless of image source, upgrade your containers with known industry fixes.


Integrated container monitoring

Monitor performance and gain insight per container into CPU, memory, and network utilization.


Private Docker image registry

With a hosted private registry, ensuring access is both secure and auditable, you can securely store and share Docker images across your organization, allowing users to push and pull containers on- and off-premises.


Enterprise-ready images

Along with any image from the Docker Hub, you can use images of WebSphere Liberty, MobileFirst Platform, StrongLoop Process Manager, and Node.js runtime in IBM Containers.


Highly available container groups

A container group includes two or more containers that run the same image. Use container groups for running long-term services with workloads that require scalability and reliability or for testing at the required scale. Container groups can run within a single availabilty zone in one Bluemix region, be spread across multiple availablity zones and even configured in different availablity zones in two regions.


Container Volumes

A container is ephemeral, and you cannot persist application data in it. However, you can use a volume to persist data between container restarts, to share data between containers in a space, and to have access to your application data when your container is not available. Data in a persistent volume can be backed up and restored through the CLI.




[OpenWhisk]


Actions

An OpenWhisk action is a piece of code that performs one specific task. An action can be written in the language of your choice. You provide your action to OpenWhisk either source code or a Docker image.
An action performs work when invoked from your code via REST API. Actions can also automatically respond toevents from Bluemix and third party services using a trigger.


Triggers & Rules

A trigger is a declaration that you want to react to a certain type of event, whether from a user or by an event source. Triggers fire when they receive an event. Events are always occurring, and it's your choice on how to respond to them.
A rule associates a trigger with an action. Every time the trigger fires, the rule invokes the associated action.


Sequences

A sequence is a chain of actions, invoked in order, where the output of one becomes the input to the next. This allows you to combine existing actions
together for quick and easy re-use. A sequence can then be invoked just like an action, through a REST API or automated in a rule.


Action Runtimes

Create actions in a variety of languages, including Node.js 6, Python, and Swift 3. You can also use any other language you prefer by putting your code into a Docker container. Develop your code in the Bluemix web-based interface, or with your favorite development IDE and use the OpenWhisk CLI to upload it.




[12 factor]

1. Codebase: Maintain a single codebase tracked in revision control, many deploys

2. Dependencies: Explicitly declare and isolate dependencies

3. Config: Store application configuration in the environment

4. Backing Services: Treat backing services as attached resources

5. Build, release, run: Strictly separate build and run stages

6. Processes: Execute the app as one or more stateless processes

7. Port binding: Export services via port binding

8. Concurrency: Scale out via the process model

9. Disposability: Maximize robustness with fast startup and graceful shutdown

10. Dev/prod parity: Keep development, staging, and production as similar as possible

11. Logs: Treat logs as event streams

12. Admin processes: Run admin/management tasks as one-off processes



[Using DevOps toolchain to develop and deliver cloud applications]

Toolchains enable development organizations to standardize and scale their continuous delivery processes.

Toolchains automate the process of constructing new dev, test and prod environments





8.2.1.2. Load Test Iterations include a baseline, and further tests to evaluate if performance can be increased. Baseline testing is the initial performance evaluation to be performed under typical load and without application scaling or service tuning.


8.2.1.3. Several third party services such as Load Impact and Blaze Meter are available in the Bluemix catalog for performing application testing. These tests provide insights on performance and can also show if horizontal scaling is responding when the application is under stress.



'Cloud > Bluemix' 카테고리의 다른 글

Cloud-Native Application Development  (0) 2017.07.10
Cloud Foundry difference between Pivotal and IBM  (0) 2017.07.10
OpenWhisk  (0) 2017.04.20
Royal Bank of Canada's Journey  (0) 2017.04.20
chatbot  (0) 2017.04.19

OpenWhisk

Cloud/Bluemix2017. 4. 20. 14:10

Serverless

- 개발자가 BizLogic에 집중할수 있도록

- not 인프라 (인프라는 개발하는데 시간이 오래걸림)

- 사실 서버리스는 참이 아니다

- 개발자관점에서 볼때 서버에 대해서 신경을 쓸필요가 없다



silo


opensource 의 장점

- 특정 클라우드 vender에 bind되어 있지 않다

- ex) cloud foundry, openwhisk...


function as a service ? <- SaaS <- PaaS <-IaaS


fire and forget


 

- queue : point-point O n(n-1)
- topic : O (1) ... Event-driven, 내가 원하는 어플리케이션은 너야

  : emit event, 원하는 이벤트가 있는 경우에만 해당코드가 돌아가면 된다


only pay what use

pay per use


vm 같은 경우는 쓰지않아도 과금됨


polyglot

poly (많다) 글록(언어) ? ... C, 파이선, ....



ex) 핸드폰 사용요금




nodejs의 restful api와 비슷한 개념인가?

- biz 로직을 js안에서 구현한다

-



TAR

trigger (emit event), humidity

action (

rules = trigger -> action, humidity 30 %...


package = trigger + action



Marchitecture




nodejs : single thread

scalar : multi thread

...scalar로 변경되는 추세임




=======================================================================

[실습]



Microsoft Windows [Version 6.1.7601]

SDS@SDS-PC C:\Users\SDS
$ cf login
API endpoint: https://api.ng.bluemix.net

Email> human537@nate.com

Password>
Authenticating...
Credentials were rejected, please try again.

Password>
Authenticating...
OK

Targeted org jmyung

Select a space (or press enter to skip):
1. dev
2. qa
3. prod

Space> 1
Targeted space dev



API endpoint:   https://api.ng.bluemix.net (API version: 2.54.0)
User:           human537@nate.com
Org:            jmyung
Space:          dev

SDS@SDS-PC C:\Users\SDS
$ wsk
'wsk'은(는) 내부 또는 외부 명령, 실행할 수 있는 프로그램, 또는
배치 파일이 아닙니다.

SDS@SDS-PC C:\Users\SDS
$ cd c:\dev

SDS@SDS-PC c:\dev
$ wsk

        ____      ___                   _    _ _     _     _
       /\   \    / _ \ _ __   ___ _ __ | |  | | |__ (_)___| | __
  /\  /__\   \  | | | | '_ \ / _ \ '_ \| |  | | '_ \| / __| |/ /
 /  \____ \  /  | |_| | |_) |  __/ | | | |/\| | | | | \__ \   <
 \   \  /  \/    \___/| .__/ \___|_| |_|__/\__|_| |_|_|___/_|\_\
  \___\/ tm           |_|

Usage:
  wsk [command]

Available Commands:
  action           work with actions
  activation       work with activations
  package          work with packages
  rule             work with rules
  trigger          work with triggers
  sdk              work with the sdk
  property         work with whisk properties
  namespace        work with namespaces
  list             list entities in the current namespace
  api-experimental work with APIs (experimental)

Flags:
      --apihost HOST         whisk API HOST
      --apiversion VERSION   whisk API VERSION
  -u, --auth KEY             authorization KEY
  -d, --debug                debug level output
  -h, --help                 help for wsk
  -i, --insecure             bypass certificate checking
  -v, --verbose              verbose output

Use "wsk [command] --help" for more information about a command.

SDS@SDS-PC c:\dev
$







'Cloud > Bluemix' 카테고리의 다른 글

Cloud Foundry difference between Pivotal and IBM  (0) 2017.07.10
Bluemix 총정리  (0) 2017.04.20
Royal Bank of Canada's Journey  (0) 2017.04.20
chatbot  (0) 2017.04.19
Service & deployment  (0) 2017.04.18

업 특성상 public으로 가는것이 어렵다
2020?


클라우드로 갈때 망설이는 요소를 제거중


[Initial Tactical goal]


1. 개발기간이 얼마나 됐나?

- Agile로 가면 개발기간이 더 늘거 같은데


2. Increase test automation

- TDD : 테스트코드를 먼저 작성해서 개발했나?


3.

금융에서는

금융거래와 관련된 고객정보, 신용정보 에 대한 개인정보는 클라우드로 전환하지 못하게 법으로 규제하게있는데

클라우드로 전환하고 싶은 금융시스템은 정보(정보보호위원회)에 비중요시스템으로 심사를 받아, 허가되면 클라우드로 변경할 수 있게 돼있다

개인신용정보 송수신도 불가


[답변]

고객정보는 메인프레임안에 들어있고, 보안터널? 을 갖추고 있다


- 보안이라는게 방화벽 (Frontend, Backend방화벽)

- 패킷을 암호화(ISAM)

- TAI로 인증



속도?

- 패킷이 커진다



블루믹스 local인가?

on-prem과 다를게 없다고 보는데

- 싱글테넌트라 자원을 share못해서 autoscaling도 약하고? autoscaling 을 어떻게 할 수 있나?

   : sticky session

   : 관계사 간에 자원을 share할 수 있다

    (로컬간에 또는 로컬-dedicated 간에도 자원 share가능. but 정책적인 문제가 더 크다)

- 비용적인 부분도 비싸기 때문에

- 물론, IBM서비스를 이용해서 개발을 할 수 있는 장점은 있으나, 이외에


기존과 어떤 장점이 있는지?





단계적으로 전환다고 했을때 전환방법론???

'Cloud > Bluemix' 카테고리의 다른 글

Bluemix 총정리  (0) 2017.04.20
OpenWhisk  (0) 2017.04.20
chatbot  (0) 2017.04.19
Service & deployment  (0) 2017.04.18
translate  (0) 2017.04.17

chatbot

Cloud/Bluemix2017. 4. 19. 10:56

https://developer.ibm.com/kr/cloud/bluemix/watsonservice/2017/01/13/watsonchatbot-1-watson-conversation/



https://developer.ibm.com/kr/cloud/bluemix/watsonservice/2017/01/20/watsonchatbot-2-watson-conversation/



SDS@SDS-PC c:\dev
$ git checkout tutorial2
fatal: Not a git repository (or any of the parent directories): .git

SDS@SDS-PC c:\dev
$ cd chatbot-tutorial

SDS@SDS-PC c:\dev\chatbot-tutorial
$ git checkout tutorial2
Switched to a new branch 'tutorial2'
Branch tutorial2 set up to track remote branch tutorial2 from origin.

SDS@SDS-PC c:\dev\chatbot-tutorial
$
SDS@SDS-PC c:\dev\chatbot-tutorial
$
SDS@SDS-PC c:\dev\chatbot-tutorial
$ dir
 C 드라이브의 볼륨에는 이름이 없습니다.
 볼륨 일련 번호: 0660-5B61

 c:\dev\chatbot-tutorial 디렉터리

2017-04-19  오전 11:45    <DIR>          .
2017-04-19  오전 11:45    <DIR>          ..
2017-04-19  오전 11:44                69 .cfignore
2017-04-19  오전 11:50               403 .env.example
2017-04-19  오전 11:44                66 .gitignore
2017-04-19  오전 11:45    <DIR>          api
2017-04-19  오전 11:44             1,001 app.js
2017-04-19  오전 11:44               212 config.json
2017-04-19  오전 11:44            10,349 LICENSE
2017-04-19  오전 11:44               400 manifest.yml
2017-04-19  오전 11:45             1,336 package.json
2017-04-19  오전 11:44    <DIR>          public
2017-04-19  오전 11:44                18 README.md
2017-04-19  오전 11:44               918 server.js
2017-04-19  오전 11:45    <DIR>          solution
2017-04-19  오전 11:45    <DIR>          training
2017-04-19  오전 11:44    <DIR>          util
              10개 파일              14,772 바이트
               7개 디렉터리  24,520,294,400 바이트 남음

SDS@SDS-PC c:\dev\chatbot-tutorial
$ type package.json
{
  "name": "conversation-simple",
  "description": "A simple Node.js based web app which shows how to use the Conv
  "version": "0.1.1",
  "main": "server.js",
  "scripts": {
    "start": "node server.js",
    "test-integration": "casperjs test ./test/integration/test.*.js",
    "test-integration-runner": "NODE_ENV=test node casper-runner.js",
    "test": "npm run lint && npm run test-unit && npm run test-integration-runne
    "test-unit": "istanbul cover ./node_modules/mocha/bin/_mocha test/unit",
    "lint": "eslint .",
    "autofix": "eslint --fix .",
    "codecov": "npm run test && (codecov || true)"
  },
  "repository": {
    "type": "git",
    "url": "https://github.com/watson-developer-cloud/conversation-simple.git"
  },
  "license": "Apache-2.0",
  "dependencies": {
    "body-parser": "^1.15.2",
    "cfenv": "*",
    "cloudant": "1.6.x",
    "dotenv": "^2.0.0",
    "express": "^4.14.0",
    "moment": "^2.17.1"
  },
  "devDependencies": {
    "babel-eslint": "^6.0.4",
    "casperjs": "^1.1.3",
    "codecov": "^1.0.1",
    "eslint": "^2.8.0",
    "istanbul": "^0.4.2",
    "mocha": "^2.4.5",
    "phantomjs-prebuilt": "^2.1.13",
    "supertest": "^1.2.0"
  },
  "engine": {
    "node": ">= 6.9.x",
    "npm": "> 3.10.x"
  }
}

SDS@SDS-PC c:\dev\chatbot-tutorial
$ npm install
npm WARN deprecated node-uuid@1.4.8: Use uuid module instead
npm WARN deprecated graceful-fs@1.2.3: graceful-fs v3.0.0 and before will fail oo find it in the tree.
npm WARN deprecated to-iso-string@0.0.2: to-iso-string has been deprecated, use npm WARN deprecated jade@0.26.3: Jade has been renamed to pug, please install thnpm WARN deprecated minimatch@0.3.0: Please update to minimatch 3.0.2 or higher

> execSync@1.0.2 install c:\dev\chatbot-tutorial\node_modules\execSync
> node install.js

[execsync v1.0.2] Attempting to compile native extensions.
{ Error: spawn node-gyp ENOENT
    at exports._errnoException (util.js:1022:11)
    at Process.ChildProcess._handle.onexit (internal/child_process.js:193:32)
    at onErrorNT (internal/child_process.js:359:16)
    at _combinedTickCallback (internal/process/next_tick.js:74:11)
    at process._tickCallback (internal/process/next_tick.js:98:9)
    at Module.runMain (module.js:606:11)
    at run (bootstrap_node.js:394:7)
    at startup (bootstrap_node.js:149:9)
    at bootstrap_node.js:509:3
  code: 'ENOENT',
  errno: 'ENOENT',
  syscall: 'spawn node-gyp',
  path: 'node-gyp',
  spawnargs: [ 'rebuild' ] }
[execSync v1.0.2]
    Native code compile failed!!
    Will try to use win32 extension.

> phantomjs-prebuilt@2.1.14 install c:\dev\chatbot-tutorial\node_modules\phantom> node install.js

PhantomJS not found on PATH
Downloading https://github.com/Medium/phantomjs/releases/download/v2.1.1/phantomSaving to C:\Users\SDS\AppData\Local\Temp\phantomjs\phantomjs-2.1.1-windows.zip Receiving...
  [=======================================-] 98%
Received 17767K total.
Extracting zip contents
Removing c:\dev\chatbot-tutorial\node_modules\phantomjs-prebuilt\lib\phantom
Copying extracted folder C:\Users\SDS\AppData\Local\Temp\phantomjs\phantomjs-2.1js-prebuilt\lib\phantom
Writing location.js file
Done. Phantomjs binary available at c:\dev\chatbot-tutorial\node_modules\phantomconversation-simple@0.1.1 c:\dev\chatbot-tutorial
+-- babel-eslint@6.1.2
| +-- babel-traverse@6.24.1
| | +-- babel-code-frame@6.22.0
| | | `-- js-tokens@3.0.1
| | +-- babel-messages@6.23.0
| | +-- babel-runtime@6.23.0
| | | +-- core-js@2.4.1
| | | `-- regenerator-runtime@0.10.3
| | `-- invariant@2.2.2
| |   `-- loose-envify@1.3.1
| +-- babel-types@6.24.1
| | `-- to-fast-properties@1.0.2
| +-- babylon@6.16.1
| +-- lodash.assign@4.2.0
| `-- lodash.pickby@4.6.0
+-- body-parser@1.17.1
| +-- bytes@2.4.0
| +-- content-type@1.0.2
| +-- debug@2.6.1
| | `-- ms@0.7.2
| +-- depd@1.1.0
| +-- http-errors@1.6.1
| | `-- inherits@2.0.3
| +-- iconv-lite@0.4.15
| +-- on-finished@2.3.0
| | `-- ee-first@1.1.1
| +-- qs@6.4.0
| +-- raw-body@2.2.0
| | `-- unpipe@1.0.0
| `-- type-is@1.6.15
|   +-- media-typer@0.3.0
|   `-- mime-types@2.1.15
|     `-- mime-db@1.27.0
+-- casperjs@1.1.3
+-- cfenv@1.0.4
| +-- js-yaml@3.7.0
| | `-- argparse@1.0.9
| |   `-- sprintf-js@1.0.3
| +-- ports@1.1.0
| `-- underscore@1.8.3
+-- cloudant@1.6.2
| +-- async@2.1.2
| +-- cloudant-nano@6.4.1
| | +-- errs@0.3.2
| | `-- follow@0.12.1
| |   +-- browser-request@0.3.3
| |   `-- request@2.55.0
| |     +-- aws-sign2@0.5.0
| |     +-- bl@0.9.5
| |     | `-- readable-stream@1.0.34
| |     +-- caseless@0.9.0
| |     +-- combined-stream@0.0.7
| |     | `-- delayed-stream@0.0.5
| |     +-- form-data@0.2.0
| |     | +-- async@0.9.2
| |     | `-- mime-types@2.0.14
| |     |   `-- mime-db@1.12.0
| |     +-- har-validator@1.8.0
| |     | `-- bluebird@2.11.0
| |     +-- hawk@2.3.1
| |     +-- http-signature@0.10.1
| |     | +-- asn1@0.1.11
| |     | +-- assert-plus@0.1.5
| |     | `-- ctype@0.5.3
| |     +-- mime-types@2.0.14
| |     | `-- mime-db@1.12.0
| |     +-- oauth-sign@0.6.0
| |     `-- qs@2.4.2
| +-- debug@2.2.0
| | `-- ms@0.7.1
| `-- request@2.76.0
|   +-- aws-sign2@0.6.0
|   +-- aws4@1.6.0
|   +-- caseless@0.11.0
|   +-- combined-stream@1.0.5
|   | `-- delayed-stream@1.0.0
|   +-- extend@3.0.0
|   +-- forever-agent@0.6.1
|   +-- form-data@2.1.4
|   | `-- asynckit@0.4.0
|   +-- har-validator@2.0.6
|   | `-- commander@2.9.0
|   |   `-- graceful-readlink@1.0.1
|   +-- hawk@3.1.3
|   | +-- boom@2.10.1
|   | +-- cryptiles@2.0.5
|   | +-- hoek@2.16.3
|   | `-- sntp@1.0.9
|   +-- http-signature@1.1.1
|   | +-- assert-plus@0.2.0
|   | +-- jsprim@1.4.0
|   | | +-- assert-plus@1.0.0
|   | | +-- extsprintf@1.0.2
|   | | +-- json-schema@0.2.3
|   | | `-- verror@1.3.6
|   | `-- sshpk@1.13.0
|   |   +-- asn1@0.2.3
|   |   +-- assert-plus@1.0.0
|   |   +-- bcrypt-pbkdf@1.0.1
|   |   +-- dashdash@1.14.1
|   |   | `-- assert-plus@1.0.0
|   |   +-- ecc-jsbn@0.1.1
|   |   +-- getpass@0.1.6
|   |   | `-- assert-plus@1.0.0
|   |   +-- jodid25519@1.0.2
|   |   +-- jsbn@0.1.1
|   |   `-- tweetnacl@0.14.5
|   +-- is-typedarray@1.0.0
|   +-- isstream@0.1.2
|   +-- json-stringify-safe@5.0.1
|   +-- node-uuid@1.4.8
|   +-- oauth-sign@0.8.2
|   +-- qs@6.3.2
|   +-- stringstream@0.0.5
|   +-- tough-cookie@2.3.2
|   | `-- punycode@1.4.1
|   `-- tunnel-agent@0.4.3
+-- codecov@1.0.1
| +-- argv@0.0.2
| +-- execSync@1.0.2
| | `-- temp@0.5.1
| |   `-- rimraf@2.1.4
| |     `-- graceful-fs@1.2.3
| `-- urlgrey@0.4.4
+-- dotenv@2.0.0
+-- eslint@2.13.1
| +-- chalk@1.1.3
| | +-- ansi-styles@2.2.1
| | +-- escape-string-regexp@1.0.5
| | +-- has-ansi@2.0.0
| | +-- strip-ansi@3.0.1
| | `-- supports-color@2.0.0
| +-- concat-stream@1.6.0
| | +-- readable-stream@2.2.9
| | | +-- buffer-shims@1.0.0
| | | +-- core-util-is@1.0.2
| | | +-- isarray@1.0.0
| | | +-- process-nextick-args@1.0.7
| | | +-- string_decoder@1.0.0
| | | `-- util-deprecate@1.0.2
| | `-- typedarray@0.0.6
| +-- doctrine@1.5.0
| | `-- isarray@1.0.0
| +-- es6-map@0.1.5
| | +-- d@1.0.0
| | +-- es5-ext@0.10.15
| | +-- es6-iterator@2.0.1
| | +-- es6-set@0.1.5
| | +-- es6-symbol@3.1.1
| | `-- event-emitter@0.3.5
| +-- escope@3.6.0
| | +-- es6-weak-map@2.0.2
| | `-- esrecurse@4.1.0
| |   `-- estraverse@4.1.1
| +-- espree@3.4.1
| | +-- acorn@5.0.3
| | `-- acorn-jsx@3.0.1
| |   `-- acorn@3.3.0
| +-- estraverse@4.2.0
| +-- esutils@2.0.2
| +-- file-entry-cache@1.3.1
| | +-- flat-cache@1.2.2
| | | +-- circular-json@0.3.1
| | | +-- del@2.2.2
| | | | +-- globby@5.0.0
| | | | | +-- array-union@1.0.2
| | | | | | `-- array-uniq@1.0.3
| | | | | `-- arrify@1.0.1
| | | | +-- is-path-cwd@1.0.0
| | | | +-- is-path-in-cwd@1.0.0
| | | | | `-- is-path-inside@1.0.0
| | | | +-- pify@2.3.0
| | | | `-- rimraf@2.6.1
| | | +-- graceful-fs@4.1.11
| | | `-- write@0.2.1
| | `-- object-assign@4.1.1
| +-- glob@7.1.1
| | +-- fs.realpath@1.0.0
| | +-- inflight@1.0.6
| | `-- minimatch@3.0.3
| |   `-- brace-expansion@1.1.7
| |     +-- balanced-match@0.4.2
| |     `-- concat-map@0.0.1
| +-- globals@9.17.0
| +-- ignore@3.2.7
| +-- imurmurhash@0.1.4
| +-- inquirer@0.12.0
| | +-- ansi-escapes@1.4.0
| | +-- ansi-regex@2.1.1
| | +-- cli-cursor@1.0.2
| | | `-- restore-cursor@1.0.1
| | |   +-- exit-hook@1.1.1
| | |   `-- onetime@1.1.0
| | +-- cli-width@2.1.0
| | +-- figures@1.7.0
| | +-- readline2@1.0.1
| | | +-- code-point-at@1.1.0
| | | +-- is-fullwidth-code-point@1.0.0
| | | | `-- number-is-nan@1.0.1
| | | `-- mute-stream@0.0.5
| | +-- run-async@0.1.0
| | +-- rx-lite@3.1.2
| | +-- string-width@1.0.2
| | `-- through@2.3.8
| +-- is-my-json-valid@2.16.0
| | +-- generate-function@2.0.0
| | +-- generate-object-property@1.2.0
| | | `-- is-property@1.0.2
| | +-- jsonpointer@4.0.1
| | `-- xtend@4.0.1
| +-- is-resolvable@1.0.0
| | `-- tryit@1.0.3
| +-- json-stable-stringify@1.0.1
| | `-- jsonify@0.0.0
| +-- levn@0.3.0
| | +-- prelude-ls@1.1.2
| | `-- type-check@0.3.2
| +-- lodash@4.17.4
| +-- mkdirp@0.5.1
| | `-- minimist@0.0.8
| +-- optionator@0.8.2
| | +-- deep-is@0.1.3
| | `-- fast-levenshtein@2.0.6
| +-- path-is-absolute@1.0.1
| +-- path-is-inside@1.0.2
| +-- pluralize@1.2.1
| +-- progress@1.1.8
| +-- require-uncached@1.0.3
| | +-- caller-path@0.1.0
| | | `-- callsites@0.2.0
| | `-- resolve-from@1.0.1
| +-- shelljs@0.6.1
| +-- strip-json-comments@1.0.4
| +-- table@3.8.3
| | +-- ajv@4.11.7
| | | `-- co@4.6.0
| | +-- ajv-keywords@1.5.1
| | +-- slice-ansi@0.0.4
| | `-- string-width@2.0.0
| |   `-- is-fullwidth-code-point@2.0.0
| +-- text-table@0.2.0
| `-- user-home@2.0.0
|   `-- os-homedir@1.0.2
+-- express@4.15.2
| +-- accepts@1.3.3
| | `-- negotiator@0.6.1
| +-- array-flatten@1.1.1
| +-- content-disposition@0.5.2
| +-- cookie@0.3.1
| +-- cookie-signature@1.0.6
| +-- encodeurl@1.0.1
| +-- escape-html@1.0.3
| +-- etag@1.8.0
| +-- finalhandler@1.0.1
| | `-- debug@2.6.3
| +-- fresh@0.5.0
| +-- merge-descriptors@1.0.1
| +-- methods@1.1.2
| +-- parseurl@1.3.1
| +-- path-to-regexp@0.1.7
| +-- proxy-addr@1.1.4
| | +-- forwarded@0.1.0
| | `-- ipaddr.js@1.3.0
| +-- range-parser@1.2.0
| +-- send@0.15.1
| | +-- destroy@1.0.4
| | `-- mime@1.3.4
| +-- serve-static@1.12.1
| +-- setprototypeof@1.0.3
| +-- statuses@1.3.1
| +-- utils-merge@1.0.0
| `-- vary@1.1.1
+-- istanbul@0.4.5
| +-- abbrev@1.0.9
| +-- async@1.5.2
| +-- escodegen@1.8.1
| | +-- estraverse@1.9.3
| | `-- source-map@0.2.0
| |   `-- amdefine@1.0.1
| +-- esprima@2.7.3
| +-- glob@5.0.15
| +-- handlebars@4.0.6
| | +-- async@1.5.2
| | +-- optimist@0.6.1
| | | `-- wordwrap@0.0.3
| | +-- source-map@0.4.4
| | `-- uglify-js@2.8.22
| |   +-- source-map@0.5.6
| |   +-- uglify-to-browserify@1.0.2
| |   `-- yargs@3.10.0
| |     +-- camelcase@1.2.1
| |     +-- cliui@2.1.0
| |     | +-- center-align@0.1.3
| |     | | +-- align-text@0.1.4
| |     | | | +-- kind-of@3.1.0
| |     | | | | `-- is-buffer@1.1.5
| |     | | | +-- longest@1.0.1
| |     | | | `-- repeat-string@1.6.1
| |     | | `-- lazy-cache@1.0.4
| |     | +-- right-align@0.1.3
| |     | `-- wordwrap@0.0.2
| |     +-- decamelize@1.2.0
| |     `-- window-size@0.1.0
| +-- nopt@3.0.6
| +-- once@1.4.0
| | `-- wrappy@1.0.2
| +-- resolve@1.1.7
| +-- supports-color@3.2.3
| | `-- has-flag@1.0.0
| +-- which@1.2.14
| | `-- isexe@2.0.0
| `-- wordwrap@1.0.0
+-- mocha@2.5.3
| +-- commander@2.3.0
| +-- debug@2.2.0
| | `-- ms@0.7.1
| +-- diff@1.4.0
| +-- escape-string-regexp@1.0.2
| +-- glob@3.2.11
| | `-- minimatch@0.3.0
| |   +-- lru-cache@2.7.3
| |   `-- sigmund@1.0.1
| +-- growl@1.9.2
| +-- jade@0.26.3
| | +-- commander@0.6.1
| | `-- mkdirp@0.3.0
| +-- supports-color@1.2.0
| `-- to-iso-string@0.0.2
+-- moment@2.18.1
+-- phantomjs-prebuilt@2.1.14
| +-- es6-promise@4.0.5
| +-- extract-zip@1.5.0
| | +-- concat-stream@1.5.0
| | | `-- readable-stream@2.0.6
| | |   `-- isarray@1.0.0
| | +-- debug@0.7.4
| | +-- mkdirp@0.5.0
| | `-- yauzl@2.4.1
| |   `-- fd-slicer@1.0.1
| |     `-- pend@1.2.0
| +-- fs-extra@1.0.0
| | +-- graceful-fs@4.1.11
| | +-- jsonfile@2.4.0
| | | `-- graceful-fs@4.1.11
| | `-- klaw@1.3.1
| |   `-- graceful-fs@4.1.11
| +-- hasha@2.2.0
| | +-- is-stream@1.1.0
| | `-- pinkie-promise@2.0.1
| |   `-- pinkie@2.0.4
| +-- kew@0.7.0
| +-- request@2.79.0
| | +-- aws-sign2@0.6.0
| | +-- caseless@0.11.0
| | +-- combined-stream@1.0.5
| | | `-- delayed-stream@1.0.0
| | +-- form-data@2.1.4
| | +-- har-validator@2.0.6
| | +-- hawk@3.1.3
| | +-- http-signature@1.1.1
| | | `-- assert-plus@0.2.0
| | +-- oauth-sign@0.8.2
| | +-- qs@6.3.2
| | `-- uuid@3.0.1
| `-- request-progress@2.0.1
|   `-- throttleit@1.0.0
`-- supertest@1.2.0
  `-- superagent@1.8.5
    +-- component-emitter@1.2.1
    +-- cookiejar@2.0.6
    +-- form-data@1.0.0-rc3
    | +-- async@1.5.2
    | `-- combined-stream@1.0.5
    |   `-- delayed-stream@1.0.0
    +-- formidable@1.0.17
    +-- qs@2.3.3
    +-- readable-stream@1.0.27-1
    | +-- isarray@0.0.1
    | `-- string_decoder@0.10.31
    `-- reduce-component@1.0.1


SDS@SDS-PC c:\dev\chatbot-tutorial
$
SDS@SDS-PC c:\dev\chatbot-tutorial
$
SDS@SDS-PC c:\dev\chatbot-tutorial
$ npm install watson-developer-cloud --save

> websocket@1.0.24 install c:\dev\chatbot-tutorial\node_modules\websocket
> (node-gyp rebuild 2> builderror.log) || (exit 0)


SDS@SDS-PC c:\dev\chatbot-tutorial\node_modules\websocket
$ if not defined npm_config_node_gyp (node "C:\Program Files\nodejs\node_modulesBuilding the projects in this solution one at a time. To enable parallel build, MSBUILD : error MSB3428: Visual C++ 구성 요소 "VCBuild.exe"을(를) 로드할 수 없습
거나, 3) 해당 구성 요소가 다른 위치에 설치되어 있는 경
우에는 그 위치를 시스템 경로에 추가하십시오.  [c:\dev\chatbot-tutorial\node_modu
MSBUILD : error MSB3428: Visual C++ 구성 요소 "VCBuild.exe"을(를) 로드할 수 없습
거나, 3) 해당 구성 요소가 다른 위치에 설치되어 있는 경
우에는 그 위치를 시스템 경로에 추가하십시오.  [c:\dev\chatbot-tutorial\node_modu
conversation-simple@0.1.1 c:\dev\chatbot-tutorial
`-- watson-developer-cloud@2.29.0
  +-- buffer-from@0.1.1
  | `-- is-array-buffer-x@1.2.1
  |   +-- has-to-string-tag-x@1.2.0
  |   | `-- has-symbol-support-x@1.2.0
  |   +-- is-object-like-x@1.2.0
  |   | +-- is-function-x@1.2.0
  |   | `-- is-primitive@2.0.0
  |   `-- to-string-tag-x@1.2.0
  |     +-- lodash.isnull@3.0.0
  |     `-- validate.io-undefined@1.0.3
  +-- csv-stringify@1.0.4
  | `-- lodash.get@4.4.2
  +-- object.omit@2.0.1
  | +-- for-own@0.1.5
  | | `-- for-in@1.0.2
  | `-- is-extendable@0.1.1
  +-- object.pick@1.2.0
  | `-- isobject@2.1.0
  |   `-- isarray@1.0.0
  +-- request@2.81.0
  | +-- aws-sign2@0.6.0
  | +-- caseless@0.12.0
  | +-- combined-stream@1.0.5
  | | `-- delayed-stream@1.0.0
  | +-- form-data@2.1.4
  | +-- har-validator@4.2.1
  | | `-- har-schema@1.0.5
  | +-- hawk@3.1.3
  | +-- http-signature@1.1.1
  | | `-- assert-plus@0.2.0
  | +-- oauth-sign@0.8.2
  | +-- performance-now@0.2.0
  | +-- safe-buffer@5.0.1
  | +-- tunnel-agent@0.6.0
  | `-- uuid@3.0.1
  +-- solr-client@0.6.0
  | +-- duplexer@0.1.1
  | +-- httperror@0.2.3
  | | `-- hnp@0.0.1
  | +-- json-bigint@0.1.4
  | | `-- bignumber.js@1.1.1
  | +-- JSONStream@1.0.7
  | | `-- jsonparse@1.3.0
  | `-- request@2.63.0
  |   +-- bl@1.0.3
  |   | `-- readable-stream@2.0.6
  |   |   `-- isarray@1.0.0
  |   +-- caseless@0.11.0
  |   +-- combined-stream@1.0.5
  |   | `-- delayed-stream@1.0.0
  |   +-- form-data@1.0.1
  |   +-- hawk@3.1.3
  |   +-- http-signature@0.11.0
  |   +-- oauth-sign@0.8.2
  |   `-- qs@5.1.0
  +-- string@3.3.3
  +-- vcap_services@0.3.4
  `-- websocket@1.0.24
    +-- nan@2.6.2
    +-- typedarray-to-buffer@3.1.2
    `-- yaeti@0.0.6


SDS@SDS-PC c:\dev\chatbot-tutorial
$ npm start

> conversation-simple@0.1.1 start c:\dev\chatbot-tutorial
> node server.js

APIs initialize
c:\dev\chatbot-tutorial\node_modules\watson-developer-cloud\lib\base_service.js:
      throw new Error('Argument error: username and password are required unless
      ^

Error: Argument error: username and password are required unless use_unauthentic
    at ConversationV1.BaseService.initCredentials (c:\dev\chatbot-tutorial\node_
    at ConversationV1.BaseService (c:\dev\chatbot-tutorial\node_modules\watson-d
    at new ConversationV1 (c:\dev\chatbot-tutorial\node_modules\watson-developer
    at Object.<anonymous> (c:\dev\chatbot-tutorial\api\message.js:23:20)
    at Module._compile (module.js:570:32)
    at Object.Module._extensions..js (module.js:579:10)
    at Module.load (module.js:487:32)
    at tryModuleLoad (module.js:446:12)
    at Function.Module._load (module.js:438:3)
    at Module.require (module.js:497:17)

npm ERR! Windows_NT 6.1.7601
npm ERR! argv "C:\\Program Files\\nodejs\\node.exe" "C:\\Program Files\\nodejs\\npm ERR! node v6.9.4
npm ERR! npm  v3.10.10
npm ERR! code ELIFECYCLE
npm ERR! conversation-simple@0.1.1 start: `node server.js`
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the conversation-simple@0.1.1 start script 'node server.js'. npm ERR! Make sure you have the latest version of node.js and npm installed.
npm ERR! If you do, this is most likely a problem with the conversation-simple pnpm ERR! not with npm itself.
npm ERR! Tell the author that this fails on your system:
npm ERR!     node server.js
npm ERR! You can get information on how to open an issue for this project with: npm ERR!     npm bugs conversation-simple
npm ERR! Or if that isn't available, you can get their info via:
npm ERR!     npm owner ls conversation-simple
npm ERR! There is likely additional logging output above.

npm ERR! Please include the following file with any support request:
npm ERR!     c:\dev\chatbot-tutorial\npm-debug.log

SDS@SDS-PC c:\dev\chatbot-tutorial
$
SDS@SDS-PC c:\dev\chatbot-tutorial
$
SDS@SDS-PC c:\dev\chatbot-tutorial
$
SDS@SDS-PC c:\dev\chatbot-tutorial
$ npm install

SDS@SDS-PC c:\dev\chatbot-tutorial
$ dir
 C 드라이브의 볼륨에는 이름이 없습니다.
 볼륨 일련 번호: 0660-5B61

 c:\dev\chatbot-tutorial 디렉터리

2017-04-19  오후 12:00    <DIR>          .
2017-04-19  오후 12:00    <DIR>          ..
2017-04-19  오전 11:44                69 .cfignore
2017-04-19  오전 11:50               403 .env.example
2017-04-19  오전 11:44                66 .gitignore
2017-04-19  오전 11:45    <DIR>          api
2017-04-19  오전 11:44             1,001 app.js
2017-04-19  오전 11:44               212 config.json
2017-04-19  오전 11:44            10,349 LICENSE
2017-04-19  오전 11:44               400 manifest.yml
2017-04-19  오후 12:00    <DIR>          node_modules
2017-04-19  오전 11:55             1,334 package.json
2017-04-19  오전 11:44    <DIR>          public
2017-04-19  오전 11:44                18 README.md
2017-04-19  오전 11:44               918 server.js
2017-04-19  오전 11:45    <DIR>          solution
2017-04-19  오전 11:45    <DIR>          training
2017-04-19  오전 11:44    <DIR>          util
              10개 파일              14,770 바이트
               8개 디렉터리  24,384,790,528 바이트 남음

SDS@SDS-PC c:\dev\chatbot-tutorial
$ cd ..

SDS@SDS-PC c:\dev
$ dir
 C 드라이브의 볼륨에는 이름이 없습니다.
 볼륨 일련 번호: 0660-5B61

 c:\dev 디렉터리

2017-04-19  오전 11:44    <DIR>          .
2017-04-19  오전 11:44    <DIR>          ..
2017-03-29  오전 09:35    <DIR>          apache-maven-3.3.9
2017-01-03  오후 04:31    <DIR>          apache-tomcat-7.0.73
2017-04-03  오후 02:07    <DIR>          bluemix-integration-lab
2017-04-19  오후 12:00    <DIR>          chatbot-tutorial
2017-04-06  오후 09:15        49,778,258 Faro.war
2017-04-11  오전 10:02    <DIR>          Microservices_UI
2017-04-05  오전 11:28             4,236 SAN.pem
2017-04-04  오전 12:12    <DIR>          wlp
               2개 파일          49,782,494 바이트
               8개 디렉터리  24,384,770,048 바이트 남음

SDS@SDS-PC c:\dev
$ cd chatbot-tutorial

SDS@SDS-PC c:\dev\chatbot-tutorial
$ dir
 C 드라이브의 볼륨에는 이름이 없습니다.
 볼륨 일련 번호: 0660-5B61

 c:\dev\chatbot-tutorial 디렉터리

2017-04-19  오후 12:00    <DIR>          .
2017-04-19  오후 12:00    <DIR>          ..
2017-04-19  오전 11:44                69 .cfignore
2017-04-19  오전 11:50               403 .env.example
2017-04-19  오전 11:44                66 .gitignore
2017-04-19  오전 11:45    <DIR>          api
2017-04-19  오전 11:44             1,001 app.js
2017-04-19  오전 11:44               212 config.json
2017-04-19  오전 11:44            10,349 LICENSE
2017-04-19  오전 11:44               400 manifest.yml
2017-04-19  오후 12:00    <DIR>          node_modules
2017-04-19  오전 11:55             1,334 package.json
2017-04-19  오전 11:44    <DIR>          public
2017-04-19  오전 11:44                18 README.md
2017-04-19  오전 11:44               918 server.js
2017-04-19  오전 11:45    <DIR>          solution
2017-04-19  오전 11:45    <DIR>          training
2017-04-19  오전 11:44    <DIR>          util
              10개 파일              14,770 바이트
               8개 디렉터리  24,384,770,048 바이트 남음

SDS@SDS-PC c:\dev\chatbot-tutorial
$
SDS@SDS-PC c:\dev\chatbot-tutorial
$
SDS@SDS-PC c:\dev\chatbot-tutorial
$
SDS@SDS-PC c:\dev\chatbot-tutorial
$ dir
 C 드라이브의 볼륨에는 이름이 없습니다.
 볼륨 일련 번호: 0660-5B61

 c:\dev\chatbot-tutorial 디렉터리

2017-04-19  오후 12:00    <DIR>          .
2017-04-19  오후 12:00    <DIR>          ..
2017-04-19  오전 11:44                69 .cfignore
2017-04-19  오전 11:50               403 .env.example
2017-04-19  오전 11:44                66 .gitignore
2017-04-19  오전 11:45    <DIR>          api
2017-04-19  오전 11:44             1,001 app.js
2017-04-19  오전 11:44               212 config.json
2017-04-19  오전 11:44            10,349 LICENSE
2017-04-19  오전 11:44               400 manifest.yml
2017-04-19  오후 12:00    <DIR>          node_modules
2017-04-19  오전 11:55             1,334 package.json
2017-04-19  오전 11:44    <DIR>          public
2017-04-19  오전 11:44                18 README.md
2017-04-19  오전 11:44               918 server.js
2017-04-19  오전 11:45    <DIR>          solution
2017-04-19  오전 11:45    <DIR>          training
2017-04-19  오전 11:44    <DIR>          util
              10개 파일              14,770 바이트
               8개 디렉터리  24,384,679,936 바이트 남음

SDS@SDS-PC c:\dev\chatbot-tutorial
$ npm start

> conversation-simple@0.1.1 start c:\dev\chatbot-tutorial
> node server.js

APIs initialize
c:\dev\chatbot-tutorial\node_modules\watson-developer-cloud\lib\base_service.js:
      throw new Error('Argument error: username and password are required unless
      ^

Error: Argument error: username and password are required unless use_unauthentic
    at ConversationV1.BaseService.initCredentials (c:\dev\chatbot-tutorial\node_
    at ConversationV1.BaseService (c:\dev\chatbot-tutorial\node_modules\watson-d
    at new ConversationV1 (c:\dev\chatbot-tutorial\node_modules\watson-developer
    at Object.<anonymous> (c:\dev\chatbot-tutorial\api\message.js:23:20)
    at Module._compile (module.js:570:32)
    at Object.Module._extensions..js (module.js:579:10)
    at Module.load (module.js:487:32)
    at tryModuleLoad (module.js:446:12)
    at Function.Module._load (module.js:438:3)
    at Module.require (module.js:497:17)

npm ERR! Windows_NT 6.1.7601
npm ERR! argv "C:\\Program Files\\nodejs\\node.exe" "C:\\Program Files\\nodejs\\npm ERR! node v6.9.4
npm ERR! npm  v3.10.10
npm ERR! code ELIFECYCLE
npm ERR! conversation-simple@0.1.1 start: `node server.js`
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the conversation-simple@0.1.1 start script 'node server.js'. npm ERR! Make sure you have the latest version of node.js and npm installed.
npm ERR! If you do, this is most likely a problem with the conversation-simple pnpm ERR! not with npm itself.
npm ERR! Tell the author that this fails on your system:
npm ERR!     node server.js
npm ERR! You can get information on how to open an issue for this project with: npm ERR!     npm bugs conversation-simple
npm ERR! Or if that isn't available, you can get their info via:
npm ERR!     npm owner ls conversation-simple
npm ERR! There is likely additional logging output above.

npm ERR! Please include the following file with any support request:
npm ERR!     c:\dev\chatbot-tutorial\npm-debug.log

SDS@SDS-PC c:\dev\chatbot-tutorial
$ C:\dev\chatbot-tutorial\.env.example ^Z

SDS@SDS-PC c:\dev\chatbot-tutorial
$ npm start

> conversation-simple@0.1.1 start c:\dev\chatbot-tutorial
> node server.js

APIs initialize
c:\dev\chatbot-tutorial\node_modules\watson-developer-cloud\lib\base_service.js:
      throw new Error('Argument error: username and password are required unless
      ^

Error: Argument error: username and password are required unless use_unauthentic
    at ConversationV1.BaseService.initCredentials (c:\dev\chatbot-tutorial\node_
    at ConversationV1.BaseService (c:\dev\chatbot-tutorial\node_modules\watson-d
    at new ConversationV1 (c:\dev\chatbot-tutorial\node_modules\watson-developer
    at Object.<anonymous> (c:\dev\chatbot-tutorial\api\message.js:23:20)
    at Module._compile (module.js:570:32)
    at Object.Module._extensions..js (module.js:579:10)
    at Module.load (module.js:487:32)
    at tryModuleLoad (module.js:446:12)
    at Function.Module._load (module.js:438:3)
    at Module.require (module.js:497:17)

npm ERR! Windows_NT 6.1.7601
npm ERR! argv "C:\\Program Files\\nodejs\\node.exe" "C:\\Program Files\\nodejs\\npm ERR! node v6.9.4
npm ERR! npm  v3.10.10
npm ERR! code ELIFECYCLE
npm ERR! conversation-simple@0.1.1 start: `node server.js`
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the conversation-simple@0.1.1 start script 'node server.js'. npm ERR! Make sure you have the latest version of node.js and npm installed.
npm ERR! If you do, this is most likely a problem with the conversation-simple pnpm ERR! not with npm itself.
npm ERR! Tell the author that this fails on your system:
npm ERR!     node server.js
npm ERR! You can get information on how to open an issue for this project with: npm ERR!     npm bugs conversation-simple
npm ERR! Or if that isn't available, you can get their info via:
npm ERR!     npm owner ls conversation-simple
npm ERR! There is likely additional logging output above.

npm ERR! Please include the following file with any support request:
npm ERR!     c:\dev\chatbot-tutorial\npm-debug.log

SDS@SDS-PC c:\dev\chatbot-tutorial
$ npm install

SDS@SDS-PC c:\dev\chatbot-tutorial
$ npm start

> conversation-simple@0.1.1 start c:\dev\chatbot-tutorial
> node server.js

APIs initialize
c:\dev\chatbot-tutorial\node_modules\watson-developer-cloud\lib\base_service.js:
      throw new Error('Argument error: username and password are required unless
      ^

Error: Argument error: username and password are required unless use_unauthentic
    at ConversationV1.BaseService.initCredentials (c:\dev\chatbot-tutorial\node_
    at ConversationV1.BaseService (c:\dev\chatbot-tutorial\node_modules\watson-d
    at new ConversationV1 (c:\dev\chatbot-tutorial\node_modules\watson-developer
    at Object.<anonymous> (c:\dev\chatbot-tutorial\api\message.js:23:20)
    at Module._compile (module.js:570:32)
    at Object.Module._extensions..js (module.js:579:10)
    at Module.load (module.js:487:32)
    at tryModuleLoad (module.js:446:12)
    at Function.Module._load (module.js:438:3)
    at Module.require (module.js:497:17)

npm ERR! Windows_NT 6.1.7601
npm ERR! argv "C:\\Program Files\\nodejs\\node.exe" "C:\\Program Files\\nodejs\\npm ERR! node v6.9.4
npm ERR! npm  v3.10.10
npm ERR! code ELIFECYCLE
npm ERR! conversation-simple@0.1.1 start: `node server.js`
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the conversation-simple@0.1.1 start script 'node server.js'. npm ERR! Make sure you have the latest version of node.js and npm installed.
npm ERR! If you do, this is most likely a problem with the conversation-simple pnpm ERR! not with npm itself.
npm ERR! Tell the author that this fails on your system:
npm ERR!     node server.js
npm ERR! You can get information on how to open an issue for this project with: npm ERR!     npm bugs conversation-simple
npm ERR! Or if that isn't available, you can get their info via:
npm ERR!     npm owner ls conversation-simple
npm ERR! There is likely additional logging output above.

npm ERR! Please include the following file with any support request:
npm ERR!     c:\dev\chatbot-tutorial\npm-debug.log

SDS@SDS-PC c:\dev\chatbot-tutorial
$ dir
 C 드라이브의 볼륨에는 이름이 없습니다.
 볼륨 일련 번호: 0660-5B61

 c:\dev\chatbot-tutorial 디렉터리

2017-04-19  오후 12:06    <DIR>          .
2017-04-19  오후 12:06    <DIR>          ..
2017-04-19  오전 11:44                69 .cfignore
2017-04-19  오후 12:05               388 .env - 복사본.example
2017-04-19  오후 12:05               388 .env.example
2017-04-19  오전 11:44                66 .gitignore
2017-04-19  오전 11:45    <DIR>          api
2017-04-19  오전 11:44             1,001 app.js
2017-04-19  오전 11:44               212 config.json
2017-04-19  오전 11:44            10,349 LICENSE
2017-04-19  오전 11:44               400 manifest.yml
2017-04-19  오후 12:05    <DIR>          node_modules
2017-04-19  오후 12:05             4,006 npm-debug.log
2017-04-19  오전 11:55             1,334 package.json
2017-04-19  오전 11:44    <DIR>          public
2017-04-19  오전 11:44                18 README.md
2017-04-19  오전 11:44               918 server.js
2017-04-19  오전 11:45    <DIR>          solution
2017-04-19  오전 11:45    <DIR>          training
2017-04-19  오전 11:44    <DIR>          util
              12개 파일              19,149 바이트
               8개 디렉터리  24,383,672,320 바이트 남음

SDS@SDS-PC c:\dev\chatbot-tutorial
$ cp .env.example .env
'cp'은(는) 내부 또는 외부 명령, 실행할 수 있는 프로그램, 또는
배치 파일이 아닙니다.

SDS@SDS-PC c:\dev\chatbot-tutorial
$ copy .env.example .env
        1개 파일이 복사되었습니다.

SDS@SDS-PC c:\dev\chatbot-tutorial
$ npm start

> conversation-simple@0.1.1 start c:\dev\chatbot-tutorial
> node server.js

APIs initialize
Server running on port: 3000
User Input : undefined
Processed Input : undefined
--------------------------------------------------
Conversation Output : Welcome!
--------------------------------------------------
User Input : hi there
Processed Input : hi there
--------------------------------------------------
Conversation Output : Hi, what can I do for you?
--------------------------------------------------
User Input : reserve room
Processed Input : reserve room
--------------------------------------------------
Conversation Output : When do you want to have a meeting?
--------------------------------------------------
User Input : 10/7 10:00
Processed Input : 10/7 10:00
--------------------------------------------------
Conversation Output : Jesang Myung, OK I will check the availabilty of room.
--------------------------------------------------
Action : check-availability
User Input : ok
Processed Input : ok
--------------------------------------------------
Conversation Output : OK.  at 10:00:00, 2017-10-07 is reserved for you.
--------------------------------------------------
Action : confirm-reservation
일괄 작업을 끝내시겠습니까 (Y/N)? y

SDS@SDS-PC c:\dev\chatbot-tutorial
$ cf lo^A

SDS@SDS-PC c:\dev\chatbot-tutorial
$







---
declared-services:
  my-conversation-service:
    label: conversation
    plan: free
  camomile-cloudantNoSQLDB:
    label: cloudantNoSQLDB
    plan: Lite
applications:
- name: meetingroom-reservation-with-jmyung
  command: npm start
  path: .
  memory: 256M
  instances: 1
  services:
  - Conversation-ug
  - iot-jmyung-cloudantNoSQLDB
  env:
    NPM_CONFIG_PRODUCTION: false









SDS@SDS-PC c:\dev\chatbot-tutorial
$ npm start

> conversation-simple@0.1.1 start c:\dev\chatbot-tutorial
> node server.js

APIs initialize
Server running on port: 3000
User Input : undefined
Processed Input : undefined
--------------------------------------------------
Conversation Output : Welcome!
--------------------------------------------------
User Input : hi
Processed Input : hi
--------------------------------------------------
Conversation Output : Hey, what can I do for you?
--------------------------------------------------
User Input : reserve
Processed Input : reserve
--------------------------------------------------
Conversation Output : When do you want to have a meeting?
--------------------------------------------------
User Input : 10/01 15:30
Processed Input : 10/01 15:30
--------------------------------------------------
Conversation Output : Jesang Myung, OK I will check the availabilty of room.
--------------------------------------------------
Action : check-availability
User Input : yes
Processed Input : yes
--------------------------------------------------
Conversation Output : OK.  at 15:30:00, 2017-10-01 is reserved for you.
--------------------------------------------------
Action : confirm-reservation






https://developer.ibm.com/kr/cloud/bluemix/watsonservice/2017/02/19/watsonchatbot-4-watson-conversation/


https://developer.ibm.com/kr/cloud/bluemix/watsonservice/2017/03/04/watsonchatbot-5-watson-conversation/



'Cloud > Bluemix' 카테고리의 다른 글

OpenWhisk  (0) 2017.04.20
Royal Bank of Canada's Journey  (0) 2017.04.20
Service & deployment  (0) 2017.04.18
translate  (0) 2017.04.17
Watson IoT  (0) 2017.04.17

1. production service

2. beta service

  - may work, may not work

3. 3rd party service



[Active deploy]


Canary release

- 언제나 롤백이 가능

- minimal risk


Blue Green Deployment

- 소소한 변경만으로도 반영

- green -> blue

- hot-standby <-> cold

- RTO, RPO

- 데이터손실이 0에 수렴

-


Red(active) Black(deactive)

- Netflix 에서 사용중


Blue Green 

and Red(active) Black(deactive)

both are Deployment methodogy to achive active deploy?



In autoscaling perspective, scale out include disk size expanding?

no

1. how to expend disk size


yes

2. when scale out occur, two instance share one db?




'Cloud > Bluemix' 카테고리의 다른 글

Royal Bank of Canada's Journey  (0) 2017.04.20
chatbot  (0) 2017.04.19
translate  (0) 2017.04.17
Watson IoT  (0) 2017.04.17
IoT  (0) 2017.04.14

translate

Cloud/Bluemix2017. 4. 17. 14:09























package.json

app.js

index.html

수정






4/17/2017 6:09:35 AMOUTAPP{ translations: [ { translation: 'Salut' } ],
4/17/2017 6:09:35 AMOUTAPPword_count: 1,
4/17/2017 6:10:19 AMOUTAPP{ translations: [ { translation: 'Bonjour' } ],
4/17/2017 6:10:19 AMOUTAPPword_count: 1,
4/17/2017 6:10:19 AMOUTAPPcharacter_count: 5 }
4/17/2017 6:10:47 AMOUTAPPword_count: 3,
4/17/2017 6:10:47 AMOUTAPPcharacter_count: 11 }
4/17/2017 6:10:58 AMOUTAPP{ translations: [ { translation: 'Apple' } ],
4/17/2017 6:10:58 AMOUTAPPword_count: 1,
4/17/2017 6:10:58 AMOUTAPPcharacter_count: 5 }
4/17/2017 6:11:04 AMOUTAPP{ translations: [ { translation: 'Bonjour' } ],
4/17/2017 6:11:04 AMOUTAPPword_count: 1,
4/17/2017 6:11:04 AMOUTAPPcharacter_count: 5 }
4/17/2017 6:11:09 AMOUTAPP{ translations: [ { translation: 'Homme' } ],
4/17/2017 6:11:09 AMOUTAPPword_count: 1,
4/17/2017 6:11:12 AMOUTAPP{ translations: [ { translation: 'Femme' } ],
4/17/2017 6:11:12 AMOUTAPPword_count: 1,
4/17/2017 6:11:12 AMOUTAPPcharacter_count: 5 }








$ cf logs "nodejs jmyung"
Connected, tailing logs for app nodejs jmyung in org jmyung / space dev as human537@nate.com...

2017-04-17T15:14:16.85+0900 [APP/0]      OUT { translations: [ { translation: 'Stylet' } ],
2017-04-17T15:14:16.85+0900 [APP/0]      OUT   word_count: 1,
2017-04-17T15:14:16.85+0900 [APP/0]      OUT   character_count: 3 }

'Cloud > Bluemix' 카테고리의 다른 글

chatbot  (0) 2017.04.19
Service & deployment  (0) 2017.04.18
Watson IoT  (0) 2017.04.17
IoT  (0) 2017.04.14
WATSON  (0) 2017.04.13

Watson IoT

Cloud/Bluemix2017. 4. 17. 11:00

Ernese Norelus


SAN Disk

Monitor EOL Burn-In Test Machines

heat - temperature


다타 : data


캐나다는 너무 추워서 원격으로 제어하고 싶어함

비콘 : 많은 리소스를 필요로함. 열이 빨리 올라가나?

log


Gateway


Topic : 신문

  - 브로드케스트와 비슷한거 같다

Queue : point-to-point



IoT : 대시보드 필요로함


MQTT : 대용량에서는 불필요

- XML을 사용할 수 없다 (태그가지고 있음)

- PoT, PoC, PoP



Function as a service



장표에서 중요한 것 하나 빠진건

- Data center가 go down 됐을때?

- 인프라의 문제



---------------------------------------------------------------------------------------------

Node.js는 기본적으로 asyncronous

Fire and forget


sync가 필요한 경우에 promise

Promise : 읽은 책은 돌려주게 된다 (양자간의 계약 필요)




Twilio


































'Cloud > Bluemix' 카테고리의 다른 글

Service & deployment  (0) 2017.04.18
translate  (0) 2017.04.17
IoT  (0) 2017.04.14
WATSON  (0) 2017.04.13
MSA  (0) 2017.04.11