ProHoster > Π‘Π»ΠΎΠ³ > administratio > Velox Deploy vm ESXi cum Terraform

Velox Deploy vm ESXi cum Terraform

Salve omnes, nomen meum est Ivan et ego administrator systematis bibitor (OPS).

Volo tibi dicere quomodo machinas virtuales in ESXi explicam sine vCenter Terraformi utens.

Saepius disponere debes / recreare machinas virtuales ut hanc vel illam applicationem experiaris. Ob ignaviam processus automandi cogitavi. Quaestio mea me ad mirificum productum societatis duxit hashicorp', terraform.

Puto multos homines scire quid sit Terraform, et quis nesciat, haec applicatio ad quamlibet nubem, infrastructuram vel servitium utens conceptu IasC disponendi.Infrastructure in codice).

Utor ESXi ut mea virtualisatio environment. Simplex, commodum et certum.
quaestionem praevenio.

Cur terraforme cum Servo vCenter uti potes?

Sane potes, sed. Uno modo haec licentia addita est, secundo, hoc productum est valde resource intensum et simpliciter non convenit in domo mea servo, et tertio facultatem ad upgrade artes.

suggestum Intel NUC ministrantem agit:

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

Prima itaque.

Nunc enim constituamus esxi, scilicet VNC portum aperi in uncinis firewall.

Defalta, tabella scribe-protected. Nos manipulationes sequentes exequimur:

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

hoc obstructionum appendice ad finem tabella:

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

Exitus, salva. Muta iura retro et sileo servitium:

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

Donec rebooted hospes est. Post haec tractatio repetenda erit.

Praeterea omnia opera prope machinae eodem servo perficiam.

Features:

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

Deinceps opus est packeretiam ex HashiCorp.

Necesse est imaginem "auream" statim convenire. quo in futurum utemur.

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

In moventur packer version error in mentem venire potest, quia RedHat-substructio sarcinam eodem nomine contineat.

which -a packer
/usr/sbin/packer

Ad solutionem symlinka creare vel absolutum uti potes /usr/bin/packer.

Nunc opus est ovftool download link. Download, servo indue et institue:

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.

Progredimur.

In gith paravi omnia quae debes. 

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

Ut folder magna necesse est ornamentum distribuendi systematis operantis. In me, hoc est, centos VII.

Etiam tabellam emendare debes. centos-7-base.json:

variables: ΡƒΠΊΠ°Π·Π°Ρ‚ΡŒ свои Π΄Π°Π½Π½Ρ‹Π΅ для ΠΏΠΎΠ΄ΠΊΠ»ΡŽΡ‡Π΅Π½ΠΈΡ
iso_urls: ΡƒΠΊΠ°Π·Π°Ρ‚ΡŒ Π°ΠΊΡ‚ΡƒΠ°Π»ΡŒΠ½Ρ‹ΠΉ
iso_checksum: чСксумма вашСго ΠΎΠ±Ρ€Π°Π·Π°

Post omnes mutationes, conventus currunt;

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

Si omnia recte configurantur et specificantur, videbis imaginem institutionis automaticae operantis. Hic processus accipit me 7-8 minuta.

Post perfectionem in folder output-packer-centos7-x86_64 fasciculus ova collocabitur.

Terraform install:

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

Cum Terraforme provisorem ESXi non habet, unum aedificare debes.

Imus:

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

Deinde provisorem colligimus;

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

Nos ad metam. Eamus imaginem nostram.

Eamus ad folder:

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

Imprimis tabellam edit variables.tf *. Opus nexum cum servo ESXi denotare debes.

In file network_config.cfg continent network occasus futuri virtualis apparatus. Muta ad necessitates tuas et unum tibicen curre;

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

Bene, in tabella main.tf si diversum est, iter in ovum fasciculum ad tuum muta.

Tempus veritatis.

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.

Perfice:

terraform apply

Si omnia recte agantur, in 2-3 minutis nova machina virtualis ex imagine facta prius explicabitur.

Usus in omnibus his non nisi imaginatione finitus est.

Modo volui optimas consuetudines communicare et praecipua demonstrare cum operando cum his productis.

Wisi enim audiat

PS: laetabor ad reprehensionem aedificandam.

Source: www.habr.com