I will test it anyway as soon as i have a time for that.

Garami Gábor
[email protected]
Skype: hron84
Tel: +36 20 235 9621

Sent from my T-Mobile G2
Ezt a levelet telefonról adták fel, ékezethibákat tartalmazhat.
2012.09.09. 1:33, "Jason Swager" <[email protected]> ezt írta:

> According to VMware, there only remote API on the free ESXi is read-only - you
> cannot "write", such as make changes. The vSphere client does use the
> write aspect of the remote API, but HOW is not published.  All of the various
> APIs, both by VMware and by third parties have a clause indicating
> they will work read-only with free ESXi.  That makes me rather curious as to
> how libvirt can manage the free ESXi - or are they just using the
> read-only aspect.
>
> On Saturday, September 8, 2012 4:14:45 AM UTC-7, Gábor Garami wrote:
>>
>> Then that's why it is not works. And there is no waz to change? I think
>> vSphere client is stops/starts instances somehow....
>>
>> I'll take a closer look, because iirc libvirt can manage free esxi hosts.
>>
>> Garami Gábor
>> [email protected]
>> Skype: hron84
>> Tel: +36 20 235 9621
>>
>> Sent from my T-Mobile G2
>> Ezt a levelet telefonról adták fel, ékezethibákat tartalmazhat.
>> 2012.09.07. 17:08, "Jason Swager" <[email protected]> ezt írta:
>>
>>> I believe that HTTPS is the ONLY allowed way of connecting.
>>>
>>> The plugin will work with a vCenter installation or with single ESXi
>>> hosts.  BUT - the ESXi host must be fully licensed, otherwise the remote
>>> APIs won't work, which is how the plugin works with the VMs.  If you get
>>> the free ESXi host with it's free license, the remote APIs are disabled and
>>> the plugin won't work.  I'll update the wiki page for this...
>>>
>>> On Friday, September 7, 2012 7:39:30 AM UTC-7, Gábor Garami wrote:
>>>>
>>>> (shake) Nothing.
>>>>
>>>> Strange question, but can it cause a problem I use https in vSphere
>>>> URL? And, this is not really a vSphere cloud but a single ESXi
>>>> server...
>>>>
>>>> Garami Gábor
>>>> E-mail: [email protected]
>>>> Tel: +36 20 235 9621
>>>> MSN: [email protected]
>>>> Skype: hron84
>>>>
>>>>
>>>> On Fri, Sep 7, 2012 at 3:31 PM, Jason Swager <[email protected]>
>>>> wrote:
>>>> > Your configurations all look good.  When Jenkins tries to start the
>>>> slave,
>>>> > do you see any commands at all appearing in vSphere?  At the very
>>>> least, I
>>>> > would hope to see a power on event.
>>>> >
>>>> >
>>>> > On Friday, September 7, 2012 3:06:50 AM UTC-7, Gábor Garami wrote:
>>>> >>
>>>> >> Jenkins node config: https://skitch.com/hron84/**e1rj**
>>>> 4/jenkins-vsphere-node<https://skitch.com/hron84/e1rj4/jenkins-vsphere-node>
>>>> >>
>>>> >> Plugin config: 
>>>> >> https://skitch.com/hron84/**e1rj**9/jenkins-vsphere<https://skitch.com/hron84/e1rj9/jenkins-vsphere>
>>>> >>
>>>> >>
>>>> >> Garami Gábor
>>>> >> E-mail: [email protected]
>>>> >> Tel: +36 20 235 9621
>>>> >> MSN: [email protected]
>>>> >> Skype: hron84
>>>> >>
>>>> >>
>>>> >> On Wed, Sep 5, 2012 at 5:49 PM, Gábor Garami <[email protected]>
>>>> wrote:
>>>> >> > Yes, that is the plugin what i use.
>>>> >> >
>>>> >> > No, test vm connection button does not says any problems.
>>>> >> >
>>>> >> > I cannot access my jenkins now, but i'll post screenshot about
>>>> settings
>>>> >> > asap.
>>>> >> >
>>>> >> > Garami Gábor
>>>> >> > [email protected]
>>>> >> > Skype: hron84
>>>> >> >
>>>> >> >
>>>> >> > Tel: +36 20 235 9621
>>>> >> >
>>>> >> > Sent from my T-Mobile G2
>>>> >> > Ezt a levelet telefonról adták fel, ékezethibákat tartalmazhat.
>>>> >> >
>>>> >> > 2012.09.05. 15:53, "Jason Swager" <[email protected]> ezt írta:
>>>> >> >
>>>> >> >> Just to confirm, we are talking about the vSphere Cloud plugin?
>>>> >> >> https://wiki.jenkins-ci.org/**di**splay/JENKINS/vSphere+Cloud+**
>>>> Pl**ugin<https://wiki.jenkins-ci.org/display/JENKINS/vSphere+Cloud+Plugin>
>>>> >> >>
>>>> >> >> Assuming that you are, the Test VM Connection button does work
>>>> and
>>>> >> >> indicates no problems?
>>>> >> >> What are the slave settings?
>>>> >> >>
>>>> >> >> On Wednesday, September 5, 2012 1:51:48 AM UTC-7, Gábor Garami
>>>> wrote:
>>>> >> >>>
>>>> >> >>> I set slave activation via SSH. But the main problem is VM does
>>>> not
>>>> >> >>> powered on. So, my problem is not the VM not boots up and
>>>> connects to
>>>> >> >>> master, but nobody pushes the power button on it... (and yes,
>>>> because
>>>> >> >>> it not powered on, it does not connects to the master :-) )
>>>> >> >>>
>>>> >> >>> If i turn on VM manually, Jenkins recognizes it and starts slave
>>>> >> >>> process correctly, however, this is not I really want (turn on
>>>> VM
>>>> >> >>> every case when I need it). I would like if Jenkins can turn
>>>> on/off VM
>>>> >> >>> on demand.
>>>> >> >>>
>>>> >> >>> Garami Gábor
>>>> >> >>> E-mail: [email protected]
>>>> >> >>> Tel: +36 20 235 9621
>>>> >> >>> MSN: [email protected]
>>>> >> >>> Skype: hron84
>>>> >> >>>
>>>> >> >>>
>>>> >> >>> On Wed, Sep 5, 2012 at 4:32 AM, Jason Swager <[email protected]>
>>>>
>>>> >> >>> wrote:
>>>> >> >>> > How is the slave agent being started?  Does the VM connect via
>>>> Java
>>>> >> >>> > Web
>>>> >> >>> > Start?  Is Jenkins supposed to start the slave agent via SSH?
>>>> >> >>> >
>>>> >> >>> > If via Java Web Start, make sure the the slave agent really
>>>> did
>>>> >> >>> > start.
>>>> >> >>> >
>>>> >> >>> > If via SSH, make sure that the VM has enough time to fully
>>>> start
>>>> >> >>> > (wait
>>>> >> >>> > for
>>>> >> >>> > VM Tools plus any necessary delay) so that the SSH server is
>>>> online
>>>> >> >>> > before
>>>> >> >>> > Jenkins tries to communicate.
>>>> >> >>> >
>>>> >> >>> >
>>>> >> >>> > On Sunday, September 2, 2012 4:44:23 AM UTC-7, Gábor Garami
>>>> wrote:
>>>> >> >>> >>
>>>> >> >>> >> Hi!
>>>> >> >>> >>
>>>> >> >>> >> I use VMware ESXi 4.0 with the vSphere plugin, and slave VM
>>>> does
>>>> >> >>> >> not
>>>> >> >>> >> being started. It is always stuck on Powering on VM state (at
>>>> least
>>>> >> >>> >> based on logs).
>>>> >> >>> >>
>>>> >> >>> >> The Test VM Connection passes.
>>>> >> >>> >>
>>>> >> >>> >> openSUSE Linux 11.4
>>>> >> >>> >> Jenkins ver. 1.479 (installed from pkg.jenkins-ci.org/opesuse
>>>> >> >>> >> started
>>>> >> >>> >> by the init script of the package).
>>>> >> >>> >> Java(TM) SE Runtime Environment (build 1.6.0_31-b05)
>>>> >> >>> >> vSphere plugins is the latest installable.
>>>> >> >>> >>
>>>> >> >>> >> Please help me...
>>>> >> >>> >>
>>>> >> >>> >> Garami Gábor
>>>> >> >>> >> E-mail: [email protected]
>>>> >> >>> >> Tel: +36 20 235 9621
>>>> >> >>> >> MSN: [email protected]
>>>> >> >>> >> Skype: hron84
>>>>
>>>

Reply via email to