Return-Path: X-Original-To: archive-asf-public-internal@cust-asf2.ponee.io Delivered-To: archive-asf-public-internal@cust-asf2.ponee.io Received: from cust-asf.ponee.io (cust-asf.ponee.io [163.172.22.183]) by cust-asf2.ponee.io (Postfix) with ESMTP id 632C7200C67 for ; Mon, 15 May 2017 09:49:08 +0200 (CEST) Received: by cust-asf.ponee.io (Postfix) id 61C24160BC2; Mon, 15 May 2017 07:49:08 +0000 (UTC) Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by cust-asf.ponee.io (Postfix) with SMTP id A8143160BC1 for ; Mon, 15 May 2017 09:49:07 +0200 (CEST) Received: (qmail 6466 invoked by uid 500); 15 May 2017 07:49:06 -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 6454 invoked by uid 99); 15 May 2017 07:49:06 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd2-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 15 May 2017 07:49:06 +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 403BB1AF8E0 for ; Mon, 15 May 2017 07:49:06 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd2-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: -100.002 X-Spam-Level: X-Spam-Status: No, score=-100.002 tagged_above=-999 required=6.31 tests=[RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001, USER_IN_WHITELIST=-100] autolearn=disabled Received: from mx1-lw-us.apache.org ([10.40.0.8]) by localhost (spamd2-us-west.apache.org [10.40.0.9]) (amavisd-new, port 10024) with ESMTP id U30kjYSRgg9s for ; Mon, 15 May 2017 07:49:05 +0000 (UTC) Received: from mailrelay1-us-west.apache.org (mailrelay1-us-west.apache.org [209.188.14.139]) by mx1-lw-us.apache.org (ASF Mail Server at mx1-lw-us.apache.org) with ESMTP id BDA7F5FAF9 for ; Mon, 15 May 2017 07:49:04 +0000 (UTC) Received: from jira-lw-us.apache.org (unknown [207.244.88.139]) by mailrelay1-us-west.apache.org (ASF Mail Server at mailrelay1-us-west.apache.org) with ESMTP id 4AEC8E0280 for ; Mon, 15 May 2017 07:49:04 +0000 (UTC) Received: from jira-lw-us.apache.org (localhost [127.0.0.1]) by jira-lw-us.apache.org (ASF Mail Server at jira-lw-us.apache.org) with ESMTP id 05BB821DEB for ; Mon, 15 May 2017 07:49:04 +0000 (UTC) Date: Mon, 15 May 2017 07:49:04 +0000 (UTC) From: "Andres Garcia Garcia (JIRA)" To: dev@brooklyn.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Created] (BROOKLYN-503) Shell.env should work with SaltEntity MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 archived-at: Mon, 15 May 2017 07:49:08 -0000 Andres Garcia Garcia created BROOKLYN-503: --------------------------------------------- Summary: Shell.env should work with SaltEntity Key: BROOKLYN-503 URL: https://issues.apache.org/jira/browse/BROOKLYN-503 Project: Brooklyn Issue Type: Improvement Affects Versions: 0.10.0 Environment: Ubuntu 14.04 Reporter: Andres Garcia Garcia I am using Brooklyn to deploy servers configured with Salt. I am trying to deploy one VM with a web server and another with MySQL, and link them together using env variables in the salt pillars. Based on the sample templates, this is my yaml. name: Salt LAMP deployment (Brooklyn Example) services: - id: mysql name: mysql type: org.apache.brooklyn.entity.cm.salt.SaltEntity formulas: - https://github.com/saltstack-formulas/mysql-formula/archive/master.tar.gz start_states: - mysql pillars: - mysql pillarUrls: - ftp://xxx/wordpress-example.tar - id: wordpress name: wordpress type: org.apache.brooklyn.entity.cm.salt.SaltEntity formulas: - https://github.com/saltstack-formulas/php-formula/archive/master.tar.gz - https://github.com/saltstack-formulas/wordpress-formula/archive/master.tar.gz - https://github.com/saltstack-formulas/apache-formula/archive/master.tar.gz - https://github.com/saltstack-formulas/mysql-formula/archive/master.tar.gz start_states: - mysql.client - php.ng - php.ng.mysql - wordpress - apache - apache.config - apache.vhosts.standard pillars: - php - wordpress - apache - mysql pillarUrls: - ftp://xxx/filezilla.tar brooklyn.config: shell.env: MYSQL_URL: $brooklyn:entity("mysql").attributeWhenReady("host.name") location: jclouds:aws-ec2: identity: xxx credential: xxx region: us-west-2 inboundPorts: - 22 - 80 - 3306 hardwareId: t2.small And then, inside the pillars, I configure them as follows wordpress: sites: username: xxx password: xxx database: xxx dbhost: {{ salt['environ.get']('MYSQL_URL') }} However, the MYSQL_URL env variable is resolved to none. I got word from svet in the IRC channel that SaltEntity doesn't support shell.env. I think it would be really helpful to make this option available in order to configure multinode deployments with Salt. -- This message was sent by Atlassian JIRA (v6.3.15#6346)