11:06:00 <gregdek> #startmeeting Recipes meeting, 2 March 2012
11:06:00 <eucabot> Meeting started Fri Mar  2 19:06:45 2012 UTC.  The chair is gregdek. Information about MeetBot at http://wiki.debian.org/MeetBot.
11:06:00 <eucabot> Useful Commands: #action #agreed #help #info #idea #link #topic.
11:06:00 <gregdek> #meetingname recipes
11:06:00 <eucabot> The meeting name has been set to 'recipes'
11:07:00 <gregdek> I'll forego the roll call. :)
11:07:00 <gregdek> #topic Official Project Meeting?
11:07:00 <gregdek> First question: should we go ahead and promote this to "official" meeting time?  Since recipes has its own project space already...
11:07:00 <gregdek> dak419: is your other meeting done? :)
11:08:00 <dak419> yup.  not rest for the weary though
11:08:00 <gholms> We are now instead colliding the with the Fedora Cloud SIG meeting. ;)
11:08:00 <gregdek> Heh.
11:08:00 <gregdek> I'm happy moving these earlier, fwiw.
11:08:00 <dak419> me too! My morning is pretty free!
11:08:00 <gregdek> The time for *this* meeting is actually tentatively an hour earlier.
11:09:00 <gregdek> But SBA doesn't want to get up at 8am. ;)
11:09:00 <dak419> nor at 5am! :-)
11:09:00 <obino> now now, we are ok at 11pm PDT, are you?
11:09:00 <obino> :D
11:10:00 <dak419> hey, I have a meeting at 6pm EST today. which makes my day even longer since I started at 7am EST
11:10:00 <gregdek> Brutal. :)
11:11:00 <gregdek> Well, right now we have 10am PT for Recipes and 11am PT for Images.
11:11:00 <gregdek> Happy to move earlier or later, but finding the right time is the painful part.
11:11:00 <obino> also I don't like to have them back to back
11:12:00 <obino> most people are common between the 2 meetings
11:12:00 <dak419> I look forward to my meeting in the next hour where I get to use voice!
11:12:00 <gregdek> obino: if people are common, doesn't that mean we *shuold* have them back to back?
11:12:00 <gregdek> We can split them up too.  :)
11:12:00 <hspencer> i have no problem doing this meeting int he morning
11:12:00 <obino> that means 2 hours straight of meeting and no time between them to switch from image issues to recipes
11:12:00 <hspencer> like 8 AM
11:13:00 <hspencer> i think keepin this meeting at 11
11:13:00 <obino> but I would like to hear what others think
11:13:00 <hspencer> i know we started early today
11:13:00 <hspencer> but keepin it at 11
11:13:00 <hspencer> then have the recipes at 8 AM
11:13:00 <hspencer> makes sense to mee
11:13:00 <gregdek> I could do that.
11:13:00 <hspencer> i am down for that
11:13:00 <gregdek> Other recipes folks?
11:14:00 <gregdek> dak419? obino? mull?
11:14:00 <dak419> I'm flexible. If eng continues to sync at 1ET (10PT), I would prefer not to have one of these meetings at same time
11:14:00 <mull> hmmm?
11:14:00 * mull reads up
11:14:00 <mull> dak419, +1
11:14:00 <obino> 11am is the cloud sig meeting
11:14:00 <obino> 8am would put the meeting very close to the internal t-service meeting (9)
11:15:00 <obino> which means I would have to drive to the office before that
11:15:00 <obino> or learn to work from home :)
11:15:00 <gregdek> LOL
11:15:00 <obino> just rambling don't listen too much to me: I'm readhy for the weekend :D
11:15:00 <dak419> obino: don't discount working in your pjs!
11:15:00 <obino> +2!
11:15:00 <obino> lol
11:16:00 <obino> actually I don't like it, but I keep thinking about dilbert when you say that
11:17:00 <gholms> Heh
11:17:00 <dak419> how many really have a conflict with fedora cloud SIG?
11:17:00 <gregdek> gholms: what do you think about 8am on friday?
11:18:00 <gholms> gregdek: I think I would be showering/dressing/etc for half of it, in transit for a quarter of it, and available for a quarter of it.
11:18:00 <gregdek> Not ideal.
11:18:00 <gholms> (assuming you mean 8 Pacific)
11:19:00 <gregdek> hspencer: your SBA crew seems to think 8am is too early.
11:19:00 <obino> gholms: we are atlking about EST
11:19:00 <cpt_yesterday> We could move our drive in time an hour earlier for Friday if it works for everyone else
11:19:00 <gholms> obino: In that case I will sleep through the whole thing. :)
11:19:00 <cpt_yesterday> But only if this isn't obino's idea
11:19:00 <obino> mutiny!!!
11:19:00 <gregdek> Or, we could pick another day.
11:19:00 <dak419> don't remote people suck? :-)
11:20:00 <cpt_yesterday> yes
11:20:00 * gholms looks for the calendar link
11:20:00 <obino> I thought it was bad people sucks
11:20:00 <dak419> didn't I just say that? :-)
11:20:00 <cpt_yesterday> assholes...just say it. Don't be afraid obino
11:20:00 <gregdek> gholms: front page of projects
11:20:00 <gholms> Thanks
11:21:00 <gholms> How do Mondays look?
11:21:00 <gregdek> Mondays are currently wide open.  I've got sr mgmt meeting from 9-11am personally, though.
11:21:00 <obino> actually I personally think that 7 or 7:30 is better than 8: at 8 is when I get ready to go
11:22:00 <obino> ok, how many tz do we need to cater here?
11:22:00 <obino> EST and PDT for sure
11:22:00 <obino> how about lwade and monolive, are they on this?
11:22:00 <obino> and jeevan_ullas are you interested in this?
11:23:00 <obino> if there is no answer then we know we have from 9am to 3pm (PDT) to pick a time
11:23:00 <dak419> yea, different day is OK with me. I'm free from 2-5, ET
11:24:00 <dak419> (mondays, that is)
11:24:00 <gregdek> ET, PT, Europe, IST generally. :)
11:24:00 * gholms recommends starting a wide open whenisgood poll and moving on
11:24:00 <jeevan_ullas> sorry, is this for some meeting?
11:24:00 <gregdek> Hahahaha
11:24:00 * jeevan_ullas scrollsback
11:24:00 <gregdek> gholms: no one responded to the last one.
11:25:00 <gregdek> Which makes me feel it's unlikely that people will respond to another one.
11:25:00 * dak419 did, so don't blame me!
11:25:00 <gregdek> LOL
11:25:00 <gholms> Fair enough
11:25:00 <obino> feel the power of the force gregdek stop trusting your eyes :)
11:25:00 <gregdek> OK. If folks pinkyswear that they'll respond, I can post to whenisgood and we can move on.
11:25:00 <jeevan_ullas> 9am PDT works for me. its 10:30PM though but i have got used to it
11:25:00 <gregdek> Does everyone promise? :)
11:25:00 <dak419> I used whenisgood for a meeting today and when I had a good ET time, I went and put it on the calendar for PT. #fail
11:26:00 <dak419> yes!
11:26:00 <gholms> I will if you send it today.
11:26:00 <gregdek> #action gregdek will set up whenisgood for recipes meeting time
11:26:00 <gregdek> I will.
11:26:00 <gregdek> Right after this meeting.
11:26:00 <gregdek> NOW!
11:26:00 <gregdek> #topic open floor
11:26:00 <dak419> I got nothing. :-)
11:26:00 <gregdek> dak419: YOU LIE!
11:27:00 * dak419 emotionally drained after time discussion
11:27:00 <gholms> Heh
11:27:00 <dak419> ok, so if this is recipes then, not sure, but if this is more images, I would love to discuss partner image details (and can supply URL for reference)
11:28:00 <gregdek> :)
11:28:00 <gregdek> Sigh.
11:28:00 <obino> lol
11:28:00 <dak419> do we have open actions? (looks)
11:28:00 <gregdek> None.
11:28:00 <gregdek> This is still unofficial discussion stage, so we haven't been tracking issues.
11:28:00 <dak419> https://projects.eucalyptus.com/redmine/projects/recipes/issues
11:29:00 <dak419> somebody has!
11:29:00 <obino> 35 I found it interesting
11:29:00 <dak419> those look old though
11:29:00 <obino> cloud-init will superseed it, but it's simplicity is very nice to me :)
11:29:00 <gregdek> They are old.
11:30:00 <dak419> valid still, so lets at least discuss
11:30:00 <gregdek> Sure.
11:30:00 <gregdek> .proj 35
11:30:00 <eucabot> gregdek: Issue 35 (New): to use makeself to create complex script - https://projects.eucalyptus.com/issues/35
11:30:00 <gregdek> #topic to use makeself to create complex script
11:30:00 * dak419 wondered how to do that
11:30:00 <obino> the same way that run-parts does it
11:30:00 <obino> one could pacakge a list of scripts to be executed in a certain order
11:31:00 <obino> then it passes it to the instance
11:31:00 <dak419> is this related to cloud-init? (a little lost on this one)
11:31:00 <obino> and voila, you can have multiple services on the same instances
11:31:00 <obino> nope
11:31:00 <gregdek> All recipes-type ideas rely on something to inject an answer to the basic question "what recipe should I run, and where is it?"
11:31:00 <dak419> in place of, but leveraging user-data?
11:31:00 <cpt_yesterday> It's really just to allow you to push through multiple smaller scripts instead of one massive script
11:32:00 <gregdek> We should probably have a good, generic answer to this basic question.
11:32:00 <gregdek> And we've had a few proposed.
11:32:00 <gregdek> Including:
11:32:00 <cpt_yesterday> Assists with maintainability, etc.
11:32:00 <gregdek> * bake shell scripts into all default euca images;
11:32:00 <gregdek> * make sure that cloud-init is in all euca images;
11:33:00 <gregdek> (Actually, i think those were the main two.)
11:33:00 <cpt_yesterday> first cloud-init has to work on all of the distros we package
11:33:00 <gregdek> yep. That was where we blocked.
11:33:00 <gregdek> Which is why shell scripting was considered instead as a stopgap.
11:33:00 <cpt_yesterday> I guess that it mostly functions but there are still issues on fedora, centos/rhel
11:34:00 <gregdek> The fundamental question for this group is: what method will we commit to for recipe injection, so that we can then focus on getting to the recipes themselves?
11:34:00 <gregdek> That's my take, anyway.
11:35:00 <obino> gregdek: I'm confused here
11:35:00 <cpt_yesterday> Well it all kinda depends
11:35:00 <cpt_yesterday> You can use the basic functionality currently to install puppet, build out your puppet script and finally manually run it
11:36:00 <gregdek> Yeah, we talked about that too.
11:37:00 <cpt_yesterday> If you want to get more complex then you can have a puppet master but you can still already use the current setup to set the hostname, setup hosts with the puppet master, install the puppet client, start the service and have the system setup
11:37:00 <cpt_yesterday> The same can probably be done for chef as well
11:37:00 * gregdek nods.
11:37:00 <cpt_yesterday> If we start with this stuff in bash then eventually we can extend it when cloud-init works everywhere if needed
11:37:00 <gregdek> So:
11:38:00 <gregdek> bash scripts for setting up chef and puppet?
11:38:00 <cpt_yesterday> That was actually supposed to be a blog post soon if I can figure out how to send things from my head to my fingers
11:38:00 * gregdek nods.
11:39:00 <cpt_yesterday> Basically going from the basics of bash to automated puppetmaster on the ECC
11:39:00 <gholms> rbergeron: You don't need to be a chair to use #action. :)
11:39:00 <gholms> Whoops, wrong channel
11:39:00 <gregdek> gholms: :)
11:39:00 <cpt_yesterday> fail
11:39:00 <rbergeron> gholms
11:39:00 <gholms> Haha!  I have successfully baited rbergeron into this meeting! :D
11:39:00 <rbergeron> #action gholms type in the right place, yo :)
11:40:00 * rbergeron waves and is glad to see the euca meeting is just as busy :) ... and runs off
11:40:00 <gregdek> thanks for sabotaging our meeting notes, O MIGHTY FPL
11:40:00 * gholms gives gregdek an #undo if he wants to use it
11:42:00 <gholms> [Meanwhile, back at the ranch...]
11:42:00 <mull> gregdek, lost his mind
11:42:00 <mull> sorry, I meant his wireless
11:42:00 <mull> he'll be back soon
11:42:00 <cpt_yesterday> For the most part with chef and puppet we mainly just need to show people how to set them up easily and then the majority of the recepies can come from the other projects' repos
11:43:00 <cpt_yesterday> And that can be with the default user-data now (bash) and cloud-init
11:43:00 <gregdek> Hi, sorry
11:44:00 <gregdek> cpt_yesterday: that makes sense to me.
11:44:00 <gholms> cpt_yesterday: +1
11:44:00 <gregdek> So again, does this boil down to docs?
11:44:00 <gregdek> "Here's how to set up puppet for euca.  here's how to set up chef for euca."
11:45:00 <cpt_yesterday> Yeah...what you need to automate for easy puppet setups
11:45:00 <cpt_yesterday> Set hostname, install client software, setup hosts entries if needed, etc
11:46:00 <gregdek> How does this differ between "setting up puppet for euca" and just "setting up puppet"?
11:46:00 <cpt_yesterday> It's rather quite basic and as long as certs are signed automatically by the puppet master then it can be rather automatic
11:46:00 <cpt_yesterday> It's mainly just showing someone who uses puppet now how to not have to login to the instance to get puppet talking to it
11:47:00 * gregdek nods.
11:47:00 <gregdek> So, cpt_yesterday, is this a blog post, that one day turns into real documentation, or something?
11:47:00 <cpt_yesterday> And if we want to show a way of creating the puppet manifest in the script and then running it manually we can
11:47:00 <gregdek> Right.
11:47:00 <cpt_yesterday> It could
11:48:00 <cpt_yesterday> I don't know really what you mean by a real document
11:48:00 <gregdek> "Real document" == in the long term, something scot or docs looks at and says "yeah, this could be official."
11:49:00 <gregdek> But not important.
11:49:00 <cpt_yesterday> Yeah I suppose it could become something like that
11:49:00 <cpt_yesterday> Nothing I do is important
11:49:00 <gregdek> cpt_yesterday: so you've basically volunteered to write this post, if I read that right up top. :)
11:49:00 <cpt_yesterday> I guess so
11:50:00 <gregdek> #action cpt_yesterday to write blog post to describe basic setup of puppet with euca
11:50:00 <gregdek> So that's a thing. :)
11:50:00 <gregdek> This could be a lot of things.  But that's a definite thing.
11:51:00 <gregdek> I know there's some confusion around what the scripts project could/should be.
11:51:00 <cpt_yesterday> I've been focusing on puppet lately but I'll look at chef too
11:51:00 <gregdek> It would be cool to be able to see how chef/puppet can turn an ECC instance into a particular flavor of something.  That would be a cool use case.
11:51:00 <cpt_yesterday> Yeah. It has the possibility of overlapping with the images stuff as well
11:52:00 <gregdek> Yep.
11:52:00 <cpt_yesterday> Yeah. I have also been try to figure out a way to setup a puppet master and a ??chef master?? on the ECC that are persistent that users can use but I don't know how well that will work
11:53:00 <gregdek> hspencer: what's your take on this?
11:53:00 <hspencer> sorry gregdek, i stepped away for a sec..lemme catch up..hold on
11:54:00 <gregdek> hspencer: no worries.
11:54:00 <hspencer> k
11:54:00 <hspencer> yea gregdek, i caught up
11:54:00 <hspencer> i read fast
11:54:00 <cpt_yesterday> Don't worry about hspencer's view...I'll change it to mine if it differs :)
11:54:00 <hspencer> so yea, cpt_yesterday is correct
11:54:00 <hspencer> there are a multiple ways to do this
11:54:00 <hspencer> the key thing
11:54:00 <hspencer> is that ther eis a way that the instance can process the user-data
11:54:00 <hspencer> this is where you will pass scripts for puppet, chef, etc
11:55:00 <gregdek> hspencer: yep.
11:55:00 <hspencer> with puppet, you can have different setups
11:55:00 <hspencer> with the puppet master can be in the cloud and outside the cloud
11:55:00 <gregdek> We really need to get cloud-init working everywhere. :/
11:55:00 <hspencer> which chef, you are just grabbin recipes
11:55:00 <hspencer> gregdek, that or custom rc.local
11:55:00 <hspencer> custom rc.local is what AWS used dto do
11:55:00 <hspencer> used to do
11:55:00 <gregdek> So in custom rc.local, how does it work, exactly?
11:56:00 <gregdek> You specify a web server in rc.local to pull the script from?
11:56:00 <hspencer> yea, we have it
11:56:00 <cpt_yesterday> pulls from metadata
11:56:00 <hspencer> its in projects
11:56:00 <obino> https://projects.eucalyptus.com/redmine/projects/recipes/wiki
11:56:00 <gregdek> pulls from metadata fed into what, from where?
11:57:00 <obino> there are links to images and the rc.local
11:57:00 <gregdek> So lemme back up.
11:57:00 <hspencer> metadata from the CC
11:57:00 <gregdek> I have a recipe for a drupal server.
11:57:00 <gregdek> In, say, puppet.
11:57:00 <gregdek> Ah, ok.
11:57:00 <gregdek> So:
11:57:00 <gregdek> there's a custom set of metadata on the cc.
11:58:00 <gregdek> And when an instance boots, how does the rc.local file know where to look for the metadata?
11:58:00 <obino> http://open.eucalyptus.com/participate/wiki/accessing-instance-metadata
11:58:00 <cpt_yesterday> It's always at 169.254.169.254
11:58:00 <gregdek> (Is there documentation I should just read?)
11:58:00 <gregdek> Ding.
11:59:00 * cpt_yesterday checks time...
11:59:00 <gregdek> Yep, getting late.
12:00:00 <gregdek> So I will send out a request for meeting time.
12:00:00 <gregdek> And cpt_yesterday, you're gonna write a blog about how to set up puppet using instance metadata?
12:00:00 <cpt_yesterday> yup
12:01:00 <gregdek> #action cpt_yesterday to write awesome blog post about setting up puppet (and maybe chef) via instance metadata
12:01:00 <gregdek> ok, that's plenty, lol
12:01:00 <gregdek> Sorry it's taking me time to figure out even which questions to ask.
12:01:00 <gregdek> But I'll get it.
12:01:00 <gregdek> Anything else, or is everyone sufficiently beaten down? :)
12:02:00 <gholms> Not from me
12:02:00 <gregdek> okeydoke.
12:02:00 <gregdek> #endmeeting