racker / gorax Goto Github PK

I'm not sure whether gorax can do mocks or not yet, but I'm putting in a vote to be able to do something like Fog.mock! does.

Probably the #3 command people expect a Go package to have are tests which the "go test" command can execute.

From @gecampbell:

Some multi-cloud providers use a model like:

Provider::Type::Service::Instance::Operation
(Rackspace::Compute::Servers::Server::Create)

While others use an inverted form of that:

Type::Service::Instance::Provider::Operation
(Compute::Server::Rackspace::Create) (just as an example)

They both have their pros and cons, but the differing architectures can wreak havoc on code. Nodejitsu/pkgcloud uses the second model, which effectively forces re-authentication every time you want to use a different service. These things can be overcome, but IMHO they're
difficult to sort out from competing options and are therefore better to be established up front.

These are just general examples, by the way. I'm just saying that it's important to lay the groundwork before you start getting competing opinions. Jesse may (and probably does) disagree with me. ;-)

On Tue, Jul 16, 2013 at 04:23:48PM -0700, Robert Collazo wrote:

[7/16/13 6:17:48 PM] Orion Henry: Gorax Server object from before and after shutdown. Nothing in there shows me Status or Progress https://gist.github.com/orionz/72e4383dc0d9fde5f4f1

Steps to reproduce were not provided, but from the discussion, it looks as if the Region.ServerInfoById() is not returning a progress or status.

First step is to attempt to reproduce this bug.

Case in point, from my recent work on the cloud servers API:

$ go run src/github.com/racker/gorax/v2.0/cloud/servers/i/list-images.go sfalvo apikeywashere20012                             
panic: Unsupported region or V1.0 services only

goroutine 1 [running]:
main.main()
    /Users/sfalvo/hackday/src/github.com/racker/gorax/v2.0/cloud/servers/i/list-images.go:27 +0x1db

Note that program behavior does go weird at some point, so thank goodness for error-checking throughout the program. Nonetheless, unless you remember to check for it, the errors don't obviously indicate bad credentials.

Surprisingly, these are still in use (V1.1 externally, and V1.0 internally).

Before making any further progress on this, I strongly urge going in and adding go docs to the code. Besides the "go get" issue (for which I have a PR open which I believe will fix), "go doc" is one of the most frequently used go toolchain commands used by people trying to learn how to use a module. We need good documentation.

This is primarily to support Rackspace-internal applications. Most likely, these can be represented through a custom region -> URL mapping.

GitHub lacks a kanban-style user interface for its issues. As we gain more issues and feature requests, the default UI might become somewhat cumbersome. To remedy this, I propose http://huboard.com/ as an alternative user interface. Huboard works as a value-add facade on top of GitHub offering what I believe is a more convenient user experience for both issue and milestone management.

Thoughts?