ProHoster > Blog > Rêveberî > Bi Terraform re Vm ESXi bi lez saz bikin

Bi Terraform re Vm ESXi bi lez saz bikin

Silav her kes, navê min Ivan e û ez rêveberek pergala alkolîk (OPS) me.

Ez dixwazim ji we re vebêjim ka ez çawa makîneyên virtual li ser ESXi bêyî vCenter bi karanîna Terraform-ê bicîh dikim.

Pir caran, ji bo ceribandina vê an wê serîlêdanê pêdivî ye ku hûn makîneyên virtual bicîh bikin / ji nû ve biafirînin. Ji ber tembeliyê, ez li ser otomatîkkirina pêvajoyê fikirîm. Lêgerîna min ez birin ber hilberek ecêb a pargîdaniyê hashicorp, terraform.

Ez difikirim ku gelek kes dizanin Terraform çi ye, û kî nizane, ev serîlêdanek e ji bo birêvebirina her ewr, binesaziyek an karûbar bi karanîna têgeha IasC (Binesaziya wekî kodê).

Ez ESXi wekî hawîrdora xweya virtualîzasyonê bikar tînim. Pir hêsan, hêsan û pêbawer.
Ez pirsek pêşbîn dikim.

Çima terraform gava ku hûn dikarin Servera vCenter bikar bînin?

Hûn dikarin bê guman, lê. Ya yekem, ev lîsansek pêvek e, ya duyemîn jî, ev hilber pir çavkaniyek zexm e û bi hêsanî li ser servera xaniyê min nagire, û ya sêyemîn jî, şiyana nûvekirina jêhatîbûnê ye.

Platforma Intel NUC wekî serverek tevdigere:

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

Û vî awayî, yekem tiştên pêşîn.

Heya nuha, em esxi saz bikin, ango, porta VNC-ê di mîhengên dîwarê de vekin.

Ji hêla xwerû ve, pel ji hêla nivîsandinê ve tê parastin. Em manipulasyonên jêrîn pêk tînin:

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

bloka jêrîn li dawiya pelê zêde bikin:

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

Derkeve, xilas bike. Mafên paşde biguherînin û karûbarê ji nû ve bidin destpêkirin:

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

Rastî heya ku mêvandar ji nû ve were destpêkirin. Piştî vê yekê, ev manîpulasyon dê were dubare kirin.

Digel vê yekê, ez ê hemî karan di makîneyek virtual de li ser heman serverê pêk bînim.

Specification Product:

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

Piştre, em hewce ne pakker, di heman demê de hilberek HashiCorp.

Pêdivî ye ku bixweber wêneya "zêrîn" were berhev kirin. ku em ê di pêşerojê de bikar bînin.

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

Li ser tevgerê guhertoya pakker dibe ku xeletiyek çêbibe, ji ber ku RedHat-based dibe ku pakêtek bi heman navî hebe.

which -a packer
/usr/sbin/packer

Ji bo çareseriyê, hûn dikarin simlinkek biafirînin, an rêyek bêkêmasî bikar bînin /usr/bin/packer.

Niha em hewceyê ovftool download link. Dakêşin, bixin ser serverê û saz bikin:

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.

Em diçin.

Li ser githê min her tiştê ku hûn hewce ne amade kir. 

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

Ji bo peldankê mezin hûn hewce ne ku kîtê belavkirina pergala xebitandinê deynin. Di doza min de, ev centos 7 e.

Hûn jî hewce ne ku pelê biguherînin. centos-7-base.json:

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

Piştî hemî guhertinan, meclîsê bimeşînin:

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

Ger her tişt rast were mîheng kirin û diyar kirin, wê hingê hûn ê wêneyek sazkirina otomatîkî ya pergala xebitandinê bibînin. Ev pêvajo ji min re 7-8 hûrdeman digire.

Piştî qedandina serkeftî di peldankê de encam-packer-centos7-x86_64 pelê ova dê were cih.

Terraform saz bikin:

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

Ji ber ku Terraform ji bo ESXi peydakarek tune, hûn hewce ne ku yek ava bikin.

Em diavêjin:

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

Piştre, em pêşkêşker berhev dikin:

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

Em di xeta dawî de ne. Ka em herin wêneyê xwe derxînin.

Ka em biçin peldankê:

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

Berî her tiştî, pelê biguherînin guherbar.tf. Pêdivî ye ku hûn pêwendiyek bi servera ESXi re diyar bikin.

Di pelê de network_config.cfg mîhengên torê yên makîneya virtual ya pêşerojê vedihewîne. Li gorî hewcedariyên xwe biguhezînin û yek-liner bimeşînin:

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

Belê, di pelê de sereke.tf riya pelê ova bi xwe biguherînin, heke cûda be.

Dema rastiyê.

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.

Qedandin:

terraform apply

Ger her tişt rast were kirin, wê hingê di nav 2-3 hûrdeman de makîneyek nû ya virtual ji wêneya berê hatî çêkirin were bicîh kirin.

Bikaranîna van hemîyan tenê ji hêla xeyala we ve têne sînorkirin.

Min tenê dixwest ku ez pratîkên çêtirîn parve bikim û gava ku bi van hilberan re dixebitim xalên sereke nîşan bidim.

Spas ji bo baldariya we!

PS: Ez ê bi rexneyên çêker kêfxweş bibim.

Source: www.habr.com

Add a comment