April 2013 - Devel - oVirt List Archives

[Engine-devel] Migrating engine-setup to otopi
by Alex Lourie 10 May '13

10 May '13

Hi All Recent development of the otopi [1] framework allows us to migrate the engine-setup, upgrade and cleanup (and potentially other) utilities to implementation as an otopi plugin. Potential benefits of such a move are: 1. Be able to port engine to other distributions. 2. Be able to install engine in a development mode. 3. Be able to customize installation easily. 4. Share installation of components (reports, dwh). 5. Modular implementation, reduce maintenance costs. 6. Code reuse of installer code for multiple purposes (host-deploy, enigne-setup). Currently we are in the process of creating a 'setup' plugin for the otopi, and the progress can be monitored at [2]. The current roadmap for the feature is as follows: 1. Recreate the configuration utilities as plugins in otopi. 2. Support side-by side installation using both the old and the new utilities. 3. Switch to the new utility when the confidence that it is on-par with an old one is high. Our goal is to have the new utilities ready for 3.3 release (at least for the step 2 in the roadmap). We'd like to hear as much feedback as possible, so we could address it as soon as possible. Thanks! [1] http://gerrit.ovirt.org/#/q/project:otopi,n,z [2] http://www.ovirt.org/Features/Otopi_Infra_Migration

6 12

[Engine-devel] Dropping encryption of database password
by Alon Bar-Lev 06 May '13

06 May '13

Hello, Currently we store database password encrypted using org.picketbox.datasource.security.SecureIdentityLoginModule. This is reverse encryption with common knowledge shared secret. Using encryption with common knowledge shared secret is close to void protection. So far we also stored the password as plain text at /etc/ovirt-engine/.pgpass, this is going to be removed as no component actually uses the .pgpass, however we do need to store non-java specific password in for utilities. In master (aiming to 3.3), we store the database connection details in own file /etc/ovirt-engine/engine.conf.d/50-setup-database.conf owned by ovirt user and not world readable. I would like to use the same 50-setup-database.conf to store plain text password and remove the java specific reversible encrypted password usage. Bottom line... 1. We drop the .pgpass file. 2. We store database connection information in /etc/ovirt-engine/engine.conf.d/<file> that is readable only by ovirt usage. 3. We drop the java specific reversible encryption in favor of plain text. Thoughts? Alon

6 16

[Engine-devel] Any way to setup ovirt engine 3.2.0 or 3.2.1 running enviroment?
by Chen, Wei D 03 May '13

03 May '13

Hi, We notice that ovirt-engine's version (rpm package and source code) has updated from 3.2.0 to 3.2.1. As our development process is always based on 3.2.0. Is there any way to re-setup 3.2.0 running environment? Besides, we also cannot setup 3.2.1 ovrit-engine running environment as its dependent package glusterfs-3.4 cannot be found from ovirt repo or fedora18 repo. How can I fix this issue? Thanks. Best Regards, Dave Chen

4 7

[Engine-devel] REST vs. UI validation
by Whitcomb, Kari 02 May '13

02 May '13

I've been making use of the oVirt REST api, and have noticed that in several cases the validation done for a REST request is different than what the admin UI does. It seems that the UI is generally more restrictive on the data it will accept than the backend. So you can set things up using the REST api that the UI wouldn't let you do. Two examples I've hit recently, both in the cluster policy (load balancing section): - Cluster load balancing policy duration - the UI requires a value between 1 and 100, but the REST api seems to let you set it to any integer. - Cluster load balancing high and low thresholds / max and min service levels - The UI restricts the high value to 51-90% and the low value to 10-50%. But the backend only requires that the values be 0-100% and that low can't be greater than high. So my question - is this intended behavior, or is it a bug that the validation is different? If similar validation should be done through both the UI and REST api, should the UI be less restrictive, or the backend more restrictive? Thanks, Kari

6 10

[Engine-devel] Error: could not create ovirtsdk API object
by 李强 02 May '13

02 May '13

