Merge lp:~dooferlad/linaro-ci-dashboard/add_api_tastypie into lp:linaro-ci-dashboard

[James Tunnicliffe]

Adds a framework for a simple RESTful API using Tastypie (http://tastypieapi.org/). This is a new requirement, listed in the README.

The current API is very limited. The intent of this MP is to get some feedback on if this is a sensible way to implement the API. Future merges will fill it out.

If you are running Ubuntu 12.04 you can run the application, just not unit test the API because it relies on LiveServerTestCase, which was introduced with Django 1.4. To work around this, instructions are provided for setting up an isolated Python environment using virtualenvwrapper are included in the README.

[lp:~dooferlad/linaro-ci-dashboard/add_api_tastypie]

77. By James Tunnicliffe on 2013-02-04

Added / updated copyright notices.

[Stevan Radaković (stevanr)]

Hey James,

Nice work rly.. I've managed to run everything pretty much smooth, tests worked, and the code looks good as well, disregarding the problem with django version for unit testing, this is really unfortunate dependency :/

First thing that kinda bothers me is that we require 'v1/' in API links. I read the tastypie docs a bit but couldn't get quick answer if this is easy to remove or not.. If there's any special reason to keep it tho, I'd like to hear it.

Second thing is just a minor code block in tests that stung me in the eye, but nothing special:

280 + # One loop is of type AndroidLoop, the other ModelBase. Find which is
281 + # which.
282 + if json[0]['type'] == 'AndroidLoop':
283 + android_loop_index = 0
284 + base_loop_index = 1
285 + else:
286 + android_loop_index = 1
287 + base_loop_index = 0
288 +
289 + # Now test the contents of the loop data
290 + self.assertEqual(json[android_loop_index]['name'],
291 + self.android_loop.name)
292 + self.assertEqual(json[base_loop_index]['name'],
293 + self.loop.name)

Why not use sets here, like

api_test_names = {json[0]['name'], json[1]['name']}
test_names = {self.android_loop.name, self.loop.name}
self.assertEqual(api_test_names, test_names)

[Milo Casagrande (milo)]

Hello James!

Nice work here! :-)

On Fri, Feb 1, 2013 at 12:57 PM, James Tunnicliffe
<email address hidden> wrote:
>
> The current API is very limited. The intent of this MP is to get some feedback on if this is a sensible way to implement the API. Future merges will fill it out.

So, some feedback.
Keep in mind that I never created RESTful API with Python nor Django
(only worked with Java on this front).

Overall, it looks a good Django-nic way of creating RESTful API
without decorators. I hove no idea of the other frameworks around, but
docs for this are well written and seems also up-to-date (a big plus I
would say).

> If you are running Ubuntu 12.04 you can run the application, just not unit test the API because it relies on LiveServerTestCase, which was introduced with Django 1.4. To work around this, instructions are provided for setting up an isolated Python environment using virtualenvwrapper are included in the README.

Regarding this, since we will deploy or install this on a 12.04
server, how are we going to handle/maintain it?
Using virtualenv? Backport? Default backport channel for 12.04 does
not have any newest version of Django available... That is something
we need to keep in mind, because I think we will be using LTS versions
(and next one will be out in 1 year time).

Anyway, using virtualenvwrapper everything worked perfectly, and tests run fine.

> === added file 'dashboard/frontend/api/urls.py'
> --- dashboard/frontend/api/urls.py 1970-01-01 00:00:00 +0000
> +++ dashboard/frontend/api/urls.py 2013-02-01 11:56:24 +0000
> @@ -0,0 +1,13 @@
> +from django.conf.urls.defaults import patterns, include
> +from dashboard.frontend.api.api import *
> +from tastypie.api import Api
> +
> +v1_api = Api(api_name='v1')
> +
> +# Register new resources here (probably defined in api.py)
> +v1_api.register(LoginTestResource())
> +v1_api.register(LoopsResource())
> +
> +urlpatterns = patterns('',
> + (r'^api/', include(v1_api.urls)),
> +)

I have to say I'm more in favor of using a normal numbering scheme
(like "1.0") for API versions (at least for stable ones, maybe a "dev"
one for bleeding-edge stuff).
I guess that if we need to change API version and bump the number, it
would be as easy as this piece of code, as long as Djano does not
complain for the double entry with the same search-pattern (r'^api/').
Did you try if it works? Can't remember out of my mind now...

Ciao!

