Latest VMWare ESXi 6 on Intel Nuc

30 April 2016 No comments
Last edited by on 30 April 2016 at 19:54
  1. Download and install VMWare vSphere PowerCLI.
    At the moment that I’m writing is version 6.3 Release 1.
  2. Open PowerCLI
  3. Add VMWare official repository
    
    
    1
    Add-EsxSoftwareDepot https://hostupdate.vmware.com/software/VUM/PRODUCTION/main/vmw-depot-index.xml
  4. Search for the latest version.
    First I tried by sorting by ModifiedTime but many were modified the same day

    
    
    1
    2
    3
    4
    5
    6
    7
    8
    9
    10
    11
    12
    13
    14
    15
    16
    17
    18
    19
    20
    21
    22
    23
    24
    25
    26
    27
    28
    29
    30
    31
    32
    33
    PowerCLI C:\> Get-EsxImageProfile -Name "ESXi-6.*" | Sort-Object "ModifiedTime"
    -Descending | format-table -property Name,CreationTime

    Name                                    CreationTime
    ----                                    ------------
    ESXi-6.0.0-20151104001-standard         04/03/2016 03:31:22
    ESXi-6.0.0-20160104001-no-tools         04/03/2016 03:31:22
    ESXi-6.0.0-20160104001-standard         04/03/2016 03:31:22
    ESXi-6.0.0-20160302001-standard         04/03/2016 03:31:22
    ESXi-6.0.0-20160302001-no-tools         04/03/2016 03:31:22
    ESXi-6.0.0-20150704001-no-tools         04/03/2016 03:31:22
    ESXi-6.0.0-20160101001s-standard        04/03/2016 03:31:22
    ESXi-6.0.0-20150504001-standard         04/03/2016 03:31:22
    ESXi-6.0.0-20150704001-standard         04/03/2016 03:31:22
    ESXi-6.0.0-20160204001-no-tools         04/03/2016 03:31:22
    ESXi-6.0.0-20150504001-no-tools         04/03/2016 03:31:22
    ESXi-6.0.0-20150404001-no-tools         04/03/2016 03:31:22
    ESXi-6.0.0-20160204001-standard         04/03/2016 03:31:22
    ESXi-6.0.0-20151104001-no-tools         04/03/2016 03:31:22
    ESXi-6.0.0-20150404001-standard         04/03/2016 03:31:22
    ESXi-6.0.0-20150701001s-standard        04/03/2016 03:31:22
    ESXi-6.0.0-20150902001-no-tools         04/03/2016 03:31:22
    ESXi-6.0.0-20160301001s-standard        04/03/2016 03:31:22
    ESXi-6.0.0-20150902001-standard         04/03/2016 03:31:22
    ESXi-6.0.0-20160301001s-no-tools        04/03/2016 03:31:22
    ESXi-6.0.0-20160101001s-no-tools        04/03/2016 03:31:22
    ESXi-6.0.0-20150901001s-standard        04/03/2016 03:31:22
    ESXi-6.0.0-20150701001s-no-tools        04/03/2016 03:31:22
    ESXi-6.0.0-20151004001-no-tools         04/03/2016 03:31:22
    ESXi-6.0.0-20150901001s-no-tools        04/03/2016 03:31:22
    ESXi-6.0.0-20151004001-standard         04/03/2016 03:31:22
    ESXi-6.0.0-2494585-no-tools             06/02/2015 02:37:25
    ESXi-6.0.0-2494585-standard             06/02/2015 02:37:25

    Then I decided to sort by Name instead.

    
    
    1
    2
    3
    4
    5
    6
    7
    8
    9
    10
    11
    12
    13
    14
    15
    16
    17
    18
    19
    20
    21
    22
    23
    24
    25
    26
    27
    28
    29
    30
    31
    32
    33
    PowerCLI C:\> Get-EsxImageProfile -Name "ESXi-6.*" | Sort-Object "Name" -Descend
    ing | format-table -property Name,CreationTime

    Name                                    CreationTime
    ----                                    ------------
    ESXi-6.0.0-2494585-standard             06/02/2015 02:37:25
    ESXi-6.0.0-2494585-no-tools             06/02/2015 02:37:25
    ESXi-6.0.0-20160302001-standard         04/03/2016 03:31:22
    ESXi-6.0.0-20160302001-no-tools         04/03/2016 03:31:22
    ESXi-6.0.0-20160301001s-standard        04/03/2016 03:31:22
    ESXi-6.0.0-20160301001s-no-tools        04/03/2016 03:31:22
    ESXi-6.0.0-20160204001-standard         04/03/2016 03:31:22
    ESXi-6.0.0-20160204001-no-tools         04/03/2016 03:31:22
    ESXi-6.0.0-20160104001-standard         04/03/2016 03:31:22
    ESXi-6.0.0-20160104001-no-tools         04/03/2016 03:31:22
    ESXi-6.0.0-20160101001s-standard        04/03/2016 03:31:22
    ESXi-6.0.0-20160101001s-no-tools        04/03/2016 03:31:22
    ESXi-6.0.0-20151104001-standard         04/03/2016 03:31:22
    ESXi-6.0.0-20151104001-no-tools         04/03/2016 03:31:22
    ESXi-6.0.0-20151004001-standard         04/03/2016 03:31:22
    ESXi-6.0.0-20151004001-no-tools         04/03/2016 03:31:22
    ESXi-6.0.0-20150902001-standard         04/03/2016 03:31:22
    ESXi-6.0.0-20150902001-no-tools         04/03/2016 03:31:22
    ESXi-6.0.0-20150901001s-standard        04/03/2016 03:31:22
    ESXi-6.0.0-20150901001s-no-tools        04/03/2016 03:31:22
    ESXi-6.0.0-20150704001-standard         04/03/2016 03:31:22
    ESXi-6.0.0-20150704001-no-tools         04/03/2016 03:31:22
    ESXi-6.0.0-20150701001s-standard        04/03/2016 03:31:22
    ESXi-6.0.0-20150701001s-no-tools        04/03/2016 03:31:22
    ESXi-6.0.0-20150504001-standard         04/03/2016 03:31:22
    ESXi-6.0.0-20150504001-no-tools         04/03/2016 03:31:22
    ESXi-6.0.0-20150404001-standard         04/03/2016 03:31:22
    ESXi-6.0.0-20150404001-no-tools         04/03/2016 03:31:22

    So in my case I took ESXi-6.0.0-20160302001-standard

  5. Clone the profile
    
    
    1
    New-EsxImageProfile -CloneProfile "ESXi-6.0.0-20160302001-standard" -name "ESXi-6.0.0-20160302001-standard-NUC” -Vendor "virten.net" -AcceptanceLevel "CommunitySupported"
  6. Add the following repository
    
    
    1
    Add-EsxSoftwareDepot http://vibsdepot.v-front.de
  7. Add the sata-xahci package
    
    
    1
    Add-EsxSoftwarePackage -ImageProfile "ESXi-6.0.0-20160302001-standard-NUC" -SoftwarePackage "sata-xahci"
  8. Export the image
    
    
    1
    Export-ESXImageProfile -ImageProfile "ESXi-6.0.0-20160302001-standard-NUC" -ExportToISO -filepath ESXi-6.0.0-20160302001-standard-NUC.iso
  9. Create a bootable USB disk using Rufus
  10. Enjoy 🙂

 

