Return-Path: X-Original-To: apmail-incubator-ambari-user-archive@minotaur.apache.org Delivered-To: apmail-incubator-ambari-user-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 5D2C110BB5 for ; Fri, 4 Oct 2013 10:50:25 +0000 (UTC) Received: (qmail 34402 invoked by uid 500); 4 Oct 2013 10:50:23 -0000 Delivered-To: apmail-incubator-ambari-user-archive@incubator.apache.org Received: (qmail 34354 invoked by uid 500); 4 Oct 2013 10:50:15 -0000 Mailing-List: contact ambari-user-help@incubator.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: ambari-user@incubator.apache.org Delivered-To: mailing list ambari-user@incubator.apache.org Received: (qmail 34340 invoked by uid 99); 4 Oct 2013 10:50:13 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 04 Oct 2013 10:50:13 +0000 X-ASF-Spam-Status: No, hits=-0.1 required=5.0 tests=HTML_MESSAGE,RCVD_IN_DNSWL_MED,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of adamos@tid.es designates 195.235.93.44 as permitted sender) Received: from [195.235.93.44] (HELO tidos.tid.es) (195.235.93.44) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 04 Oct 2013 10:50:09 +0000 Received: from sbrightmailg01.hi.inet (sbrightmailg01.hi.inet [10.95.64.104]) by tid.hi.inet (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0MU500J0F4QYVV@tid.hi.inet> for ambari-user@incubator.apache.org; Fri, 04 Oct 2013 12:49:46 +0200 (MEST) Received: from dequeue_removeroute (tid.hi.inet [10.95.64.10]) by sbrightmailg01.hi.inet (Symantec Messaging Gateway) with SMTP id 84.28.03197.A4D9E425; Fri, 04 Oct 2013 12:49:46 +0200 (CEST) Received: from correo.tid.es (mailhost.hi.inet [10.95.64.100]) by tid.hi.inet (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0MU500JKJ4QWVQ@tid.hi.inet> for ambari-user@incubator.apache.org; Fri, 04 Oct 2013 12:49:44 +0200 (MEST) Received: from EX10-MB2-MAD.hi.inet ([169.254.2.165]) by EX10-HTCAS6-MAD.hi.inet ([::1]) with mapi id 14.03.0123.003; Fri, 04 Oct 2013 12:49:44 +0200 Date: Fri, 04 Oct 2013 10:49:43 +0000 From: ADAMOS LOIZOU Subject: Reconfiguring services with client only components X-Originating-IP: [10.95.64.115] To: "ambari-user@incubator.apache.org" Message-id: <3719AEF2-7FBC-48AF-8E3E-57FDC613F144@tid.es> MIME-version: 1.0 Content-type: multipart/alternative; boundary="Boundary_(ID_f5GA/mXGvNhiII+lppu03A)" Content-language: en-US Accept-Language: en-GB, es-ES, en-US Thread-topic: Reconfiguring services with client only components Thread-index: AQHOwO9vxc8ETQuKDUmxRow3Z2NaaQ== X-AuditID: 0a5f4068-b7f3e8e000000c7d-67-524e9d4a58bc X-MS-Has-Attach: X-MS-TNEF-Correlator: X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFnrHLMWRmVeSWpSXmKPExsXCFe/Apes11y/I4NRPOYu/i3eyOzB6zFq2 lSmAMYrLJiU1J7MstUjfLoEr40fjNcaChSoVXecvszUwvpPrYuTkkBAwkWhc8osJwhaTuHBv PVsXIxeHkMBBRonTB2ezQjhdTBLLn81ih3BmMkps6OwBa2ERUJWY2LOaDcRmE1CWuLt/CpDN wSEsYC1x4JsDxFQFiT/nHrOA2CICnhJXmnaCtfIKWEq8vtPJCmELSvyYfA+shlkgWuLC/A9M ELa4RHPrTbA4o4CKxPSJP9kh5jhILHrSzAZh60m0rNnHDrFLQGLJnvPMELaoxMvH/1gnMArP QrJiFpIVs5CsgLB1JBbs/sQGYWtLLFv4mhnGPnPgMVS9mcSqBftYkdUsYORYxShWnFSUmZ5R kpuYmZNuYKiXkamXmZdasokREkcZOxiX71Q5xCjAwajEw7sixzdIiDWxrLgy9xCjBAezkgjv 8Ul+QUK8KYmVValF+fFFpTmpxYcYmTg4pRoYa2bp59pu3OIpoa1o/aOct/mh78wnrl9/tqjP kb73vuqhVN75MH39DUXN841jBNuu58VLK+SebQ4JCo1dLbbFpsFE8NJ2naU/X/+LaBKXm336 x523p8WjiuzcTu2fNfX9g9T280IrOdLV5SIO9P+Ypvjows90abnTm3oFznAWhMcd2uCZ8n6f EktxRqKhFnNRcSIAjkPZ+4ECAAA= X-Virus-Checked: Checked by ClamAV on apache.org --Boundary_(ID_f5GA/mXGvNhiII+lppu03A) Content-type: text/plain; charset=us-ascii Content-transfer-encoding: 7BIT Hello, We use a custom service in our Ambari instance that comprises only of client components (i.e. no daemons). We used to control its reconfiguration by: 1. Stopping the service by changing the service state to INSTALLED 2. Changing the cluster configuration with a PUT in e.g. http://localhost:8080/api/v1/clusters/mycluster with the following body: { "Clusters": { "desired_configs": { "type": "your_custom_service_type", "tag": "your_new_version", "properties": { }# properties here } } } 3. "Starting" the service by changed the state to STARTED. Even though the service would always remain in INSTALLED state (as being with client-only components) it had the effect of applying the changed configuration. We've recently synced our Ambari version with the latest from trunk and we no longer see that behaviour (the configuration is not applied). What would the correct way be of reconfiguring a service with client only components? Thank you Kind Regards Adamos ________________________________ Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra pol?tica de env?o y recepci?n de correo electr?nico en el enlace situado m?s abajo. This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at: http://www.tid.es/ES/PAGINAS/disclaimer.aspx --Boundary_(ID_f5GA/mXGvNhiII+lppu03A) Content-id: <11C5C7042EA0D946ACBF6AC9C6A67775@hi.inet> Content-type: text/html; charset=us-ascii Content-transfer-encoding: 7BIT Hello,

We use a custom service in our Ambari instance that comprises only of client components (i.e. no daemons).

We used to control its reconfiguration by:

1. Stopping the service by changing the service state to INSTALLED
2. Changing the cluster configuration with a PUT in e.g. http://localhost:8080/api/v1/clusters/mycluster with the following body:
  {
    "Clusters": {
      "desired_configs": {
        "type": "your_custom_service_type",
        "tag": "your_new_version",
        "properties": { }# properties here
      }
    }
  }

3. "Starting" the service by changed the state to STARTED. Even though the service would always remain in INSTALLED state (as being with client-only components) it had the effect of applying the changed configuration.

We've recently synced our Ambari version with the latest from trunk and we no longer see that behaviour (the configuration is not applied).

What would the correct way be of reconfiguring a service with client only components?

Thank you

Kind Regards
Adamos



Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra política de envío y recepción de correo electrónico en el enlace situado más abajo.
This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at:
http://www.tid.es/ES/PAGINAS/disclaimer.aspx
--Boundary_(ID_f5GA/mXGvNhiII+lppu03A)--