--
Milo Casagrande | Infrastructure Team
Linaro.org <www.linaro.org> │ Open source software for ARM SoCs

[James Tunnicliffe (dooferlad)]

On 4 February 2013 16:09, Stevan Radaković <email address hidden> wrote:
> Hey James,
>
> Nice work rly.. I've managed to run everything pretty much smooth, tests worked, and the code looks good as well, disregarding the problem with django version for unit testing, this is really unfortunate dependency :/
>
> First thing that kinda bothers me is that we require 'v1/' in API links.
> I read the tastypie docs a bit but couldn't get quick answer if this is
> easy to remove or not.. If there's any special reason to keep it tho,
> I'd like to hear it.

I haven't looked into that much, but versioning is probably a good
idea. so incompatible changes can be rolled out without breaking old
clients (well, we will phase out old clients eventually). I don't care
what the version string is though. I like Milo's comment about just
having a number or "dev". My vote is for major.minor version as stable
API versions and dev, which will always point to the latest API.

> Second thing is just a minor code block in tests that stung me in the eye, but nothing special:
>
> 280 + # One loop is of type AndroidLoop, the other ModelBase. Find which is
> 281 + # which.
> 282 + if json[0]['type'] == 'AndroidLoop':
> 283 + android_loop_index = 0
> 284 + base_loop_index = 1
> 285 + else:
> 286 + android_loop_index = 1
> 287 + base_loop_index = 0
> 288 +
> 289 + # Now test the contents of the loop data
> 290 + self.assertEqual(json[android_loop_index]['name'],
> 291 + self.android_loop.name)
> 292 + self.assertEqual(json[base_loop_index]['name'],
> 293 + self.loop.name)
>
> Why not use sets here, like
>
> api_test_names = {json[0]['name'], json[1]['name']}
> test_names = {self.android_loop.name, self.loop.name}
> self.assertEqual(api_test_names, test_names)

I like your version. I clearly ran out of Python at that point :-)

Thanks,

--
James Tunnicliffe

[James Tunnicliffe (dooferlad)]

On 4 February 2013 16:31, Milo Casagrande <email address hidden> wrote:
> Hello James!
>
> Nice work here! :-)
>
> On Fri, Feb 1, 2013 at 12:57 PM, James Tunnicliffe
> <email address hidden> wrote:
>>
>> The current API is very limited. The intent of this MP is to get some feedback on if this is a sensible way to implement the API. Future merges will fill it out.
>
> So, some feedback.
> Keep in mind that I never created RESTful API with Python nor Django
> (only worked with Java on this front).
>
> Overall, it looks a good Django-nic way of creating RESTful API
> without decorators. I hove no idea of the other frameworks around, but
> docs for this are well written and seems also up-to-date (a big plus I
> would say).
>
>> If you are running Ubuntu 12.04 you can run the application, just not unit test the API because it relies on LiveServerTestCase, which was introduced with Django 1.4. To work around this, instructions are provided for setting up an isolated Python environment using virtualenvwrapper are included in the README.
>
> Regarding this, since we will deploy or install this on a 12.04
> server, how are we going to handle/maintain it?
> Using virtualenv? Backport? Default backport channel for 12.04 does
> not have any newest version of Django available... That is something
> we need to keep in mind, because I think we will be using LTS versions
> (and next one will be out in 1 year time).

It is only the testing that requires Django 1.4, not running the API
library. Using LiveServerTestCase instead of TestCase starts up a
server per-test that the test can interact with. This was introducted
with 1.4. It shouldn't change the functionality of the API at all. Of
course, there is a risk that a bug will be present running under 1.3
that we don't see with 1.4, but so far I haven't encountered any.

> Anyway, using virtualenvwrapper everything worked perfectly, and tests run fine.
>
>> === added file 'dashboard/frontend/api/urls.py'
>> --- dashboard/frontend/api/urls.py 1970-01-01 00:00:00 +0000
>> +++ dashboard/frontend/api/urls.py 2013-02-01 11:56:24 +0000
>> @@ -0,0 +1,13 @@
>> +from django.conf.urls.defaults import patterns, include
>> +from dashboard.frontend.api.api import *
>> +from tastypie.api import Api
>> +
>> +v1_api = Api(api_name='v1')
>> +
>> +# Register new resources here (probably defined in api.py)
>> +v1_api.register(LoginTestResource())
>> +v1_api.register(LoopsResource())
>> +
>> +urlpatterns = patterns('',
>> + (r'^api/', include(v1_api.urls)),
>> +)
>
> I have to say I'm more in favor of using a normal numbering scheme
> (like "1.0") for API versions (at least for stable ones, maybe a "dev"
> one for bleeding-edge stuff).
> I guess that if we need to change API version and bump the number, it
> would be as easy as this piece of code, as long as Djano does not
> complain for the double entry with the same search-pattern (r'^api/').
> Did you try if it works? Can't remember out of my mind now...

