Return-Path: X-Original-To: apmail-incubator-cloudstack-marketing-archive@minotaur.apache.org Delivered-To: apmail-incubator-cloudstack-marketing-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 641B0E2AF for ; Tue, 26 Feb 2013 22:25:51 +0000 (UTC) Received: (qmail 86013 invoked by uid 500); 26 Feb 2013 22:25:51 -0000 Delivered-To: apmail-incubator-cloudstack-marketing-archive@incubator.apache.org Received: (qmail 85979 invoked by uid 500); 26 Feb 2013 22:25:51 -0000 Mailing-List: contact cloudstack-marketing-help@incubator.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: cloudstack-marketing@incubator.apache.org Delivered-To: mailing list cloudstack-marketing@incubator.apache.org Received: (qmail 85971 invoked by uid 99); 26 Feb 2013 22:25:51 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 26 Feb 2013 22:25:51 +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 (athena.apache.org: domain of imusayev@webmd.net designates 216.32.180.11 as permitted sender) Received: from [216.32.180.11] (HELO va3outboundpool.messaging.microsoft.com) (216.32.180.11) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 26 Feb 2013 22:25:45 +0000 Received: from mail97-va3-R.bigfish.com (10.7.14.248) by VA3EHSOBE002.bigfish.com (10.7.40.22) with Microsoft SMTP Server id 14.1.225.23; Tue, 26 Feb 2013 22:25:24 +0000 Received: from mail97-va3 (localhost [127.0.0.1]) by mail97-va3-R.bigfish.com (Postfix) with ESMTP id D21A72A0151 for ; Tue, 26 Feb 2013 22:25:24 +0000 (UTC) X-Forefront-Antispam-Report: CIP:67.130.38.18;KIP:(null);UIP:(null);IPV:NLI;H:EXHT02L-CRP-06.webmdhealth.net;RD:none;EFVD:NLI X-SpamScore: -7 X-BigFish: VPS-7(zzbb2dI98dI9371I1454I542I1432I1447Izz1f42h1ee6h1de0h1202h1e76h1d1ah1d2ahzz17326ah8275dh8275bhz31h2a8h668h839h947hd25hf0ah1288h12a5h12a9h12bdh137ah13b6h1441h14ddh1504h1537h153bh15d0h162dh1631h1758h18e1h1946h19b5h1155h) Received-SPF: softfail (mail97-va3: transitioning domain of webmd.net does not designate 67.130.38.18 as permitted sender) client-ip=67.130.38.18; envelope-from=imusayev@webmd.net; helo=EXHT02L-CRP-06.webmdhealth.net ;mdhealth.net ; Received: from mail97-va3 (localhost.localdomain [127.0.0.1]) by mail97-va3 (MessageSwitch) id 1361917522235916_27896; Tue, 26 Feb 2013 22:25:22 +0000 (UTC) Received: from VA3EHSMHS006.bigfish.com (unknown [10.7.14.240]) by mail97-va3.bigfish.com (Postfix) with ESMTP id 2B55330005B for ; Tue, 26 Feb 2013 22:25:22 +0000 (UTC) Received: from EXHT02L-CRP-06.webmdhealth.net (67.130.38.18) by VA3EHSMHS006.bigfish.com (10.7.99.16) with Microsoft SMTP Server (TLS) id 14.1.225.23; Tue, 26 Feb 2013 22:25:22 +0000 Received: from EXDFO01L-CRP-06.webmdhealth.net ([fe80::9dd9:c35b:dd4e:f7cf]) by EXHT02L-CRP-06.webmdhealth.net ([::1]) with mapi id 14.02.0342.003; Tue, 26 Feb 2013 17:25:21 -0500 From: "Musayev, Ilya" To: "cloudstack-marketing@incubator.apache.org" Subject: RE: CloudStack Laynard Sponsorship at ChefConf#13 Thread-Topic: CloudStack Laynard Sponsorship at ChefConf#13 Thread-Index: Ac4UWQ6X3Jc7FzqkRpCJ06NTt61rZAALB58AAAAJ1gAAAsmegAAAGqwAAABGVgAAAG92AAAA1TyAAAA5hYAACfQDoA== Date: Tue, 26 Feb 2013 22:25:20 +0000 Message-ID: References: <02cc01ce1469$d48b65b0$7da23110$@apache.org> <02e601ce146e$0f3b36a0$2db1a3e0$@apache.org> In-Reply-To: <02e601ce146e$0f3b36a0$2db1a3e0$@apache.org> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [10.220.112.99] Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 X-OriginatorOrg: webmd.net X-Virus-Checked: Checked by ClamAV on apache.org http://www.opscode.com/blog/2012/02/13/chef-support-for-citrix-cloudstack/ -----Original Message----- From: Kelcey Damage (BT) [mailto:kelcey@backbonetechnology.com] On Behalf O= f kdamage@apache.org Sent: Tuesday, February 26, 2013 5:10 PM To: cloudstack-marketing@incubator.apache.org Subject: RE: CloudStack Laynard Sponsorship at ChefConf#13 Well there are many user who make great tools based on chef,puppet,fabric,p= aython,pearl,and I'm sure many more by using our APIs + something else. I j= ust though a cookbook that had something for everyone would be nice. I myse= lf don't use chef/puppet, I also wrote an API manager in IronPython and .ne= t/xaml. So there are a lot of cool tricks an how-to's floating around. It was just an idea. -kelcey Damage =A0 >-----Original Message----- >From: Kelly Hair [mailto:kelly.hair@citrix.com] >Sent: Tuesday, February 26, 2013 2:04 PM >To: cloudstack-marketing@incubator.apache.org >Subject: Re: CloudStack Laynard Sponsorship at ChefConf#13 > >Kelcey, all, > > >Received confirmation from OpsCode that they are working on a cookbook=20 >as we speak. That's probably based more on the customers they are=20 >working with :) So, that's good news.. > >What other folks were you thinking of outside of the one that comes to=20 >mind when you say Chef and that's Puppet? > > > > > > > >On 2/26/13 4:40 PM, "kdamage@apache.org" wrote: > >>I personally think it would be nice to put a cookbook together under=20 >>community guidance, and leverage official TM. Also not restrict the=20 >>cookbook to any particular platform (ie: Chef, etc), Really would be=20 >>nice to create a true 'automation/operation/pure-cool' recipe book=20 >>from the communities experiences. >> >>I am also open to mentoring books that are 2nd/3rd party to the community= . >>Just tell me what you guys need, or feel free to invite me into the=20 >>discussion ;). >> >>Best of luck, and thanks for the congrats! >> >>-Kelcey Damage >> >> >> >>>-----Original Message----- >>>From: Kelly Hair [mailto:kelly.hair@citrix.com] >>>Sent: Tuesday, February 26, 2013 1:28 PM >>>To: cloudstack-marketing@incubator.apache.org >>>Subject: Re: CloudStack Laynard Sponsorship at ChefConf#13 >>> >>>Congratulations in advance on the book. Looking forward to seeing it. >>>That's good stuff! >>> >>>I can reach out to the OpsCode folks. Probably best to take it=20 >>>offline and formulate use cases based on provisioning & management. >>> >>> >>> >>>On 2/26/13 4:19 PM, "kdamage@apache.org" >wrote: >>> >>>>I the nearing the final stages of Packt Publishings CloudStack book,=20 >>>>and would be happy to look into mentoring a cookbook. >>>> >>>>-Kelcey Damage >>>> >>>>>-----Original Message----- >>>>>From: Kelly Hair [mailto:kelly.hair@citrix.com] >>>>>Sent: Tuesday, February 26, 2013 1:17 PM >>>>>To: cloudstack-marketing@incubator.apache.org >>>>>Subject: Re: CloudStack Laynard Sponsorship at ChefConf#13 >>>>> >>>>>Can affirm Matt's observations. We had some recent conversations=20 >>>>>and see there's interest in building a CloudStack cookbook. >>>>> >>>>> >>>>> >>>>> >>>>>On 2/26/13 2:56 PM, "Sebastien Goasguen" >wrote: >>>>> >>>>>>+1 >>>>>> >>>>>>On Feb 26, 2013, at 2:55 PM, Mathias Mullins=20 >>>>>> >>>>>>wrote: >>>>>> >>>>>>> +1 >>>>>>> >>>>>>> Great idea Mark. >>>>>>> >>>>>>> We are hearing a lot about Chef usage in the implementation=20 >>>>>>>community and a lot of generated interest in the possibility of=20 >>>>>>>the two working together. Something that people really want to see. >>>>>>> >>>>>>> Matt >>>>>>> >>>>>>> >>>>>>> On 2/26/13 2:39 PM, "Mark Hinkle" wrote: >>>>>>> >>>>>>>> I have the Lanyard sponsorship for #ChefConf this year on April >>>>>>>>24-26: >>>>>>>> http://chefconf.opscode.com/ >>>>>>>> I was planning on donating the sponsorship to Apache CloudStack=20 >>>>>>>>to help raise the project profile I know we have quite a few=20 >>>>>>>>Chef users >>>>too. >>>>>>>> Basically we get the CloudStack logo on the lanyards and a 50=20 >>>>>>>>word blurb for the ChefConf#13 website. >>>>>>>> >>>>>>>> Any thought? Mark >>>>>>>> >>>>>>>> >>>>>>>> >>>>>>>> >>>>>>>> >>>>>>>> Mark R. Hinkle >>>>>>>> Senior Director, Cloud Computing Community Citrix Systems >>>>>>>> e: mark.hinkle@citrix.com >>>>>>>> Twitter: @mrhinkle >>>>>>>> Skype: mrhinkle >>>>>>>> >>>>>>>> >>>>>>>> >>>>>>> >>>>>> >>>> >>>> >> >>