Rackspace Cloud API Documentation - Latest Comments

Re: Chapter 2. Install and Configure - Rackspace Cloud Monitoring Getting Started Guide - API v1.4

dispalt — Tue, 21 May 2013 17:34:22 -0000

Deployed

Re: 4.4. Checks - Rackspace Cloud Monitoring Developer Guide - API v1.4

Adrian Otto — Tue, 21 May 2013 15:21:48 -0000

For specifying monitoring zones, is the option monitoring_zones_poll or monitoring_zones. The raxmon-checks-create --help output seems to think it's monitoring_zones. If this is not a documentation bug, why the discrepancy?

Re: Chapter 2. Install and Configure - Rackspace Cloud Monitoring Getting Started Guide - API v1.4

Adrian Otto — Tue, 21 May 2013 14:37:24 -0000

The sudo/root/user correction does not appear to be here yet.

Re: 2.1.4. Update Server - Next Generation Cloud Servers™ Developer Guide - API v2

Diane Fleming — Mon, 20 May 2013 16:05:22 -0000

Sam, I updated the documentation so the examples appear on the same page as the API description, and I clarified that you can update the IPv4 and IPv6 addresses individually. Thanks, Diane

Re: 2.1.4. Update Server - Next Generation Cloud Servers™ Developer Guide - API v2

Diane Fleming — Mon, 20 May 2013 13:03:53 -0000

Sam,

I can change this so the examples appear inline. And yes, you can update the IPv4 and IPv6 addresses independently. Thanks, Diane

Re: 3.4.1. Attach Volume to Server - Next Generation Cloud Servers™ Developer Guide - OpenStack Compute API v2

Cat Lookabaugh — Mon, 20 May 2013 13:02:38 -0000

abhisar,

Could you provide the request you used that gave this response, please? That will help me find out why the system responded as it did. Thanks, Cat.

Re: Preface - Next Generation Cloud Servers™ Developer Guide - API v2

Cat Lookabaugh — Mon, 20 May 2013 12:53:00 -0000

I just found out that this issue has been resolved. Thanks! --cat

Re: 2.1.1. List Servers - Next Generation Cloud Servers™ Developer Guide - API v2

Cat Lookabaugh — Mon, 20 May 2013 12:52:18 -0000

Viktor, Thanks for reporting this issue. It should be resolved now! ---cat

Re: 3.4.1. List Flavors - Cloud Servers Developer Guide - API v2

Cat Lookabaugh — Mon, 20 May 2013 12:48:09 -0000

Samuel,

The 203 response tells you that the response has been cached. Hope that helps, Cat.

Re: Preface - Next Generation Cloud Servers™ Developer Guide - API v2

Cat Lookabaugh — Mon, 20 May 2013 12:43:10 -0000

Thanks for the question. I'll find out and let you know. --cat

Re: Images - Next Generation Cloud Servers™ Getting Started - API v2

Cat Lookabaugh — Mon, 20 May 2013 11:53:42 -0000

Bill and Alfred,

Thanks for the question. Let find out for you. Stay tuned! --cat

Re: 2.1.4. Update Server - Next Generation Cloud Servers™ Developer Guide - API v2

Cat Lookabaugh — Mon, 20 May 2013 09:18:03 -0000

Samuel,

Don't worry about "naggy"! Questions (good, bad, indifferent, or naggy), help us improve the documentation. And improved docs, help developers succeed, so keep asking! In the meantime, let me get you an answer! --cat

Re: 2.2.1. Get All Agents for this User - Rackspace Cloud Backup Developer Guide - API v1.0

Dominic LoBue — Fri, 17 May 2013 15:37:03 -0000

Example 2.9 contains invalid JSON. The array containing all the agent objects has no key in the root object.

Additionally I need to know what type of data is found in the TimeOfLastSuccessfulBackup field when it isn't null.

Thanks!

Dominic LoBue

Re: 2.1.4. Update Server - Next Generation Cloud Servers™ Developer Guide - API v2

Samuel Falvo II — Fri, 17 May 2013 13:13:11 -0000

I think we really need an example of how to use this API, as the description is not adequate to answer certain questions like, "What happens if I send an empty request?", or "what should the envelop be named?" (I'm guessing the container is named "server", but that's a only a guess), or lastly, "Do I have to specify all parameters, or can we only include those that differ?" etc. Finally, what happens if we provide an attribute, e.g., accessIPv4, but set its value to null? Does it unassign that field?

