=== gondoi is now known as zz_gondoi === zz_gondoi is now known as gondoi === gondoi is now known as zz_gondoi === shardy_afk is now known as shardy === zz_gondoi is now known as gondoi === gondoi is now known as zz_gondoi [16:04] whats the best CentOS 6 AMI with cloud-init? [16:57] i am using Bashton's CentOS 6.4 AMI with cloud-init. i am installing the puppetlabs yum repo via "yum_repo module," for use with installing puppet via the "puppet module". unfortunately the yum repo doesn't get added, so the puppet install fails. any ideas? [16:57] i got the ubuntu version of my cloud-config working (installs puppetlabs apt repo, then installs puppet) [16:58] also, how do i test cloud-init manually? right now i keep on spinning up new instances to test === harlowja_away is now known as harlowja [17:50] Hi folks -- I'm trying to configure chef using cloud init, and it's giving me complaints about apt-get in a stacktrace. But I'm using install_type: "omnibus" ... which shouldn't do an apt-get. Is omnibus still a valid type? [18:05] ah, apparently 12.04 has an earlier version of cloud-init that doesn't support omnibus === zz_gondoi is now known as gondoi [19:06] * sauce_ patiently waits for smoser to get back === alexpilotti_ is now known as alexpilotti [19:21] sauce_, easiest way to do it is with lxc. [19:21] second easiest is with kvm [19:22] both of those are basically just faster ways than ec2 to create a "new instance" [19:43] smoser i think you're reading yesterday's question [19:43] my question today has to do with yum_repos module not kicking in [19:44] i dont know about the yum_repo. [19:44] if i had to geuss, i'd guess the version of cloud-init youhave is old and doesn't support that. [19:44] if that was wrong, i'd ask harlowja . [19:45] ya, depends on the version and such [19:45] all smoser fault! [19:45] lol [19:48] how about the one that ships with amazon linux AMI? [19:48] not sure, which one is that [19:48] never quite know what amazon runs :-P [19:49] ok let me ask you this [19:49] hmmm not sure how you can help me without getting annoyed, cause i am using old cloud-init [19:49] let me play around a bit then i'll get back to you guys [19:50] basically i need to set up my software repo before puppet module kicks in [19:56] ok next question: [19:56] i got the repo installed via: runcmd: [19:56] - rpm -ivh https://yum.puppetlabs.com/el/6/products/x86_64/puppetlabs-release-6-7.noarch.rpm [19:57] but unfortunately, the puppet module launched BEFORE that. how can i set up dependencies with cloud-init? [19:57] u have to alter the cloud.cfg that is used, which has the sections of what is ran, bb [19:58] gotcha [20:13] sauce_, don't use runcmd [20:13] probaably your cloud-init supports bootcmd [20:13] which happens much earlier. [20:13] and probably you can insert the repo then [20:13] gotcha