Fluch ynset fan vm ESXi mei Terraform

Hallo elkenien, myn namme is Ivan en ik bin in alkoholist systeembehearder (OPS).

Ik soe graach fertelle jo hoe't ik ynsette firtuele masines op ESXi sûnder vCenter mei help fan Terraform.

Hiel faak moatte jo firtuele masines ynsette / opnij oanmeitsje om dizze of dy applikaasje te testen. Fanwegen luiheid tocht ik oan it automatisearjen fan it proses. Myn syktocht late my ta in prachtich produkt fan it bedriuw hashicorp, terraform.

Ik tink dat in protte minsken witte wat Terraform is, mar dejingen dy't it net witte, it is in applikaasje foar it behearen fan elke wolk, ynfrastruktuer of tsjinst mei it IasC-konsept (Ynfrastruktuer as koade).

Ik brûk ESXi as myn virtualization omjouwing. Hiel ienfâldich, handich en betrouber.
Ik foarsjoch in fraach.

Wêrom terraform as jo vCenter Server brûke kinne?

Fansels kinne jo, mar ... As earste is dit in ekstra lisinsje, as twadde is dit produkt heul boarne-yntinsyf en past gewoan net op myn thússerver, en as tredde is it in kâns om jo feardigens te ferbetterjen.

It Intel NUC-platfoarm fungearret as in server:

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.)

En dus, earste dingen earst.

Litte wy no esxi konfigurearje, nammentlik de VNC-poarte iepenje yn 'e firewallynstellingen.

Standert is it bestân skriuwbeskerme. Wy fiere de folgjende manipulaasjes:

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

foegje it folgjende blok ta oan it ein fan it bestân:

<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>

Wy geane út en bewarje. Feroarje de rjochten werom en start de tsjinst opnij:

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

Jildich oant de host op 'e nij opstart is. Neitiid sil dizze manipulaasje werhelle wurde moatte.

Fan no ôf sil ik al it wurk dwaan yn in firtuele masine op deselde server.

Produkt spesifikaasjes:

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

Folgjende wy moatte pakker, ek in produkt fan HashiCorp.

It is nedich om de "gouden" ôfbylding automatysk te sammeljen. Wat wy yn 'e takomst sille brûke.

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

Ûnderweis packer ferzje In flater kin foarkomme om't RedHat-basearre in pakket mei deselde namme kin befetsje.

which -a packer
/usr/sbin/packer

Om dit op te lossen, kinne jo in symlink meitsje of in absolút paad brûke /usr/bin/packer.

No moatte wy ovftool download keppeling. Download, set op de tsjinner en ynstallearje:

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.

Lit ús fierder gean.

Ik haw alles klearmakke wat ik nedich wie foar it optreden.

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

Nei map grut jo moatte ynstallearje it bestjoeringssysteem distribúsje. Yn myn gefal is it centos 7.

Jo moatte ek de triem bewurkje centos-7-base.json:

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

Nei alle wizigingen útfiere de build:

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

As alles goed is konfigureare en spesifisearre, sille jo in ôfbylding sjen fan 'e automatyske ynstallaasje fan it bestjoeringssysteem. Dit proses nimt my 7-8 minuten.

Nei suksesfolle foltôging yn 'e map output-packer-centos7-x86_64 der sil in ova-bestân wêze.

Ynstallearje 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

Sûnt Terraform hat gjin provider foar ESXi, Jo moatte bouwe ien.

Set gean:

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

Dêrnei sammelje wy de provider:

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

Wy binne by de finish. Litte wy ús ôfbylding útrolje.

Gean nei de map:

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

Earst fan alles, bewurkje de triem variables.tf. Jo moatte opjaan in ferbining mei de ESXi tsjinner.

Yn triem network_config.cfg befettet de netwurkynstellingen fan 'e takomstige firtuele masine. Wy feroarje it om oan ús behoeften te passen en rinne de one-liner út:

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

No, yn it bestân main.tf feroarje it paad nei it ova-bestân nei jo eigen, as oars.

It momint fan 'e wierheid.

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.

Ein:

terraform apply

As alles goed is dien, dan sil yn 2-3 minuten in nije firtuele masine wurde ynset fan 'e earder oanmakke ôfbylding.

De opsjes foar it brûken fan dit alles wurde allinich beheind troch jo ferbylding.

Ik woe gewoan myn ûnderfining diele en de haadpunten sjen litte by it wurkjen mei dizze produkten.

Tank foar dyn oandacht!

PS: Ik sil bliid wêze mei konstruktive krityk.

Boarne: www.habr.com