Quick Deploy vm ESXi nge Terraform

Sanibonani nonke, igama lami ngingu-Ivan futhi ngingumqondisi wesistimu yotshwala (OPS).

Ngingathanda ukukutshela ukuthi ngihambisa kanjani imishini ebonakalayo ku-ESXi ngaphandle kwe-vCenter usebenzisa i-Terraform.

Imvamisa, kufanele usebenzise / udale kabusha imishini ebonakalayo ukuze uhlole lokhu noma lolo hlelo lokusebenza. Ngenxa yobuvila, ngacabanga ngokwenza inqubo ngokuzenzakalelayo. Ukusesha kwami ​​kwangiholela emkhiqizweni omuhle wenkampani i-hashicorp, terraform.

Ngicabanga ukuthi abantu abaningi bayazi ukuthi i-Terraform iyini, futhi ngubani ongazi, lolu uhlelo lokusebenza lokuphatha noma yiliphi ifu, ingqalasizinda noma isevisi usebenzisa umqondo we-IasC (Ingqalasizinda njengekhodi).

Ngisebenzisa i-ESXi njengendawo yami yokwenza izinto ezibonakalayo. Ilula, elula futhi enokwethenjelwa.
Ngilindele umbuzo.

Kungani terraform lapho ungasebenzisa vCenter Server?

Ungakwazi Yebo, kodwa. Okokuqala, lena ilayisensi eyengeziwe, okwesibili, lo mkhiqizo unamandla kakhulu futhi awuhambisani neseva yami yasekhaya, futhi okwesithathu, ikhono lokuthuthukisa amakhono.

Ipulatifomu ye-Intel NUC isebenza njengeseva:

CPU: 2 CPUs x Intel(R) Core(TM) i3-4010U CPU @ 1.70GHz
RAM: 8Gb
HDD: 500Gb
ESXi version: ESXi-6.5.0-4564106-standard (VMware, Inc.)

Futhi ngakho, izinto zokuqala kuqala.

Okwamanje, ake simise i-esxi, okungukuthi, sivule imbobo ye-VNC kuzilungiselelo zohlelo lokuvikela.

Ngokuzenzakalelayo, ifayela livikelwe ngokubhala. Senza lokhu kukhohlisa okulandelayo:

chmod 644 /etc/vmware/firewall/service.xml
chmod +t /etc/vmware/firewall/service.xml
vi /etc/vmware/firewall/service.xml

engeza ibhulokhi elandelayo ekupheleni kwefayela:

<service id="1000">
  <id>packer-vnc</id>
  <rule id="0000">
    <direction>inbound</direction>
    <protocol>tcp</protocol>
    <porttype>dst</porttype>
    <port>
      <begin>5900</begin>
      <end>6000</end>
    </port>
  </rule>
  <enabled>true</enabled>
  <required>true</required>
</service>

Phuma, londoloza. Shintsha amalungelo emuva futhi uqale kabusha isevisi:

chmod 444 /etc/vmware/firewall/service.xml
esxcli network firewall refresh

Okwangempela kuze kube yilapho umsingathi eqalwa kabusha. Ngemva kwalokho, lokhu kukhwabanisa kuzodingeka kuphindwe.

Ngaphezu kwalokho, ngizokwenza wonke umsebenzi emshinini obonakalayo kuseva efanayo.

Ukucaciswa komkhiqizo:

OS: Centos 7 x86_64 minimal
RAM: 1GB
HDD: 20GB
Selinux: disable
firewalld: disable

Okulandelayo, sidinga iphakethe, futhi umkhiqizo we-HashiCorp.

Kudingeka ukuhlanganisa ngokuzenzakalela isithombe "segolide". esizoyisebenzisa esikhathini esizayo.

yum install unzip git -y
curl -O https://releases.hashicorp.com/packer/1.5.5/packer_1.5.5_linux_amd64.zip
unzip packer_1.5.5_linux_amd64.zip -d /usr/bin && rm -rf packer_1.5.5_linux_amd64.zip
packer version
Packer v1.5.5

Ohambweni Packer version kungase kwenzeke iphutha, njengoba i-RedHat-based ingase iqukethe iphakheji enegama elifanayo.

which -a packer
/usr/sbin/packer

Ukuze uthole isisombululo, ungakha i-symlink, noma usebenzise indlela ephelele /usr/bin/packer.

Manje sidinga ovftool ukulanda isixhumanisi. Landa, faka iseva bese ufaka:

chmod +x VMware-ovftool-4.4.0-15722219-lin.x86_64.bundle
./VMware-ovftool-4.4.0-15722219-lin.x86_64.bundle
Extracting VMware Installer...done.
You must accept the VMware OVF Tool component for Linux End User
License Agreement to continue.  Press Enter to proceed.
VMWARE END USER LICENSE AGREEMENT
Do you agree? [yes/no]:yes
The product is ready to be installed.  Press Enter to begin
installation or Ctrl-C to cancel. 
Installing VMware OVF Tool component for Linux 4.4.0
    Configuring...