HI：All I build source and rpm -Uvh ovirt-engine-setup-plugin-allinone-3.3.0-0.2.master.20130427145036.fc18.noarch.rpm But I engine-setup have ERROR. Error: could not create ovirtsdk API object OS:F18 mini install. =================================== [root@localhost ~]# engine-setup Welcome to oVirt Engine setup utility WARNING: oVirt Engine setup has already been run on this host. To remove all configuration and reset oVirt Engine please run engine-cleanup. Please be advised that executing engine-setup without cleanup is not supported. Would you like to proceed? (yes|no): yes In order to proceed the installer must stop the ovirt-engine service Would you like to stop the ovirt-engine service? (yes|no): yes oVirt Engine uses httpd to proxy requests to the application server. It looks like the httpd installed locally is being actively used. The installer can override current configuration . Alternatively you can use JBoss directly (on ports higher than 1024) Do you wish to override current httpd configuration and restart the service? ['yes'| 'no'] [yes] : HTTP Port [80] : HTTPS Port [443] : Setup can configure server default page to launch oVirt Engine. Do you wish to do so? ['yes'| 'no'] [yes] : Host fully qualified domain name. Note: this name should be fully resolvable [localhost] : engine.startn.com Enter a password for an internal oVirt Engine administrator user (admin@internal) : Warning: Weak Password. Confirm password : Organization Name for the Certificate [localhost] : The engine can be configured to present the UI in three different application modes. virt [Manage virtualization only], gluster [Manage gluster storage only], and both [Manage virtualization as well as gluster storage] ['virt'| 'gluster'| 'both'] [both] : The default storage type you will be using ['NFS'| 'FC'| 'ISCSI'| 'POSIXFS'] [NFS] : Enter DB type for installation ['remote'| 'local'] [local] : Enter a password for a local oVirt Engine DB admin user (engine) : Warning: Weak Password. Confirm password : Local ISO domain path [/var/lib/exports/iso_2013_04_28_15_18_22] : Firewall ports need to be opened. The installer can configure firewall automatically overriding the current configuration. The old configuration will be backed up. Alternately you can configure the firewall later using an example file selecting None. Which firewall manager do you wish to use? ['None'| 'Firewalld'| 'iptables']: Firewalld Configure VDSM on this host? ['yes'| 'no'] [yes] : yes Local storage domain path [/var/lib/images_2013_04_28_15_18_22] : Confirm root password : oVirt Engine will be installed using the following configuration: ================================================================= override-httpd-config: yes http-port: 80 https-port: 443 override-httpd-root: yes host-fqdn: engine.startn.com auth-pass: ******** org-name: localhost application-mode: both default-dc-type: NFS db-remote-install: local db-local-pass: ******** nfs-mp: /var/lib/exports/iso_2013_04_28_15_18_22 firewall-manager: Firewalld config-allinone: yes storage-path: /var/lib/images_2013_04_28_15_18_22 superuser-pass: ******** Proceed with the configuration listed above? (yes|no): yes Installing: AIO: Validating CPU Compatibility... [ DONE ] AIO: Adding firewall rules... [ DONE ] Configuring oVirt Engine... [ DONE ] Configuring JVM... [ DONE ] Creating CA... [ DONE ] Updating ovirt-engine service... [ DONE ] Setting Database Configuration... [ DONE ] Setting Database Security... [ DONE ] Upgrading Database Schema... [ DONE ] Editing oVirt Engine Configuration... [ DONE ] Editing Postgresql Configuration... [ DONE ] Configuring the Default ISO Domain... [ DONE ] Configuring Firewall... [ DONE ] Starting ovirt-engine Service... [ DONE ] Configuring HTTPD... [ DONE ] AIO: Creating storage directory... [ DONE ] AIO: Adding Local Datacenter and cluster... [ ERROR ] Error: could not create ovirtsdk API object Please check log file /var/log/ovirt-engine/engine-setup_2013_04_28_15_18_21.log for more information =LOG========================================== FragmentPath=/usr/lib/systemd/system/firewalld.service UnitFileState=enabled InactiveExitTimestamp=Sun 2013-04-28 15:16:26 CST InactiveExitTimestampMonotonic=2057927058 ActiveEnterTimestamp=Sun 2013-04-28 15:16:26 CST ActiveEnterTimestampMonotonic=2058029155 ActiveExitTimestamp=Sun 2013-04-28 15:16:26 CST ActiveExitTimestampMonotonic=2057262228 InactiveEnterTimestamp=Sun 2013-04-28 15:16:26 CST InactiveEnterTimestampMonotonic=2057889979 "/var/log/ovirt-engine/engine-setup_2013_04_28_15_18_21.log" 2023L, 122617C 2013-04-28 15:19:34::DEBUG::engine-setup::2069::root:: db-remote-install: local 2013-04-28 15:19:34::DEBUG::engine-setup::2069::root:: db-host: localhost 2013-04-28 15:19:34::DEBUG::engine-setup::2069::root:: db-local-pass: ******** 2013-04-28 15:19:34::DEBUG::engine-setup::2069::root:: nfs-mp: /var/lib/exports/iso_2013_04_28_15_18_22 2013-04-28 15:19:34::DEBUG::engine-setup::2069::root:: iso-domain-name: ISO_DOMAIN 2013-04-28 15:19:34::DEBUG::engine-setup::2069::root:: config-nfs: yes 2013-04-28 15:19:34::DEBUG::engine-setup::2069::root:: firewall-manager: Firewalld 2013-04-28 15:19:34::DEBUG::engine-setup::2069::root:: config-allinone: yes 2013-04-28 15:19:34::DEBUG::engine-setup::2069::root:: storage-path: /var/lib/images_2013_04_28_15_18_22 2013-04-28 15:19:34::DEBUG::engine-setup::2069::root:: superuser-pass: ******** 2013-04-28 15:19:34::ERROR::engine-setup::2504::root:: Traceback (most recent call last): File "/usr/bin/engine-setup", line 2498, in <module> main(confFile) File "/usr/bin/engine-setup", line 2265, in main runSequences() File "/usr/bin/engine-setup", line 2184, in runSequences controller.runAllSequences() File "/usr/share/ovirt-engine/scripts/setup_controller.py", line 54, in runAllSequences sequence.run() File "/usr/share/ovirt-engine/scripts/setup_sequences.py", line 154, in run step.run() File "/usr/share/ovirt-engine/scripts/setup_sequences.py", line 60, in run function() File "/usr/share/ovirt-engine/scripts/plugins/all_in_one_100.py", line 252, in initAPI raise Exception(ERROR_CREATE_API_OBJECT) Exception: Error: could not create ovirtsdk API object ============================================ [root@localhost ~]# rpm -qa | grep ovirt ovirt-engine-sdk-3.3.0.1-1.20130427.gitfc5985e.fc18.noarch ovirt-engine-backend-3.3.0-0.2.master.20130427145036.fc18.noarch ovirt-engine-setup-plugin-allinone-3.3.0-0.2.master.20130427145036.fc18.noarch ovirt-host-deploy-1.0.1-1.fc18.noarch ovirt-engine-setup-3.3.0-0.2.master.20130427145036.fc18.noarch ovirt-engine-cli-3.2.0.11-1.fc18.noarch ovirt-iso-uploader-3.3.0-0.0.master.20130318.gitec3e5e7.fc18.noarch ovirt-engine-restapi-3.3.0-0.2.master.20130427145036.fc18.noarch ovirt-engine-webadmin-portal-3.3.0-0.2.master.20130427145036.fc18.noarch ovirt-host-deploy-offline-1.0.1-1.fc18.noarch ovirt-image-uploader-3.3.0-0.0.master.20130423.git8dde3cc.fc18.noarch ovirt-engine-dbscripts-3.3.0-0.2.master.20130427145036.fc18.noarch ovirt-engine-userportal-3.3.0-0.2.master.20130427145036.fc18.noarch ovirt-release-fedora-5-3.1.noarch ovirt-host-deploy-java-1.0.1-1.fc18.noarch ovirt-engine-tools-3.3.0-0.2.master.20130427145036.fc18.noarch ovirt-log-collector-3.3.0-0.0.master.20130421.git1c4542d.fc18.noarch ovirt-engine-3.3.0-0.2.master.20130427145036.fc18.noarch [root@localhost ~]# rpm -qa | grep vdsm vdsm-python-4.10.3-10.fc18.x86_64 vdsm-xmlrpc-4.10.3-10.fc18.noarch vdsm-4.10.3-10.fc18.x86_64 vdsm-cli-4.10.3-10.fc18.noarch vdsm-bootstrap-4.10.3-10.fc18.noarch [root@localhost ~]# cat /etc/hosts 10.0.10.181 engine.startn.com [root@localhost ~]# ifconfig eth0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500 inet 192.168.11.4 netmask 255.255.255.0 broadcast 192.168.11.255 inet6 fe80::20c:29ff:feed:4f64 prefixlen 64 scopeid 0x20<link> ether 00:0c:29:ed:4f:64 txqueuelen 1000 (Ethernet) RX packets 22780 bytes 31526531 (30.0 MiB) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 7612 bytes 547095 (534.2 KiB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 eth1: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500 inet 10.0.10.181 netmask 255.255.255.0 broadcast 10.0.10.255 inet6 fe80::20c:29ff:feed:4f6e prefixlen 64 scopeid 0x20<link> ether 00:0c:29:ed:4f:6e txqueuelen 1000 (Ethernet) RX packets 45792 bytes 58908887 (56.1 MiB) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 11143 bytes 2063171 (1.9 MiB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 lo: flags=73<UP,LOOPBACK,RUNNING> mtu 65536 inet 127.0.0.1 netmask 255.0.0.0 inet6 ::1 prefixlen 128 scopeid 0x10<host> loop txqueuelen 0 (Local Loopback) RX packets 180949 bytes 62786059 (59.8 MiB) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 180949 bytes 62786059 (59.8 MiB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 virbr0: flags=4099<UP,BROADCAST,MULTICAST> mtu 1500 inet 192.168.122.1 netmask 255.255.255.0 broadcast 192.168.122.255 ether 16:aa:69:7c:1e:3e txqueuelen 0 (Ethernet) RX packets 0 bytes 0 (0.0 B) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 0 bytes 0 (0.0 B) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 [root@localhost ~]# dig -x 10.0.10.181 ; <<>> DiG 9.9.2-rl.028.23-P2-RedHat-9.9.2-10.P2.fc18 <<>> -x 10.0.10.181 ;; global options: +cmd ;; Got answer: ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 21966 ;; flags: qr aa rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 1, ADDITIONAL: 2 ;; OPT PSEUDOSECTION: ; EDNS: version: 0, flags:; udp: 4096 ;; QUESTION SECTION: ;181.10.0.10.in-addr.arpa. IN PTR ;; ANSWER SECTION: 181.10.0.10.in-addr.arpa. 1200 IN PTR engine.startn.com. ;; AUTHORITY SECTION: 10.0.10.in-addr.arpa. 1200 IN NS engine.startn.com. ;; ADDITIONAL SECTION: engine.startn.com. 86400 IN A 10.0.10.181 ;; Query time: 0 msec ;; SERVER: 10.0.10.181#53(10.0.10.181) ;; WHEN: Sun Apr 28 15:36:34 2013 ;; MSG SIZE rcvd: 114 [root@localhost ~]# dig engine.startn.com ; <<>> DiG 9.9.2-rl.028.23-P2-RedHat-9.9.2-10.P2.fc18 <<>> engine.startn.com ;; global options: +cmd ;; Got answer: ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 36210 ;; flags: qr aa rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 1, ADDITIONAL: 1 ;; OPT PSEUDOSECTION: ; EDNS: version: 0, flags:; udp: 4096 ;; QUESTION SECTION: ;engine.startn.com. IN A ;; ANSWER SECTION: engine.startn.com. 86400 IN A 10.0.10.181 ;; AUTHORITY SECTION: startn.com. 86400 IN NS engine.startn.com. ;; Query time: 0 msec ;; SERVER: 10.0.10.181#53(10.0.10.181) ;; WHEN: Sun Apr 28 15:36:40 2013 ;; MSG SIZE rcvd: 76 ============================================= --- 有问题请通知我，谢谢，李强 ------------------------------------------------------------------------------ + 太初有道，道与神同在，道就是神。(约翰福音1:1) + ------------------------------------------------------------------------------

