base L3's create_router should process extensions

[Armando Migliaccio]

Change:

https://github.com/openstack/neutron/commit/634fd1d23fb241bc4990275d5a4da0c3ab66e2de

Tweaked base create_router in l3_db.py to process the extensions or not; however it was chosen at the time, to set the process_extensions flag to False. This effectively disable the ability for extensions made to create_router's method to handle extension's attributes correctly.

A more appropriate value should be True, so that extension attributes can be shown during the create process.

[OpenStack Infra (hudson-openstack)]

Fix proposed to branch: master
Review: https://review.openstack.org/97275

[OpenStack Infra (hudson-openstack)]

Reviewed: https://review.openstack.org/97275
Committed: https://git.openstack.org/cgit/openstack/neutron/commit/?id=0759ed18a95b438bf775d6905256119f1cee75db
Submitter: Jenkins
Branch: master

commit 0759ed18a95b438bf775d6905256119f1cee75db
Author: armando-migliaccio <email address hidden>
Date: Mon Jun 2 07:31:33 2014 -0700

    Allow L3 base to handle extensions on router creation

    By changing the boolean flag, API extensions made to
    the router model can be handled correctly: this means
    that on router creation, the response body will
    contain all the extension attributes being part of
    the resource. Prior to this fix, it was only on GETs
    or PUTs, leaving the user at loss as to whether
    the flag was actually being processed.

    Closes-bug: #1325608
    Supports-blueprint: neutron-ovs-dvr

    Change-Id: I6f913c8417676a789177e00f30eb5875e7aaa3ae