[######################################################################] 100%
Installation was successful.

Siqhubekela phambili.

Ku-gith ngilungiselele konke okudingayo.

git clone https://github.com/letnab/create-and-deploy-esxi.git && cd create-and-deploy-esxi

Kufolda big udinga ukubeka ikhithi yokusabalalisa yesistimu yokusebenza. Endabeni yami, lokhu kungu-centos 7.

Udinga futhi ukuhlela ifayela. centos-7-base.json:

variables: указать свои данные для подключения
iso_urls: указать актуальный
iso_checksum: чексумма вашего образа 

Ngemuva kwazo zonke izinguquko, qalisa umhlangano:

/usr/bin/packer build centos-7-base.json

Uma konke kulungiselelwe futhi kucaciswe kahle, khona-ke uzobona isithombe sokufakwa okuzenzakalelayo kwesistimu yokusebenza. Le nqubo ingithatha amaminithi angu-7-8.

Ngemva kokuqedwa ngempumelelo kufolda okukhipha-packer-centos7-x86_64 ifayela le-ova lizotholakala.

Faka i-Terraform:

curl -O https://releases.hashicorp.com/terraform/0.12.24/terraform_0.12.24_linux_amd64.zip
unzip terraform_0.12.24_linux_amd64.zip -d /usr/bin/ && rm -rf terraform_0.12.24_linux_amd64.zip
terraform version
Terraform v0.12.24

Njengoba i-Terraform ingenaye umhlinzeki we-ESXi, udinga ukwakha eyodwa.

Siyahamba:

cd /tmp
curl -O https://dl.google.com/go/go1.14.2.linux-amd64.tar.gz
tar -C /usr/local -xzf go1.14.2.linux-amd64.tar.gz && rm -rf go1.14.2.linux-amd64.tar.gz
export PATH=$PATH:/usr/local/go/bin
go version
go version go1.14.2 linux/amd64

Okulandelayo, siqoqa umhlinzeki:

go get -u -v golang.org/x/crypto/ssh
go get -u -v github.com/hashicorp/terraform
go get -u -v github.com/josenk/terraform-provider-esxi
export GOPATH="$HOME/go"
cd $GOPATH/src/github.com/josenk/terraform-provider-esxi
CGO_ENABLED=0 GOOS=linux GOARCH=amd64 go build -a -ldflags '-w -extldflags "-static"' -o terraform-provider-esxi_`cat version`
cp terraform-provider-esxi_`cat version` /usr/bin

Sesisentanjeni. Asihambe sikhiphe isithombe sethu.

Asiye kufolda:

cd /root/create-and-deploy-esxi/centos7

Okokuqala, hlela ifayela okuguquguqukayo.tf. Udinga ukucacisa uxhumano kwiseva ye-ESXi.

Kufayela network_config.cfg ziqukethe izilungiselelo zenethiwekhi zomshini wokubuka wesikhathi esizayo. Shintsha ezidingweni zakho bese usebenzisa i-one-liner:

sed -i -e '2d' -e '3i "network": "'$(gzip < network_config.cfg| base64 | tr -d 'n')'",' metadata.json

Awu, kufayela main.tf shintsha indlela eya kufayela le-ova ibe ngeyakho, uma ihlukile.

Isikhathi seqiniso.

terraform init
Initializing the backend...

Initializing provider plugins...

The following providers do not have any version constraints in configuration,
so the latest version was installed.

To prevent automatic upgrades to new major versions that may contain breaking
changes, it is recommended to add version = "..." constraints to the
corresponding provider blocks in configuration, with the constraint strings
suggested below.

* provider.esxi: version = "~> 1.6"
* provider.template: version = "~> 2.1"

Terraform has been successfully initialized!

You may now begin working with Terraform. Try running "terraform plan" to see
any changes that are required for your infrastructure. All Terraform commands
should now work.

If you ever set or change modules or backend configuration for Terraform,
rerun this command to reinitialize your working directory. If you forget, other
commands will detect it and remind you to do so if necessary.

terraform plan
Refreshing Terraform state in-memory prior to plan...
The refreshed state will be used to calculate this plan, but will not be
persisted to local or remote state storage.

data.template_file.Default: Refreshing state...
data.template_file.network_config: Refreshing state...

------------------------------------------------------------------------

An execution plan has been generated and is shown below.
Resource actions are indicated with the following symbols:
  + create

Terraform will perform the following actions:

  # esxi_guest.Default will be created
  + resource "esxi_guest" "Default" {
      + boot_disk_size         = (known after apply)
      + disk_store             = "datastore1"
      + guest_name             = "centos7-test"
      + guest_shutdown_timeout = (known after apply)
      + guest_startup_timeout  = (known after apply)
      + guestinfo              = {
          + "metadata"          = "base64text"
          + "metadata.encoding" = "gzip+base64"
          + "userdata"          = "base64text"
          + "userdata.encoding" = "gzip+base64"
        }
      + guestos                = (known after apply)
      + id                     = (known after apply)
      + ip_address             = (known after apply)
      + memsize                = "1024"
      + notes                  = (known after apply)
      + numvcpus               = (known after apply)
      + ovf_properties_timer   = (known after apply)
      + ovf_source             = "/root/create-and-deploy-esxi/output-packer-centos7-x86_64/packer-centos7-x86_64.ova"
      + power                  = "on"
      + resource_pool_name     = (known after apply)
      + virthwver              = (known after apply)

      + network_interfaces {
          + mac_address     = (known after apply)
          + nic_type        = (known after apply)
          + virtual_network = "VM Network"
        }
    }

Plan: 1 to add, 0 to change, 0 to destroy.

------------------------------------------------------------------------

Note: You didn't specify an "-out" parameter to save this plan, so Terraform
can't guarantee that exactly these actions will be performed if
"terraform apply" is subsequently run.

Qeda:

terraform apply

Uma konke kwenziwa ngendlela efanele, khona-ke emaminithini angu-2-3 umshini omusha we-virtual uzosetshenziswa kusukela esithombeni esenziwe ngaphambilini.

Ukusetshenziswa kwakho konke lokhu kunqunyelwe umcabango wakho kuphela.

Bengifuna nje ukwabelana ngemikhuba ehamba phambili futhi ngibonise amaphuzu abalulekile lapho ngisebenza ngale mikhiqizo.

Ngiyabonga ngokunaka!

PS: Ngingakujabulela ukugxekwa okwakhayo.

Source: www.habr.com