Hi Everyone,
We have a requirement to automate our entire infrastructure build using vRO. On a bare minimum below are the list of things we would like to achieve.
1. Automated ESXI installation using vRO (SAN boot).
2. The Hardware is CISCO UCS blades.
What is the best suitable option that helps us to achieve the same. If anyone can guide us on the components that are needed it would be really helpful.
Thanks
Sandeep
There is a lot of complexity here and so the first thing is to build your list of requirements and constraints which will inform how you are able to go about automating this. To answer some basic questions.
1. Can we implement the E2E Automation using Auto-deploy?
You can use Auto Deploy for unattended installation of ESXi, yes.
2. Do we need a DHCP/PXE/ server or a kickstart file embedded with in ISO so that the installation wizard can be avoided.
You will need to look at the requirements for Auto Deploy in an unattended install scenario to see what all is required. Auto Deploy itself is going to require DHCP, PXE, TFTP, and a number of other infrastructure pieces in addition to built images, image profiles, host profiles, and other things.
You may also want to look into the possibility of existing vRO packages for Cisco UCS automation. I don't know if such a thing exists, but it stands to reason it might. You'll probably have some requirement to configure the hardware a certain way unless this is done via UCS profiles. Otherwise, you'll still need to control the blades through the CIMC/USCM for basic power and boot tasks.
You will need an extended and complex vRO workflow(s) to achieve this.
Thanks daphnissov for your swift reply. We are looking for high level solution for achieving the same, We have understanding on basic vRO workflows.
To accomplish the ESXI deployment what are the components required. Below are the queries.
1. Can we implement the E2E Automation using Auto-deploy?
2. Do we need a DHCP/PXE/ server or a kickstart file embedded with in ISO so that the installation wizard can be avoided.
@daphnissov We need your expertise so that we can take the implemntation of the workflow forward. The best possible solution suggestion would be really helpful
Looking forward for your response.
Thanks
Sandeep
There is a lot of complexity here and so the first thing is to build your list of requirements and constraints which will inform how you are able to go about automating this. To answer some basic questions.
1. Can we implement the E2E Automation using Auto-deploy?
You can use Auto Deploy for unattended installation of ESXi, yes.
2. Do we need a DHCP/PXE/ server or a kickstart file embedded with in ISO so that the installation wizard can be avoided.
You will need to look at the requirements for Auto Deploy in an unattended install scenario to see what all is required. Auto Deploy itself is going to require DHCP, PXE, TFTP, and a number of other infrastructure pieces in addition to built images, image profiles, host profiles, and other things.
You may also want to look into the possibility of existing vRO packages for Cisco UCS automation. I don't know if such a thing exists, but it stands to reason it might. You'll probably have some requirement to configure the hardware a certain way unless this is done via UCS profiles. Otherwise, you'll still need to control the blades through the CIMC/USCM for basic power and boot tasks.
@daphnissov we could successfully deploy ESXI using Auto-deploy. But we would like to convert the installation to 'Stateful' at later stage.
Looking forward for your response.
Regards
Sandeep
You have the ability to leverage Auto Deploy for stateful installs right from the beginning. There's no need to "convert" from stateless. If you read the documentation, it outlines your options.