Build failed in Jenkins: cloudstack-4.3-maven-build #689

See Changes: [Rohit Yadav] use a preferable protocol that works on jvm 1.6 -- [...truncated 931 lines...] Results : Tests run: 0, Failures: 0, Errors: 0, Skipped: 0 [INFO]

Re: systemvm java 7

4.4 Systemvms and above have openjdk/jre 7. ACS 4.3.2 does not require any systemvm changes for the poodle fix. The latest 4.3 should not give you TLS related errors when used with jre 1.6. > On 28-Jan-2015, at 6:39 am, Marcus wrote: > > Anyone know if there's a systemvm version shipping with j

Re: quality improvement project status (fyi != just for your information)

I did not see any reactions, are we on for tonight? On Sun, Jan 25, 2015 at 12:10 PM, Daan Hoogland wrote: > H, > > This is a question for feedback (fyi == For Your Input;). In the > meetings we had so far, we created a couple of lists. These are our > only deliverables to date. In order to know

Jenkins build is back to normal : cloudstack-4.3-maven-build #690

See

Jenkins build is back to normal : cloudstack-4.4-maven-build #559

See

RE: XenServer 6.5

And where exactly do we stand with this right now? Can I install with ACS 4.5? -Original Message- From: Daan Hoogland [mailto:daan.hoogl...@gmail.com] Sent: Wednesday, January 14, 2015 3:17 AM To: dev Subject: Re: xenserver 6.5 Adrian, I think your questions/considerations are right and

Jenkins build is back to normal : build-master #2196

See

Re: XenServer 6.5

with 4.5 you should be fine On Wed, Jan 28, 2015 at 2:14 PM, Matthew Midgett wrote: > And where exactly do we stand with this right now? Can I install with ACS 4.5? > > -Original Message- > From: Daan Hoogland [mailto:daan.hoogl...@gmail.com] > Sent: Wednesday, January 14, 2015 3:17 AM >

Build failed in Jenkins: cloudstack-4.3-maven-build-noredist #528

See -- [...truncated 2013 lines...] [INFO] --- maven-install-plugin:2.3.1:install (default-install) @ cloud-framework-jobs --- [INFO] Installing

Re: XenServer 6.5

small issue: https://issues.apache.org/jira/browse/CLOUDSTACK-8175 but in general it works fine 2015-01-28 14:16 GMT+01:00 Daan Hoogland : > with 4.5 you should be fine > > On Wed, Jan 28, 2015 at 2:14 PM, Matthew Midgett > wrote: > > And where exactly do we stand with this right now? Can I ins

Jenkins build is back to normal : build-master-simulator #1623

See

Build failed in Jenkins: build-master-noredist #4056

See Changes: [mike.tutkowski] Putting in an extra check to see if this volume is already attached to a VM [jessicawang] CLOUDSTACK-8182: UI > volumes > upload volume from URL > add Custom Disk Offering field which is optio

Jenkins build is still unstable: simulator-singlerun #936

See

Re: XenServer 6.5

this waas fixed Tomasz, Not sure if it made the last release candidate but I suppose it did. On Wed, Jan 28, 2015 at 2:21 PM, Tomasz Zięba wrote: > small issue: > https://issues.apache.org/jira/browse/CLOUDSTACK-8175 > > but in general it works fine > > 2015-01-28 14:16 GMT+01:00 Daan Hoogland :

Re: XenServer 6.5

Yes, this issue is fixed https://issues.apache.org/jira/browse/CLOUDSTACK-8178 Please, close the other as duplicate. > On 28-Jan-2015, at 8:28 pm, Daan Hoogland wrote: > > this waas fixed Tomasz, Not sure if it made the last release > candidate but I suppose it did. > > On Wed, Jan 28, 2015 at 2

Jenkins build is still unstable: simulator-singlerun #937

See

Re: systemvm java 7

Confirmed, thanks. On Jan 28, 2015 5:00 AM, "Rohit Yadav" wrote: > 4.4 Systemvms and above have openjdk/jre 7. ACS 4.3.2 does not require any > systemvm changes for the poodle fix. The latest 4.3 should not give you TLS > related errors when used with jre 1.6. > > > On 28-Jan-2015, at 6:39 am, Ma

Build failed in Jenkins: build-4.5 #309

See Changes: [Rohit Yadav] appliance: upgrade systemvm to latest packages [Rohit Yadav] appliance: fix missing statement -- [...truncated 2726 lines...] [INFO]

Build failed in Jenkins: cloudstack-4.4-maven-build #560

See Changes: [Rohit Yadav] appliance: upgrade systemvm to latest packages [Rohit Yadav] appliance: fix missing statement -- [...truncated 1207 lines...] T E S T S ---

Re: Guest VM hostname to its IP address mapping is not getting set in Virtual Router's /etc/hosts file

Hi Sheng, Thank you very much for the information. After debugging, I also figured out that addDhcpEntry() method in VR takes care of adding the hostname-IP mapping. So, when I used the same implementation in NuageVspElement, hostname-Ip mapping was getting set on VR. And after setting VR as the

Jenkins build is back to normal : cloudstack-4.3-maven-build-noredist #529

