Re: How setting development environment without network connection

[Ian Duffy]

Assuming you have all dependencies cached in your m2 folded you can use
with -o flag
On 13 Sep 2014 07:28, "Yitao Jiang"  wrote:

> Hi, stackers
> Is there any way that i can setting development environment without network
> connnection. I mean i had been once set up everything ok in development
> with network. Every time i launch cloudstack using command mvn jetty run it
> will update some dependence pom , it  failed without network connection. Is
> it configurable that do not update m2 repos locally since they are already
> esists
>

Re: How setting development environment without network connection

[Yitao Jiang]

Thanks it work
 On Sep 13, 2014 3:49 PM, "Ian Duffy"  wrote:

> Assuming you have all dependencies cached in your m2 folded you can use
> with -o flag
> On 13 Sep 2014 07:28, "Yitao Jiang"  wrote:
>
> > Hi, stackers
> > Is there any way that i can setting development environment without
> network
> > connnection. I mean i had been once set up everything ok in development
> > with network. Every time i launch cloudstack using command mvn jetty run
> it
> > will update some dependence pom , it  failed without network connection.
> Is
> > it configurable that do not update m2 repos locally since they are
> already
> > esists
> >
>

Re: Access to non-oss builds

[Pradeep Cloudstack]

Thanks




 From: Ian Duffy 
To: Pradeep Cloudstack ; CloudStack Dev 
 
Sent: Friday, September 12, 2014 10:16 PM
Subject: Re: Access to non-oss builds
 

Hi Pradeep,

As far as I know there isn't an issue. The community supplied repos
includes non-oss libraries.

I believe its only an issue if they are hosted on Apache infrastructure.



On 12 Sep 2014 16:29, "Pradeep Cloudstack"
 wrote:

> We have a customer who is interested in trying out non-oss build (for eg:
> support for VMWare, SRX).Internally, we have built and tested the non-oss
> builds.
>
>
> What are the licensing implications in distributing such non-oss builds?
> Does it follow Apache license ?
> Is there any process involved ?
>
>
> -Pradeep
>

Re: [VOTE] Release Apache CloudStack 4.3.1 round #4

[ilya musayev]

Upgraded one of my test environments, no issues found so far +1 binding.
On 9/11/14, 4:07 PM, Mike Tutkowski wrote:

Based on my regression testing, I am +1.

On Thu, Sep 11, 2014 at 1:50 PM, Sebastien Goasguen 
wrote:


On Sep 11, 2014, at 3:47 PM, Mike Tutkowski 
wrote:


OK, I looked into this more.

It turns out the regression test that was failing is only valid in 4.4

and

beyond, so it is not a valid test for 4.3.


so can you vote ? we need your binding vote :)


On Thu, Sep 11, 2014 at 11:14 AM, Mike Tutkowski <
mike.tutkow...@solidfire.com> wrote:


I have an integration test failing when trying to create a (XenServer)
storage repository.

Let me look into it for an hour or so and then I can respond back as to

if

it's a code issue.

I'm thinking now it's a problem with XAPI. At first the code wasn't
compiling due to XAPI changes and now I'm getting this XAPI issue when
trying to create a storage repository. Seems possibly related.

On Thu, Sep 11, 2014 at 10:37 AM, Erik Weber 

wrote:

Except heartbleed fix.

I was merely checking if it's even poosible to do an automated upgrade.

The way i know the upgrade process we add some sql magic to check for

new

systemvm templates. If that's not made for 4.3.1 it won't do much good

to

add it as systemvm-hypervisor-version.

Erik
11. sep. 2014 15:45 skrev "Wei ZHOU"  følgende:


As far as I know, there is no systemvm change during upgrade from

4.3.0

to

4.3.1

2014-09-11 15:22 GMT+02:00 Erik Weber :


On Thu, Sep 11, 2014 at 3:01 PM, Nux!  wrote:


Hello,

I've upgraded and it looks ok for now.
I have used these system VMs


http://jenkins.buildacloud.org/view/4.3/job/cloudstack-4.3-systemvm/

and

added them as systemvm-kvm-4.3 in the Templates.
I expected them to replace SystemVM Template (KVM), but they are

still

listed as systemvm-kvm-4.3 alongside the old ones.
Other than that everything seems ok for now.



Is there an upgrade path from 4.3.0 systemvm template to 4.3.1? Log

on

to a

newly deployed one and check /etc/cloudstack-version

--
Erik




--
*Mike Tutkowski*
*Senior CloudStack Developer, SolidFire Inc.*
e: mike.tutkow...@solidfire.com
o: 303.746.7302
Advancing the way the world uses the cloud
*™*




--
*Mike Tutkowski*
*Senior CloudStack Developer, SolidFire Inc.*
e: mike.tutkow...@solidfire.com
o: 303.746.7302
Advancing the way the world uses the cloud
*™*