I haven't tried it. I am sure we can find something that works and we
all like. For now I will change the api_name to "dev" and when we
release we can create a duplicate interface under 1.0, v1.0 or
whatev...

[lp:~dooferlad/linaro-ci-dashboard/add_api_tastypie]

78. By James Tunnicliffe on 2013-02-04

Changes as suggested from merge proposal:
 * Name API version "dev" for the moment
 * Tidy up tests

[Stevan Radaković (stevanr)]

Thanks for the changes!

Approve +1

review: Approve

[Milo Casagrande (milo)]

> I haven't looked into that much, but versioning is probably a good
> idea. so incompatible changes can be rolled out without breaking old
> clients (well, we will phase out old clients eventually). I don't care
> what the version string is though. I like Milo's comment about just
> having a number or "dev". My vote is for major.minor version as stable
> API versions and dev, which will always point to the latest API.

I'm in favor of introducing some sort of versioning too: major.minor numbering and a "dev" one looks OK.
Anyway, MP looks good.

review: Approve

=== modified file 'README'
--- README	2012-09-21 02:10:21 +0000
+++ README	2013-02-04 17:57:22 +0000
@@ -16,6 +16,31 @@
   python-dev
   build-essential
   openjdk-6-jre-headless
+  python-tastypie
+
+To unit test the API that tastypie provides you need Django version of at least
+1.4. If you have Django 1.3 the API will still work, but not be unit tested.
+
+If you are running Ubuntu 12.04 or earlier, you can install Django 1.4 in
+an isolated Python environment using http://www.virtualenv.org/en/latest/.
+These instructions are for the slightly friendlier interface offered by
+http://virtualenvwrapper.readthedocs.org/en/latest/.
+
+  First install virtualenv and virtualenv wrapper:
+  > pip install virtualenvwrapper
+
+  Create a virtual environment to work in:
+  > mkvirtualenv ciloops
+
+  Enable the virtual environment:
+  > workon ciloops
+
+  Install the required Python packages:
+  > pip install -r requirements.txt
+
+  If any new Python packages are required, they can be installed using pip then
+  a new requirements.txt generated:
+  > pip freeze > requirements.txt
 
 Running the application
 -----------------------
 
=== added directory 'dashboard/frontend/api'
=== added file 'dashboard/frontend/api/__init__.py'
=== added file 'dashboard/frontend/api/api.py'
--- dashboard/frontend/api/api.py	1970-01-01 00:00:00 +0000
+++ dashboard/frontend/api/api.py	2013-02-04 17:57:22 +0000
@@ -0,0 +1,56 @@
+# Copyright (C) 2013 Linaro
+#
+# This file is part of linaro-ci-dashboard.
+#
+# linaro-ci-dashboard is free software: you can redistribute it and/or modify
+# it under the terms of the GNU Affero General Public License as published by
+# the Free Software Foundation, either version 3 of the License, or
+# (at your option) any later version.
+#
+# linaro-ci-dashboard is distributed in the hope that it will be useful,
+# but WITHOUT ANY WARRANTY; without even the implied warranty of
+# MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the
+# GNU Affero General Public License for more details.
+#
+# You should have received a copy of the GNU Affero General Public License
+# along with linaro-ci-dashboard.  If not, see <http://www.gnu.org/licenses/>.
+
+from tastypie.resources import ModelResource
+from tastypie.authorization import DjangoAuthorization
+from tastypie.authentication import ApiKeyAuthentication
+from dashboard.frontend.models.loop import Loop
+
+"""
+Add API endpoint logic here. The documentation to do this can be found here:
+http://django-tastypie.readthedocs.org/en/latest/tutorial.html
+
+After creating a class here, make sure you register it in urls.py
+
+TODO: Handle loop creation and builds.
+"""
+
+
+class LoginTestResource(ModelResource):
+    class Meta:
+        """This exists just so a client can test its login data.
+
+        It must use the same authentication mechanism as other protected
+        classes so it will reject connections that aren't authenticated.
+
+        The return data doesn't matter. Ideally, it should put minimal load
+        on the server to generate the return data.
+        """
+
+        queryset = Loop.objects.none()
+        resource_name = 'login_test'
+        authorization = DjangoAuthorization()
+        authentication = ApiKeyAuthentication()
+
+
+class LoopsResource(ModelResource):
+    class Meta:
+        """Returns a list of all loops."""
+        queryset = Loop.objects.all()
+        resource_name = 'loops'
+        authorization = DjangoAuthorization()
+        authentication = ApiKeyAuthentication()
 