3 4

[Engine-devel] FeatureSupported and compatibility versions
by Shireesh Anjal 02 May '13

02 May '13

Hi all, The current mechanism in oVirt to check whether a feature is supported in a particular compatibility version is to use the FeatureSupported class. e.g. FeatureSupported.networkLinking(getVm().getVdsGroupCompatibilityVersion()) Checks whether the "network linking" feature is supported for the the VM's cluster compatibility version. This internally checks whether the value of the corresponding config (NetworkLinkingSupported) for the given compatibility version is true/false. I'm not sure if this is a good idea, since a feature is typically supported "from" a particular version. E.g. Gluster support was introduced in 3.1, and it continues to be available in all subsequent versions. So I see no point in adding configuration for every version indicating whether the feature is supported in that version or not. I suggest to use either of the following options: 1) Instead of using a boolean config for each version, use a single string config that indicates the "supported from" version e.g. GlusterSupportedFrom = 3.1. There could be rare cases where a feature, for some reason, is removed in some release. In such cases, we could use one additional config for the "supported to" version. 2) Continue with the boolean approach, but do not have entries for every version; rather make use of the "default value" for majority of cases, and add the explicit version mapping for the minority e.g. GlusterSupported = true by default, and false in case of 3.0 (only one config required for 3.0) Thoughts? Regards, Shireesh

