protected String imageIdForZone(String zoneId) {
ImageApi imageApi = api.getImageApiForZone(zoneId);
- return Iterables.getLast(imageApi.list().concat()).getId();
+ return Iterables.getFirst(imageApi.list().concat(), null).getId();
Live tests still happy.
---
Reply to
[
https://issues.apache.org/jira/browse/JCLOUDS-147?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13984460#comment-13984460
]
Everett Toews commented on JCLOUDS-147:
---
I'm only interested in the Javadocs
Everett Toews created JCLOUDS-555:
-
Summary: Duplicate bouncycastle resources when depending on
MockWebServer
Key: JCLOUDS-555
URL: https://issues.apache.org/jira/browse/JCLOUDS-555
Project: jclouds
CreateServerOptions options = new CreateServerOptions();
- ServerCreated server = serverApi.create(hostName,
imageIdForZone(regionId), flavorRefForZone(regionId), options);
+ if (availabilityZoneId != null) {
+ options = options.availabilityZone(availabilityZoneId);
I dunno. I'm okay with it the way it is. Adding the version number to the
Install button everywhere seems redundant.
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds-site/pull/89#issuecomment-41714721
Merged to master and 1.7.x.
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds/pull/355#issuecomment-41724480
Let’s just see what happens.
Everett
On Apr 29, 2014, at 12:51 PM, Andrew Phillips aphill...@qrmedia.com wrote:
What data would we need on the DEV@cloud builds to start experimenting here?
Or should we simply add -T 2C or so to the PR builds and see what happens?
ap
[
https://issues.apache.org/jira/browse/JCLOUDS-551?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Everett Toews closed JCLOUDS-551.
-
Resolution: Duplicate
Move JavaDocs to jclouds.apache.org
[
https://issues.apache.org/jira/browse/JCLOUDS-542?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Everett Toews closed JCLOUDS-542.
-
Resolution: Not a Problem
JIRA really isn't the place to go on troubleshooting random problems
[
https://issues.apache.org/jira/browse/JCLOUDS-545?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Everett Toews updated JCLOUDS-545:
--
Description:
So far there are a number of issue with the Beta SwiftApi and related Apis
div id=quicknews class=alert alert-info
-{% for page in site.pages %}
-{% if page.quicknew %}
-{% assign newspresent = true %}
+{% for page in site.pages %}{% if page.quicknew %}{% assign newspresent =
true %}
With the way liquid works, having them on the same line generates a ton
No thanks. The very first thing on the root page of a web site (especially for
something like a Java toolkit) should be a clear explanation of what the thing
is about. Moving the latest version to the very top would violate that
principle.
Look at it from the perspective of someone who is
@@ -13,7 +13,7 @@
/div
div class=col-md-2 column
p class=text-center
-a class=text-primary
href=https://wiki.apache.org/jclouds/How%20to%20Contribute%20Documentation;Fix
This Page/a
+a
Fixed.
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds-site/pull/87#issuecomment-41589211
Closed #88.
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds-site/pull/88
Merged and deployed.
This conversation needs to continue on the dev list or in
[JCLOUDS-147](https://issues.apache.org/jira/browse/JCLOUDS-147).
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds-site/pull/88#issuecomment-41589664
@@ -13,7 +13,7 @@
/div
div class=col-md-2 column
p class=text-center
-a class=text-primary
href=https://wiki.apache.org/jclouds/How%20to%20Contribute%20Documentation;Fix
This Page/a
+a
@@ -13,7 +13,7 @@
/div
div class=col-md-2 column
p class=text-center
-a class=text-primary
href=https://wiki.apache.org/jclouds/How%20to%20Contribute%20Documentation;Fix
This Page/a
+a
[
https://issues.apache.org/jira/browse/JCLOUDS-545?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Everett Toews updated JCLOUDS-545:
--
Description:
So far there are a number of issue with the Beta SwiftApi and related Apis
Merged and deployed.
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds-site/pull/90#issuecomment-41598197
@@ -52,13 +53,22 @@ public BaseNovaApiLiveTest() {
provider = openstack-nova;
}
- protected SetString zones;
+ protected SetString zones = Sets.newHashSet();
Sure.
---
Reply to this email directly or view it on GitHub:
CreateServerOptions options = new CreateServerOptions();
- ServerCreated server = serverApi.create(hostName,
imageIdForZone(regionId), flavorRefForZone(regionId), options);
-
- blockUntilServerInState(server.getId(), serverApi, serverStatus);
+ if (availabilityZoneId
protected String imageIdForZone(String zoneId) {
ImageApi imageApi = api.getImageApiForZone(zoneId);
- return Iterables.getLast(imageApi.list().concat()).getId();
+ return Iterables.getFirst(imageApi.list().concat(), null).getId();
Yes. The lighter images tend to be first
+import com.google.common.base.Predicate;
+import org.jclouds.openstack.nova.v2_0.domain.Server;
+import org.jclouds.openstack.nova.v2_0.domain.ServerCreated;
+import org.jclouds.openstack.nova.v2_0.features.ServerApi;
+
+import static com.google.common.base.Preconditions.checkNotNull;
+ *
+ * You can also use the static convenience methods as so.
+ *
+ * pre
+ * {@code
+ * Server server = serverApi.create(100);
+ *
+ * if (!ServerPredicates.awaitAvailable(serverApi).apply(server.getId())) {
+ *throw new TimeoutException(Timeout on server: + server);
+ * }
+ public static PredicateServer awaitShutoff(ServerApi serverApi) {
+ ServerStatusPredicate statusPredicate = new
ServerStatusPredicate(serverApi, SHUTOFF);
+
+ return retry(statusPredicate, 600, 5, 5, SECONDS);
+ }
+
+ public static PredicateServer awaitStatus(
+
+ this.status = checkNotNull(status, status must be defined);
+ }
+
+ /**
+ * @return boolean Return true when the server reaches status, false
otherwise
+ */
+ @Override
+ public boolean apply(Server server) {
+ checkNotNull(server,
+ public boolean apply(Server server) {
+ checkNotNull(server, server must be defined);
+
+ if (status.equals(server.getStatus())) {
+return true;
+ }
+ else {
+Server serverUpdated = serverApi.get(server.getId());
+
+ else {
+Server serverUpdated = serverApi.get(server.getId());
+checkNotNull(serverUpdated, Server %s not found.,
server.getId());
+
+return status.equals(serverUpdated.getStatus());
+ }
+ }
+ }
+
+public
@@ -131,9 +135,12 @@ public void testCreateInWrongAvailabilityZone() {
for (String zoneId : zones) {
ServerApi serverApi = api.getServerApiForZone(zoneId);
try {
-serverId = createServer(zoneId, err,
Server.Status.ERROR).getId();
-Server
Everett Toews created JCLOUDS-554:
-
Summary: openstack-nova defaults to API v1.1
Key: JCLOUDS-554
URL: https://issues.apache.org/jira/browse/JCLOUDS-554
Project: jclouds
Issue Type: Bug
I figured out a way to unit test them with MockWebServer and it's actually
pretty clean!
As for taking serverApi, I think I'll be leaving it as it is. The number one
reason is consistency with all of the other *Predicates classes in all of the
other modules. Developers should have as
Closed #89.
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds-site/pull/89
Merged and deployed.
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds-site/pull/89#issuecomment-41637028
?
On Fri, Apr 25, 2014 at 8:46 PM, Everett Toews
everett.to...@rackspace.commailto:everett.to...@rackspace.com wrote:
There’s a bit of a terminology disconnect in jclouds when it comes to OpenStack
regions.
The jclouds term for an OpenStack region is zone.
e.g. If you were working with Nova Servers
You can merge this Pull Request by running:
git pull https://github.com/rackerlabs/jclouds-site labs-rel-notes
Or you can view, comment on it, or merge it online at:
https://github.com/jclouds/jclouds-site/pull/88
-- Commit Summary --
* Links to OpenStack Labs Javadoc
-- File Changes
You can merge this Pull Request by running:
git pull https://github.com/rackerlabs/jclouds-site release-news
Or you can view, comment on it, or merge it online at:
https://github.com/jclouds/jclouds-site/pull/89
-- Commit Summary --
* Always display the latest release on the home page
You can merge this Pull Request by running:
git pull https://github.com/rackerlabs/jclouds-site fix-this-page
Or you can view, comment on it, or merge it online at:
https://github.com/jclouds/jclouds-site/pull/90
-- Commit Summary --
* Fix This Page links directy to GitHub file
--
@@ -36,6 +36,11 @@
/div
/div
+div id=releasenews class=alert alert-info
I think it looks okay. I specifically do want separate boxes as the latest
version one will always be there.
![screen shot 2014-04-25 at 1 32 58
@@ -36,6 +36,11 @@
/div
/div
+div id=releasenews class=alert alert-info
+pThe latest version is {{ site.latest_version }} released
on {{ site.latest_version_date }}! Read the a href=/releasenotes/{{
site.latest_version
They really do belong on the site. Create a JIRA issue for it.
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds-site/pull/88#issuecomment-41441479
You can merge this Pull Request by running:
git pull https://github.com/rackspace/jclouds server-predicates
Or you can view, comment on it, or merge it online at:
https://github.com/jclouds/jclouds/pull/355
-- Commit Summary --
* ServerPredicates to make waiting easier.
-- File
There’s a bit of a terminology disconnect in jclouds when it comes to OpenStack
regions.
The jclouds term for an OpenStack region is zone.
e.g. If you were working with Nova Servers,
NovaApi.getServerApiForZone(“RegionOne”);
I’ve documented in the Terminology section [1] of the OpenStack
[
https://issues.apache.org/jira/browse/JCLOUDS-542?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13979642#comment-13979642
]
Everett Toews commented on JCLOUDS-542:
---
Neither NovaAsyncApi nor RestContextS
You can merge this Pull Request by running:
git pull https://github.com/rackerlabs/jclouds-examples reorder-pom
Or you can view, comment on it, or merge it online at:
https://github.com/jclouds/jclouds-examples/pull/46
-- Commit Summary --
* Reorder the deps and better comments
--
You can merge this Pull Request by running:
git pull https://github.com/rackerlabs/jclouds-site escape-qmark
Or you can view, comment on it, or merge it online at:
https://github.com/jclouds/jclouds-site/pull/86
-- Commit Summary --
* Escape the ? in the awk command
-- File Changes --
You can merge this Pull Request by running:
git pull https://github.com/rackerlabs/jclouds-site blog-gsoc
Or you can view, comment on it, or merge it online at:
https://github.com/jclouds/jclouds-site/pull/87
-- Commit Summary --
* Blog post on GSoC
-- File Changes --
A
[
https://issues.apache.org/jira/browse/JCLOUDS-542?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13978240#comment-13978240
]
Everett Toews commented on JCLOUDS-542:
---
http://jclouds.apache.org/guides/openstack
Everett Toews created JCLOUDS-545:
-
Summary: SwiftApi and related Apis improvements
Key: JCLOUDS-545
URL: https://issues.apache.org/jira/browse/JCLOUDS-545
Project: jclouds
Issue Type: Bug
[
https://issues.apache.org/jira/browse/JCLOUDS-540?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13978307#comment-13978307
]
Everett Toews commented on JCLOUDS-540:
---
But listNodes() has been around forever
Merged, deployed, and tweeted. :)
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds-site/pull/87#issuecomment-41220587
Closed #68.
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds-site/pull/68
Reopened #68.
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds-site/pull/68
Closed #68.
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds-site/pull/68
Closed #68.
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds-site/pull/68
Everett Toews created JCLOUDS-547:
-
Summary: Rackspace Cloud Files create static website is broken
Key: JCLOUDS-547
URL: https://issues.apache.org/jira/browse/JCLOUDS-547
Project: jclouds
[
https://issues.apache.org/jira/browse/JCLOUDS-547?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Everett Toews updated JCLOUDS-547:
--
Description:
*This doesn't work 1.7.2*
{code}CDNApi.update(CONTAINER_PUBLISH
[
https://issues.apache.org/jira/browse/JCLOUDS-547?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13979048#comment-13979048
]
Everett Toews commented on JCLOUDS-547:
---
The [jclouds-site-staging job config
Rackspace Cloud Files create static website is broken in 1.7.2, see
[JCLOUDS-547](https://issues.apache.org/jira/browse/JCLOUDS-547).
I've repaired the jclouds-site-staging job by reverting it to 1.7.1 for the
time being.
---
Reply to this email directly or view it on GitHub:
Closed #46.
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds-examples/pull/46
Fixed. Merged.
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds-examples/pull/46#issuecomment-41226408
Closed #86.
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds-site/pull/86
Merged.
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds-site/pull/86#issuecomment-41226474
Fixed. Squashed. Merged. Deployed!
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds-site/pull/84#issuecomment-4106
Closed #84.
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds-site/pull/84
Merged and deployed.
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds-site/pull/85#issuecomment-41066690
[
https://issues.apache.org/jira/browse/JCLOUDS-542?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Everett Toews reassigned JCLOUDS-542:
-
Assignee: Everett Toews
I am trying some examples on openstack using jclouds.I have
[
https://issues.apache.org/jira/browse/JCLOUDS-542?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13977069#comment-13977069
]
Everett Toews commented on JCLOUDS-542:
---
I just updated the examples to 1.7.2
[
https://issues.apache.org/jira/browse/JCLOUDS-540?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13977229#comment-13977229
]
Everett Toews commented on JCLOUDS-540:
---
I think it would need
Google Cloud Storage support for jclouds [1]
Student: Bhathiya
Mentor: Matt Stephenson
Porting EC2 support with JClouds integration in Apache Airavata
Student: Nipun Udara
Mentors: Suresh Marru, Lahiru Gunathilake
Amazon Glacier support for jclouds
Student: Roman Coedo
Mentor: Andrew Gaul
Did
On Apr 22, 2014, at 9:54 AM, Jeremy Daggett jeremy.dagg...@rackspace.com
wrote:
I thought we had a coding best practices doc somewhere, but I can¹t seem
to locate it. Any pointers? It would be good to capture any best practices
like this for community members to reference.
Please start one
Hi Mehmet,
There’s a couple of ways you can solve this problem.
1. Client side
If you’re writing some sort of client for a customer to solve this problem, you
can use a multi-cloud SDK like jclouds, libcloud, or Fog to store their files
in one cloud or the other depending on how full Swift
Closed #81.
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds-site/pull/81
You can merge this Pull Request by running:
git pull https://github.com/rackerlabs/jclouds-site logging-https
Or you can view, comment on it, or merge it online at:
https://github.com/jclouds/jclouds-site/pull/84
-- Commit Summary --
* How to use a proxy with jclouds
-- File Changes
Closed #41.
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds-site/pull/41
+1. Proxy Proxy Settings SSL tab
+1. Check Enable SSL Proxying
+1. Add Locations. e.g.
+1. *.rackspacecloud.com
+1. *.clouddrive.com
+
+jclouds also requires some configuration to use a proxy.
+
+{% highlight java %}
+import static org.jclouds.Constants.*;
+
+// snip
+
@@ -7,6 +7,7 @@ permalink: /reference/logging/
1. [Install](#install)
1. [Configure](#configure)
1. [Enable](#enable)
+1. [Proxy](#proxy)
I'll change it to HTTP(S) Proxy.
---
Reply to this email directly or view it on GitHub:
You can merge this Pull Request by running:
git pull https://github.com/rackerlabs/jclouds-site openstack-up
Or you can view, comment on it, or merge it online at:
https://github.com/jclouds/jclouds-site/pull/85
-- Commit Summary --
* Update to latest version of jclouds
-- File
Squashed and merged.
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds-examples/pull/45#issuecomment-40984787
Closed #45.
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds-examples/pull/45
Don't forget to squash first!
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds-site/pull/68#issuecomment-40984853
[
https://issues.apache.org/jira/browse/JCLOUDS-526?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Everett Toews updated JCLOUDS-526:
--
Fix Version/s: 1.7.3
Remove QuotaClassApi in Nova
On Apr 21, 2014, at 9:10 AM, SANDEEP BAZAR sandeepba...@gmail.com wrote:
*) In table under https://github.com/jclouds/jclouds-labs-openstack;,
openstack-swift is shown *BETA*. By when it will be production ready?
Probably jclouds 1.8.0 or 1.8.1. There is no firm release date for those yet.
@@ -114,14 +114,21 @@ You'll also need a logback.xml configuration file on
your classpath. Here's an e
## a id=enable/aEnable Logging
-Below is some example code of how to enable your code to use SLF4J. The
SLF4JLoggingModule needs to be passed in to the ContextBuilder of whatever
Whatever works for you. I’ll be offline for the next hour or so. Go ahead and
update and deploy. :)
On Apr 17, 2014, at 9:15 AM, Andrew Phillips
notificati...@github.commailto:notificati...@github.com wrote:
How about linking to
http://people.apache.org/committers-by-project.html#jclouds
@demobox Do you need me to deploy this? I'm excited to get the release out
there!
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds-site/pull/78#issuecomment-40727917
You can merge this Pull Request by running:
git pull https://github.com/rackerlabs/jclouds-site twitter
Or you can view, comment on it, or merge it online at:
https://github.com/jclouds/jclouds-site/pull/81
-- Commit Summary --
* Added a Twitter timeline to the community page
-- File
LGTM. Thanks @demobox!
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds-site/pull/78#issuecomment-40753025
+1
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds-site/pull/82#issuecomment-40753088
Can you please run through all of the ctors and update the URLs?
Should be http://jclouds.apache.org/guides/rackspace/
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds-examples/pull/45#issuecomment-40758113
After the main method comments are fixed I'm a +1. I ran all of the examples
and everything is fine.
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds-examples/pull/45#issuecomment-40765742
Merged and deployed.
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds-site/pull/81#issuecomment-40765842
@demobox Spoke too soon. In your commit, the contents of the
/releasenotes/atom.xml entries was markdown instead of the generated html that
it should have been. See this
[diff](http://svn.apache.org/viewvc/jclouds/site-content/releasenotes/atom.xml?view=diffr1=1588337r2=1588338pathrev=1588338).
/parent
groupIdorg.apache.jclouds.examples/groupId
artifactIdjclouds-examples/artifactId
- version1.7.2-SNAPSHOT/version
+ version1.7.3-SNAPSHOT/version
Is the versioning scheme for the examples themselves important?
I would be fine leaving them at 1.0 just so they never have to
@demobox Also, can you make sure you upgrade to jekyll 1.5.1 before generating
the site?
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds-site/pull/78#issuecomment-40618772
You can merge this Pull Request by running:
git pull https://github.com/rackerlabs/jclouds-site generic-logging
Or you can view, comment on it, or merge it online at:
https://github.com/jclouds/jclouds-site/pull/79
-- Commit Summary --
* More generic logging example code
-- File
You can merge this Pull Request by running:
git pull
https://github.com/rackerlabs/jclouds-site?utm_campaign=websiteutm_source=sendgrid.comutm_medium=email
move-providers
Or you can view, comment on it, or merge it online at:
Closed #80.
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds-site/pull/80
How do we get rid of those archetypes permanently?
They’ve become a red herring.
Everett
On Apr 16, 2014, at 3:31 AM, Ignasi Barrera ignasi.barr...@gmail.com wrote:
Hi Nilay,
The archetypes are for building new jclouds providers and are quite
obsolete. You'd better have a look at the
Closed #77.
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds-site/pull/77
701 - 800 of 1710 matches
Mail list logo