=== added file 'dashboard/frontend/api/urls.py'
--- dashboard/frontend/api/urls.py	1970-01-01 00:00:00 +0000
+++ dashboard/frontend/api/urls.py	2013-02-04 17:57:22 +0000
@@ -0,0 +1,13 @@
+from django.conf.urls.defaults import patterns, include
+from dashboard.frontend.api.api import *
+from tastypie.api import Api
+
+v1_api = Api(api_name='dev')
+
+# Register new resources here (probably defined in api.py)
+v1_api.register(LoginTestResource())
+v1_api.register(LoopsResource())
+
+urlpatterns = patterns('',
+   (r'^api/', include(v1_api.urls)),
+)
 
=== added file 'dashboard/frontend/templates/api_key.html'
--- dashboard/frontend/templates/api_key.html	1970-01-01 00:00:00 +0000
+++ dashboard/frontend/templates/api_key.html	2013-02-04 17:57:22 +0000
@@ -0,0 +1,6 @@
+{% if request.user.username %}
+  <div>Your Linaro CI CLI login information is:</div>
+  <div class="data">User: {{ request.user }}</div>
+  <div class="data">API Key: {{ api_key }}</div>
+{% else %}
+{% endif %}
 
=== modified file 'dashboard/frontend/tests/__init__.py'
--- dashboard/frontend/tests/__init__.py	2012-09-14 08:15:50 +0000
+++ dashboard/frontend/tests/__init__.py	2013-02-04 17:57:22 +0000
@@ -1,9 +1,29 @@
+# Copyright (C) 2013 Linaro
+#
+# This file is part of linaro-ci-dashboard.
+#
+# linaro-ci-dashboard is free software: you can redistribute it and/or modify
+# it under the terms of the GNU Affero General Public License as published by
+# the Free Software Foundation, either version 3 of the License, or
+# (at your option) any later version.
+#
+# linaro-ci-dashboard is distributed in the hope that it will be useful,
+# but WITHOUT ANY WARRANTY; without even the implied warranty of
+# MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the
+# GNU Affero General Public License for more details.
+#
+# You should have received a copy of the GNU Affero General Public License
+# along with linaro-ci-dashboard.  If not, see <http://www.gnu.org/licenses/>.
+
 from dashboard.frontend.tests.test_views import *
 from dashboard.frontend.tests.test_models import *
 from dashboard.frontend.tests.test_clientresponse import *
 from dashboard.frontend.tests.test_custom_commands import *
 from dashboard.frontend.tests.test_xml_to_dict import *
 
+import django
+if not(django.VERSION[0] == 1 and django.VERSION[1] <= 3):
+    from dashboard.frontend.tests.test_api import *
 
 #starts the test suite
 __test__ = {
@@ -15,3 +35,6 @@
            'XmlToDictTest': XmlToDictTest,
            'DictToXmlTest': DictToXmlTest,
            }
+
+if not(django.VERSION[0] == 1 and django.VERSION[1] <= 3):
+    __test__['ApiTests'] = ApiTests
 
