Fix some typos in the documents
This patch fixes some typos in the documents Change-Id: Ib183b2bb0130a04abd4faa9cff7026e552adad93
This commit is contained in:
parent
6e65e6f881
commit
361214ddc8
@ -266,7 +266,7 @@ API end points for 'vim' resource as described below:
|
|||||||
|
|
||||||
Security impact
|
Security impact
|
||||||
---------------
|
---------------
|
||||||
VIM passwords are encrypted and stored in a seperate 'vimauth' table accessible
|
VIM passwords are encrypted and stored in a separate 'vimauth' table accessible
|
||||||
to db admin only. The fernet keys are stored in root file system and will be
|
to db admin only. The fernet keys are stored in root file system and will be
|
||||||
used to decrypt vim passwords.
|
used to decrypt vim passwords.
|
||||||
|
|
||||||
|
@ -8,16 +8,16 @@ This work is licensed under a Creative Commons Attribution 3.0 Unported
|
|||||||
Tacker API Framework
|
Tacker API Framework
|
||||||
====================
|
====================
|
||||||
|
|
||||||
Currently there is a API implementation in tacker but it doesn't follow the
|
Currently there is an API implementation in tacker but it doesn't follow the
|
||||||
OpenStack standard. There are two API frameworks which are largely adopted
|
OpenStack standard. There are two API frameworks which are largely adopted
|
||||||
by the community 1. PECAN 2. Falcon
|
by the community 1. PECAN 2. Falcon
|
||||||
I have gone through all the posibilities about the selecting the framework
|
I have gone through all the possibilities about the selecting the framework
|
||||||
but the PECAN's adoption is very high as compare to Falcon by Openstack
|
but the PECAN's adoption is very high as compare to Falcon by Openstack
|
||||||
community. Currently there are many OpenStack project already using
|
community. Currently there are many OpenStack project already using
|
||||||
PECAN like zaqar, magnum & others but Ironic is facing lot of issues in
|
PECAN like zaqar, magnum & others but Ironic is facing lot of issues in
|
||||||
PECAN + WSME approach. Pecan community is not providing the support on
|
PECAN + WSME approach. Pecan community is not providing the support on
|
||||||
filed bugs. Falcon is faster and more secure as compare to PECAN.
|
filed bugs. Falcon is faster and more secure as compare to PECAN.
|
||||||
We dont need to depend on third part project like WSME for attribute
|
We don't need to depend on third part project like WSME for attribute
|
||||||
validation if we use Falcon. Falcon has less dependencies as compare to
|
validation if we use Falcon. Falcon has less dependencies as compare to
|
||||||
PECAN.
|
PECAN.
|
||||||
There are many project using PECAN now but taking all the above
|
There are many project using PECAN now but taking all the above
|
||||||
@ -27,7 +27,7 @@ Falcon is developed for complete Cloud REST API's. Currently Zaqar is using.
|
|||||||
Problem description
|
Problem description
|
||||||
===================
|
===================
|
||||||
|
|
||||||
We need a API framework which gives us better performance, secure and
|
We need an API framework which gives us better performance, secure and
|
||||||
has good community support.
|
has good community support.
|
||||||
Current implementation is not adopted by OpenStack community & has less
|
Current implementation is not adopted by OpenStack community & has less
|
||||||
performance as compare to Falcon/PECAN.
|
performance as compare to Falcon/PECAN.
|
||||||
@ -53,7 +53,7 @@ Following are the changes -
|
|||||||
|
|
||||||
Implement Controllers instead extensions -
|
Implement Controllers instead extensions -
|
||||||
|
|
||||||
We have written seperate extension for nfvo & vnfm for API. We need to
|
We have written separate extension for nfvo & vnfm for API. We need to
|
||||||
introduce new controllers to below extensions.
|
introduce new controllers to below extensions.
|
||||||
tacker/extension/nfvo.py
|
tacker/extension/nfvo.py
|
||||||
tacker/extension/vnfm.py
|
tacker/extension/vnfm.py
|
||||||
@ -89,11 +89,11 @@ falcon.HTTPInternalServerError
|
|||||||
|
|
||||||
Plugins -
|
Plugins -
|
||||||
|
|
||||||
I dont think there will be direct impact on existing plugins, but for new
|
I don't think there will be direct impact on existing plugins, but for new
|
||||||
features, we should write separate controllers & introduce the functionality.
|
features, we should write separate controllers & introduce the functionality.
|
||||||
Like VNFFG, its better to write seperate api/controller/v1/vnffg.py because
|
Like VNFFG, it's better to write separate api/controller/v1/vnffg.py because
|
||||||
we are offering complete CRUD for VNFFG.
|
we are offering complete CRUD for VNFFG.
|
||||||
Its always better to write separate controller file for those who offer
|
It's always better to write separate controller file for those who offer
|
||||||
complete CRUD operations.
|
complete CRUD operations.
|
||||||
|
|
||||||
Authentication -
|
Authentication -
|
||||||
|
Loading…
Reference in New Issue
Block a user