SOURCE: ESXi 6.0 Image for Intel NUC

Categories: VMWare Tags: , multiplemultiple

Use the Virtual Network Editor in VMware Player 7

7 October 2015 No comments

On VMware Player you don’t have the Virtual Network Editor which is available in VMware Workstation.

To have it in VMware Player 7, you can take it from the VMware Workstation 11 installation package. It will not work if you use VMware Workstation 12.

Open a prompt command, go to the directory where you have the installation package and extract the content with


1
VMware-workstation-full-12.0.0-2985596.exe /extract .\vmware

All files will be extracted into a vmware directory.
Inside here you will find a package called vmwareworkstation.msi.Extract it using 7-Zip. Enter the extracted directory and extract Core.cab.
Go inside the extract directory and you will find vmnetcfg.exe
Now copy this file into your VMware Player diretory, like


1
C:\Program Files (x86)\VMware\VMware Player

Now you can open it and edit your interfaces.

 

SOURCE: How to add Virtual Network Editor to VMware Player, [2], [3]

Ansible: variables resolution in task name.

19 June 2015 No comments
Last edited by on 7 October 2015 at 19:37

Simply you can’t.
Variables are not resolved inside the

1
name

Only inside the actual tasks/conditions etc. the placeholders will be resolved.

 

 

SOURCE: Ansible: variable interpolation in task name

Categories: Ansible Tags: , multiple

Considerations on Ansible handlers

17 June 2015 No comments

1) Handlers should go at the bottom of the PLAY
https://docs.ansible.com/playbooks_roles.html
“And in your main playbook file, just include it like so, at the bottom of a play:”

But I have seen that if you declare it even at the beginning, it works anyway.

2) You can call handlers/*.yml whatever you want, it doesn’t have to be necessarily main.yml

3) In notify you can use


1
notify: mysql_restart

or


1
2
notify:
- mysql_restart

both will work

4) If the handler is defined inside the PLAY, you can call it even from an included task

5) A handler will always be called at the end of the play.
If you need to run it when you notify it, you need to add


1
- meta: flush_handlers

http://wherenow.org/ansible-handlers/

6) Calling the handler multiple times will result in only one run.

https://docs.ansible.com/playbooks_intro.html
“These ‘notify’ actions are triggered at the end of each block of tasks in a playbook, and will only be triggered once even if notified by multiple different tasks.”

Categories: Ansible Tags: , multiple

User input in Ansible

17 June 2015 No comments

To retrieve user input in ansible, you can use vars_prompt but all questions will be asked at the beginning at the playbook.

So there is no way to ask for user input at a task level.

 

SOURCE: Ansible to Conditionally Prompt for a Variable?

Categories: Ansible Tags: , multiple