Hi everyone,

Development is considering the following candidate items for AIX Ansible collection updates. Please vote for your top 3. Also, if you have a suggestion for an automation use case that AIX administrators would highly value, please share in this discussion thread.

Thank you.

1. New module for hdcrypt_facts (showvg, showlv, showconv)
2. NIM module updates to support new AIX installs
3. NIM module updates to support adding filesets into existing lpp sources
4. Enhance the group module to manage LDAP information
5. Add patching support for AIX Live Kernel Update
6. New module to help manage network routes
7. New module to manage paging space
8. New module to manage NFS
9. New module to manage password rules and related policies
10. New module to help with managing GPFS on AIX

Carl,

Hi, good morning.

Here's my Top 3 plus an "ask"

1. Add patching support for AIX Live Kernel Update
2. New module to manage NFS
3. NIM module updates to support new AIX installs

The "ask"

Expand the functionality of the "nim_alt_disk_migration" Role so that it can use Cache VGs along with pre- (Phase 4) and post- (Phase 7) script executions.

Many thanks, Steve

Hi Steve.

Your "ask" is already included in the collection as part of the additions I made for a previous requirement, however it is probably currently undocumented.

There are three additional options:
- nimadm_cache_vg:  Name of VG on NIM Master to use for cacheVG
- nimadm_bundle:    Name of Bundle resource to install post upgrade
- nimadm_bidata:    Name of custom Bos Inst Data to use during upgrade

Below is an example of how to invoke the options.
I'd added the "default('N/A')" to avoid errors if the variable was not defined, as the role is coded for "N/A", but should also work with "default(omit)" 

------------------------------
Rich Jefferies
------------------------------

Rich,

Ah-ha!  Thanks for the guidance.  So we'd be able to use a "script" resource against the "nimadm_bundle" option, correct?

Many thanks, steve

Hi Steve.

The bundle is for fixes to be installed I'm not sure you could use it for the scripts.
My modification on the role was to build up a variable "nimadm_options" which was then passed to the nimadm command:
command: "/usr/sbin/nimadm -c {{ nim_client }} -l {{ lpp_source }} -s {{ spot }} {{ nimadm_options }} -Y -d {{ client_target_disk | quote }}"

The role could be further modified to allow for pre/post scripts to be included. Just watch out for the logic that clears the nimadm_options  variable if  the cache VG or bundle had not previously been passed.

Rich,

Ah, understood.

The piece I'm thinking of is as per the below (taken from my current script).

nimadm -j $cacheVG -l 7311lpp_res -c $1 -s 7311spot_res -a AIX73premigration -z AIX73postmigration -d $2 -P1,2,3,4,5,6 -Y

Where "-a <premigration.script> -z <postmigration.script>" is what I'm wishing to be included within the Role.

I'll take a look to see if I can fathom how to include these as part of the overall Role.  Initial thoughts would be to have "extra" options for "just" the "pre" and "post" scripts a.k.a. Phase 4 and 7 as they're called out in the actual nimadm command's -a and -z parms.

Many thanks, Steve

Hi Carl,

my choice would be:

• 7. New module to manage paging space
• 2. NIM module update to support new AIX installs
• 5. Add patching support for AIX Live Kernel Update

Thanks for asking and the modules development!

Hi Carl,

thanks for asking.

• NIM module updates to support new AIX installs
• New module to manage password rules and related policies
• New module to help with managing GPFS on AIX

Thanks Sascha

My votes would go to ...

2. NIM module updates to support new AIX installs

7. New module to manage paging space

9. New module to manage password rules and related policies

Hi Carl.

Thanks for giving the opportunity for feedback on this.

I'll vote for:

2. NIM module updates to support new AIX installs
5. Add patching support for AIX Live Kernel Update
6. New module to help manage network routes

Cheers Rich

Hi Carl.

Good idea. Thanks.

My wishes:

1. NIM module updates to support new AIX installs
2. New module to manage NFS
3. New module to help with managing GPFS on AIX

Regards

Hi Carl,

thanks for asking.

• NIM module updates to support new AIX installs
• New module to manage paging space
• New module to help with managing GPFS on AIX

My top 3 would be:

1. NIM module updates to support new AIX installs
2. Add patching support for AIX Live Kernel Update
3. New module to manage password rules and related policies

Thank you for the opportunity!

Hello Carl,

here are my top 3.

9. New module to manage password rules and related policies

2. NIM module updates to support new AIX installs

3. NIM module updates to support adding filesets into existing lpp sources

Thanks,

Sebastian

Hello @Carl Burnett!

My favorites would be:

1. Enhance the group module to manage LDAP information
2. New module to manage NFS
3. New module to manage password rules and related policies

Thanks in advance,

With kind regards,

Stephan Dietl

Hi Carl,

My vote is:

Add patching support for AIX Live Kernel Update

NIM module updates to support new AIX installs

New module to manage password rules and related policies

------------------------------
Jeff Yanoviak
------------------------------

