| === 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] <sauce_> whats the best CentOS 6 AMI with cloud-init? | |
| [16:57] <sauce_> 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] <sauce_> i got the ubuntu version of my cloud-config working (installs puppetlabs apt repo, then installs puppet) | |
| [16:58] <sauce_> 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] <smithmb> 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] <smithmb> 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] <smoser> sauce_, easiest way to do it is with lxc. | |
| [19:21] <smoser> second easiest is with kvm | |
| [19:22] <smoser> both of those are basically just faster ways than ec2 to create a "new instance" | |
| [19:43] <sauce_> smoser i think you're reading yesterday's question | |
| [19:43] <sauce_> my question today has to do with yum_repos module not kicking in | |
| [19:44] <smoser> i dont know about the yum_repo. | |
| [19:44] <smoser> if i had to geuss, i'd guess the version of cloud-init youhave is old and doesn't support that. | |
| [19:44] <smoser> if that was wrong, i'd ask harlowja . | |
| [19:45] <harlowja> ya, depends on the version and such | |
| [19:45] <harlowja> all smoser fault! | |
| [19:45] <harlowja> lol | |
| [19:48] <sauce_> how about the one that ships with amazon linux AMI? | |
| [19:48] <harlowja> not sure, which one is that | |
| [19:48] <harlowja> never quite know what amazon runs :-P | |
| [19:49] <sauce_> ok let me ask you this | |
| [19:49] <sauce_> hmmm not sure how you can help me without getting annoyed, cause i am using old cloud-init | |
| [19:49] <sauce_> let me play around a bit then i'll get back to you guys | |
| [19:50] <sauce_> basically i need to set up my software repo before puppet module kicks in | |
| [19:56] <sauce_> ok next question: | |
| [19:56] <sauce_> i got the repo installed via: runcmd: | |
| [19:56] <sauce_> - rpm -ivh https://yum.puppetlabs.com/el/6/products/x86_64/puppetlabs-release-6-7.noarch.rpm | |
| [19:57] <sauce_> but unfortunately, the puppet module launched BEFORE that. how can i set up dependencies with cloud-init? | |
| [19:57] <harlowja> u have to alter the cloud.cfg that is used, which has the sections of what is ran, bb | |
| [19:58] <sauce_> gotcha | |
| [20:13] <smoser> sauce_, don't use runcmd | |
| [20:13] <smoser> probaably your cloud-init supports bootcmd | |
| [20:13] <smoser> which happens much earlier. | |
| [20:13] <smoser> and probably you can insert the repo then | |
| [20:13] <sauce_> gotcha | |