Return-Path: X-Original-To: apmail-brooklyn-dev-archive@minotaur.apache.org Delivered-To: apmail-brooklyn-dev-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id B06D8185EC for ; Mon, 21 Dec 2015 19:30:45 +0000 (UTC) Received: (qmail 93418 invoked by uid 500); 21 Dec 2015 19:30:45 -0000 Delivered-To: apmail-brooklyn-dev-archive@brooklyn.apache.org Received: (qmail 93381 invoked by uid 500); 21 Dec 2015 19:30:45 -0000 Mailing-List: contact dev-help@brooklyn.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@brooklyn.apache.org Delivered-To: mailing list dev@brooklyn.apache.org Received: (qmail 93369 invoked by uid 99); 21 Dec 2015 19:30:45 -0000 Received: from Unknown (HELO spamd2-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 21 Dec 2015 19:30:45 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd2-us-west.apache.org (ASF Mail Server at spamd2-us-west.apache.org) with ESMTP id 9BAB61A018F for ; Mon, 21 Dec 2015 19:30:44 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd2-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: 0.447 X-Spam-Level: X-Spam-Status: No, score=0.447 tagged_above=-999 required=6.31 tests=[KAM_LAZY_DOMAIN_SECURITY=1, RP_MATCHES_RCVD=-0.554, URIBL_BLOCKED=0.001] autolearn=disabled Received: from mx1-us-west.apache.org ([10.40.0.8]) by localhost (spamd2-us-west.apache.org [10.40.0.9]) (amavisd-new, port 10024) with ESMTP id wxI55vdPRwlV for ; Mon, 21 Dec 2015 19:30:32 +0000 (UTC) Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by mx1-us-west.apache.org (ASF Mail Server at mx1-us-west.apache.org) with SMTP id D65E420FF3 for ; Mon, 21 Dec 2015 19:30:31 +0000 (UTC) Received: (qmail 93207 invoked by uid 99); 21 Dec 2015 19:30:31 -0000 Received: from git1-us-west.apache.org (HELO git1-us-west.apache.org) (140.211.11.23) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 21 Dec 2015 19:30:31 +0000 Received: by git1-us-west.apache.org (ASF Mail Server at git1-us-west.apache.org, from userid 33) id 83620E07BA; Mon, 21 Dec 2015 19:30:31 +0000 (UTC) From: shartzel To: dev@brooklyn.incubator.apache.org Reply-To: dev@brooklyn.incubator.apache.org References: In-Reply-To: Subject: [GitHub] incubator-brooklyn pull request: DO NOT MERGE - "Getting Started" ... Content-Type: text/plain Message-Id: <20151221193031.83620E07BA@git1-us-west.apache.org> Date: Mon, 21 Dec 2015 19:30:31 +0000 (UTC) Github user shartzel commented on a diff in the pull request: https://github.com/apache/incubator-brooklyn/pull/1116#discussion_r48180991 --- Diff: docs/guide/start/managing-cli.md --- @@ -0,0 +1,309 @@ +--- +title: Monitoring and Managing Applications +title_in_menu: Monitoring and Managing Applications +layout: website-normal +menu_parent: index-cli.md +children: +- { section: Applications } +- { section: Entities } +- { section: Sensors } +- { section: Effectors } +- { section: Activities } +--- + + + +So far we have touched on Brooklyn's ability to *deploy* an application blueprint to a cloud provider, but this just +the beginning. The sections below outline how to manage the application that has been deployed. + +## Applications + +Having created the application we can query its status. We can find a summary of all deployed apps: +{% highlight bash %} +$ br app + Id Name Status Location + hTPAF19s Tomcat RUNNING ajVVAhER +{% endhighlight %} + +or the details of a given app. The ID, hTPAF19s, can also be used instead of the name "Tomcat". +{% highlight bash %} +$ br app Tomcat + Id: hTPAF19s + Name: Tomcat + Status: RUNNING + ServiceUp: true + Type: org.apache.brooklyn.entity.stock.BasicApplication + CatalogItemId: null + LocationId: ajVVAhER + LocationName: FixedListMachineProvisioningLocation:ajVV + LocationSpec: vagrantbyon + LocationType: org.apache.brooklyn.location.byon.FixedListMachineProvisioningLocation +{% endhighlight %} + +To ease management of multiple applications, or even to reduce the amount of typing required, it is convenient --- End diff -- l43-49 can probably be dropped. It's a small digression from the flow that we don't revisit anywhere following. --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enabled but not working, please contact infrastructure at infrastructure@apache.org or file a JIRA ticket with INFRA. ---