7 16

Re: [Engine-devel] Root password to add Host
by Alon Bar-Lev 01 May '13

01 May '13

Please reply to 'all'. When you login as admin you should be presented with Text User Interface. Within this interface there should be options on the left and a dialog on the right. At the left you should see 'ovirt-engine' or similar option, when selecting it, you should see on the right an input field of address of the ovirt-engine server, specifying the engine address and selecting apply will initiate registration into the engine. Once registered, you should see the host in the engine, select it and click on "Approve". Another option is to specify password at the same dialog without filling the engine address. This password may be used as the password withi the 'Add Host' dialog. Alon ----- Original Message ----- > From: "Florian BRUSCHET" <florian.bruschet(a)gmail.com> > To: "Alon Bar-Lev" <alonbl(a)redhat.com> > Sent: Wednesday, May 1, 2013 12:00:01 AM > Subject: Re: [Engine-devel] Root password to add Host > > I think I don't really understand what you call TUI? > Yes I'm log as admin on ovirt-node to use Hypervisor > > (And sorry if I make some language faults English isn't my native language > ^^) > > > 2013/4/30 Alon Bar-Lev <alonbl(a)redhat.com> > > > > > You cannot do this via agent by via the TUI of the ovirt-node. > > > > Just to make sure, you are using ovirt-node as hypervisor, right? > > > > ----- Original Message ----- > > > From: "Florian BRUSCHET" <florian.bruschet(a)gmail.com> > > > To: "Alon Bar-Lev" <alonbl(a)redhat.com> > > > Sent: Tuesday, April 30, 2013 11:47:53 PM > > > Subject: Re: [Engine-devel] Root password to add Host > > > > > > Oh ok, i didn't know ... > > > > > > I was looking my oVirt Engine and i don't understand how i can add an > > Host > > > without this password ... > > > For me i have to right click on the Hosts panel, select "new" and it asks > > > me to give name, address and Root password. > > > I have already register this Host from oVirt Node Hypervisor, i add my > > > Management Server and there is no problem i can see "Certificate Status : > > > Verified" but this Host don't appears in the Web page ... > > > > > > > > > 2013/4/30 Alon Bar-Lev <alonbl(a)redhat.com> > > > > > > > > > > > > > > > ----- Original Message ----- > > > > > From: "Florian BRUSCHET" <florian.bruschet(a)gmail.com> > > > > > To: "Alon Bar-Lev" <alonbl(a)redhat.com> > > > > > Sent: Tuesday, April 30, 2013 11:06:14 PM > > > > > Subject: Re: [Engine-devel] Root password to add Host > > > > > > > > > > For me single mode it's when you add "single" at the end of the > > kernel > > > > > commande line like that you boot on shell commande as > > > > > root@localhostand > > > > > you can do what you want. > > > > > > > > Oh... this is "single user mode"... :) > > > > > > > > > > > > > > I will try it soon! > > > > > > > > > > Thank you > > > > > > > > > > Florian > > > > > > > > > > > > > > > 2013/4/30 Alon Bar-Lev <alonbl(a)redhat.com> > > > > > > > > > > > What is 'single mode'? > > > > > > > > > > > > You should be able to set root password via node TUI, at ovirt tab. > > > > > > Or... you can simply perform registration via the node TUI, so you > > > > don't > > > > > > need to specify password at all. > > > > > > > > > > > > ----- Original Message ----- > > > > > > > From: "Florian BRUSCHET" <florian.bruschet(a)gmail.com> > > > > > > > To: engine-devel(a)ovirt.org > > > > > > > Sent: Tuesday, April 30, 2013 7:28:12 PM > > > > > > > Subject: [Engine-devel] Root password to add Host > > > > > > > > > > > > > > Hi, > > > > > > > > > > > > > > I try to add Host from oVirt Engine Web Administration, but it > > asks > > > > me to > > > > > > > give a Root Password (It's not the same that i used to log in > > admin > > > > on > > > > > > the > > > > > > > Node). > > > > > > > Do i really need this Root Password? Because i can't have it and > > i > > > > don't > > > > > > want > > > > > > > to change it by using single mode... > > > > > > > There is an other solution to add Hosts? > > > > > > > > > > > > > > Thank you, > > > > > > > > > > > > > > Florian BRUSCHET > > > > > > > > > > > > > > > > > > > > > > > > > > > > _______________________________________________ > > > > > > > Engine-devel mailing list > > > > > > > Engine-devel(a)ovirt.org > > > > > > > http://lists.ovirt.org/mailman/listinfo/engine-devel > > > > > > > > > > > > > > > > > > > > > > > > > > > >

2 9

Re: [Engine-devel] Root password to add Host
by Alon Bar-Lev 30 Apr '13

30 Apr '13

You cannot do this via agent by via the TUI of the ovirt-node. Just to make sure, you are using ovirt-node as hypervisor, right? ----- Original Message ----- > From: "Florian BRUSCHET" <florian.bruschet(a)gmail.com> > To: "Alon Bar-Lev" <alonbl(a)redhat.com> > Sent: Tuesday, April 30, 2013 11:47:53 PM > Subject: Re: [Engine-devel] Root password to add Host > > Oh ok, i didn't know ... > > I was looking my oVirt Engine and i don't understand how i can add an Host > without this password ... > For me i have to right click on the Hosts panel, select "new" and it asks > me to give name, address and Root password. > I have already register this Host from oVirt Node Hypervisor, i add my > Management Server and there is no problem i can see "Certificate Status : > Verified" but this Host don't appears in the Web page ... > > > 2013/4/30 Alon Bar-Lev <alonbl(a)redhat.com> > > > > > > > ----- Original Message ----- > > > From: "Florian BRUSCHET" <florian.bruschet(a)gmail.com> > > > To: "Alon Bar-Lev" <alonbl(a)redhat.com> > > > Sent: Tuesday, April 30, 2013 11:06:14 PM > > > Subject: Re: [Engine-devel] Root password to add Host > > > > > > For me single mode it's when you add "single" at the end of the kernel > > > commande line like that you boot on shell commande as root@localhost and > > > you can do what you want. > > > > Oh... this is "single user mode"... :) > > > > > > > > I will try it soon! > > > > > > Thank you > > > > > > Florian > > > > > > > > > 2013/4/30 Alon Bar-Lev <alonbl(a)redhat.com> > > > > > > > What is 'single mode'? > > > > > > > > You should be able to set root password via node TUI, at ovirt tab. > > > > Or... you can simply perform registration via the node TUI, so you > > don't > > > > need to specify password at all. > > > > > > > > ----- Original Message ----- > > > > > From: "Florian BRUSCHET" <florian.bruschet(a)gmail.com> > > > > > To: engine-devel(a)ovirt.org > > > > > Sent: Tuesday, April 30, 2013 7:28:12 PM > > > > > Subject: [Engine-devel] Root password to add Host > > > > > > > > > > Hi, > > > > > > > > > > I try to add Host from oVirt Engine Web Administration, but it asks > > me to > > > > > give a Root Password (It's not the same that i used to log in admin > > on > > > > the > > > > > Node). > > > > > Do i really need this Root Password? Because i can't have it and i > > don't > > > > want > > > > > to change it by using single mode... > > > > > There is an other solution to add Hosts? > > > > > > > > > > Thank you, > > > > > > > > > > Florian BRUSCHET > > > > > > > > > > > > > > > > > > > > _______________________________________________ > > > > > Engine-devel mailing list > > > > > Engine-devel(a)ovirt.org > > > > > http://lists.ovirt.org/mailman/listinfo/engine-devel > > > > > > > > > > > > > > >

