[09:55] <Odd_Bloke> smoser: So I think https://access.redhat.com/documentation/en-US/Red_Hat_Software_Collections/1/html/1.0_Release_Notes/chap-RHSCL.html#sect-RHSCL-Features is enough for us to be happy that Python 2.7 is viable on RHEL6.
[09:55] <Odd_Bloke> "all Red Hat Software Collections components are fully supported under Red Hat Enterprise Linux Subscription Level Agreements, are functionally complete, and are intended for production use."
[09:58] <Odd_Bloke> smoser: And, in fact, GCE Red Hat 6 instances come with the Python 2.7 SCL already installed.
[12:29] <gin> Hello, would you be kind to help me out with Cloud-Init configuration? I want to bootstrap Puppet agent for CentOS 7 (AWS AMI). The given example http://cloudinit.readthedocs.org/en/latest/topics/examples.html#setup-and-run-puppet does not work. From the logs I can see puppet package is missing.
[12:29] <gin> Is this the expected behaviour and I need to add puppet repository myself?
[12:55] <smoser> Odd_Bloke, that is odd. why is that not even remotely what you get when you google python 2.7 rhel
[12:56] <smoser> as recent as july, you have posts like this:
[12:56] <smoser>  http://tecadmin.net/install-python-2-7-on-centos-rhel/#
[13:00] <Odd_Bloke> smoser: If you're a RHEL user, I don't think you have to Google to find solutions.
[13:00] <Odd_Bloke> You have Red Hat to tell you about them. :p
[13:00] <smoser> that just doesnt make sense though.
[13:01] <smoser> and if people are writing things like that blog post (who apparently *are* redhat customers) then surely they're not just doing it because they like compiling their own python
[13:02] <Odd_Bloke> Well, that blog post is about CentOS, not RHEL.
[13:07] <Odd_Bloke> smoser: CentOS appears to have SCLs as well.
[13:08] <smoser> https://wiki.centos.org/AdditionalResources/Repositories/SCL#head-9c6aea9c13b921d5258446c4c5e5886571bdb741
[13:08] <smoser> yeah.
[13:08] <smoser> (x86_64 only)
[13:08] <smoser> ok. i'm sold on 2.7 for rhel
[13:11] <Odd_Bloke> smoser: GCE image for CentOS 6 also has Python 2.7 installed via SCL, so I think it's viable for both.
[13:23] <gin> How to enforce sequential execution in cloud-init script? The following script adds repository after the attempt to install the package that requires it. http://pastebin.com/YK2SRBnZ
[13:28] <gin> I can't seem to find any documentation regarding this...
[13:30] <larsks> gin: modules are executed in the order in which they are listed in your cloud-init configuration (usually, /etc/cloud/cloud.cfg + whatever #cloud-config data you pass in)
[13:30] <larsks> Typically, runcmd happens near the end of things.
[13:30] <larsks> However, there is an "add repository" module that may be enabled to run before "
[13:30] <larsks> ...before "packages"
[13:31] <larsks> E.g., this example: http://cloudinit.readthedocs.org/en/latest/topics/examples.html#adding-a-yum-repository
[13:32] <larsks> In centos and RHEL, the yum-add-repo module is enabled by default and configured to run before package-update-upgrade-install.
[13:35] <gin> thanks larsks for calrifying. Will try it out now.
[14:51] <gin> has anyone tried cloud-init puppet conf? (http://cloudinit.readthedocs.org/en/latest/topics/examples.html#setup-and-run-puppet)
[14:51] <gin> for CentOS7
[14:52] <gin> I get warning and hence empty puppet.conf file:  util.py[WARNING]: Running puppet (<module 'cloudinit.config.cc_puppet' from '/usr/lib/python2.7/site-packages/cloudinit/config/cc_puppet.pyc'>) failed
[15:02] <smoser> gin,  i suspect it needs fixing.
[15:28] <gin> smoser, seems like so.
[15:37] <smoser> Odd_Bloke, https://code.launchpad.net/~daniel-thewatkins/cloud-init/shim_fixes/+merge/269199
[15:37] <smoser> comments tehre.
[15:48] <Odd_Bloke> smoser: Oh, yeah, I'd lost track of that.
[15:48] <Odd_Bloke> Thanks!