@nacx I've applied the patch from jclouds/jclouds#724, rebuilt there then
removed the workaround from here: everything is working, cool!
Shall I wait for that PR to be merged before removing the workaround here?
---
Reply to this email directly or view it on GitHub:
@nacx Everything working as expected: looking forward for this PR to get merged
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds/pull/724#issuecomment-90822263
- refactor AccountApiExpectedTest to AccountApiMockTest
- refactor DatacenterApiExpectTest to DatacenterApiMockTest
- refactor SoftwareDescriptionApiExpectTest to SoftwareDescriptionApiMockTest
- refactor VirtualGuestApiExpectTest to VirtualGuestApiMockTest
- refactor
Yaron Rosenbaum created JCLOUDS-880:
---
Summary: Create instance with additional disk attached / redefine
boot disk size
Key: JCLOUDS-880
URL: https://issues.apache.org/jira/browse/JCLOUDS-880
Francesco Chicchiriccò created JCLOUDS-879:
--
Summary: Reserved IP address support
Key: JCLOUDS-879
URL: https://issues.apache.org/jira/browse/JCLOUDS-879
Project: jclouds
Issue
[
https://issues.apache.org/jira/browse/JCLOUDS-879?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ignasi Barrera reassigned JCLOUDS-879:
--
Assignee: Ignasi Barrera
Reserved IP address support
---
[
https://issues.apache.org/jira/browse/JCLOUDS-879?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ignasi Barrera updated JCLOUDS-879:
---
Assignee: fabio martelli (was: Ignasi Barrera)
Reserved IP address support
You can view, comment on, or merge this pull request online at:
https://github.com/jclouds/jclouds-labs-openstack/pull/188
-- Commit Summary --
* adding: StackApi
-- File Changes --
M openstack-heat/pom.xml (8)
M
[
https://issues.apache.org/jira/browse/JCLOUDS-879?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14484977#comment-14484977
]
fabio martelli commented on JCLOUDS-879:
[~nacx], can you assign this issue to
@andreaturli there are now just two commits, the original and the squashed
review changes, which I think preserves enough context without cluttering up
the commit history. Or would you prefer squashed to a single commit?
---
Reply to this email directly or view it on GitHub:
@andreaturli ok build seems happy now :frog:
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds-labs/pull/162#issuecomment-90961150
Pushed to master and 1.9.x.
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds/pull/724#issuecomment-90930247
[
https://issues.apache.org/jira/browse/JCLOUDS-880?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ignasi Barrera updated JCLOUDS-880:
---
Priority: Major (was: Blocker)
Create instance with additional disk attached / redefine
Squashed and pushed to master and 1.9.x. Many thanks @ilgrosso!
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds-labs/pull/156#issuecomment-90936758
Closed #724.
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds/pull/724#event-276271159
[
https://issues.apache.org/jira/browse/JCLOUDS-876?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14485293#comment-14485293
]
Ignasi Barrera commented on JCLOUDS-876:
master:
[
https://issues.apache.org/jira/browse/JCLOUDS-850?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14485306#comment-14485306
]
ASF subversion and git services commented on JCLOUDS-850:
-
Commit
[
https://issues.apache.org/jira/browse/JCLOUDS-876?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ignasi Barrera resolved JCLOUDS-876.
Resolution: Fixed
Fix Version/s: 1.9.1
loginPassword / loginPrivateKey not
[
https://issues.apache.org/jira/browse/JCLOUDS-850?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ignasi Barrera resolved JCLOUDS-850.
Resolution: Fixed
Fix Version/s: 1.9.1
Add the live test that extends the
That would be the plan going forward, though maybe not as part of this PR. I am
not sure what the right timing would be to do that, yet.
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds/pull/725#issuecomment-90946669
[
https://issues.apache.org/jira/browse/JCLOUDS-850?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14485312#comment-14485312
]
ASF subversion and git services commented on JCLOUDS-850:
-
Commit
[
https://issues.apache.org/jira/browse/JCLOUDS-839?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ignasi Barrera updated JCLOUDS-839:
---
Assignee: Bhathiya Supun
Complete CloudService support
-
[
https://issues.apache.org/jira/browse/JCLOUDS-853?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ignasi Barrera updated JCLOUDS-853:
---
Assignee: Bhathiya Supun
Improve Create Virtual Machine Deployment Operation
[
https://issues.apache.org/jira/browse/JCLOUDS-881?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14485766#comment-14485766
]
Christopher Lane Hinson (w/ Web Performance) commented on JCLOUDS-881:
@andreaturli what do you mean?
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds-labs/pull/162#issuecomment-91011138
thanks @grkvlt, could you please squash the commits so that I can merge it?
thanks!
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds-labs/pull/162#issuecomment-90962193
@grkvlt the previous build failed because of an external error, so I asked for
a rebuild in that way.
Merging the PR just now
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds-labs/pull/162#issuecomment-91012168
@andreaturli np, thanks!
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds-labs/pull/162#issuecomment-91013904
Merged at
[8d1404038dfe952b7fc](https://git1-us-west.apache.org/repos/asf?p=jclouds-labs.git;a=commit;h=8d140403)
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds-labs/pull/162#issuecomment-91014842
Closed #162.
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds-labs/pull/162#event-27687
Also backported to 1.9.x at
http://git-wip-us.apache.org/repos/asf/jclouds-labs/commit/38b09ced
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds-labs/pull/162#issuecomment-91017810
See https://jclouds.ci.cloudbees.com/job/jclouds-karaf/1086/
--
Started by upstream project jclouds-labs build number 866
originally caused by:
Started by an SCM change
Building remotely on 2d9e8f20 (lxc-fedora17 standard m1.large large) in
workspace
[
https://issues.apache.org/jira/browse/JCLOUDS-881?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ignasi Barrera resolved JCLOUDS-881.
Resolution: Duplicate
This is an already known issue. jclouds uses a lot of reflection,
See https://jclouds.ci.cloudbees.com/job/jclouds-labs-openstack/721/
--
[...truncated 2264 lines...]
Downloading:
https://repository-jclouds.forge.cloudbees.com/release/org/codehaus/plexus/plexus-velocity/1.1.8/plexus-velocity-1.1.8.jar
Downloading:
Both
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds/pull/725#issuecomment-91056170
See https://jclouds.ci.cloudbees.com/job/jclouds-karaf/1087/
Hi @fmartelli!
Now that the other Azure PRs have been merged, could you rebase this one so it
only contains the commits that are relevant to the JIRA issue? I look forward
to having a look at this and merging it!
Thanks!
---
Reply to this email directly or view it on GitHub:
[
https://issues.apache.org/jira/browse/JCLOUDS-881?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14486287#comment-14486287
]
Christopher Lane Hinson (w/ Web Performance) commented on JCLOUDS-881:
Just that minor and it will be ready to be merged. Apologies for the delay in
the reviews!
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds-labs/pull/143#issuecomment-91041514
Andrew Gaul created JCLOUDS-883:
---
Summary: Swift portable copy blob cannot replace metadata
Key: JCLOUDS-883
URL: https://issues.apache.org/jira/browse/JCLOUDS-883
Project: jclouds
Issue Type:
and update the Firewall and Server list handler tests to properly test the
new elements introduced in this commit
The server object now seems to have nested load balancers, and the handler was
updated to handle that. Update the handler tests to exercise that path too.
---
Reply to this
Do you refer to the removal of the existing cloudfiles provider, or to adding
the new provides to the blobstore aggregator pom?
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds/pull/725#issuecomment-91044628
+1! During the 1.9 release I had to fix the branding dependency in the pom.xml
but forgot to amend the assembly descriptors, as the build was passing.
Thanks!
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds-cli/pull/26#issuecomment-91121260
[
https://issues.apache.org/jira/browse/JCLOUDS-651?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14486396#comment-14486396
]
ASF subversion and git services commented on JCLOUDS-651:
-
Commit
See
https://jclouds.ci.cloudbees.com/job/jclouds-labs-openstack/org.apache.jclouds.labs$openstack-glance/722/
Follow-up to 01dcca14
Before change:
After change:
Also needs to be
@@ -796,9 +808,8 @@ public void testCopyBlobReplaceMetadata() throws
Exception {
} finally {
Closeables2.closeQuietly(is);
}
- // TODO: S3 overrideMetadataWith also overrides system metadata
- // TODO: Swift does not preserve system metadata
See
https://jclouds.ci.cloudbees.com/job/jclouds-1.9.x-branch/org.apache.jclouds$jclouds-project/7/
--
[...truncated 829 lines...]
Downloading:
@nacx: Just to be sure...is this OK for you?
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds/pull/721#issuecomment-91096783
Yes! :) Thanks for taking care of this!
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds/pull/721#issuecomment-91121070
See
https://jclouds.ci.cloudbees.com/job/jclouds-labs-openstack/org.apache.jclouds.labs$openstack-glance/721/
--
[...truncated 2110 lines...]
Downloading:
@nacx: ping? ;-)
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds-cli/pull/26#issuecomment-91096715
See
https://jclouds.ci.cloudbees.com/job/jclouds-labs-google/org.apache.jclouds.labs$jclouds-labs-google/537/
Thanks @neykov!
So this seems to be useful to manage local boxes, as Vagrant does not have an
API. Unlike other providers, the jclouds code will deploy nodes int he same
machine where the code runs, instead of deploying them in a target
provider/api/endpoint.
With my limited experience with
@andrewgaul I'm ok with that. Figuring out the swift quirk might need some more
work.
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds/pull/722#issuecomment-91101772
[
https://issues.apache.org/jira/browse/JCLOUDS-882?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14486360#comment-14486360
]
Christopher Dancy commented on JCLOUDS-882:
---
I'll take on the work for
+1 to merge it as-is then. Thanks!
What are waiting to remove the old providers? Is it something to
deprecate/announce/discuss in the mailing list?
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds/pull/725#issuecomment-91121414
This works pretty well across the major providers -- should we merge as-is and
open a JIRA issue for the Swift quirk?
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds/pull/722#issuecomment-91083960
58 matches
Mail list logo