1 0

[Engine-devel] Root password to add Host
by Florian BRUSCHET 30 Apr '13

30 Apr '13

Hi, I try to add Host from oVirt Engine Web Administration, but it asks me to give a Root Password (It's not the same that i used to log in admin on the Node). Do i really need this Root Password? Because i can't have it and i don't want to change it by using single mode... There is an other solution to add Hosts? Thank you, Florian BRUSCHET

2 1

[Engine-devel] Fwd: the procedure of storage-related
by Vered Volansky 29 Apr '13

29 Apr '13

----- Forwarded Message ----- > From: "Vered Volansky" <vered(a)redhat.com> > To: "bigclouds" <bigclouds(a)163.com> > Sent: Sunday, April 28, 2013 12:39:31 PM > Subject: Re: [Engine-devel] the procedure of storage-related > > Hi, > > Find my answers below. > > Best Regards, > Vered > > ----- Original Message ----- > > From: "bigclouds" <bigclouds(a)163.com> > > To: "engine-devel" <engine-devel(a)ovirt.org> > > Sent: Saturday, April 27, 2013 8:40:56 AM > > Subject: [Engine-devel] the procedure of storage-related > > > > hi,all > > 1.i am now not very familar with the right procedure of storage, > > please give me a simply introduction of their concept and relation. > > help > > me out > > > > StoragePool,StorageDomain > > image,volume > > You should find the following link helpful: > http://www.ovirt.org/Vdsm_Storage_Terminology > > As per your other questions, you might find the following guide helpul: > http://www.ovirt.org/Quick_Start_Guide#Configure_Storage > > Of not, please rephrase them as they're not clear enough and I'd rather not > guess. > > > > > > > > 2.please help me confirm. > > i find only one place call mount command, which is > > poolConnectStorageServer. > > if poolConnectStorageServer is before create and active > > StoragePool,StorageDomain? > > > > 3.if attach is just modify metadata, not anything else? > > > > 4.sp.py, deactivateSD > > if i deactivate ISO storage,it finally umount masterDir, why ? > > if masterDir is not mastersd? > > thanks > > > > > > > > _______________________________________________ > > Engine-devel mailing list > > Engine-devel(a)ovirt.org > > http://lists.ovirt.org/mailman/listinfo/engine-devel > > >

3 3