Tim, during 4.0/4.1 we used to install a very old xstools 5.6, can we just use
that and if we do will that cause any (potential) issue since you mentioned it
has few bugs in it?
Regards.
On 20-Nov-2014, at 10:23 pm, Tim Mackey tmac...@gmail.com wrote:
It's the other way around. Newer
The big problem I recall with the 5.6 Linux tools happened during live
migration. I don't recall the specific circumstances, but if the VM was
migrated, it could cause either the guest or the host to crash. I've never
paid attention to the specific Linux version in the system VMs, but the
tools
See http://jenkins.buildacloud.org/job/build-4.5/157/changes
Changes:
[wstevens] CLOUDSTACK-7822: Fixed SSL Cert Tests and relaxed chain validation
[wstevens] CLOUDSTACK-7952: Remove private key from SslCertResponse
(listSslCerts)
--
[...truncated 2860
Is there available RPM Repository with ACS 4.4.2 ?
2014-11-21 3:59 GMT+01:00 Daan Hoogland daan.hoogl...@gmail.com:
Hi All,
I've created a 4.4.2 release, with the following artifacts up for a vote:
Git Branch and Commit SH:
On 11/20/2014 07:50 PM, Marcus wrote:
For RPMs, the package.sh script that sets things up for rpmbuild could do
the mvn if we wanted to keep the RPM build process from downloading.
Something similar could be done from DEB, perhaps.
Debian has helpers for that, so that hopefully smooths it
On 11/21/2014 10:23 AM, Tomasz Zięba wrote:
Is there available RPM Repository with ACS 4.4.2 ?
You can find those on Jenkins:
http://jenkins.buildacloud.org/view/4.4/job/cloudstack-4.4-package-rpm/
2014-11-21 3:59 GMT+01:00 Daan Hoogland daan.hoogl...@gmail.com:
Hi All,
I've created a
Tomasz,
On Fri, Nov 21, 2014 at 10:23 AM, Tomasz Zięba t.a.zi...@gmail.com wrote:
Is there available RPM Repository with ACS 4.4.2 ?
No there isn't one, but the jenkins.buildacloud.org jobs for 4.4
should have some artifacts. I will prepare a set soon. You won't want
to wait on me on this
Hi,
Built OSS rpms here http://tmp.nux.ro/acs442/
The jenkins build are they oss or noredist? I could not build noredist:
Could not resolve dependencies for project
org.apache.cloudstack:cloud-plugin-netapp:jar:4.4.2: Could not find artifact
com.cloud.com.netapp:manageontap:jar:4.0 in central
Lucian, the non oss deps need to be added to the repository by hand.
They can not be downloaded automatically. This is basically why there
is a separate build (from a tech point of view).
On Fri, Nov 21, 2014 at 10:42 AM, Nux! n...@li.nux.ro wrote:
Hi,
Built OSS rpms here
GitHub user pyr opened a pull request:
https://github.com/apache/cloudstack/pull/44
Remove AWS api bridge
This has been a discussion point for a while. The (mostly generated)
code for the AWS api bridge is by far the largest source component in
Cloudstack, while seldomly
See http://jenkins.buildacloud.org/job/build-4.5/158/
--
[...truncated 3522 lines...]
[INFO] Deleting
http://jenkins.buildacloud.org/job/build-4.5/ws/plugins/user-authenticators/sha256salted
(includes = [target, dist], excludes = [])
[INFO]
[INFO] ---
---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/28325/
---
Review request for cloudstack and Kishan Kavala.
Bugs: CLOUDSTACK-7948
See http://jenkins.buildacloud.org/job/build-4.5/159/
--
[...truncated 6018 lines...]
[INFO] --- maven-resources-plugin:2.5:testResources (default-testResources) @
cloud-plugin-storage-image-default ---
[debug] execute contextualize
[INFO] Using 'UTF-8'
Looks like it was fixed
https://issues.apache.org/jira/browse/CLOUDSTACK-6261
From: Francois Gaudreault
fgaudrea...@cloudops.commailto:fgaudrea...@cloudops.com
Reply-To: dev@cloudstack.apache.orgmailto:dev@cloudstack.apache.org
dev@cloudstack.apache.orgmailto:dev@cloudstack.apache.org,
Hello,
EC2 compatibility is an essential feature for potential ACS adopters.
What alternatives are there for the AWSAPI component?
Lucian
--
Sent from the Delta quadrant using Borg technology!
Nux!
www.nux.ro
- Original Message -
From: pyr g...@git.apache.org
To:
Oh, roger that, thanks.
--
Sent from the Delta quadrant using Borg technology!
Nux!
www.nux.ro
- Original Message -
From: Daan Hoogland daan.hoogl...@gmail.com
To: dev dev@cloudstack.apache.org
Sent: Friday, 21 November, 2014 10:18:18
Subject: Re: [ACS44]release 4.4.2 release
See http://jenkins.buildacloud.org/job/build-master-noredist/3836/changes
Changes:
[Will Stevens] Updated the system vm build to remove incompatible qemu-img
'compat' option
--
[...truncated 14255 lines...]
221/509 KB 150/166 KB 51/51 KB 394/441 KB
I didn't even realise we still support XS 5.6. I would advocate not supporting
that any more, independent of this tools discussion, because Citrix won't fix
any bugs on it now, even security bugs. Can't we move to a model where we only
support hypervisor versions that the hypervisor vendor
See http://jenkins.buildacloud.org/job/build-4.5/160/
See http://jenkins.buildacloud.org/job/build-4.5-simulator/60/changes
Changes:
[Will Stevens] CLOUDSTACK-7822: Fixed SSL Cert Tests and relaxed chain
validation
[Will Stevens] CLOUDSTACK-7952: Remove private key from SslCertResponse
(listSslCerts)
--
See http://jenkins.buildacloud.org/job/simulator-singlerun/changes
Github user runseb commented on the pull request:
https://github.com/apache/cloudstack/pull/44#issuecomment-63965999
This is green on travis, so let's discuss on the list. I am asking asf
infra to create a cloudstack-awsapi repo.
One alternative is
Hi,
On Fri, Nov 21, 2014 at 4:29 PM, sw...@apache.org wrote:
Repository: cloudstack
Updated Branches:
refs/heads/master 83656a6ea - 8e689b114
Updated the system vm build to remove incompatible qemu-img 'compat' option
This sort of reverts the following fix from Edison; (should we do it
Hi Edison,
On Fri, Nov 21, 2014 at 12:30 AM, edi...@apache.org wrote:
Repository: cloudstack
Updated Branches:
refs/heads/4.5 1d6ca5eac - 50d756e87
Occasionally the while loop can exit with no data (Probably recieving an
EOF) before receiveing CMDline data from the certial port.
I created an issue for this:
https://issues.apache.org/jira/browse/CLOUDSTACK-7959
How do we deal with the fact that the system vm build machines do not
support this option? By removing this, the master system vms now build
again. If this is required for RHEL 6, do we have to update our system
As Seb mentioned on list there is an alternative. I don't think we
should remove this before the factored out version is working as well
(or the alternative he mentions is at least as complete) The idea of
isolating this bit is appealing though.
Daan
On Fri, Nov 21, 2014 at 12:23 PM, Nux!
See http://jenkins.buildacloud.org/job/build-master-noredist/3837/changes
Hi Prachi,
Since we’re already allowing users to specific account and list VMs by account,
following the same pattern I added the case so as to allow users to specify
user_id in both list/deploy VM commands. In case the userid is not specified,
in that case the logged in user’s ID will be
See http://jenkins.buildacloud.org/job/simulator-singlerun/changes
+1 what Daan said.
Once ec2stack works well, then nuke awsapi.
my 2 pence
--
Sent from the Delta quadrant using Borg technology!
Nux!
www.nux.ro
- Original Message -
From: Daan Hoogland daan.hoogl...@gmail.com
To: dev dev@cloudstack.apache.org
Sent: Friday, 21 November, 2014
On Nov 21, 2014, at 8:33 AM, Nux! n...@li.nux.ro wrote:
+1 what Daan said.
Once ec2stack works well, then nuke awsapi.
it works well.
where can we see test about awsapi ?
my 2 pence
--
Sent from the Delta quadrant using Borg technology!
Nux!
www.nux.ro
- Original
On 21-Nov-2014, at 6:43 pm, Will Stevens wstev...@cloudops.com wrote:
I created an issue for this:
https://issues.apache.org/jira/browse/CLOUDSTACK-7959
How do we deal with the fact that the system vm build machines do not
support this option? By removing this, the master system vms now
Let’s start by getting this on a feature branch.
I would like to make sure that everything works before we remove the code and
that includes deb and rpm packaging. We also need to think about the upgrade
path. If a user is currently using awsapi, he needs an upgrade path the start
using the
See http://jenkins.buildacloud.org/job/simulator-singlerun/changes
+1 on ec2stack working well (bias view).
I've used it via vagrant-aws, boto and eucalyptus eutester without issue.
It could use some documentation on deployment for production purposes, the
embedded webserver it exposes is OK but I'd feel safer with it bring behind
nginx/Apache.
On 21 Nov 2014
See http://jenkins.buildacloud.org/job/build-4.5-simulator/61/changes
It would be interesting to have usage stats on the AWS cloud bridge.
It is very hard to get working right correctly (especially when compared to
something like ec2stack) so I'd be very surprised if:
- There were a large number of users
- They had upgrade path issues
I think the idea of chunking
See http://jenkins.buildacloud.org/job/cloudstack-4.3-maven-build/639/
--
[...truncated 3684 lines...]
remote: Counting objects: 68009
remote: Counting objects: 68024
remote: Counting objects: 68029
remote: Counting objects:
If I understood correctly, (account, domainId) passed into deployVMCmd is
used for impersonation-like behavior, that is, caller is deploying a VM on
behalf of an account. Personally I don't like this kind of putting so many
parameters in one API to perform several different functionalities,
See http://jenkins.buildacloud.org/job/cloudstack-4.3-maven-build/640/changes
Changes:
[Rohit Yadav] Revert Bump release version to 4.3.2-SNAPSHOT and add empty db
upgrade path
[Rohit Yadav] CLOUDSTACK-7415. Host remains in Alert after vCenter restart.
See http://jenkins.buildacloud.org/job/cloudstack-4.3-maven-build/641/changes
Changes:
[Rohit Yadav] Revert Revert Bump release version to 4.3.2-SNAPSHOT and add
empty db upgrade path
[Rohit Yadav] fixed CLOUDSTACK-6261: remove the forceful timeout setting when
login to NetScaler.
[Rohit
See http://jenkins.buildacloud.org/job/simulator-singlerun/680/changes
Hi Rohit,
The accountId in deployVm API is serving the purpose of impersonation and can
be passed typically by admin accounts to deploy VM on behalf of other User.
So Ideally with IAM, this parameter should be removed from the API and
impersonation should be handled separately.
Keeping this
See http://jenkins.buildacloud.org/job/simulator-singlerun/681/changes
See http://jenkins.buildacloud.org/job/simulator-singlerun/changes
---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/28292/#review62647
---
Ship it!
Ship It!
- sangeetha hariharan
On Nov. 20, 2014, 7:26
---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/28300/#review62649
---
Ship it!
Ship It!
- sangeetha hariharan
On Nov. 20, 2014, 9:49
See http://jenkins.buildacloud.org/job/simulator-singlerun/changes
Hi Min, Prachi,
Thanks for your comments. I see your point, the use case is to list VMs for a
user_id (uuid, not name). I’m going to add the arg/option the listVM api to
accept user_id and return the list of VMs for that user, and add option in the
UI to do the same. Note, this is not for
49 matches
Mail list logo
