name our new CloudServers NextGen provider!

[Adrian Cole]

Hi, all.

I finally got a login to the new Rackspace Nova install. We can now
get this into jclouds 1.5.. whoo-hoo!

Now's the fun part: what should we name the provider?

Currently, we have:

cloudfiles-us
cloudfiles-uk
cloudservers-us
cloudservers-uk

Here's the docs:
http://docs.rackspace.com/servers/api/v2/cs-devguide/content/ch_preface.html#webhelp-currentid

Should we name it...

rackspace-nova-us
or..
cloudservers-nextgen-us
or..
<your entry here>

-A

[Chris Strand]

Hey,

I think we should try and be as consistent with naming as possible. There is already "trystack-nova" and "openstack-nova" as APIs/providers so tagging "nova" on the end seems pretty reasonable. Similarly it may be best to stick with "cloudservers..." rather than moving over to "rackspace...". So my suggestion is:

cloudservers-nova-us

Does anyone know if Rackspace are going to keep their UK/US regions on separate accounts still? I would assume so, but I haven't noticed any mention of it. If they are merging them then dropping the uk/us would be wise ;)

Slightly off-topic, but do you know if the server sizes (flavors) will be the same as before?

Chris

[Adrian Cole]

Chris, makes total sense. I'll update you with results in the next hour!

-A

> --
> You received this message because you are subscribed to the Google Groups
> "jclouds" group.
> To post to this group, send email to jcl...@googlegroups.com.
> To unsubscribe from this group, send email to
> jclouds+u...@googlegroups.com.
> For more options, visit this group at
> http://groups.google.com/group/jclouds?hl=en.

[Mathieu Guillaume]

I think rackspace-nova would be clearer myself when looking through the list of providers for the open you need.

Why do we need different providers for us and uk, isn't it just a region setting which would change the endpoint?

On Wednesday, June 6, 2012 6:04:42 PM UTC+2, Adrian Cole wrote:

Chris, makes total sense.  I'll update you with results in the next hour!

-A

[Adrian Cole]

p.s. still time to decide which branding wins: offering or company!

currently, we are:

cloudservers-nova-us

we could go to:

rax-nova-us or rackspace-nova-us, and follow suit for the other
offerings they have.

FWIW, here's the keystone data on the service:

"endpoints": [{
"region": "DFW",
"tenantId": "40806637803162",
"publicURL":
"https:\/\/dfw.servers.api.rackspacecloud.com\/v2\/40806637803162",
"versionInfo":
"https:\/\/dfw.servers.api.rackspacecloud.com\/v2",
"versionList": "https:\/\/dfw.servers.api.rackspacecloud.com\/",
"versionId": "2"
}],
"name": "cloudServersOpenStack",
"type": "compute"

While the code is still in labs, I see no problem renaming, if we
thing there's a better name.

-A

> --
> You received this message because you are subscribed to the Google Groups

> "jclouds-dev" group.
> To view this discussion on the web visit
> https://groups.google.com/d/msg/jclouds-dev/-/HNRFMXnLJCYJ.
> To post to this group, send email to jclou...@googlegroups.com.

> To unsubscribe from this group, send email to

> jclouds-dev...@googlegroups.com.

> For more options, visit this group at

> http://groups.google.com/group/jclouds-dev?hl=en.

[Andrew Phillips]

Not to want to confuse things at this late stage, but how do the
proposals match up against "aws-ec2"?

That would seem to follow <vendor>-<offering> (and yes, unfortunately
also <vendor>-<API> because they're the same, but I think it was named
after the offering "first").

Would that then be "rackspace-cloudservers" where "cloudservers" is an
offering that's (currently) based on nova, but may at some point be
based on something else?

ap

> Groups "jclouds" group.
> To post to this group, send email to jcl...@googlegroups.com.

> To unsubscribe from this group, send email to

> jclouds+u...@googlegroups.com.

> For more options, visit this group at

> http://groups.google.com/group/jclouds?hl=en.
>
>



--
Andrew Phillips
qrmedia

Unless expressly stated otherwise, this message is confidential.
Access to this e-mail by anyone else is unauthorised. If you are
not an addressee, any disclosure or copying of the contents of
this e-mail or any action taken (or not taken) in reliance on it
is unauthorised and may be unlawful. If you are not an addressee,
please inform the sender immediately.

This message is confidential and may not be redistributed or
broadcast in whole or part in any form, including but not limited
to any form of internet transmission including email, usenet,
newsgroups, www, irc, icq, etc.
All liability for errors and viruses is disclaimed.

[Adrian Cole]

Not a bad idea, actually.

We could make the new rackspace providers follow that convention vs
something longer. Only thing is that in rackspace, there's no global
account namespace, hence needing the -country suffix

so, I'm totally game for:

rackspace-cloudidentity-us
rackspace-cloudfiles-us
rackspace-cloudloadbalancers-us
rackspace-cloudservers-us
...

as the replacements for the ones w/o the rackspace prefix.

Anyone opposed?
-A

[Chris Strand]

Makes sense to me!

Chris

[Adrian Cole]

done

http://code.google.com/p/jclouds/issues/detail?id=961