Return-Path: X-Original-To: apmail-cloudstack-users-archive@www.apache.org Delivered-To: apmail-cloudstack-users-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 25F2C10EE9 for ; Thu, 5 Dec 2013 01:57:27 +0000 (UTC) Received: (qmail 51422 invoked by uid 500); 5 Dec 2013 01:57:26 -0000 Delivered-To: apmail-cloudstack-users-archive@cloudstack.apache.org Received: (qmail 51383 invoked by uid 500); 5 Dec 2013 01:57:26 -0000 Mailing-List: contact users-help@cloudstack.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: users@cloudstack.apache.org Delivered-To: mailing list users@cloudstack.apache.org Received: (qmail 51375 invoked by uid 99); 5 Dec 2013 01:57:26 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 05 Dec 2013 01:57:26 +0000 X-ASF-Spam-Status: No, hits=-0.7 required=5.0 tests=RCVD_IN_DNSWL_LOW,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: local policy includes SPF record at spf.trusted-forwarder.org) Received: from [209.85.220.171] (HELO mail-vc0-f171.google.com) (209.85.220.171) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 05 Dec 2013 01:57:19 +0000 Received: by mail-vc0-f171.google.com with SMTP id ik5so12162742vcb.2 for ; Wed, 04 Dec 2013 17:56:58 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:content-type; bh=ZsXvNPtNzdkJqYdPbmiDhrsUqQ/ZBJlz7relWWMdHO4=; b=EG5wYLWA+UhgWdrggnduWQBpNS3dDiZExBJLz83CfWfOWaNsaUAmjgHG2Fis5SiskW 6v3M33Xj6zgcUzoSGiyZqvse/Z34V/Ispd5PWJM+6j/tq/stA06HakpWcpBX29aoilLE trj++EeVHbPUQEDfxytWW3/2PlB2HBy3At+p1lMEO2hAhVfg+9fdy9bFa5TexW0sBh5/ jCoyqjvF20WtvpG+9MiPm3KFcv2WRdwLEnhMkWlme5MfeTCqzFIPAEIwZqIVlILCVyHl cZGuf6nt/M0/f9pjd/gB8rP31K5qOxN1Fy/tDqewmPeapbTWWVJxzorufef1Z1P4EzMQ LMkA== X-Gm-Message-State: ALoCoQnNs07qAhmtLFmvLEN0yomsY/TpMGZF67Ix6r5RODL+6gvXStORWQp4AlRQnGJ1+D6OaRYm X-Received: by 10.58.210.39 with SMTP id mr7mr45698547vec.18.1386208617923; Wed, 04 Dec 2013 17:56:57 -0800 (PST) MIME-Version: 1.0 Received: by 10.220.0.137 with HTTP; Wed, 4 Dec 2013 17:56:36 -0800 (PST) In-Reply-To: References: <652D8534-77BB-4A1A-B4DF-45991451A147@gmail.com> From: David Nalley Date: Wed, 4 Dec 2013 20:56:36 -0500 Message-ID: Subject: Re: Cloudstack user-data empty for VMs To: "users@cloudstack.apache.org" Content-Type: text/plain; charset=ISO-8859-1 X-Virus-Checked: Checked by ClamAV on apache.org Yeah - it's definitely a work in progress - if you look at Dan Bode's cloudstack_resources, he actually has a ton of additional work in a different branch that hasn't yet been validated. It's on my list to get around to that in the next few weeks. What you likely saw (esp if it was my presentation) was a combination of Jason Hancock's work around userdata and his fact - and then separately the resources and types for CloudStack. There are some folks who use CloudStack's records of hosts as a ENC - and that's where the 'Group=' stuff leaks into the presentation - essentially they query for the host - and parse the Group records and make catalog decisions off of that rather than a fact. (Keep in mind the 'down side' of going the fact route, is that essentially an attacker could pass any information back to puppet and get anything in the catalog theoretically) Please do submit a pull request for the userdata feature (feel free to submit it against my repo or Dan's) --David On Wed, Dec 4, 2013 at 6:44 PM, Derek Cole wrote: > Well I started to post about getting something broken. I modified > cloudstack_resources to take an argument for userdata. I was getting all > kinds of issues with that, until I realized that the argument in userdata > has to be base64 encoded. I fixed that, and now my VMs can get their > metadata! I had seen a demo with this software at a puppet conference but > it's become clear to me it's not exactly complete, so I have been fighting > to learn ruby ever since to make things work. > > Thanks for the help.