Per AppDynamics cum Rubrum Hat OpenShift v3

Per AppDynamics cum Rubrum Hat OpenShift v3
Multis Institutis nuper aspicientibus applicationes suas movere a monolithis ad microservias utentes in rostris ut servitii (PaaS) sicut RedHat OpenShift v3, AppDynamics significantes collocationes fecit in praebendo top-incisura integrationem cum talibus provisoribus.

Per AppDynamics cum Rubrum Hat OpenShift v3

AppDynamics integrant procuratores suos cum RedHat OpenShift v3 utens methodologiam Source-ad-Image (S2I). S2I instrumentum est ad fabricandas imagines reproducibiles Docker. Imagines paratas ad currendum gignit, applicationem fontem in imaginem Docker inserendo et novam Docker imaginem aedificat. Nova imago, quae basem imaginem (aedificantem) et fontem aedificatum includit, prompta est uti cum imperio currere. S2I subsidia incrementalia aedificat quae reuse dependentiae antea receptae, artificiata antea creata, etc.

processus

Omnino processus utendi AppDynamics cum RedHat OpenShift

Gradus I: RedHat iam provisum

Ad gradus 2 et 3, complere potes scriptis S2I in sequentibus GitHub repositorium et instructiones quomodo creare imaginum fabricatoris auctus pro JBoss Wildfly et EAP servientibus. sequere nexum
Intueamur omnia per exemplum specificum et applicationem template sequere nexum.

PRAEREQUISITIS:

  • Fac in OS installatur (Link)
  • Fac sti installatur (Link)
  • Fac tibi rationem dockerhub (Link)

Gradus II: crea in AppDynamics conditor Image

 $ git clone https://github.com/Appdynamics/sti-wildfly.git
$ cd sti-wildfly
$ make build VERSION=eap6.4 

Gradus III, crea applicationem imaginem

 $ s2i build  -e “APPDYNAMICS_APPLICATION_NAME=os3-ticketmonster,APPDYNAMICS_TIER_NAME=os3-ticketmonster-tier,APPDYNAMICS_ACCOUNT_NAME=customer1_xxxxxxxxxxxxxxxxxxf,APPDYNAMICS_ACCOUNT_ACCESS_KEY=xxxxxxxxxxxxxxxxxxxxx,APPDYNAMICS_CONTROLLER_HOST=xxxx.saas.appdynamics.com,APPDYNAMICS_CONTROLLER_PORT=443,APPDYNAMICS_CONTROLLER_SSL_ENABLED=true” https://github.com/jim-minter/ose3-ticket-monster appdynamics/sti-wildfly-eap64-centos7:latest pranta/appd-eap-ticketmonster
$ docker tag openshift-ticket-monster pranta/openshift-ticket-monster:latest
$ docker push pranta/openshift-ticket-monster 

Gradus IV: explica applicationem ad OpenShift

$ oc login 10.0.32.128:8443
$ oc new-project wildfly
$ oc project wildfly
$ oc new-app –docker-image=pranta/appd-eap-ticketmonster:latest –name=ticketmonster-demo

Per AppDynamics cum Rubrum Hat OpenShift v3

Nunc potes in moderatorem ac tesseram applicationem in applicatione locationis videre:

Per AppDynamics cum Rubrum Hat OpenShift v3

Source: www.habr.com

Add a comment