=== added file 'dashboard/frontend/tests/test_api.py'
--- dashboard/frontend/tests/test_api.py	1970-01-01 00:00:00 +0000
+++ dashboard/frontend/tests/test_api.py	2013-02-04 17:57:22 +0000
@@ -0,0 +1,95 @@
+# Copyright (C) 2013 Linaro
+#
+# This file is part of linaro-ci-dashboard.
+#
+# linaro-ci-dashboard is free software: you can redistribute it and/or modify
+# it under the terms of the GNU Affero General Public License as published by
+# the Free Software Foundation, either version 3 of the License, or
+# (at your option) any later version.
+#
+# linaro-ci-dashboard is distributed in the hope that it will be useful,
+# but WITHOUT ANY WARRANTY; without even the implied warranty of
+# MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the
+# GNU Affero General Public License for more details.
+#
+# You should have received a copy of the GNU Affero General Public License
+# along with linaro-ci-dashboard.  If not, see <http://www.gnu.org/licenses/>.
+
+from django.contrib.auth.models import User
+from django.test import LiveServerTestCase
+from tastypie.models import ApiKey
+from dashboard.frontend.models.loop import Loop
+from dashboard.frontend.android_build.models.android_loop import AndroidLoop
+import requests
+from urlparse import urljoin
+
+
+class ApiTests(LiveServerTestCase):
+    # Use ``fixtures`` & ``urls`` as normal. See Django's ``TestCase``
+    # documentation for the gory details.
+    fixtures = ['test_entries.json']
+
+    def setUp(self):
+        super(ApiTests, self).setUp()
+
+        # Create a user.
+        self.username = 'daniel'
+        self.password = 'pass'
+        self.user = User.objects.create_user(
+                        self.username, '[e-mail]', self.password)
+
+        self.api_key = "0"
+
+        # Add a couple of jobs to test against.
+        self.android_loop = AndroidLoop()
+        self.android_loop.name = "testjob_android"
+        self.android_loop.build_type = "build-android"
+        self.android_loop.save()
+
+        self.loop = Loop()
+        self.loop.name = 'a-loop'
+        self.loop.type = Loop.__class__.__name__
+        self.loop.save()
+
+    def get(self, url):
+        payload = {"username": self.username,
+                   "api_key": self.api_key,
+                   "format": "json"}
+        url = urljoin("http://localhost:8081", "/api/dev/" + url)
+        return requests.get(url, params=payload)
+
+    def login(self):
+        self.api_key = ApiKey.objects.create(user=self.user).key
+        #self.create_apikey(self.username, self.api_key)
+
+    def test_login_test_unauthorzied(self):
+        r = self.get("login_test")
+        self.assertEqual(r.status_code, requests.codes.unauthorized)
+
+    def test_loops_unauthorzied(self):
+        r = self.get("loops")
+        self.assertEqual(r.status_code, requests.codes.unauthorized)
+
+    def test_login_test_authorized(self):
+        self.login()
+        r = self.get("login_test")
+        self.assertEqual(r.status_code, requests.codes.ok)
+
+    def test_loops_authorized(self):
+        self.login()
+        r = self.get("loops")
+        self.assertEqual(r.status_code, requests.codes.ok)
+
+    def test_loops_list(self):
+        self.login()
+        r = self.get("loops")
+        self.assertEqual(r.status_code, requests.codes.ok)
+        json = r.json()['objects']
+
+        # 2 defined loops. Both should be returned.
+        self.assertEqual(len(json), 2)
+
+        # Make sure both loops contain the expected data.
+        api_test_names = {json[0]['name'], json[1]['name']}
+        test_names = {self.android_loop.name, self.loop.name}
+        self.assertEqual(api_test_names, test_names)
 
=== modified file 'dashboard/frontend/urls.py'
--- dashboard/frontend/urls.py	2012-09-24 19:09:05 +0000
+++ dashboard/frontend/urls.py	2013-02-04 17:57:22 +0000
@@ -24,6 +24,7 @@
 from frontend.views.loop_build_view import LoopBuildView
 from frontend.views.loop_get_chainable_view import LoopGetChainableView
 from frontend.views.loop_build_detail_view import LoopBuildDetailView
+from frontend.views.api_key import ApiKeyView
 
 
 urlpatterns = patterns('',
@@ -40,4 +41,5 @@
         LavaSelectView.as_view(), name='LavaSelectView'),
     url(r'^lava/ajax/get-test-names/$',
         LavaSelectTestNames.as_view(), name='LavaSelectTestsNames'),
+    url(r'^api_key/$', ApiKeyView.as_view(), name='ApiKeyView'),
 )
 
