It should be closed but I'd like to hear from @amirlanesman first before doing
so in case I'm way off base about it.
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds/pull/282#issuecomment-34228743
@zack-shoylev Can you please include some code here in the PR comments
demonstrating exactly how this method would be used in a LiveTest?
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds/pull/283#issuecomment-34229197
@@ -74,6 +77,20 @@ protected String setIfTestSystemPropertyPresent(Properties
overrides, String key
return null;
}
+ /**
+* This helps live testing against specific zones only.
+* @param zones A list of zones, usually from getConfiguredZones()
+* @return a set
+ ProfileApi getProfileApiForZone(@EndpointParam(parser =
ZoneToEndpoint.class) @Nullable String zone);
+
+ /**
+* Provides access to all Profile features.
+* @param zone The zone (region) for the profile API.
+* @return A cluster API context.
+*/
+ @Delegate
+
+ * Your Cloud Big Data profile is different from your cloud account. Your
profile has the following characteristics and requirements:
+ * A profile is the configuration for the administration and login account
for the cluster.
+ * Only one profile is allowed for each user or account.
+ *
+ .clusterType(in.getClusterType())
+ .flavorId(in.getFlavorId())
+ .nodeCount(in.getNodeCount())
+ .postInitScript(in.getPostInitScript());
+ }
+ }
+
+ @Override
+ public int compareTo(CreateCluster that) {
+
+ * The cluster is deleted.
+ */
+ DELETED,
+ /**
+ * A fatal error has occurred during cluster provisioning.
+ */
+ ERROR,
+ /**
+ * Unrecognized status response.
+ */
+ UNRECOGNIZED;
+
+ /**
+ * @return The
+.add(links, links);
+ }
+
+ @Override
+ public String toString() {
+ return string().toString();
+ }
+
+ /**
+* Lists possible Cluster status.
+* @author zack-shoylev
+*/
+ public enum Status {
+ /**
+ * The cluster is in the
+import org.jclouds.rackspace.cloudbigdata.v1.features.ClusterApi;
+
+import com.google.common.base.Objects;
+import com.google.common.base.Objects.ToStringHelper;
+import com.google.common.collect.ImmutableList;
+
+/**
+ * Cloud Big Data Cluster. This class is used for responses.
+ *
+
+ /**
+* @return The operation progress of this cluster.
+*/
+ public float getProgress() {
+ return progress;
+ }
+
+ /**
+* @return the current status.
+*/
+ public Status getStatus() {
+ return status;
+ }
+
+ /**
+* @return the
+ private final Status status;
+ private final ImmutableListLink links;
+
+ @ConstructorProperties({
+ name, clusterType, flavorId, nodeCount, pointInitScript,
+ id, created, updated, postInitScriptStatus, progress,
status, links
+ })
+ protected Cluster(String name,
+ /**
+* @return the timestamp when this cluster was created.
+*/
+ public String getCreated() {
+ return created;
+ }
+
+ /**
+* @return the timestamp when this cluster was updated. This can be empty.
+*/
+ public String getUpdated() {
+ return
+*/
+ public static Builder builder() {
+ return new Builder();
+ }
+
+ /**
+* @return The Builder object
+*/
+ public Builder toBuilder() {
+ return new Builder().fromCreateProfile(this);
+ }
+
+ /**
+* Implements the Builder pattern
+*/
+ */
+package org.jclouds.rackspace.cloudbigdata.v1.domain;
+
+import static com.google.common.base.Preconditions.checkNotNull;
+
+import java.beans.ConstructorProperties;
+
+import org.jclouds.openstack.v2_0.domain.Link;
+import org.jclouds.rackspace.cloudbigdata.v1.features.ProfileApi;
+import org.jclouds.Fallbacks.EmptyFluentIterableOnNotFoundOr404;
+import org.jclouds.Fallbacks.NullOnNotFoundOr404;
+import org.jclouds.openstack.keystone.v2_0.filters.AuthenticateRequest;
+import org.jclouds.rackspace.cloudbigdata.v1.domain.Cluster;
+import
+import org.jclouds.rackspace.cloudbigdata.v1.features.ProfileApi;
+
+import com.google.common.base.Objects;
+import com.google.common.base.Objects.ToStringHelper;
+import com.google.common.collect.ImmutableList;
+
+/**
+ * Cloud Big Data CreateProfile. This class is used for requests.
+
@zack-shoylev Good work on the code here but can you please give the Javadoc
some more love?
Look at it from the perspective of a user who knows little about big data and
nothing about jclouds. The class level Javadoc should be extra descriptive.
Please double check every single line of
+ * @return The string value.
+ */
+ public String value() {
+ return name();
+ }
+
+ @Override
+ public String toString() {
+ return value();
+ }
+
+ /**
+ * @param status The string representation of a Status
+ *
The Javadoc can always be updated in later PRs. No need to block merging on
Javadoc at this point in time.
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds-labs-openstack/pull/78#issuecomment-34887114
@@ -123,4 +127,25 @@
@Fallback(EmptySetOnNotFoundOr404.class)
ListenableFuture? extends Set? extends Role
listRolesOfUserOnTenant(@PathParam(userId) String userId,
@PathParam(tenantId) String tenantId);
+
+ /** @see UserApi#add(String, String, Boolean, String) */
@@ -123,4 +127,25 @@
@Fallback(EmptySetOnNotFoundOr404.class)
ListenableFuture? extends Set? extends Role
listRolesOfUserOnTenant(@PathParam(userId) String userId,
@PathParam(tenantId) String tenantId);
+
+ /** @see UserApi#add(String, String, Boolean, String) */
The code looks good but we really do need at least a couple of live tests
before we can accept this. When the live tests are ready I'll test them against
[DevStack with
Havana](http://blog.phymata.com/2013/12/18/devstack-havana-on-the-rackspace-cloud/).
---
Reply to this email directly or view
@trainman419 The live test is failing for me. It's running against Keystone v2
API in Havana. I'm running it with the following command in the
`apis/openstack-keystone` dir.
mvn clean test -Plive
-Dtest.openstack-keystone.endpoint=http://162.242.219.27:5000/v2.0/
All you have to do is close and reopen.
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds/pull/290#issuecomment-35414823
@sallum Any progress on these comments and test runs?
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds-labs-openstack/pull/77#issuecomment-35665271
Right.
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds-site/commit/fccd39703cad2438141dc2eea3aa0a1313306f88#commitcomment-5442288
They're expecting to configure jclouds itself, which is the overall context.
Calling it jclouds Configuration is redundant (you could prefix everything
with jclouds).
Logging should not be a part of this as it has its own page and we don't want
to spread such an important topic over 2 pages.
It's not always obvious. Good catch!
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds-site/commit/fccd39703cad2438141dc2eea3aa0a1313306f88#commitcomment-5442410
@nacx How would you feel about renaming the gettingstarted dir to just start?
I'm not crazy about compound words in URLs.
Also, how about renaming installation-guide to just install?
---
Reply to this email directly or view it on GitHub:
Let's publish this!
What's left that __absolutely__ needs to be done?
- [ ] Decide on the slogan
- [ ] Decide on the tag line
When these thing are done, let's publish it. We should publish on March 3rd or
before, in time for the next meetup.
---
Reply to this email directly or view it on
On Feb 22, 2014, at 12:58 AM, Andrew Phillips
notificati...@github.commailto:notificati...@github.com wrote:
How about something like The Java multi-cloud library? Does cloud
interfaces sound a little too abstract to others, too? We see a lot of
developers asking about cloud APIs or cloud
The Javadoc really needs some love. I fully realize that you didn't write most
of the existing Javadoc but, nonetheless, it needs to be fixed. It's crucial.
Please go through all of the Javadoc for the all Api classes and all domain
objects with a fine toothed comb.
Here's what needs to be
@nacx As you can see in b945be5 I shortened the gettingstarted dir to just
start and installation-guide to just install. I did that because i'm not
crazy about compound words in URLs and such an important URL like
http://jclouds.apache.org/start/install/ should be short. If you're not happy
I'm okay with further documentation improvements to be addressed in future PRs.
+1 to merge when the other reviewers are satisfied.
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds-labs-openstack/pull/79#issuecomment-36485023
I just noticed the Installation Guide is for 1.7.0. That should be 1.7.1.
That's it. Let's go for it!
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds-site/pull/58#issuecomment-36485189
@nacx Thought of one more. It would be nice to have if we could have the actual
blog posts under jclouds.apache.org/blog//MM/DD instead of how they current
are under jclouds.apache.org//MM/DD.
I'm in the middle of a 12 hour meeting right now so I really don't have a
chance to dig into
Wait. Why did this get merged?
The dependent code NovaTemplateOptions.configDrive() hasn't been released yet.
Unless I'm missing something, this needs to be reverted ASAP.
---
Reply to this email directly or view it on GitHub:
Please go through the imports. I count 5 that are unnecessary.
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds-examples/pull/32#issuecomment-36598318
@zack-shoylev Yes the configDrive change backport was merged but 1.7.2 hasn't
been released yet. Examples are only to be merged when the corresponding code
has been released. Examples must not depend on unreleased code. As it stands
right now, this code doesn't compile if you follow the
+
+iframe width=640 height=360
src=//www.youtube.com/embed/8nuON0zGVJI?rel=0 frameborder=0
allowfullscreen/iframe
+
+## Presentations
+
+I kicked things off with an Introduction to jclouds. I'll be giving this
presentation at ApacheCon on April 7, 2014 and wanted to take this
+---
+layout: post
+title: jclouds Meetup
+author: a href=https://twitter.com/everett_toews;Everett Toews/a
+comments: true
+---
+
+Last night we held a jclouds meetup at Cloudera offices in San Francisco. It
was a well attended meetup and there were a number of new faces along
That still wouldn't make it unique. ;)
I think just having the usual date on the post is okay for uniqueness.
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds-site/pull/62#issuecomment-36929368
Merged and deployed.
http://jclouds.apache.org/blog/2014/03/04/jclouds-meetup/
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds-site/pull/62#issuecomment-36935632
@@ -1,5 +1,7 @@
#!/bin/sh
+set -o errexit
+1 to verbose shell options
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds-site/pull/63/files#r10371334
I'm okay with this being merged as long as a follow up PR can be done right
away.
Will you have time for that this week @zack-shoylev?
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds-labs-openstack/pull/47#issuecomment-37209984
@pnavarro has a point. I'm not seeing POST /users and DELETE /users/{userId}
methods in the [Identity Service admin API
v2.0](http://api.openstack.org/api-ref-identity.html#identity-admin-v2)
However, I do see POST /users and DELETE /users/{userId} methods in the
[Identity Service API
Closed #282.
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds/pull/282
@zack-shoylev Can you please provide a minimal sample of code for how this
would work with nova-network *and* Neutron?
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds/pull/311#issuecomment-37236443
+ this.networkUuid = networkUuid;
+ return this;
+ }
+
+ /**
+ * @param portUuid The port UUID for this neutron Network.
+ * @return The builder object.
+ * @see Network#getPortUuid()
+ */
+ public Builder portUuid(String portUuid)
+ protected String networkUuid;
+ protected String portUuid;
+ protected String fixedIp;
+
+ /**
+ * @param networkUuid The UUID for the nova network or neutron subnet
to be attached.
+ * @return The builder object.
+ * @see
+ * distributed under the License is distributed on an AS IS BASIS,
+ * WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+ * See the License for the specific language governing permissions and
+ * limitations under the License.
+ */
+package
@@ -575,4 +604,14 @@ public NovaTemplateOptions configDrive(boolean
configDrive) {
this.configDrive = configDrive;
return this;
}
+
+ /**
+* @param novaNetworks The list of network declarations.
Comment on the difference between this and networks().
---
Reply to
+1
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds/pull/311#issuecomment-37341757
+1
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds/pull/303#issuecomment-37375489
Closed #290.
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds/pull/290
Thanks a lot for the update and the PR @trainman419! I'll close this as a
duplicate and we'll move forward with #303.
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds/pull/290#issuecomment-37375486
Did you run the SmokeTest with these changes?
When that passes, I'm a +1.
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds-examples/pull/35#issuecomment-37594984
@iocanel @nacx Do either of you have an opinion on this?
I know zilch about Karaf.
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds-karaf/pull/40#issuecomment-38491152
@jasdeep-hundal Have you tested this against a DevStack instance that's running
both versions of the Glance API?
Can you please share your DevStack localrc in a gist?
Can you please share the jclouds code in a gist that you ran against a DevStack
instance?
I'd like to try this in a realish
@jasdeep-hundal @nacx I made [a
comment](https://issues.apache.org/jira/browse/JCLOUDS-515?focusedCommentId=13948419page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-13948419)
that was more appropriate to be made over in the issue.
---
Reply to this email directly or
@@ -102,6 +103,27 @@ public String toString() {
}
+ public static class BlockDevice{
Are you confident that BlockDevice will only ever be used within the context of
CreateServerOptions?
Also there should be a space before the {
---
Reply to this email directly or view it on
@@ -102,6 +103,27 @@ public String toString() {
}
+ public static class BlockDevice{
+ @Named(volume_size)
+ String volumeSize = ;
+ @Named(volume_id)
+ String volumeId;
+ @Named(delete_on_termination)
+ int deleteOnTermination = 0;
+
@@ -102,6 +103,27 @@ public String toString() {
}
+ public static class BlockDevice{
My suggestion would be to get it running properly in the NovaApi with expect
tests and live tests first. That stuff really needs to be done before you can
add proper support in the ComputeService
We'll also need more Javadoc for all of the parameters that can be used to
create a BlockDevice.
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds/pull/326#issuecomment-38742092
@@ -102,6 +103,27 @@ public String toString() {
}
+ public static class BlockDevice{
Considering there's already a feature in Nova that boots from block devices
using the term block-device, I think it's more appropriate to call this object
BlockDeviceMapping.
---
Reply to this
You can merge this Pull Request by running:
git pull https://github.com/rackerlabs/jclouds-site guest-post
Or you can view, comment on it, or merge it online at:
https://github.com/jclouds/jclouds-site/pull/67
-- Commit Summary --
* Link to how to write a guest blog post
-- File
Closed #67.
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds-site/pull/67
+1
I'm okay with this. I suspect the value is set that way because of a driver in
Cinder. I could see this being the case for other Cinder driver's as well.
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds/pull/327#issuecomment-39128245
Merged to master and 1.7.x.
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds/pull/327#issuecomment-39129202
Closed #327.
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds/pull/327
Closed #36.
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds-examples/pull/36
Merged.
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds-examples/pull/36#issuecomment-39141829
Can you please put the STOPPED state back?
I realize the OpenStack doesn't return this but that state has been in jclouds
for a long time and some code is bound to depend on it. @Deprecated STOPPED and
add a comment telling users to change it to SHUTOFF.
---
Reply to this email directly or
SGTM. No translation logic is necessary. AFAICT, the actual string STOPPED
has never been returned by OpenStack.
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds/pull/334#issuecomment-39207787
@jdaggett Does this need to be updated prior to the 1.7.2 release? We should
really get this into 1.7.2.
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds/pull/237#issuecomment-39219519
Closed #309.
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds/pull/309
Closed #310.
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds/pull/310
Closed #314.
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds/pull/314
You can merge this Pull Request by running:
git pull https://github.com/rackerlabs/jclouds-examples cbs-ssd
Or you can view, comment on it, or merge it online at:
https://github.com/jclouds/jclouds-examples/pull/39
-- Commit Summary --
* Change example to use Ubuntu and SSD
-- File
Merged
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds-examples/pull/37#issuecomment-39240683
Merged.
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds-examples/pull/38#issuecomment-39240886
Closed #38.
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds-examples/pull/38
Goofed the rebase. Opening a new PR.
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds-examples/pull/39#issuecomment-39251414
You can merge this Pull Request by running:
git pull https://github.com/rackerlabs/jclouds-examples cbs-ssd-2
Or you can view, comment on it, or merge it online at:
https://github.com/jclouds/jclouds-examples/pull/41
-- Commit Summary --
* Change example to use Ubuntu and SSD
-- File
Closed #41.
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds-examples/pull/41
Merged.
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds-examples/pull/41#issuecomment-39251703
Closed #40.
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds-examples/pull/40
Merged.
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds-examples/pull/40#issuecomment-39251737
Closed #69.
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds-site/pull/69
Reopened #69.
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds-site/pull/69
Closed #69.
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds-site/pull/69
Closed #69.
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds-site/pull/69
Reopened #69.
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds-site/pull/69
Closed #69.
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds-site/pull/69
Added latest_snapshot.txt
Merged and deployed.
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds-site/pull/69#issuecomment-39371163
Needs a live test for the head() method.
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds-labs-openstack/pull/89#issuecomment-39378402
+1
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds-labs-openstack/pull/88#issuecomment-39452754
+1
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds-labs-openstack/pull/91#issuecomment-39454494
+1
Merge away when other reviewers are happy.
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds-labs-openstack/pull/85#issuecomment-39466124
@CodingFabian We're well aware that the old SwiftClient has been around for a
long time and is heavily used. I also understand it's a bit confusing. I think
the source of the confusion is that we're being very cautious (overly
cautious?) about this transition.
We're playing it cautious by
1 - 100 of 744 matches
Mail list logo