*EDIT* :: OH, I see, the examples are in the sub-sections linked at the top of the article. I think it would be more helpful if the examples were included inline. But now I have a new question: the example shows the request issuing an update to both accessIPv4 and accessIPv6 in a single request; but can they be set independently?

Sorry for all the naggy questions. :)

Re: http://docs-beta.rackspace.com/servers/api/v1.0/cs-devguide/content/Overview-d1e70.html

babulal — Fri, 17 May 2013 09:01:38 -0000

how can i add api key in cloud server

Re: Appendix A. Alert Triggering and Alarms - Rackspace Cloud Monitoring Developer Guide - API v1.4

dispalt — Thu, 16 May 2013 13:24:15 -0000

We'll get on some more examples in the meantime:

---
:set consistencyLevel=ALL

if (metric['code'] == "404") {
return new AlarmStatus(CRITICAL, "Page not found!");
}

----

Think of it like an outer loop of N datacenters, so in this case if you had this on 3 datacenters, all 3 would have to return 404 before the alert would trigger.

---
:set consecutiveCount=3

if (metric['code'] == "404") {
return new AlarmStatus(CRITICAL, "Page not found!");
}

----

This would be that 3 404's per datacenter would need to happen in succession before you'd get an alert, and can also weave in consistencyLevel here too.

Re: 2.1.2. Create Server - Next Generation Cloud Servers™ Developer Guide - API v2

Tomas — Thu, 16 May 2013 04:57:17 -0000

There is a networks element in xml request. I do not see this element in server.xsd defined in openstack. Where can I get official xsd files used in Rackspace?

Re: Appendix A. Alert Triggering and Alarms - Rackspace Cloud Monitoring Developer Guide - API v1.4

Ed K — Wed, 15 May 2013 20:14:55 -0000

The Alert Policies (Consistency Levels) also give no usage or syntax example.

Re: Chapter 3. Rackspace Extensions - Next Generation Cloud Servers™ Developer Guide - API v2

David W — Wed, 15 May 2013 11:37:05 -0000

Per Mike A.'s comment here [1], the bandwidth extensions have not yet been implemented as of 2013/04/12.

[1]: https://community.rackspace.co...

Re: 3.1.2.3. Server Personality - Cloud Servers Developer Guide - API v2

Diane Fleming — Tue, 14 May 2013 13:57:52 -0000

Samuel, Thanks! I'm updating the docs.

Re: http://docs-beta.rackspace.com/loadbalancers/api/v1.0/clb-devguide/content/Concepts-d1e233.html

phil — Tue, 14 May 2013 10:29:18 -0000

Timeout for HTTPS pass through is based off a 'cached' based model, where the session will be stored until the 'cache' is full.

Re: 2.6.3. Delete Image - Next Generation Cloud Servers™ Developer Guide - API v2

Thomas Duesing — Mon, 13 May 2013 18:00:18 -0000

Hi there Sam,

The computeFault errors are only returned in the rare case where we can't control the specific error being returned. I don't expect that you'll see this much (if at all) in the v2 API, although you might see it occasionally in the v1 API. A badRequest (400) error is returned when the request could not be understood because of some malformed syntax.

As for unauthorized (401) and forbidden (403), we return unauthorized when the request does not have the proper authentication credentials for their account (or the account of the resource they're trying to access). We return forbidden when the request is properly authorized, but that particular user doesn't have the proper authorization to access that resource. It's also not uncommon today for some applications to return a 404 instead of a 403, for security reasons.

-Thomas

Re: http://docs-beta.rackspace.com/loadbalancers/api/v1.0/clb-devguide/content/Concepts-d1e233.html

Phillip Couto — Mon, 13 May 2013 13:57:09 -0000

What is the timeout for Session Persistence on an HTTPS pass through load balancer?

Re: Chapter 2. Install and Configure - Rackspace Cloud Monitoring Getting Started Guide - API v1.4

dispalt — Mon, 13 May 2013 11:35:46 -0000

Good catch, we are going to deploy a fix later today, using # for root commands and $ for user commands.

Re: Chapter 2. Install and Configure - Rackspace Cloud Monitoring Getting Started Guide - API v1.4

Christian Ashby — Sat, 11 May 2013 04:40:12 -0000

Just a minor point on this doc - there's a mix of 'sudo' and non sudo commands in the debian/ubuntu portion of the document which seem wrong; either do the whole thing as root or use sudo...