=== added file 'dashboard/frontend/views/api_key.py'
--- dashboard/frontend/views/api_key.py	1970-01-01 00:00:00 +0000
+++ dashboard/frontend/views/api_key.py	2013-02-04 17:57:22 +0000
@@ -0,0 +1,47 @@
+# Copyright (C) 2013 Linaro
+#
+# This file is part of linaro-ci-dashboard.
+#
+# linaro-ci-dashboard is free software: you can redistribute it and/or modify
+# it under the terms of the GNU Affero General Public License as published by
+# the Free Software Foundation, either version 3 of the License, or
+# (at your option) any later version.
+#
+# linaro-ci-dashboard is distributed in the hope that it will be useful,
+# but WITHOUT ANY WARRANTY; without even the implied warranty of
+# MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the
+# GNU Affero General Public License for more details.
+#
+# You should have received a copy of the GNU Affero General Public License
+# along with linaro-ci-dashboard.  If not, see <http://www.gnu.org/licenses/>.
+
+from django.views.generic.base import TemplateView
+from tastypie.models import ApiKey
+from django.contrib.auth.decorators import login_required
+from django.utils.decorators import method_decorator
+
+
+class ApiKeyView(TemplateView):
+    """Provide the user with their API key, generating one if required."""
+    template_name = "api_key.html"
+
+    @method_decorator(login_required)
+    def dispatch(self, *args, **kwargs):
+        return super(ApiKeyView, self).dispatch(*args, **kwargs)
+
+    def get_context_data(self, **kwargs):
+        context = super(ApiKeyView, self).get_context_data(**kwargs)
+        context['request'] = self.request
+
+        # TODO: Reset API key on request. This can be done by:
+        # api_key.key = None
+        # api_key.save() -- will generate a new key (won't accept None)
+
+        try:
+            api_key = ApiKey.objects.get(user=self.request.user)
+        except ApiKey.DoesNotExist:
+            api_key = ApiKey.objects.create(user=self.request.user)
+
+        context['api_key'] = api_key.key
+
+        return context
 
=== modified file 'dashboard/settings.py'
--- dashboard/settings.py	2012-10-04 15:39:41 +0000
+++ dashboard/settings.py	2013-02-04 17:57:22 +0000
@@ -18,6 +18,7 @@
 
 import os
 import sys
+import django
 
 DEBUG = True
 TEMPLATE_DEBUG = DEBUG
@@ -127,11 +128,16 @@
     'django.middleware.common.CommonMiddleware',
     'django.contrib.sessions.middleware.SessionMiddleware',
     'django.middleware.csrf.CsrfViewMiddleware',
-    'django.middleware.csrf.CsrfResponseMiddleware',
     'django.contrib.auth.middleware.AuthenticationMiddleware',
     'django.contrib.messages.middleware.MessageMiddleware',
 )
 
+# The CSRF middleware moved in Django 1.4...
+if django.VERSION[0] == 1 and django.VERSION[1] <= 3:
+    MIDDLEWARE_CLASSES += ('django.middleware.csrf.CsrfResponseMiddleware',)
+else:
+    MIDDLEWARE_CLASSES += ('django.middleware.csrf.CsrfViewMiddleware',)
+
 ROOT_URLCONF = 'dashboard.urls'
 
 INSTALLED_APPS = (
@@ -151,9 +157,9 @@
     'frontend.integration_loop',
     'frontend.android_textfield_loop',
     'frontend.hwpack_loop',
+    'frontend.api',
+    'tastypie',
     'south',
-    # Uncomment the next line to enable the admin:
-    # 'django.contrib.admin',
     # Uncomment the next line to enable admin documentation:
     # 'django.contrib.admindocs',
 )
 
=== modified file 'dashboard/urls.py'
--- dashboard/urls.py	2012-09-24 19:09:05 +0000
+++ dashboard/urls.py	2013-02-04 17:57:22 +0000
@@ -39,4 +39,5 @@
     url(r'^', include('dashboard.frontend.integration_loop.urls')),
     url(r'^', include('dashboard.frontend.android_textfield_loop.urls')),
     url(r'^', include('dashboard.frontend.hwpack_loop.urls')),
+    url(r'^', include('dashboard.frontend.api.urls')),
 )
 
=== added file 'requirements.txt'
--- requirements.txt	1970-01-01 00:00:00 +0000
+++ requirements.txt	2013-02-04 17:57:22 +0000
@@ -0,0 +1,15 @@
+Django==1.4.3
+South==0.7.6
+argparse==1.2.1
+distribute==0.6.24
+django-openid-auth==0.4
+django-openid-consumer==0.1.1
+django-tastypie==0.9.11
+jenkins==1.0.2
+mimeparse==0.1.3
+mock==1.0.1
+python-dateutil==1.5
+python-jenkins==0.2
+python-openid==2.2.5
+requests==1.1.0
+wsgiref==0.1.2