Assuming that you have updated the core code to recognise and use 'newer' libraries/SDKs than
the ones currently in use (and thoroughly tested it) then, please do create a pull request.
Otherwise, I personally would advise that you leave things 'as-is' to get the most stable
experience.
I don't *think* that you need to run
mvn clean
mvn install -Dnoredist
*After* installing the non-oss components.
You might want to do a mvn clean before you start.
It's been a while since I've done it manually now.
paul.angus@shapeblue.com
www.shapeblue.com
Amadeus House, Floral Street, London WC2E 9DPUK
@shapeblue
-----Original Message-----
From: Florent Paillot <florent.paillot@inria.fr>
Sent: 15 April 2019 13:17
To: users <users@cloudstack.apache.org>
Subject: Re: Problem with ACS 4.11.2 and vCenter server
Yes, this is the list of the files in deps/ :
cloud-iControl.jar cloud-netscaler-sdx.jar iControl-12.1.0.jar install-non-oss.sh manageontap.jar
vim25_51.jar vim25_55.jar vim25_60.jar vim25_65.jar vim25_67.jar
I had to add the following lines to "install-non-oss.sh" to get the build pass :
mvn install:install-file -Dfile=vim25_67.jar -DgroupId=com.cloud.com.vmware -DartifactId=vmware-vim25
-Dversion=6.7 -Dpackaging=jar
mvn install:install-file -Dfile=iControl-12.1.0.jar -DgroupId=com.cloud.com.f5 -DartifactId=icontrol
-Dversion=12.1 -Dpackaging=jar
I can open a PR or an issue if it makes sense.
Florent
--
Florent PAILLOT
SESI - Cellule architecture
INRIA Bordeaux -Sud-Ouest
05.24.57.41.25
----- Mail original -----
> De: "Paul Angus" <paul.angus@shapeblue.com>
> À: "users" <users@cloudstack.apache.org>
> Envoyé: Lundi 15 Avril 2019 14:10:21
> Objet: RE: Problem with ACS 4.11.2 and vCenter server
> When packaging, did you install all of the nonoss libraries into the
> build before packaging? including vmware-vim25-6.5.jar
>
> paul.angus@shapeblue.com
> www.shapeblue.com
> Amadeus House, Floral Street, London WC2E 9DPUK @shapeblue
>
>
>
>
> -----Original Message-----
> From: Dag Sonstebo <Dag.Sonstebo@shapeblue.com>
> Sent: 15 April 2019 12:43
> To: users@cloudstack.apache.org
> Subject: Re: Problem with ACS 4.11.2 and vCenter server
>
> Florent,
>
> Not aware of any issues but I'm no packaging expert so will let others
> respond to this.
>
> However - any reason you're not just using the RPM repositories rather
> than packaging yourself?
>
> Regards,
> Dag Sonstebo
> Cloud Architect
> ShapeBlue
>
>
>On 15/04/2019, 11:46, "Florent Paillot" <florent.paillot@inria.fr> wrote:
>
> Hi everyone,
> We have a problem with our test environment running ACS 4.11.2 on CentOS 7, not
> communicating with a vCenter (upgraded from 4.9.3 to 4.11.2 and CentOS 6 o
> CentOS 7). We have no problems with our KVM host.
> Our production is using 4.9.3 o, Centos 6 and everything is OK.
>
> I used tcpdump and see nothing going out from the management server to the
> vCenter or the ESXi host.
>
> Could it be a package building problem or a vmware module loading?
>
> I used the following commands to build the packages :
> install-non-oss.sh
> mvn clean
> mvn install -Dnoredist
> package.sh -p noredist -d centos7
>
>
> On the production server I see a :
> /usr/share/cloudstack-management/webapps/client/WEB-INF/lib/vmware-vim25-6.0.jar
> file.
> I can't find it on the test environnement, is it linked to jetty ?
>
> Any help is welcome :)
> Regards,
>
>
>
>
>
> Dag.Sonstebo@shapeblue.com
> www.shapeblue.com
> Amadeus House, Floral Street, London WC2E 9DPUK @shapeblue
|