This seems kind of fun.

Advent of Code is a series of small programming puzzles for a variety of skill levels. They are self-contained and are just as appropriate for an expert who wants to stay sharp as they are for a beginner who is just learning to code. Each puzzle calls upon different skills and has two parts that build on a theme.”

I may give this a shot — or at least do the first few days until it gets to be more work than fun.

If you want a good excuse to write do some code in a random language of your choosing, this could be it. I’m using these first few programs as an excuse to write some more Python programs.

Out of box Rundeck does not support pulling LDAP credentials. The basic authentication module only checks against the LDAP server for success/failure, but the internal rdusers database still stores First Name, Last Name, and E-Mail address for each user, but expects them to manually fill out this information themselves.

In a small 5-10 person environment, that’s probably fine. In a 100+ person environment, that’s just asking for problems.

I worked with the Rundeck developers and found out there’s been a ticket for over a year requesting the feature, but it sounds like they don’t really need use/need that, and therefor it’s very low priority (aka probably not going to happen any time soon).

I took a look at the Jetty authentication module which was terrible, and decided I could write a quick fix for myself at least.

It’s not as optimal as having the application do it on login, but I chose to go with a batch script that runs daily and checks for missing e-mail address and pulls the information from LDAP.

The information is fairly static, but I may add a once a month job that re-scans all users and does a force update no matter what — just in case e-mail or name changes (marriage?). Seems unlikely, but it’s something.

I posted the python script on github, and the Rundeck devs were pretty excited and seemed to like it. So that was fun.

Plus, it was a fun excuse to write a python program.

In May of last year I had posted a method to import PeopleSoft OVAs into ESXi. This method was an extension of Nicolas Gasparotto‘s guide that worked for releases 9.2.001 through 9.2.005. The method I posted worked great for 9.2.006 through 9.2.008. However, with the release of 9.2.009 the PeopleSoft image was updated to PeopleTools 8.54, and something has changed. Nicolas has a great write-up of his debugging method, but long story short, you need to update the corresponding OVF:CAPACITY arguments for reach disk from the listed capacity and change it to (capacity*2)-64512.

This method has been successfully tested with 9.2.009 and 9.2.010.

As a very high-level rundown:

  1. Download the ZIPS from Oracle (use the handy wget script supplied through eDelivery)
  2. Unzip the OVA files from the archive. (I recommend unzipping the first file, and running the ova_gen.bat/ file)
  3. Concatenate the OVA files into a single OVA. (see Step 2 suggestion, which will do this for you)
  4. Extract the contents of the OVA file using TAR. (tar xvf FSCM-920-UPD-XXX.OVA)

Up to this point, nothing has changed from the original guide. Here is where the new steps come in.

You must update the following lines of the OVF file:

  1. Find each of the <Disk ovf:capacity=”#######” …> lines.
    • Open up a calculator and change each of the #######’s to ( (#######*2) – 64512).
  2. Update the OperatingSystemSection:
    • Update the ovf:id,  <OperatingSystemSection ovf:id=”101“>
    • Update the Description,  <Description>oracleLinux64Guest</Description>
    • Update the vbox:OSType,   <vbox:OSType ovf:required=”false”>oracleLinux64Guest</vbox:OSType>
  3. Update the VirtualHardwareSection:
    • <vssd:VirtualSystemType>vmx-08</vssd:VirtualSystemType>

From this point on you can continue with the original guide as normal, but skipping the vmkfstools steps. Which leaves:

  1. If you don’t already have it, download install the lastest OvfTool:
    • ./VMware-ovftool-4.0.0-2301625-lin.x86_64.bundle
  2. Import the OVF into your VMware environment:
    • ovftool –lax -ds=<datastorename> “–net:HostOnly=<Network Name>” <APP>DB-SES-854-05.ovf “vi://<vmware_user>:<vmware_password>@<IP_ADDRESS>:433″

That’s it. You have imported the new PeopleSoft Update Image into VMware!

« newerolder »