Hi Itamar,

Unfortunately I am restricted to using CLI on the machine running the engine.  
Is there any way to use ovirt CLI to do this?

David



>________________________________
> From: Itamar Heim <[email protected]>
>To: David Li <[email protected]>; "[email protected]" <[email protected]> 
>Sent: Wednesday, December 18, 2013 5:31 PM
>Subject: Re: [Users] What parameters to use in automated node install to 
>enable engine CLI register?
> 
>
>On 12/18/2013 04:33 PM, David Li wrote:
>> I am still confused. My ovirt shell cli is in "disconnected" mode like this:
>>
>> [oVirt shell (disconnected)]#
>> [oVirt shell (disconnected)]#
>> [oVirt shell (disconnected)]#
>>
>>
>> The only commands I can use are connect, exit and help. How do I see my
>> node?  Or maybe the question is if the parameters I provided to the
>> kernel boot options have indeed enabled the node to register with the
>> engine. But again I have no way to know this. Is there a log on the node
>> side that might give me some clues?
>
>well, to begin with, do you see the node in the engine via the webadmin gui?
>
>>
>> David
>>
>>     ------------------------------------------------------------------------
>>     *From:* Itamar Heim <[email protected]>
>>     *To:* David Li <[email protected]>; "[email protected]"
>>     <[email protected]>
>>     *Sent:* Wednesday, December 18, 2013 12:04 PM
>>     *Subject:* Re: [Users] What parameters to use in automated node
>>     install to enable engine CLI register?
>>
>>     On 12/18/2013 10:39 AM, David Li wrote:
>>      > Hi Itamar,
>>      >
>>      > I am not sure I understand the question.
>>      > How can I see the node from over-shell CLI if it's not connected
>>     to it?
>>      >  Are you refering to some CLI cmd that allows me to do this?
>>
>>
>>     if you PXE boot the node to register to the engine, it will register
>>     itself in the engine, so the ovirt-shell can "see it" and approve it.
>>
>>     note you can also just add the ovirt-node directly from the engine (via
>>     the gui/cli/api/sdk without the node registering (you would need to
>>     know
>>     set in the node the root password (for ssh) or the engine ssh key for
>>     this to be able to add the node without registering it first.
>>     if you register it, it will also get the engine ssh key as part of
>>     registration)
>>
>>      >
>>      > David
>>      >
>>      >
>>     ------------------------------------------------------------------------
>>      >    *From:* Itamar Heim <[email protected] <mailto:[email protected]>>
>>      >    *To:* David Li <[email protected]
>>     <mailto:[email protected]>>; "[email protected]
>>     <mailto:[email protected]>"
>>      >    <[email protected] <mailto:[email protected]>>
>>      >    *Sent:* Wednesday, December 18, 2013 1:17 AM
>>      >    *Subject:* Re: [Users] What parameters to use in automated node
>>      >    install to enable engine CLI register?
>>      >
>>      >    On 12/17/2013 05:59 PM, David Li wrote:
>>      >      > Hi,
>>      >      >
>>      >      >
>>      >      > My node install followed the automatic install instructions in
>>      >     >
>>      >      >
>>      >
>>    
>>https://access.redhat.com/site/documentation/en-US/Red_Hat_Enterprise_Virtualization/3.0/html/Hypervisor_Deployment_Guide/sect-Deployment_Guide-Installing_Red_Hat_Enterprise_Virtualization_Hypervisors-RHEV_Hypervisor_Kernel_Parameters_and_Automated_Installation.html
>>      >      >
>>      >      >
>>      >      > For the kernel boot parameters, I used
>>      >      >
>>      >      > management_server=<my machine IP running ovirt-shell CLI>
>>      >      > rhevm_admin_password=xyz
>>      >      >
>>      >
>>      >    do you see the node in pending approval state in the engine?'
>>      >
>>      >
>>      >      > However I see a few problems when I tried to use
>>     ovirt-shell CLI to
>>      >      > connect to the engine.
>>      >      >
>>      >      > [oVirt shell (disconnected)]# connect --url
>>      >    "http://<node-IP>:8080/api"
>>      >      > --username "admin" --password "xyz"
>>      >
>>      >    ovirt-shell is to engine to approve the node, not to node
>>     directly.
>>      >
>>      >      >
>>      >      >
>>      >      > 1. Though I can ping the node, but this cmd gave errors:
>>     error:
>>      >    [Errno
>>      >      > 113] No route to host
>>      >      > 2. What should I use for "--username" argument?  What is
>>     "@domain"?
>>      >      >
>>      >      > David
>>      >      >
>>      >      >
>>      >      >
>>      >      >
>>      >      > _______________________________________________
>>      >      > Users mailing list
>>      >      > [email protected] <mailto:[email protected]>
>>     <mailto:[email protected] <mailto:[email protected]>>
>>      >      > http://lists.ovirt.org/mailman/listinfo/users
>>      >      >
>>      >
>>      >
>>      >
>>
>>
>>
>
>
>
>
_______________________________________________
Users mailing list
[email protected]
http://lists.ovirt.org/mailman/listinfo/users

Reply via email to