HNHacker News
TopNewBestAskShowJobs

jnoller

8,376 karma · joined October 9, 2008

http://jessenoller.com jnoller@gmail.com @jessenoller http://www.hackernewsers.com/users/jnoller.html
submissionscomments
jnoller··on Rackspace Launches Developer Discount
Sent to the product team
jnoller··on Rackspace Launches Developer Discount
We don't have data centers in Canada, but Chicago may have recently been annexed to Canada. So, if you are fine with using a US based cloud account, just sign up and use the Chicago region/datacenter.

You, and all of Canada are welcome!

jnoller··on Rackspace Launches Developer Discount
Here is a benchmark from the Rackspace site on SSD performance via Cloud Block Storage: (PDF) http://c744563d32d0468a7cf1-2fe04d8054667ffada6c4002813eccf0...
jnoller··on Rackspace Launches Developer Discount
Yes. This is an extremely high priority
jnoller··on Rackspace Launches Developer Discount
We do not have a plan to terminate this discount that anyone has told me. In fact I would like to keep it for the foreseeable future.
jnoller··on Rackspace Launches Developer Discount
I'm going to apologize - but I can not comment future-looking/roadmap items like this. I can say I would like it - but beyond that not much else.
jnoller··on Rackspace Launches Developer Discount
We do not have an end date for this discount right now. Hopefully we can just continually improve it.
jnoller··on Rackspace Launches Developer Discount
I agree; in a perfect world (and the one I'd like to see) we would be able to apply this to existing accounts. Given internal limitations though, it's not as simple as it should be. Let me talk to customer service and see if we can do this if a user contacts us.
jnoller··on Rackspace Launches Developer Discount
Just like kordless said: I concur, this is not good. I'd be just as annoyed as you, so please accept my personal apology. Kord has already filed a tracker issue for this, and I am emailing this straight to the internal teams that control signup.

Again: I'm sorry

jnoller··on Rackspace Launches Developer Discount
Like kordless said: Completely and totally agreed. Tutorials and best practices are critical and it is probably one of my top to-do items.
jnoller··on Rackspace Launches Developer Discount
Nice! This is excellent. We're freely hosting many OSS projects - the more FOSS/.edu/dev discounts, free tiers and benefits we can get out to the world, the better
jnoller··on Rackspace Launches Developer Discount
Checking with the product team right now.
jnoller··on Rackspace Launches Developer Discount
http://www.rackspace.com/cloud/servers/ http://www.rackspace.com/cloud/files/pricing/
jnoller··on Rackspace Launches Developer Discount
Got it - escalating to the product teams. As for the final one:

> Why does Rackspace's API use "Keystone" auth instead of just API tokens or Oauth like everyone else? We would have to create a special Rackspace auth system just to support Rackspace with our service. Everyone else in the world uses Oauth or API tokens, or passwords which works a lot like API tokens, but Rackspace uses this crazy system nobody else in the world uses that requires refreshing tokens.

Actually, Token-based auth is quite common, as well as token refreshes. This is pretty standard for cloud provider APIs for compute, storage, etc. Amazon, Rackspace, Google and others all use the account -> API Key model. This actually uses API tokens which is the industry and OpenStack standard.

For OAuth - we've discussed this, there is a cloud partner in the cloud tools market place which does this. This isn't the first time I've gotten this request, so I'm going to pass it to the product teams as well.

jnoller··on Rackspace Launches Developer Discount
Yes, we're actually very cost competitive for VMs - and cloud files includes a global CDN. I'm really, really, really happy this put us back on your radar. If you run into issues or have questions - jesse.noller@rackspace.com - my door is always open.
jnoller··on Rackspace Launches Developer Discount
I apologize; new accounts only - we can not back date or apply to existing. Limitations! :(
jnoller··on Rackspace Launches Developer Discount
Cloud Sites is a specific product: you want to use "Cloud Account" - sorry I couldn't strip out the other options when signing up. There's some history / time there that applies.
jnoller··on Rackspace Launches Developer Discount
It's not: I just pushed a change to master and I am waiting on the cache to invalidation. Anyone anywhere can use either the UK or US clouds. I made a mistake saying "I am in..."
jnoller··on Rackspace Launches Developer Discount
And like always: I'm around to answer questions.
jnoller··on Gophercloud: A Multi-cloud Software Development Kit for Go
Will pass to product management. Could be possible.
jnoller··on Gophercloud: A Multi-cloud Software Development Kit for Go
We wanted to do a quick introduction to Go ideas so that those of us "not in the know" would know the why, what and additional context.
jnoller··on Gophercloud: A Multi-cloud Software Development Kit for Go
Thank you for the feedback - there is definitely a risk of lowest common denominator, and some truth that a generalized toolkit won't be as "good" as a domain-specific tool. For openstack specifically there's goose/juju right now.

We (rackspace) have had great success with Fog, jclouds, pkgcloud, libcloud, and other multi-cloud toolkits. For openstack / Rackspace cloud we also have php-opencloud, openstack.net and pyrax (which uses the python-XXXX clients from openstack core).

It definitely is a fine line to walk; a good abstraction though means that you can use the most common features easily and float through providers, but you have access to the advanced features if you need or want them.

Commonly those advanced features (on a provider level) mean a greater level of vendor lock-in which is why they may not make sense to expose in the higher level abstraction.

jnoller··on Gophercloud: A Multi-cloud Software Development Kit for Go
I shot this to Samuel the current dev lead - thank you!
jnoller··on Gophercloud: A Multi-cloud Software Development Kit for Go
Thanks! I'll take care of it or file an issue. As for GPL vs LGPL - I am aware, but given the goals of not focusing on openstack solely and also that all of our other work is Apache 2 for maximum flexibility and freedom, we currently prefer this approach.

The LCD issue is being resolve in libcloud - we have multiple FT devs working on it right now, and does not come up as an issue with Fog, jclouds, or pkgcloud. It's possible to make an abstraction that is simple enough to start but powerful enough to access the advanced features of each individual cloud host.

I hope users and consumers will keep us honest - as we said in the post, our interest is pretty much no lock-in on an API level (hence: openstack) and no lock-in on the code level. We really want to make tools that allow our users and others to fluidly move between hosts.

jnoller··on Gophercloud: A Multi-cloud Software Development Kit for Go
No, there is no caveat; we're working on openstack first, then rackspace, then others. It's just started out obviously. We examined goose/juju and preferred to approach this via the Apache 2 license ala all of the other tooling/SDKs out there we (Rackspace) support and assign developers to.

Yes, it is currently focused on openstack clouds, but the goal is to reach parity with Fog (ruby), jclouds (Java), Libcloud (Python), pkgcloud (node.js), and so on.

The focus is a series of clean abstractions for users to be able to build tools and programs which can talk across any cloud provider easily using a common set of names / abstractions.

jnoller··on GCloud – Go Packages for Cloud Services
Fwiw, rackspace is funding/working on a library just for this - multi cloud interface, OpenStack and rackspace cloud support, and AWS and other welcome.

We have it on github already: https://github.com/rackspace/gophercloud

jnoller··on AMA: Jesse Noller
So, I spoke to the product team and they told me that this is still in the pipeline and part of the plan. The team is pretty heads down focused on scalability, performance and other key items - so yes, this is still coming, and hopefully sooner rather than later.

Sorry I can't give you a specific date, but I don't want to set unreasonable expectations.

jnoller··on AMA: Jesse Noller
I've reached out to the Cloud Servers team and will post what I find out.
jnoller··on AMA: Jesse Noller
You haven't lost the plot.

Sooner or later in any programmers life you're going to reach a point where it seems / feels easier to start with less. You start reaching for tools that feel more like the unix way - they do one thing very well, and allow you greater compose-ability and flexibility.

On the other hand, I have to fight this urge: because much like Python - the language that comes with community included, you sort of don't want to be the one person using something, or understanding what you did.

Your best bet is to find something that provides the simplicity you find yourself looking for, but that still has the greater community support you and others can lean on, and existing domain knowledge.

For example - let's say you want to go with a micro framework: look at bottle, web.py and my favorite: Flask. The nice thing with Flask for example is it stays out of my way, still has a ton of plugins (so, for example, I don't have to write my own damned Oauth system) and a vibrant community.

That ache in your gut is looking for things that get rid of boilerplate and get out of your way to just write awesome stuff. If you don't feel like the bigger frameworks like django (which I love for larger projects) get out of your way enough: don't drop down to raw WSGI, go spend some time with something smaller!

jnoller··on AMA: Jesse Noller
So, I won't repeat what Ed said - the tl;dr is that pyrax should support Python 2.6, and your point about dedicated servers only supporting CentOS6 is something we need to consider.

As for the rest - yes. The communications and deprecation of python-cloudfiles was poorly handled. The crux of what happened is that python-cloudfiles was a part time project and ultimately superseded by the python-swiftclient work in OpenStack.

We have requirements that for an SDK / tool to be officially supported, we have dedicated full time headcount to support and maintain the package(s) - the decision was made to proceed with Pyrax which leverages python-swiftclient and other openstack tools under the covers as the official Python SDK for Rackspace.

This was not made clear to the users, or the community by any parties involved, and for that I apologize. We're continually working on better upstream communication/collaboration and this series of events (you're not the first to give us this feedback) has made us take a very hard look internally on how this is all managed and communicated.

The good news is that Ed - our current Pyrax SDK maintainer is full time and dedicated to working with you and others on pyrax - this means the Python 2.6 support will be taken care of.

Tangentially: Yes - python-novaclient and python-swiftclient from OpenStack will work on Rackspace Cloud - you can actually look at the Pyrax source to see that it uses these under the covers. Rackspace runs OpenStack with as few differences as possible so OpenStack tools should work great on Rackspace.

So, in short: I apologize. The communications and management of this to upstream (the community) were poor, and we are renewing all of our efforts to focus on upstream first.

Jesse

← PreviousPage 4 of 21Next →