Thanks for the pull request but it's release week in jclouds and that means
it's time to clean up the PR queue. This PR will be over 6 months old as of
April 1. If you intend to continue work on it, please make a comment by April
2. Otherwise it will be closed on April 3.
---
Reply to this
If no one who knows Karaf cares to merge this, I'll just go ahead and close it
on April 3. I'd rather close it unmerged than risk breaking Karaf in some weird
way I'm not prepared to deal with.
---
Reply to this email directly or view it on GitHub:
Thanks for the pull request but it's release week in jclouds and that means
it's time to clean up the PR queue. This PR will be over 6 months old as of
April 1. If you intend to continue work on it, please make a comment by April
2. Otherwise it will be closed on April 3.
---
Reply to this
Thanks for the pull request but it's release week in jclouds and that means
it's time to clean up the PR queue. This PR will be over 6 months old as of
April 1. If you intend to continue work on it, please make a comment by April
2. Otherwise it will be closed on April 3.
---
Reply to this
:+1:
Success on OpenStack Juno (with DevStack)
mvn clean test -Plive
-Dtest.openstack-nova.endpoint=http://$DEVSTACK_HOST:5000/v2.0/
-Dtest.openstack-nova.identity=demo:demo
-Dtest.openstack-nova.credential=devstack
-Dtest.openstack-nova.image-id=$IMAGE_ID
You can view, comment on, or merge this pull request online at:
https://github.com/jclouds/jclouds/pull/709
-- Commit Summary --
* Modernize the VolumeAttachmentApiLiveTest
-- File Changes --
M apis/openstack-nova/pom.xml (6)
M
Hopefully this is in reasonably good shape now. I'll be on vacation until
Monday and won't have my laptop with me. If changes need to be made, go ahead
and push on top of my commits or just cherry pick or whatever. I just don't
want to hold the release up.
---
Reply to this email directly or
@nacx Shall we pull this into 1.9.0?
It's related to the bug that broke the rc and it's just a doc change so it's
zero risk.
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds/pull/708#issuecomment-83757390
There are a couple of problems with this.
When I compile I get the warning.
$ javac -classpath
jclouds-1.9.0-rc1/lib/*:src/main/java/:src/main/resources/
src/main/java/org/jclouds/examples/rackspace/*.java
You can view, comment on, or merge this pull request online at:
https://github.com/jclouds/jclouds-examples/pull/71
-- Commit Summary --
* Updated Rackspace examples to 1.9.0
-- File Changes --
M rackspace/pom.xml (4)
M
You can view, comment on, or merge this pull request online at:
https://github.com/jclouds/jclouds/pull/708
-- Commit Summary --
* Deprecate Nova API for volumes in favour of Cinder API for volumes
-- File Changes --
M
-1 binding
During my smoke testing I discovered that this change [1] broke volume
attachments for the Nova API. Being able to attach a volume to a VM is a
crucial part of working with VMs and I consider it to be a blocker bug.
Reverting the change to that line is easy enough but testing it has
On Mar 12, 2015, at 1:42 PM, Brian Rosmaita brian.rosma...@rackspace.com
wrote:
I don't know how elaborate we want to get here, but Everett Toews had an
interesting suggestion in the openstack-api channel. It would go something
like this:
(1) User gets /x1/search endpoint from service
:+1:
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds-labs-openstack/pull/179#issuecomment-78336509
+ * Licensed to the Apache Software Foundation (ASF) under one or more
+ * contributor license agreements. See the NOTICE file distributed with
+ * this work for additional information regarding copyright ownership.
+ * The ASF licenses this file to You under the Apache License, Version 2.0
+
+import javax.inject.Named;
+import javax.ws.rs.Consumes;
+import javax.ws.rs.DELETE;
+import javax.ws.rs.POST;
+import javax.ws.rs.Path;
+import javax.ws.rs.PathParam;
+import javax.ws.rs.core.MediaType;
+
+/**
+ * interface api for nova
+ */
@@ -457,4 +457,12 @@ ImageApi getImageApiForZone(
@Delegate
Optional? extends ConsolesApi getConsolesExtensionForZone(
@EndpointParam(parser = RegionToEndpoint.class) String zone);
+
+/**
+ * Provides access to interface Type features.
+ */
+@Delegate
+
+@RequestFilters(AuthenticateRequest.class)
+@Consumes(MediaType.APPLICATION_JSON)
+@Path(/servers)
+public interface InterfaceApi {
+
+ @Named(interface:attach)
+ @POST
+ @SelectJson(interfaceAttachment)
+ @Path(/{server_id}/os-interface)
+ InterfaceAttachment
+public Setorg.jclouds.openstack.nova.v2_0.domain.FixedIp getFixedIps()
{
+return fixedIps;
+}
+
+public String getPortId() {
+return portId;
+}
+
+public String getNetId() {
+return netId;
+}
+
+public static class Builder {
+
+
+import javax.ws.rs.PathParam;
+import javax.ws.rs.core.MediaType;
+
+/**
+ * interface api for nova
+ */
+@RequestFilters(AuthenticateRequest.class)
+@Consumes(MediaType.APPLICATION_JSON)
+@Path(/servers)
+public interface InterfaceApi {
+
+ @Named(interface:attach)
+ @POST
+
+ @Named(service:list)
+ @GET
+ @ResponseParser(ParseServices.class)
+ @Transform(ServicesToPagedIterable.class)
+ @Fallback(Fallbacks.EmptyPagedIterableOnNotFoundOr404.class)
+ PagedIterableService list();
+
+ /**
+* Lists services by providing a specific set of listing
+ @Override
+ public R extends HttpRequest R bindToRequest(R request, MapString,
Object postParams) {
+ String jsonPatch = null;
+ Service service = (Service) postParams.get(service);
+
+ Json json = Guice.createInjector(new
GsonModule()).getInstance(Json.class);
+
+
+
+ @Override
+ public R extends HttpRequest R bindToRequest(R request, MapString,
Object postParams) {
+ String jsonPatch = null;
+ Service service = (Service) postParams.get(service);
+
+ Json json = Guice.createInjector(new
GsonModule()).getInstance(Json.class);
+
+* @param id the id of the service to delete
+* @return true if delete was successful, false if not
+*/
+ @Named(network:delete)
+ @DELETE
+ @Path(/{id})
+ @Fallback(Fallbacks.FalseOnNotFoundOr404.class)
+ boolean delete(@PathParam(id) String id);
+
+ /**
+*
+ @Fallback(NullOnNotFoundOr404.class)
+ @Nullable
+ Service get(@PathParam(id) String id);
+
+ /**
+* Creates a service.
+*
+* @param options the options to create the service with
+* @return a URI to the created service
+*/
+ @Named(service:create)
+
On Feb 25, 2015, at 10:47 AM, Doug Hellmann
d...@doughellmann.commailto:d...@doughellmann.com wrote:
On Wed, Feb 25, 2015, at 09:33 AM, Eugeniya Kudryashova wrote:
Hi, stackers!
As was suggested in topic [1], using an HTTP header was a good solution
for
communicating common/standardized
On Feb 16, 2015, at 1:14 PM, Joe Topjian j...@topjian.net wrote:
Hello,
When using the APIs directly to manage instances, which API is preferable for
associating and disassociating Floating IPs?
Nova has the os-floating-ips extension which works for nova-network based
environments and,
On Feb 12, 2015, at 9:29 AM, Ryan Brown
rybr...@redhat.commailto:rybr...@redhat.com wrote:
On 02/10/2015 08:01 AM, Everett Toews wrote:
On Feb 9, 2015, at 9:28 PM, Jay Pipes
jaypi...@gmail.commailto:jaypi...@gmail.com
mailto:jaypi...@gmail.com wrote:
On 02/02/2015 02:51 PM, Stefano Maffulli
I’ll be missing the next API WG meeting [1] as I’m in some all day training.
Someone else will have to #startmeeting api wg
Cheers,
Everett
[1] https://wiki.openstack.org/wiki/Meetings/API-WG
__
OpenStack Development
[
https://issues.apache.org/jira/browse/JCLOUDS-819?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14317160#comment-14317160
]
Everett Toews commented on JCLOUDS-819:
---
Me too. As long as it gets well documented
On Feb 9, 2015, at 9:28 PM, Jay Pipes
jaypi...@gmail.commailto:jaypi...@gmail.com wrote:
On 02/02/2015 02:51 PM, Stefano Maffulli wrote:
On Fri, 2015-01-30 at 23:05 +, Everett Toews wrote:
To converge the OpenStack APIs to a consistent and pragmatic RESTful
design by creating guidelines
Everett Toews created JCLOUDS-819:
-
Summary: Allow prepending a custom user agent
Key: JCLOUDS-819
URL: https://issues.apache.org/jira/browse/JCLOUDS-819
Project: jclouds
Issue Type
, Everett Toews wrote:
It was suggested that the API WG use the openstack-specs [1] and/or
the api-wg [2] repo to publish its guidelines. We’ve already arrived
at the consensus that we should only use 1 repo [3]. So the purpose of
this thread is to decide...
Should the API WG use the openstack-specs repo
On Feb 3, 2015, at 10:07 AM, michael mccune m...@redhat.com wrote:
On 02/02/2015 08:58 AM, Chris Dent wrote:
This is pretty good but I think it leaves unresolved the biggest
question I've had about this process: What's so great about
converging the APIs? If we can narrow or clarify that
On Feb 2, 2015, at 7:24 PM, Sean Dague s...@dague.netmailto:s...@dague.net
wrote:
On 02/02/2015 05:35 PM, Jay Pipes wrote:
On 01/29/2015 12:41 PM, Sean Dague wrote:
Correct. This actually came up at the Nova mid cycle in a side
conversation with Ironic and Neutron folks.
HTTP error codes are
On Jan 29, 2015, at 7:34 PM, Rochelle Grober
rochelle.gro...@huawei.commailto:rochelle.gro...@huawei.com wrote:
Hi folks!
Changed the tags a bit because this is a discussion for all projects and
dovetails with logging rationalization/standards/
At the Paris summit, we had a number of session
Hi All,
Something we in the API WG keep bumping into are misconceptions around what our
mission really is. There’s general agreement in the WG about our mission but we
haven’t formalized it.
It’s really highlighted the need for a mission statement/elevator pitch/mantra
that we can repeat to
On Jan 30, 2015, at 4:57 PM, Everett Toews everett.to...@rackspace.com wrote:
Hi All,
Something we in the API WG keep bumping into are misconceptions around what
our mission really is. There’s general agreement in the WG about our mission
but we haven’t formalized it.
It’s really
On Jan 29, 2015, at 11:41 AM, Sean Dague s...@dague.net wrote:
Correct. This actually came up at the Nova mid cycle in a side
conversation with Ironic and Neutron folks.
HTTP error codes are not sufficiently granular to describe what happens
when a REST service goes wrong, especially if it
The suggestion of whether to use 1 or 2 repos for the API WG surfaced on the ML
here [1]. That thread then morphed into a discussion on whether to use 1 or 2
repos. I believe it’s correct to say that the consensus on that thread was for
1 repo.
We also discussed the question of 1 or 2 repos
On Jan 30, 2015, at 3:17 PM, Jesse Keating j...@bluebox.net wrote:
On 1/30/15 1:08 PM, Everett Toews wrote:
Project: A client dealing with the API already knows what project
(service) they’re dealing with. Including this in an API error message
would be redundant. That’s not necessarily so
It was suggested that the API WG use the openstack-specs [1] and/or the api-wg
[2] repo to publish its guidelines. We’ve already arrived at the consensus that
we should only use 1 repo [3]. So the purpose of this thread is to decide...
Should the API WG use the openstack-specs repo or the
I just submitted an Introduction to Apache jclouds talk to ApacheCon. I didn’t
see a way to include multiple people in the submission but if you want to
co-present, I’m all for it. If you come up with something new and do that
instead, that works too. :)
Cheers,
Everett
On Jan 23, 2015, at
On Jan 18, 2015, at 9:25 PM, Jay Pipes jaypi...@gmail.com wrote:
On 01/13/2015 07:41 AM, Sean Dague wrote:
On 01/09/2015 04:17 PM, Everett Toews wrote:
One thing that has come up in the past couple of API WG meetings
[1] is just how useful a proper API definition would be for the
OpenStack
A couple of important topics came up as a result of attending the Cross Project
Meeting. I’ve added both to the agenda for the next meeting on Thursday
2015/01/29 at 16:00 UTC.
https://wiki.openstack.org/wiki/Meetings/API-WG#Agenda
The first is the suggestion from ttx to consider using
I just submitted an Introduction to Apache jclouds talk to ApacheCon. I didn’t
see a way to include multiple people in the submission but if you want to
co-present, I’m all for it. If you come up with something new and do that
instead, that works too. :)
Cheers,
Everett
On Jan 23, 2015, at
Reopened #152.
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds-site/pull/152#event-224733887
Closed #152.
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds-site/pull/152#event-224737596
Reopened #152.
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds-site/pull/152#event-224737646
You can view, comment on, or merge this pull request online at:
https://github.com/jclouds/jclouds-site/pull/152
-- Commit Summary --
* Encourage users to join the jclouds community
-- File Changes --
M guides/rackspace.md (2)
-- Patch Links --
Closed #152.
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds-site/pull/152#event-224733857
Closed #152.
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds-site/pull/152#event-224789716
Merged and published.
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds-site/pull/152#issuecomment-71502957
[
https://issues.apache.org/jira/browse/JCLOUDS-655?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Everett Toews closed JCLOUDS-655.
-
Resolution: Fixed
Fix Version/s: 1.9.0
1.8.2
Merged to
[1.8.x](http://git-wip-us.apache.org/repos/asf/jclouds/commit/f708d203) and
[master](http://git-wip-us.apache.org/repos/asf/jclouds/commit/73600c81)
Nice work @monitorjbl! This was a tough one but you stuck with it. Can we give
you a shout out on Twitter? If so, what's your Twitter
Closed #626.
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds/pull/626#event-224901404
Everett Toews created JCLOUDS-810:
-
Summary: Example of jclouds in a JEE container
Key: JCLOUDS-810
URL: https://issues.apache.org/jira/browse/JCLOUDS-810
Project: jclouds
Issue Type: Bug
[
https://issues.apache.org/jira/browse/JCLOUDS-219?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Everett Toews reassigned JCLOUDS-219:
-
Assignee: (was: Everett Toews)
Change disk config attribute in Nova to use an Enum
[
https://issues.apache.org/jira/browse/JCLOUDS-454?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Everett Toews reassigned JCLOUDS-454:
-
Assignee: (was: Everett Toews)
NovaComputeService should query extensions to see
[Checkstyle
violation](https://jclouds.ci.cloudbees.com/job/jclouds-pull-requests/1527/org.apache.jclouds.api$openstack-nova/violations/file/src/test/java/org/jclouds/openstack/nova/v2_0/config/ImageAdapterTest.java/)
Unused import in `ImageAdapterTest.java`
---
Reply to this email directly or
On Dec 12, 2014, at 4:56 PM, Andrew Phillips andr...@apache.org wrote:
So my main appeal to us all at this point is *be vocal*. If you are a jclouds
user, tell us what you want to see added to or improved about jclouds. If you
are a jclouds dev or PMC member, reach out to all the jclouds
Merged
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds-examples/pull/68#issuecomment-70881777
Merged.
`rackspace-cloudnetworks-us` wasn't part of the 1.8.1 release so it will have
to wait. I don't want this to be interactive so I'll pass on the captcha for
now. I think naming it DeleteAll makes it pretty explicit what it does.
---
Reply to this email directly or view it on GitHub:
Closed #70.
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds-examples/pull/70#event-222473088
I’d like to announce that a new API guideline has been accepted for Collection
Resources.
http://specs.openstack.org/openstack/api-wg/guidelines/representation_structure.html#collection-resources
JSON request and response representations for collection resources should be
an object that
On Jan 9, 2015, at 8:15 AM, Jay Pipes jaypi...@gmail.com wrote:
Adding [api] topic.
On 01/08/2015 07:47 PM, Kevin Benton wrote:
Is there another openstack service that allows this so we can make the
API consistent between the two when this change is made?
Kevin, thank you VERY much for
[
https://issues.apache.org/jira/browse/JCLOUDS-807?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Everett Toews closed JCLOUDS-807.
-
Resolution: Duplicate
We're getting close to a fix!
https://github.com/jclouds/jclouds/pull/626
@@ -85,6 +86,7 @@ public static Status fromValue(String v) {
protected int minDisk;
protected int minRam;
protected Resource server;
+ protected ListBlockDeviceMapping blockDeviceMapping;
This should be initialized with `ImmutableList.of()` (unless there's a really
@@ -221,6 +229,7 @@ protected Image(String id, @Nullable String name,
java.util.SetLink links, @Nu
this.progress = progress;
this.minDisk = minDisk;
this.minRam = minRam;
+ this.blockDeviceMapping = blockDeviceMapping;
Init the same as `metadata`
---
Reply to
You can view, comment on, or merge this pull request online at:
https://github.com/jclouds/jclouds-examples/pull/70
-- Commit Summary --
* Delete all resources in all regions of an account
-- File Changes --
A rackspace/src/main/java/org/jclouds/examples/rackspace/DeleteAll.java
+api.getVirtualGuestApi();
+api.getDatacenterApi();
+api.getSoftwareDescriptionApi();
+api.getVirtualGuestBlockDeviceTemplateGroupApi();
+api.getAccountApi();
+
+// Be sure to close the context when done
+computeServiceContext.close();
+{% endhighlight %}
+
+## SoftLayer Object Storage
@monitorjbl Sorry I haven't been able to have a look at this. I've been
fighting the flu.
@nacx Can you help with the unit test of just the adapter? If not, I can look
at it later this week or next.
---
Reply to this email directly or view it on GitHub:
Have a look at how the Context is built in the OpenStack Getting Started Guide
http://jclouds.apache.org/guides/openstack/
That will steer you clear of those deprecations.
Thanks,
Everett
On Jan 9, 2015, at 4:53 AM, Karim
karim.es...@gmail.commailto:karim.es...@gmail.com wrote:
Hello,
I'm
One thing that has come up in the past couple of API WG meetings [1] is just
how useful a proper API definition would be for the OpenStack projects.
By API definition I mean a format like Swagger, RAML, API Blueprint, etc. These
formats are a machine/human readable way of describing your API.
You can merge this Pull Request by running:
git pull https://github.com/rackerlabs/jclouds-labs-openstack fix-test-props
Or you can view, comment on it, or merge it online at:
https://github.com/jclouds/jclouds-labs-openstack/pull/175
-- Commit Summary --
* Fix test properties
-- File
Just trying something out.
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds-labs-openstack/pull/175#issuecomment-69256482
Closed #175.
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds-labs-openstack/pull/175#event-216189025
+api.getVirtualGuestApi();
+api.getDatacenterApi();
+api.getSoftwareDescriptionApi();
+api.getVirtualGuestBlockDeviceTemplateGroupApi();
+api.getAccountApi();
+
+// Be sure to close the context when done
+computeServiceContext.close();
+{% endhighlight %}
+
+## SoftLayer Object Storage
Can you add that test code as a commit so we can see it? (don't squash it)
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds/pull/626#issuecomment-69248945
On Jan 6, 2015, at 12:46 PM, Kevin L. Mitchell kevin.mitch...@rackspace.com
wrote:
On Tue, 2015-01-06 at 12:19 -0600, Anne Gentle wrote:
I'm all for consistency. Sounds like a great case for the API Working
Group to document. You can propose a patch describing the way we want
sorting to
Closed #57.
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds-examples/pull/57#event-210986066
:+1:
And note that
[BlockDeviceMapping.java](https://github.com/jclouds/jclouds/blob/master/apis/openstack-nova/src/main/java/org/jclouds/openstack/nova/v2_0/domain/BlockDeviceMapping.java)
already exists.
---
Reply to this email directly or view it on GitHub:
I thought the analysis on service catalogs might attract some attention. ;)
More inline
On Dec 19, 2014, at 10:17 AM, Amit Gandhi amit.gan...@rackspace.com wrote:
How do the allocation of the service types in the service catalog get created.
AFAICT it’s arbitrary. Provider picks the string
Hi All,
At the recent API WG meeting [1] we discussed the need for more analysis of
current API design.
We need to get better at doing analysis of current API design as part of our
guideline proposals. We are not creating these guidelines in a vacuum. The
current design should be analyzed and
You can merge this Pull Request by running:
git pull https://github.com/rackerlabs/jclouds-examples 1-8-1
Or you can view, comment on it, or merge it online at:
https://github.com/jclouds/jclouds-examples/pull/68
-- Commit Summary --
* Update examples to 1.8.1
-- File Changes --
If you’re only using the example from the website, there should be no trace of
jclouds 1.5.7 in your dependency tree. Can you please share your pom.xml file
with us?
It should exactly match this one [1].
Thanks,
Everett
[1] http://jclouds.apache.org/guides/openstack/#pom
On Dec 16, 2014, at
})
protected ServerInternalWithoutImage(String id, @Nullable String
name, java.util.SetLink links, @Nullable String uuid, String tenantId,
- String userId, Date updated, Date created,
@Nullable String hostId, @Nullable String accessIPv4,
@@ -56,9 +61,10 @@
@Singleton
public MapType, Object provideCustomAdapterBindings() {
return ImmutableMap.Type, Objectof(
-HostResourceUsage.class, new HostResourceUsageAdapter(),
-ServerWithSecurityGroups.class, new
ServerWithSecurityGroupsAdapter(),
super(id, name, links, uuid, tenantId, userId, updated, created,
hostId, accessIPv4, accessIPv6, status, null, flavor, keyName, configDrive,
addresses, metadata, extendedStatus, extendedAttributes, diskConfig);
}
}
}
+
+ @Singleton
+ public static
+ @Override
+ public Image deserialize(JsonElement jsonElement, Type type,
JsonDeserializationContext context)
+ throws JsonParseException {
+ JsonObject json = jsonElement.getAsJsonObject();
+
+ MapString, Object complexMetatdata = null;
+
@@ -271,6 +282,10 @@ public Resource getServer() {
return this.metadata;
}
+ public MapString, Object getComplexMetadata() {
Both `getComplexMetadata()` and `getMetadata()` will need to be documented very
well. Please explain why each one exists and that `metadata` will
+ }
+],
+checksum: 32c08d302f9206668030d47789b77858,
+min_ram: 1,
+disk_format: qcow2,
+image_name: Ubuntu LTS 14.04,
+bdm_v2: True,
+image_id: cfefefc1-eba2-4b1e-9b07-a8c74a872d65,
+root_device_name: /dev/vda,
+
I think this is a reasonable way to approach this and not break backwards
compatibility or force the user to always deal with `MapString, Object` when
the more common case is `MapString, String`
@nacx @inbarsto Since you were kind enough to reply to the [Dealing with
different JSON value types
+ /**
+ * @param capabilities The capabilities of this Stack.
+ * @return The builder object.
+ * @see Stack#getCapabilities()
+ */
+ public T capabilities(SetString capabilities) {
+ this.capabilities = capabilities;
+ return self();
+
+
+ try {
+ HeatApi heatApi = api(server.getUrl(/).toString(),
openstack-heat, overrides);
+ StackApi api = heatApi.getStackApi(RegionOne);
+
+ AutoStack stack = api.get(simple_stack,
3095aefc-09fb-4bc7-b1f0-f21a304e864c);
+
return props;
}
+ @Override
+ @BeforeClass(groups = live)
+ public void setup() {
+ super.setup();
+ String providedRegion = System.getProperty(test. +
LocationConstants.PROPERTY_REGION);
+ if (providedRegion != null) {
+regions =
Nothing happening here. It's long past time to close this PR. I'll leave it to
@inbarsto to choose a path forward. Considering the [Api/Provider Writing
Practices](https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=49578594)
a fresh start may be in order.
---
Reply to this email
[
https://issues.apache.org/jira/browse/JCLOUDS-655?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Everett Toews updated JCLOUDS-655:
--
Assignee: Taylor Jones
com.google.gson.JsonSyntaxException on trying to start a new instance
})
protected ServerInternalWithoutImage(String id, @Nullable String
name, java.util.SetLink links, @Nullable String uuid, String tenantId,
- String userId, Date updated, Date created,
@Nullable String hostId, @Nullable String accessIPv4,
@@ -271,6 +282,10 @@ public Resource getServer() {
return this.metadata;
}
+ public MapString, Object getComplexMetadata() {
Put the Javadoc on both `getComplexMetadata()` and `getMetadata()`. Don't worry
about the lack of Javadoc elsewhere in this class at the moment. It's
101 - 200 of 1710 matches
Mail list logo
