Ovirt Special topic: Hosted Engine Appliance Use (3)

(6) Engine VM operation Flow
A. Configure the network

ip:192.168.14.77netmask:255.255.252.0gateway:192.168.14.1

B. Configure domain name resolution

192.168.14.67 node.test192.168.14.77 Engine.test

C, execute the command, deploy engine

# engine-setup --config-append=/root/ovirt-engine-answers --offline         # (call answer for configuration (answer file was placed in appliance when making engine-appliance), with offline mode RPM package installed)  [  Info  ] stage: initializing [ info  ] stage: environment  setup           configuration files: [' /etc/ovirt-engine-setup.conf.d/10-packaging-jboss.conf ',  '/etc/ovirt-engine-setup.conf.d/10- Packaging.conf ',  '/root/ovirt-engine-answers ']            Log file: /var/log/ovirt-engine/setup/ovirt-engine-setup-20141009035420-427q5m.log            Version: otopi-1.3.0_master  ( OTOPI-1.3.0-0.0.MASTER.20140911.GIT7C7D631.EL6)  [ info  ] stage: environment  packages setup [ info &nbSP;]  Stage: Programs detection [ INFO  ] Stage: Environment  setup [ info  ] stage: environment customization                      --==  PRODUCT OPTIONS ==--                      Configure Engine on this host  ( Yes, no)  [yes]:            configure  WebSocket Proxy on this host  (Yes, no)  [Yes]:                       -- == packages ==--                                 --== all in one  CONFIGURATION ==--                                -- == network configuration ==--                      setup can automatically configure  the firewall on this system.            note: automatic configuration of the firewall may overwrite  current settings.           do you  want Setup to configure the firewall?  (Yes, no)  [Yes]:   [ info  ] iptables will be configured as firewall manager.            host fully qualified dns name of this  server [engine.test.eayun]:  [WARNING] Failed to resolve  engine.test.eayun using dns, it can be resolved only locally                       --== DATABASE CONFIGURATION ==--                                 --== OVIRT ENGINE CONFIGURATION ==--                      engine  admin password:            confirm engine admin password:                        --== PKI CONFIGURATION ==--                      organization name for  certificate [test.eayun]:                       --== apache configuration ==--                                 --== SYSTEM  configuration ==--                                --== misc configuration ==--                                 --== END OF  configuration ==--           [ info   ] Stage: Setup validation [WARNING] Less than 16384MB of  memory is available        # Memory size detection (ovirt3.5 recommended engine memory size 16384MB)                      --== CONFIGURATION PREVIEW ==--                       application mode                        :  virt           datacenter storage type                  :  false           firewall manager                          : iptables           update  Firewall                          : True            Host FQDN                                :  engine.test.eayun           engine database  name                     : engine           Engine  database secured connection      : false            Engine database host                     : localhost            Engine database user name                : engine            engine database host name validation    : false            Engine database port                     :  5432           engine installation                       : True           PKI organization                          : test.eayun            configure local engine database         :  True           Set application as default page          : True            Configure Apache SSL                     : True            Configure WebSocket Proxy                : True [ INFO  ] Stage:  Transaction setup [ info  ] stopping engine service [ info   ] Stopping ovirt-fence-kdump-listener service [ INFO  ]  stopping websocket-proxy service [ info  ] stage: misc  CONFIGURATION [ INFO  ] Stage: Package installation [ INFO  ] Stage: Misc  CONFIGURATION [ INFO  ] INITIALIZING POSTGRESQL [ INFO  ]  Creating PostgreSQL  ' engine '  database [ info  ] configuring  postgresql [ info  ] creating/refreshing engine database schema  [ INFO  ] Creating CA [ INFO  ] Configuring  Websocket proxy [ info  ] generating post install configuration  file  '/etc/ovirt-engine-setup.conf.d/20-setup-ovirt-post.conf '  [ INFO  ]  stage: transaction commit [ info  ] stage: closing up                       --== summary ==--           [warning] less than 16384mb  Of memory is available           ssh  fingerprint: D9:E9:E9:B5:0C:17:16:9F:8E:9D:B1:12:FD:AE:CA:17            internal ca d1:91:7e:6e:1c:1f:a5:ec:91:be:5a:c5:ed:6b:63:f4:94:a8:df : 31           web access is enabled  at:               http:// engine.test.eayun:80/ovirt-engine                https://engine.test.eayun:443/ovirt-engine            Please use the user  "Admin"  and password specified  in order to login                      --== END OF SUMMARY ==--            [ INFO  ] STARTING ENGINE SERVICE [ INFO  ]  Restarting httpd [ INFO  ] Stage: Clean up            log file is located at /var/log/ Ovirt-engine/setup/ovirt-engine-setup-20141009035420-427q5m.log [ info  ] generating  answer file  '/var/lib/ovirt-engine/setup/answers/20141009035903-setup.conf '  [ info   ] stage: pre-termination [ info  ] stage: termination  [ info  ] execution of setup completed successfully

Here we return to step (5) To continue with the following operation.

Ok. So far, the engine appliance-based hosted engine has been configured.

Open the browser and access the engine's IP address: 192.168.14.77 can access the Ovirt Web management interface.

Some detailed analysis of the whole process, followed by adding ...

This article is from the "Blackart" blog, make sure to keep this source http://blackart.blog.51cto.com/1142352/1561891

Ovirt Special topic: Hosted Engine Appliance Use (3)