+import org.jclouds.openstack.nova.v2_0.NovaAsyncApi;
+import org.jclouds.openstack.nova.v2_0.compute.options.NovaTemplateOptions;
+import org.jclouds.openstack.nova.v2_0.domain.zonescoped.ZoneAndId;
+import org.jclouds.rest.RestContext;
+import org.jclouds.scriptbuilder.ScriptBuilder;
+import com.google.common.collect.Iterables;
+import com.google.common.io.Closeables;
+import com.google.inject.Module;
+
+import org.apache.commons.codec.binary.Base64;
+
+/**
+ * Create a public key in the cloud and write the private key file to the
local working directory. The public
@@ -541,5 +561,18 @@ public NovaTemplateOptions userData(byte[] userData) {
public NovaTemplateOptions diskConfig(String diskConfig) {
this.diskConfig = diskConfig;
return this;
- }
+ }
+
+ /**
+* OpenStack can be configured to write metadata to a special
@@ -290,6 +297,7 @@ public CreateServerOptions metadata(MapString, String
metadata) {
* Custom user-data can be also be supplied at launch time.
* It is retrievable by the instance and is often used for launch-time
configuration
* by instance scripts.
+* This parameter
@@ -297,6 +305,14 @@ public CreateServerOptions userData(byte[] userData) {
}
/**
+* This needs to be set to true when trying to use user data for
cloud-init.
Document the base case as well as the exceptional (cloud-init) case?
Something like: Set to true to use a config
Thanks also for the style cleanup. Why is this a bugfix, by the way? Looks like
new functionality?
Not that that matters, just out of curiosity...
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds/pull/307#issuecomment-36430950
| rackspace-autoscale-us | Provider | No |
+| rackspace-cloudfiles-uk | Provider | No |
+| rackspace-cloudfiles-us | Provider | No |
Is the production readiness status of all three providers No?
---
Reply to this email directly or view it on GitHub:
One small question. Thanks for the update, @jdaggett!
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds-labs-openstack/pull/80#issuecomment-36431024
Do we need a test to actually see if the command is correctly retried on a 408?
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds/pull/306#issuecomment-36431159
@@ -71,7 +71,7 @@
endpoints: [
{
tenantName: 40806637803162,
-publicURL: https://glance.jclouds.org:9292/v1.0;,
+publicURL: https://glance.jclouds.org:9292;,
This change on the
+import com.google.common.collect.ImmutableList;
+import com.google.common.collect.ImmutableMap;
+
+/**
+ * An image the Glance server knows about
+ *
+ * @author Ignacio Mulas
+ *
+ * @see a href= http://glance.openstack.org/glanceapi.html; /
+ * @see a href=
+ *
+ public void testUpdateWhenReponseIs404IsNull() throws Exception {
+ HttpRequest patch = HttpRequest.builder().method(PATCH)
+
.endpoint(https://glance.jclouds.org:9292/v2/images/da3b75d9-3f4a-40e7-8a2c-bfab23927dea;)
+
@jdaggett I have credentials for several Swift providers and none of them seem
to use the openstack-keystone/Keystone 2.0 functionality. If someone finds
such a provider we can add this functionality in a subsequent commit, otherwise
let's just patch known issues and move forward with the
13 matches
Mail list logo
