Thanks @igreenfield and agreed that we should have especially been careful
around the vijava thing as this was attempted and rejected in the past. You'll
notice we've also just dropped virtualbox for similar reasons. I'll point
anyone who asks about jclouds vsphere to you, and thanks for giving
Closed #61.
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds-labs/pull/61#event-186348878
[jclouds-labs-pull-requests
#358](https://jclouds.ci.cloudbees.com/job/jclouds-labs-pull-requests/358/)
FAILURE
Looks like there's a problem with this pull request
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds-labs/pull/61#issuecomment-60713845
[jclouds » jclouds-labs
#1809](https://buildhive.cloudbees.com/job/jclouds/job/jclouds-labs/1809/)
SUCCESS
This pull request looks good
[(what's this?)](https://www.cloudbees.com/what-is-buildhive)
---
Reply to this email directly or view it on GitHub:
[jclouds-labs-pull-requests
#355](https://jclouds.ci.cloudbees.com/job/jclouds-labs-pull-requests/355/)
FAILURE
Looks like there's a problem with this pull request
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds-labs/pull/61#issuecomment-60616382
[jclouds » jclouds-labs
#1804](https://buildhive.cloudbees.com/job/jclouds/job/jclouds-labs/1804/)
ABORTED
[(what's this?)](https://www.cloudbees.com/what-is-buildhive)
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds-labs/pull/61#issuecomment-60637019
Hi @igreenfield @if6was9 ,
I understand that the merge can be urgent, but many of the comments have still
not being addressed (for example, the interfaces coupled to vijava).
There have been recently several discussions about the providers in labs.
You'll have seen that we've removed many of
My apologies for that.
The recover the labs essence discussion was started after this PR was
initially reviewed, and although the initial expectations have changed I hope
people will understand that the change is for the benefit of jclouds.
I really appreciate all the effort here and hope te
[jclouds-labs-pull-requests
#332](https://jclouds.ci.cloudbees.com/job/jclouds-labs-pull-requests/332/)
FAILURE
Looks like there's a problem with this pull request
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds-labs/pull/61#issuecomment-60122763
[jclouds » jclouds-labs
#1742](https://buildhive.cloudbees.com/job/jclouds/job/jclouds-labs/1742/)
SUCCESS
This pull request looks good
[(what's this?)](https://www.cloudbees.com/what-is-buildhive)
---
Reply to this email directly or view it on GitHub:
[jclouds-labs-pull-requests
#328](https://jclouds.ci.cloudbees.com/job/jclouds-labs-pull-requests/328/)
FAILURE
Looks like there's a problem with this pull request
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds-labs/pull/61#issuecomment-59885649
[jclouds » jclouds-labs
#1727](https://buildhive.cloudbees.com/job/jclouds/job/jclouds-labs/1727/)
SUCCESS
This pull request looks good
[(what's this?)](https://www.cloudbees.com/what-is-buildhive)
---
Reply to this email directly or view it on GitHub:
https://code.google.com/p/powermock/issues/detail?id=504
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds-labs/pull/61#issuecomment-59886644
Hi @nacx ,
The merge turn to be very URGENT for me,
My dependent project need to be built and I need the snapshot version of this
JAR.
thanks
Izek
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds-labs/pull/61#issuecomment-59907126
Getting a working working, supported vSphere support is very compelling for
doing integration and automation in environments that have no IaaS
support...which is most vCenter deployments.
The vSphere API is extremely complicated and unpleasant to use.
---
Reply to this email directly or view
[jclouds-labs-pull-requests
#290](https://jclouds.ci.cloudbees.com/job/jclouds-labs-pull-requests/290/)
FAILURE
Looks like there's a problem with this pull request
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds-labs/pull/61#issuecomment-57938488
[jclouds » jclouds-labs
#1609](https://buildhive.cloudbees.com/job/jclouds/job/jclouds-labs/1609/)
SUCCESS
This pull request looks good
[(what's this?)](https://www.cloudbees.com/what-is-buildhive)
---
Reply to this email directly or view it on GitHub:
[jclouds » jclouds-labs
#1571](https://buildhive.cloudbees.com/job/jclouds/job/jclouds-labs/1571/)
FAILURE
Looks like there's a problem with this pull request
[(what's this?)](https://www.cloudbees.com/what-is-buildhive)
---
Reply to this email directly or view it on GitHub:
[jclouds-labs-pull-requests
#271](https://jclouds.ci.cloudbees.com/job/jclouds-labs-pull-requests/271/)
FAILURE
Looks like there's a problem with this pull request
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds-labs/pull/61#issuecomment-57434915
[jclouds » jclouds-labs
#1572](https://buildhive.cloudbees.com/job/jclouds/job/jclouds-labs/1572/)
FAILURE
Looks like there's a problem with this pull request
[(what's this?)](https://www.cloudbees.com/what-is-buildhive)
---
Reply to this email directly or view it on GitHub:
[jclouds-labs-pull-requests
#272](https://jclouds.ci.cloudbees.com/job/jclouds-labs-pull-requests/272/)
FAILURE
Looks like there's a problem with this pull request
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds-labs/pull/61#issuecomment-57437490
[jclouds » jclouds-labs
#1573](https://buildhive.cloudbees.com/job/jclouds/job/jclouds-labs/1573/)
SUCCESS
This pull request looks good
[(what's this?)](https://www.cloudbees.com/what-is-buildhive)
---
Reply to this email directly or view it on GitHub:
[jclouds-labs-pull-requests
#273](https://jclouds.ci.cloudbees.com/job/jclouds-labs-pull-requests/273/)
SUCCESS
This pull request looks good
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds-labs/pull/61#issuecomment-57441059
+
+ VirtualMachine cloned = null;
+ try {
+ FolderNameToFolderManagedEntity toFolderManagedEntity = new
FolderNameToFolderManagedEntity(serviceInstance, master);
+ Folder folder = toFolderManagedEntity.apply(folderName);
+ Task task =
[jclouds-labs-pull-requests
#265](https://jclouds.ci.cloudbees.com/job/jclouds-labs-pull-requests/265/)
FAILURE
Looks like there's a problem with this pull request
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds-labs/pull/61#issuecomment-57284475
[jclouds » jclouds-labs
#1564](https://buildhive.cloudbees.com/job/jclouds/job/jclouds-labs/1564/)
FAILURE
Looks like there's a problem with this pull request
[(what's this?)](https://www.cloudbees.com/what-is-buildhive)
---
Reply to this email directly or view it on GitHub:
[jclouds » jclouds-labs
#1565](https://buildhive.cloudbees.com/job/jclouds/job/jclouds-labs/1565/)
FAILURE
Looks like there's a problem with this pull request
[(what's this?)](https://www.cloudbees.com/what-is-buildhive)
---
Reply to this email directly or view it on GitHub:
[jclouds-labs-pull-requests
#266](https://jclouds.ci.cloudbees.com/job/jclouds-labs-pull-requests/266/)
FAILURE
Looks like there's a problem with this pull request
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds-labs/pull/61#issuecomment-57287931
[jclouds » jclouds-labs
#1566](https://buildhive.cloudbees.com/job/jclouds/job/jclouds-labs/1566/)
SUCCESS
This pull request looks good
[(what's this?)](https://www.cloudbees.com/what-is-buildhive)
---
Reply to this email directly or view it on GitHub:
[jclouds-labs-pull-requests
#267](https://jclouds.ci.cloudbees.com/job/jclouds-labs-pull-requests/267/)
SUCCESS
This pull request looks good
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds-labs/pull/61#issuecomment-57293342
[jclouds » jclouds-labs
#1567](https://buildhive.cloudbees.com/job/jclouds/job/jclouds-labs/1567/)
SUCCESS
This pull request looks good
[(what's this?)](https://www.cloudbees.com/what-is-buildhive)
---
Reply to this email directly or view it on GitHub:
[jclouds-labs-pull-requests
#268](https://jclouds.ci.cloudbees.com/job/jclouds-labs-pull-requests/268/)
SUCCESS
This pull request looks good
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds-labs/pull/61#issuecomment-57301670
+
+ VirtualMachine cloned = null;
+ try {
+ FolderNameToFolderManagedEntity toFolderManagedEntity = new
FolderNameToFolderManagedEntity(serviceInstance, master);
+ Folder folder = toFolderManagedEntity.apply(folderName);
+ Task task =
The APIs are for feature when we implement without vijava
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds-labs/pull/61#issuecomment-57076529
+ xsi:schemaLocation=http://maven.apache.org/POM/4.0.0
http://maven.apache.org/maven-v4_0_0.xsd;
+
+modelVersion4.0.0/modelVersion
+parent
+groupIdorg.apache.jclouds.labs/groupId
+artifactIdjclouds-labs/artifactId
+version2.0.0-SNAPSHOT/version
+
+import com.vmware.vim25.mo.ManagedEntity;
+
+import java.rmi.RemoteException;
+import java.util.List;
+
+/**
+ * Date: 26/06/2014 10:26 AM
+ * Package: org.jclouds.vsphere
+ */
+public interface AlarmManagerApi {
+ ListAlarmExpression getDefaultExpression();
+
+ AlarmDescription
+ /**
+* @since 4.0
+*/
+ boolean areAlarmActionsEnabled(ManagedEntity entity) throws RuntimeFault,
RemoteException;
+
+ /**
+* @since 4.0
+*/
+ void enableAlarmActions(ManagedEntity entity, boolean enabled) throws
RuntimeFault, RemoteException;
+
+ Alarm
+dependency
+groupIdorg.apache.jclouds/groupId
+artifactIdjclouds-core/artifactId
+version${project.version}/version
+typetest-jar/type
+scopetest/scope
+/dependency
+dependency
+
+import com.vmware.vim25.AlarmDescription;
+import com.vmware.vim25.AlarmExpression;
+import com.vmware.vim25.AlarmSpec;
+import com.vmware.vim25.AlarmState;
+import com.vmware.vim25.DuplicateName;
+import com.vmware.vim25.InvalidName;
+import com.vmware.vim25.RuntimeFault;
+import
+import com.vmware.vim25.mo.ManagedEntity;
+
+import java.rmi.RemoteException;
+import java.util.List;
+
+/**
+ * Date: 26/06/2014 10:26 AM
+ * Package: org.jclouds.vsphere
+ */
+public interface AlarmManagerApi {
+ ListAlarmExpression getDefaultExpression();
+
+ AlarmDescription
+ /**
+* @since 4.0
+*/
+ boolean areAlarmActionsEnabled(ManagedEntity entity) throws RuntimeFault,
RemoteException;
+
+ /**
+* @since 4.0
+*/
+ void enableAlarmActions(ManagedEntity entity, boolean enabled) throws
RuntimeFault, RemoteException;
+
+ Alarm
+* @throws RemoteException if something is wrong with web service call,
+* either because of the web service itself, or
because of the service
+* provider unable to handle the request.
+*/
+ Extension findExtension(String
+
+long currentDiskSize = 0;
+int numberOfHardDrives = 0;
+
+int diskKey = 0;
+
+for (VirtualDevice device :
master.getConfig().getHardware().getDevice()) {
+ if (device instanceof VirtualDisk) {
+
+
+ }
+}
+updates.addAll(createNicSpec(networkConfigs,
vOptions.postConfiguration(), vOptions.distributedVirtualSwitch()));
+virtualMachineConfigSpec.setDeviceChange(updates.toArray(new
VirtualDeviceConfigSpec[updates.size()]));
+
+//
+
cloned.getServerConnection().getServiceInstance().getCustomFieldsManager().setField(cloned,
customFields.get().get(VSphereConstants.JCLOUDS_TAGS).getKey(),
tags.toString());
+
+//virtualMachineConfigSpec.setBootOptions(bootOptions);
+
+cloneSpec.setConfig(virtualMachineConfigSpec);
+
+vOptions.getPublicKey();
+
+VirtualMachine cloned = null;
+try {
+ cloned = cloneMaster(master, tag,
+
+
+NodeAndInitialCredentialsVirtualMachine
nodeAndInitialCredentials = new
NodeAndInitialCredentialsVirtualMachine(cloned, cloned.getName(),
+LoginCredentials.builder().user(root)
+.password(vmInitPassword)
+
+}
+ });
+ } catch (Throwable e) {
+ logger.error(Can't find vm, e);
+ }
+ return vms;
+ }
+
+ @Override
+ public IterableVirtualMachine listNodes() {
+ Closer closer = Closer.create();
+ VSphereServiceInstance instance =
+ @Override
+ public IterableVirtualMachine listNodes() {
+ Closer closer = Closer.create();
+ VSphereServiceInstance instance = serviceInstance.get();
+ closer.register(instance);
+
+ try {
+ try {
+return listNodes(instance);
+ }
+return listNodes(instance);
+ } catch (Throwable e) {
+logger.error(Can't find vm, e);
+throw closer.rethrow(e);
+ } finally {
+closer.close();
+ }
+ } catch (Throwable t) {
+ return ImmutableSet.of();
+ .build());
+
+ hardware.add(new
HardwareBuilder().ids(InstanceType.C2_M6_D40).hypervisor(vSphere).name(InstanceType.C2_M6_D40)
+ .processor(new Processor(2, 2.0))
+ .ram(6 * 1024)
+ .volume(new
+
+ VirtualMachine cloned = null;
+ try {
+ FolderNameToFolderManagedEntity toFolderManagedEntity = new
FolderNameToFolderManagedEntity(serviceInstance, master);
+ Folder folder = toFolderManagedEntity.apply(folderName);
+ Task task =
+ } catch (Exception e) {
+ logger.error(Can't clone vm: + e.toString(), e);
+ propagate(e);
+ }
+ return checkNotNull(cloned, cloned);
+ }
+
+ private static void sleep(long time) {
+ try {
+ Thread.sleep(time);
+ } catch
+ try {
+ vm = (VirtualMachine) new
InventoryNavigator(nodesFolder).searchManagedEntity(VirtualMachine, vmName);
+ } catch (Exception e) {
+ logger.error(Can't find vm, e);
+ propagate(e);
+ }
+ return vm;
+ }
+
+ private VirtualMachine
+ propagate(e);
+ }
+ return vm;
+ }
+
+ private VirtualMachine getVMwareTemplate(String imageName, Folder
rootFolder) {
+ VirtualMachine image = null;
+ try {
+ VirtualMachine node = getVM(imageName, rootFolder);
+ if
+//
+// private GuestNicInfo[] getGuestNicInfo(VirtualMachine virtualMachine) {
+// GuestNicInfo[] nics = virtualMachine.getGuest().getNet();
+// if (nics == null) {
+// VSpherePredicate.WAIT_FOR_NIC(1000 * 60 * 5,
TimeUnit.MILLISECONDS).apply(virtualMachine);
+//
+ gps.programPath = /bin/sh;
+
+ StringBuilder ethScript = new StringBuilder();
+
+ ethScript.append(\necho \\\#!/bin/bash\\\ /tmp/ping_dns.sh;);
+ ethScript.append(\necho \\\c=1\\\ /tmp/ping_dns.sh;);
+ ethScript.append(\necho \\\while [ \\$c -le 12 ]; do\\\
I've been reviewing the code for a while now, mainly focused on the
ComputeService implementation, and I think there is enough TBD before we
continue with the rest:
* If I am not wrong, all these API classes that are tied to vijava don't have
an implementation. Why are they needed? Can they be
[jclouds » jclouds-labs
#1546](https://buildhive.cloudbees.com/job/jclouds/job/jclouds-labs/1546/)
SUCCESS
This pull request looks good
[(what's this?)](https://www.cloudbees.com/what-is-buildhive)
---
Reply to this email directly or view it on GitHub:
@nacx @aledsage Can we progress with the merge?
By the end of this week / early next one I'll review again the PR so we can
move forward. Apologies for the delay @igreenfield, I've been on vacation and I
haven't had much review time.
---
Reply to this email directly or view it on GitHub:
Thank you.
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds-labs/pull/61#issuecomment-56000547
@if6was9 I comment out the code that try to done the fix of the NIC
configuration. so could we progress?
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds-labs/pull/61#issuecomment-55871691
Sometimes there is problem in the network configuration of the VM.
I try to fix this while reading the configuration.
Maybe my fix does not work on all ENV so I remove it. (on my env it work
perfectly.)
---
Reply to this email directly or view it on GitHub:
@nacx @aledsage Can we progress with the merge?
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds-labs/pull/61#issuecomment-55516861
[jclouds » jclouds-labs
#1504](https://buildhive.cloudbees.com/job/jclouds/job/jclouds-labs/1504/)
SUCCESS
This pull request looks good
[(what's this?)](https://www.cloudbees.com/what-is-buildhive)
---
Reply to this email directly or view it on GitHub:
[jclouds-labs-pull-requests
#245](https://jclouds.ci.cloudbees.com/job/jclouds-labs-pull-requests/245/)
SUCCESS
This pull request looks good
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds-labs/pull/61#issuecomment-54966360
I know from where it comes. I done this by propose.
Do you have in your vCenter machine that does not have IPv4?
From: Rob Schoening [mailto:notificati...@github.com]
Sent: Saturday, September 06, 2014 7:34 PM
To: jclouds/jclouds-labs
Cc: Izek Greenfield (igreenfi)
Subject: Re: [jclouds-labs] Add
[jclouds-labs-pull-requests
#240](https://jclouds.ci.cloudbees.com/job/jclouds-labs-pull-requests/240/)
SUCCESS
This pull request looks good
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds-labs/pull/61#issuecomment-54746750
@igreenfield found a fairly serious bug in this. the act of simply listing
compute instances--which should be a read-only operation--is actually mutating
configuration in vmware. and in some cases, doing it wrong. you may want try
running a test suite with read-only operations against a
[jclouds » jclouds-labs
#1475](https://buildhive.cloudbees.com/job/jclouds/job/jclouds-labs/1475/)
SUCCESS
This pull request looks good
[(what's this?)](https://www.cloudbees.com/what-is-buildhive)
---
Reply to this email directly or view it on GitHub:
[jclouds-labs-pull-requests
#238](https://jclouds.ci.cloudbees.com/job/jclouds-labs-pull-requests/238/)
SUCCESS
This pull request looks good
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds-labs/pull/61#issuecomment-54138105
Brilliant! So you can remove vijava dependency right now from pom.xml!
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds-labs/pull/61#issuecomment-54031325
I don’t understand what we will achieve by removing it and generating the
classes by ourselves
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds-labs/pull/61#issuecomment-54032524
Removing the vijava dependency and using our own generated classes won't
provide any direct benefit. Please, continue the discussion in the mailing list
thread that was opened for this purpose. Otherwise let's proceed as proposed
and merge the PR in labs *with*^the vijava dependency, after the
[jclouds » jclouds-labs
#1473](https://buildhive.cloudbees.com/job/jclouds/job/jclouds-labs/1473/)
SUCCESS
This pull request looks good
[(what's this?)](https://www.cloudbees.com/what-is-buildhive)
---
Reply to this email directly or view it on GitHub:
[jclouds-labs-pull-requests
#237](https://jclouds.ci.cloudbees.com/job/jclouds-labs-pull-requests/237/)
SUCCESS
This pull request looks good
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds-labs/pull/61#issuecomment-54059635
Almost all the code of the vijava is auto generated code from the WSDL of
vSphere SDK.
So I don’t see why there is a problem.
If there is any issue we can just regenerate it from the uptodate WSDL.
---
Reply to this email directly or view it on GitHub:
I know it is only that,
I try to generate it…
From: Andrea Turli [mailto:notificati...@github.com]
Sent: Sunday, August 31, 2014 12:01 PM
To: jclouds/jclouds-labs
Cc: Izek Greenfield (igreenfi)
Subject: Re: [jclouds-labs] Add vSphere support (#61)
I don't think vijava offers only the auto
I don't know if we have a soap based provider, but in the end, it is all about
generating the request with the right body. You can take a look at the vcloud
api in the main jclouds repo, which targets an XML api.
You'll see that it is generating the request bodies kinda manually, but we also
I'll do my best to help you in this process.
If I can help, of course I'll be glad to assist to. Although @nacx is much more
of a domain expert in compute providers than I am ;-)
Thanks for sticking with this @igreenfield!
---
Reply to this email directly or view it on GitHub:
@igreenfield I'm not familiar with the vSphere SOAP API, but in the next days
I'll try to build some base classes that help building SOAP payloads, as long
as an implementation of a single API call using that, with the corresponding
tests.
That hopefully will show how things should be done and
Thanks for keeping the PR up to date @igreenfield, it is highly appreciated!
There are several things that have to be discussed before merging it. Big pull
requests like this one require a considerable amount of time to review, so
please, be patient. I look forward to helping you as long as we
With my comment above I didn't mean *sort it out for yourself*. Unfortunately
we don't have a detailed developer guide, so I think it is best for you to have
a look at how other providers are implemented and use the mailing list and the
IRC channel to work together. I'll be happy to help!
---
Could you point soap provider I can look at? Thanks.
Original message
From: Ignasi Barrera notificati...@github.com
Date:
To: jclouds/jclouds-labs jclouds-l...@noreply.github.com
Cc: Izek Greenfield (igreenfi) igree...@cisco.com
Subject: Re: [jclouds-labs] Add vSphere support
...@cisco.com
Subject: Re: [jclouds-labs] Add vSphere support (#61)
@igreenfieldhttps://github.com/igreenfield Before this can be merged to
master, you will will need to rebase and squash the 53 commits in this PR! cc/
@aledsagehttps://github.com/aledsage @nacxhttps://github.com/nacx
—
Reply to this email
@igreenfield Before this can be merged to `master`, you will will need to
rebase and squash the 53 commits in this PR! cc/ @aledsage @nacx
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds-labs/pull/61#issuecomment-53143122
What you think about merge it now?
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds-labs/pull/61#issuecomment-52895617
[jclouds-labs-pull-requests
#233](https://jclouds.ci.cloudbees.com/job/jclouds-labs-pull-requests/233/)
SUCCESS
This pull request looks good
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds-labs/pull/61#issuecomment-52600932
[jclouds » jclouds-labs
#1411](https://buildhive.cloudbees.com/job/jclouds/job/jclouds-labs/1411/)
SUCCESS
This pull request looks good
[(what's this?)](https://www.cloudbees.com/what-is-buildhive)
---
Reply to this email directly or view it on GitHub:
[jclouds-labs-pull-requests
#230](https://jclouds.ci.cloudbees.com/job/jclouds-labs-pull-requests/230/)
SUCCESS
This pull request looks good
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds-labs/pull/61#issuecomment-51878861
[jclouds-labs-pull-requests
#231](https://jclouds.ci.cloudbees.com/job/jclouds-labs-pull-requests/231/)
SUCCESS
This pull request looks good
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds-labs/pull/61#issuecomment-51914160
@@ -0,0 +1,7 @@
+Apache jclouds labs
+Copyright 2009-2014 The Apache Software Foundation
+
+This product includes software developed at
+The Apache Software Foundation (http://www.apache.org/).
+
+The VMWare vSphere API includes software developed at Cisco Systems, Inc
Thanks for the
legal system and we can remove this line by now.
I will remove it and commit.
From: Andrew Phillips [mailto:notificati...@github.com]
Sent: Tuesday, August 12, 2014 5:28 PM
To: jclouds/jclouds-labs
Cc: Izek Greenfield (igreenfi)
Subject: Re: [jclouds-labs] Add vSphere support (#61)
In NOTICE
[jclouds-labs-pull-requests
#232](https://jclouds.ci.cloudbees.com/job/jclouds-labs-pull-requests/232/)
SUCCESS
This pull request looks good
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds-labs/pull/61#issuecomment-51925141
[jclouds » jclouds-labs
#1400](https://buildhive.cloudbees.com/job/jclouds/job/jclouds-labs/1400/)
FAILURE
Looks like there's a problem with this pull request
[(what's this?)](https://www.cloudbees.com/what-is-buildhive)
---
Reply to this email directly or view it on GitHub:
[jclouds-labs-pull-requests
#225](https://jclouds.ci.cloudbees.com/job/jclouds-labs-pull-requests/225/)
FAILURE
Looks like there's a problem with this pull request
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds-labs/pull/61#issuecomment-51766079
[jclouds » jclouds-labs
#1401](https://buildhive.cloudbees.com/job/jclouds/job/jclouds-labs/1401/)
FAILURE
Looks like there's a problem with this pull request
[(what's this?)](https://www.cloudbees.com/what-is-buildhive)
---
Reply to this email directly or view it on GitHub:
[jclouds-labs-pull-requests
#226](https://jclouds.ci.cloudbees.com/job/jclouds-labs-pull-requests/226/)
FAILURE
Looks like there's a problem with this pull request
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds-labs/pull/61#issuecomment-51767912
[jclouds-labs-pull-requests
#227](https://jclouds.ci.cloudbees.com/job/jclouds-labs-pull-requests/227/)
FAILURE
Looks like there's a problem with this pull request
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds-labs/pull/61#issuecomment-51768231
[jclouds » jclouds-labs
#1402](https://buildhive.cloudbees.com/job/jclouds/job/jclouds-labs/1402/)
FAILURE
Looks like there's a problem with this pull request
[(what's this?)](https://www.cloudbees.com/what-is-buildhive)
---
Reply to this email directly or view it on GitHub:
1 - 100 of 229 matches
Mail list logo