Hi Carl,

  My "votes" would be:

2. NIM module updates to support new AIX installs

3. NIM module updates to support adding filesets into existing lpp sources

5. Add patching support for AIX Live Kernel Update

Tim

Hi Carl,
My top 3 would be:

2. NIM module updates to support new AIX installs
5. Add patching support for AIX Live Kernel Update
8. New module to manage NFS

------------------------------
Michal Wiktorek
https://www.linkedin.com/in/michal-wiktorek-83b2b47b
------------------------------

Here is a summary of the voting so far. Thanks to everyone who provided feedback to help us pursue the items of greatest interest.

Hi!

My personal favorites would be:

9. New module to manage password rules and related policies

8. New module to manage NFS

7. New module to manage paging space

Thanks,

  Alexander

Carl,

A module to collect diagnostics for techsupport.

Stephen,

1. `snap` on regular LPAR and on VIOS run with different switches.
2. Non-AIX LPARs use another command.
3. Sometimes logs from HMC are needed too.
4. Collecting diagnostics from all machines is a regular routine.
5. The module is about to collect them all in one place.

Thanks for the suggestion Dennis. There is a Power workstream underway right now exploring automation of first failure data capture from a central point of control. I will make sure they see your post.

One aspect they are looking at is if the data were collected and accessible by the HMC, should there be an option to use call home support to send it to IBM and potentially create a support case. What would be your thoughts on that? Do a large percentage of Clients enable HMC call home?

Carl,

We don't use Call Home support. But the option might be useful for somebody, why not.

Hi!

We usually have it enabled in our HMCs.

Best regards,

  Alexander

This is a long asked for item.  HMCs have the unique position of being connected to " everything " in that they can reach VIOS / VMs AND out to IBM Support via callhome.  Often multiple snaps are required per support ticket.  Initiating these via HMC and then having the uploaded automated with case number.  This would be similar to the LPARDBG but more moxie. 
~
lpardbg -o c -t vios -m sys1 -p vios1,vios2 -r sftp -h sftpserver -u sftpuser --passwd password -c TS123456789  
~
Should be able to select multiple guest VMs as well.

Carl,

I'd rather see an ibm.support collection with modules to open a ticket, upload a file, and add a message to a support ticket (maybe the last two are the same one). Basically API access to the sup[port system, but through Ansible.

ibm.power_aix, ibm.power_hmc, ibm.power_ibmi, ibm.power_vios, et al. should each provide modules that correctly collecte snapshots, logs, or relevant data from their respective platforms.

Separating things this way also allows automating in environments where the uploaded data would need some review - or to pass over an air gap, etc. This gives the client an option to review files that they need to upload, as well as integrate opening tickets into their existing operations. IBM should provide "sample" playbooks in the ibm.power_aix and ibm.power_hmc, and other collections to collect and upload to an existing ticket.

It could also be used by the entire IBM support organization, consulting, services, et al. For all of the platforms.

Thanks Dennis for the suggestion on log collection. As Carl mentioned, it would be helpful to have a discussion and get few more details. If you are interested, please let us know and we will setup a discussion on this topic.

>I'd rather see an ibm.support collection with modules to open a ticket, upload a file, and add a message to a support ticket (maybe the last two
>are the same one). Basically API access to the support system, but through Ansible.

I work in AIX/PowerHA/VM Recovery Manager Support and i really agree with this approach.   I expand it a bit more.

If the above is made available, then IBM SW Products themselves could exploit it automatically, for example:

1) AIX does a system dump, through automation the dump is gathered, a ticket is open to IBM Support, the dump itself is uploaded to the IBM Support testcase server, the Client is informed of all this
2) PowerHA does an unplanned automatic failover from Production to Standby LPAR: same steps as above
3) VM Recovery Manager does an unplanned automatic failover: same steps as above

Going forward the IBM SW Products, in case of the most common/frequent "major" failures, should trigger the above process automatically.

Hi Carl,

My top 3 picks are:

1. New module to help manage network routes
2. New module to manage NFS
3. New module to help with managing GPFS on AIX

Hi Carl.

Following a recent Ansible engagement the recent "VIO Server Readiness" HMC feature came up.
https://www.ibm.com/docs/en/power10?topic=servers-validating-virtual-io-server-maintenance-readiness

It would be very useful to be able to invoke this via Ansible - as the only options are directly on the HMC or using a RestAPI.

Ideally we would be able to use both the readiness check and also the prepare VIOS for maintenance features.

Many thanks
Rich

Hi Rich,

   Thanks for the feedback. We will consider both the VIOS validation and prepare capabilities for future enhancements in the HMC Ansible collections. 

Please find below.

1. Add patching support for AIX Live Kernel Update.
2. NIM module updates to support new AIX installs/upgrade.
3. AIX patching and compliance ready report for regular basis like monthly or as and when required.
4. Proactive health check or server performance ready to use ansible playbook
5. ASM disk creation.
6. GPFS file system expansion.