See

Build failed in Jenkins: build-4.5 #310

See Changes: [Rohit Yadav] appliance: hold on to openswan version, don't upgrade -- [...truncated 1813 lines...] [INFO] --- maven-surefire-plugin:2.12:test (default-test) @ cloud-server --- [INFO]

Build failed in Jenkins: cloudstack-4.4-maven-build #561

See Changes: [Rohit Yadav] appliance: hold on to openswan version, don't upgrade -- [...truncated 1327 lines...] main: [copy] Copying 3 files to

Build failed in Jenkins: build-master-simulator #1626

See -- [...truncated 1105 lines...] [INFO] No sources to compile [INFO] [INFO] --- maven-surefire-plugin:2.18.1:test (default-test) @ cloud-framework-cluster --- [INFO]

Jenkins build is still unstable: simulator-singlerun #938

See

Ghost glibc vulnerability and CloudStack

There’s a new vulnerability out in most Linux distributions that has potential to be fairly severe. As it affects most Linux distributions, we’re putting mitigation steps out immediately at [1]. This affects many Linux distributions, so please review management servers, databases, storage syste

[DISCUSS] we need a better SSVM solution

Every time there’s an issue (security or otherwise) with the system VM ISOs, it’s a relative pain to fix. They’re sort of a closed system, people know little (relative to other ACS parts, IMHO) about their innards, and updating them is more difficult than it should be. I’d love to see a Better

Re: [DISCUSS] we need a better SSVM solution

On Wed, Jan 28, 2015 at 9:44 PM, John Kinsella wrote: > Every time there’s an issue (security or otherwise) with the system VM > ISOs, it’s a relative pain to fix. They’re sort of a closed system, people > know little (relative to other ACS parts, IMHO) about their innards, and > updating them is

Re: [DISCUSS] we need a better SSVM solution

+1 ! On Jan 28, 2015 10:01 PM, "Erik Weber" wrote: > On Wed, Jan 28, 2015 at 9:44 PM, John Kinsella wrote: > > > Every time there’s an issue (security or otherwise) with the system VM > > ISOs, it’s a relative pain to fix. They’re sort of a closed system, > people > > know little (relative to ot

Re: Ghost glibc vulnerability and CloudStack

https://blogs.apache.org/cloudstack/entry/cloudstack_and_the_ghost_glibc has now been updated with links to download the updated SSVM John On Jan 28, 2015, at 11:55 AM, John Kinsella mailto:j...@stratosec.co>> wrote: There’s a new vulnerability out in most Linux distributions that has potentia

Re:[DISCUSS] we need a better SSVM solution

+1 some trivial cases: When user upload a template , add option or tags to identify the template is SystemVm template . Allow user have their own custom "SystemVm Service Offering " , in which has an option for user assign/choice systemvm template . -- Regards, ChunFe

Orphaned Data Disks

Has anyone noticed that after destroying and expunging an instance that has a data disk attached, cloudstack leaves the datadisk orphaned? If so is this expected behavior, and if so is there an option to change it?

RE: Orphaned Data Disks

That is expected behavior. Right now there is no option to change it. Sanjeev, CloudPlatform Engineering, Citrix Systems, Inc. -Original Message- From: Michael Phillips [mailto:mphilli7...@hotmail.com] Sent: Thursday, January 29, 2015 10:43 AM To: dev@cloudstack.apache.org Subject: Orph

RE: Orphaned Data Disks

What was the logic behind leaving the disks orphaned? > From: sanjeev.neelar...@citrix.com > To: dev@cloudstack.apache.org > Subject: RE: Orphaned Data Disks > Date: Thu, 29 Jan 2015 05:30:49 + > > That is expected behavior. Right now there is no option to change it. > > Sanjeev, > CloudPlat

Re: Orphaned Data Disks

Data disks are their own entity. You can detach them and attach them to other VMs. CloudStack doesn't assume that you want all the disks to die when you destroy a VM simply because they happen to be attached to that vm at the moment. On Wed, Jan 28, 2015 at 10:47 PM, Michael Phillips wrote: > Wha

Jenkins build is back to normal : build-master-simulator #1627

See

Build failed in Jenkins: build-master #2198

See Changes: [marcus_sorensen] LibvirtComputingResource: make Oracle linux support virtio -- [...truncated 1418 lines...] Tests run: 2, Failures: 0, Errors: 0, Skipped: 2, Time elapsed: 0.004 s

Build failed in Jenkins: simulator-singlerun #939

See Changes: [marcus_sorensen] LibvirtComputingResource: make Oracle linux support virtio -- [...truncated 3468 lines...] [INFO] Installing

RE: Orphaned Data Disks

To me that's kind of strange to NOT assume to delete the disks that are attached to an instance at time of deletion. I think in most real world environments a data disk will belong to one machine only. Of course the exception is clustering and that is probably outside of this scope. Even if I

Re: Orphaned Data Disks

The trick is to not think of them as orphaned. The data disk is its own entity, it stands alone from the VM, and really the ability to create a data disk along with vm deployment is just a convenience, data disk lifecycle is to be created standalone, attached, detached, and deleted standalone. It'