Adding provision to have the feature packages to do initialization upon jobServer Start Adding API featureInit() which the feature package should call if they want some initialization in webroot/common/api/init.api.js file

Change-Id: I682b9a0f81857d4537efea9fdea78940b73288f3
Nova Compute code was reseting the header of the request.
Passed both header and parameter seperate to retain the headder.

Change-Id: Ib44ceddbf4118146270d5add279f276bc6bbe531
Related-Bug: #1390392
1. Clear vmware session while logging out WebUI session
2. Added 'Private VLAN' text field in Create Network popup in case of vCenter
   orchestration mode. It will not be visible in Edit Network popup

Change-Id: I3fb9ebb5cd069a1c5ae2878a2a4adea47a4a4ef1
Merge "Related-Bug: #1390392 1. Clear vmware session while logging out WebUI session 2. Added 'Private VLAN' text field in Create Network popup in case of vCenter    orchestration mode. It will not be visible in Edit Network popup"
Merge "Nova Compute code was reseting the header of the request. Passed both header and parameter seperate to retain the headder."
1. Get the admin_user/passwd/tenant from seperate UI auth config file.
    This will be used only in middleware for recurrent jobs, in case of jobs
    which gets kick started upon restart of jobServer, but due to not logged in
    user, API Server response always gets failed if multi_tenancy is enabled,
    so though we are starting jobs at init time, but we do not get much info,
    only from OpServer. So at init time also read this config file, and get the
    token from keystone and communicate with API Server. Once token gets
    expired, then also use the same user auth to get new token. In case the user
    auth file does not exist or auth does not get succeed, return error to
    client.
2. Once authentication occurs, then after getting new token, store that new
    token against job name, when the job is rescheduled then check if there is any
    registered job task data change, if so, then before recreating new job, update
    the taskdata with all the changed parameters, in this case, we change the
    authObj and tokenObjs in jobData which is used for next time auth to API Server.
3. After purging all redis DBs only, start jobSrever's other tasks.
4. Removed some unwanted log messages.
5. Reissuing of auths using username and password are managed now in jobServer
    only.
6. Do not delete the pubChannel entry if the job is recurrent job, as this may
    be required for redirectToLogout utility.

Change-Id: I78c4aaabfa8c2199e854c7f98dcf52c94b7b257c
Related-Bug:#1391447
Merged two different flags used for physical topology changes in UI to one
Earlier we were maintaining another flag underlayEnabled in default.config.global.js now we removed this.

Change-Id: I43cf0c05c3f2a31871eab6d540935e66d2aa701c
Merge pull request #62 from Juniper/master

Pull changes from Juniper/web-core to absingla/web-core
If postCallback is set, then sending response creates error
Fix: Corrected the typo error

Change-Id: I71a752ab8715f060cee4d9dafb67ce3ba1b0d330
Merge "1. Get the admin_user/passwd/tenant from seperate UI auth config file.     This will be used only in middleware for recurrent jobs, in case of jobs     which gets kick started upon restart of jobServer, but due to not logged in     user, API Server response always gets failed if multi_tenancy is enabled,     so though we are starting jobs at init time, but we do not get much info,     only from OpServer. So at init time also read this config file, and get the     token from keystone and communicate with API Server. Once token gets     expired, then also use the same user auth to get new token. In case the user     auth file does not exist or auth does not get succeed, return error to     client. 2. Once authentication occurs, then after getting new token, store that new     token against job name, when the job is rescheduled then check if there is any     registered job task data change, if so, then before recreating new job, update     the taskdata with all the changed parameters, in this case, we change the     authObj and tokenObjs in jobData which is used for next time auth to API Server. 3. After purging all redis DBs only, start jobSrever's other tasks. 4. Removed some unwanted log messages. 5. Reissuing of auths using username and password are managed now in jobServer     only. 6. Do not delete the pubChannel entry if the job is recurrent job, as this may     be required for redirectToLogout utility."
Merge "Related-Bug:#1391447 Merged two different flags used for physical topology changes in UI to one Earlier we were maintaining another flag underlayEnabled in default.config.global.js now we removed this."
Once postCallback is set and forceRefresh is set as false, then the response
does not come back to callback handler.
Fix: Corrected the logic to handle the response back to the handler.

Change-Id: Ib507862f75384a0fbe8903c97422ff43d889464d
Fixed the issue no data avialable is displaying while loading the networking dashboard projects chart when we redirect from other pages

Change-Id: Ia13dbd8cddc3c8385474997d6cdad3238c291570
Merge "If postCallback is set, then sending response creates error Fix: Corrected the typo error"
Use logutils instead of console.log on server side

Change-Id: I15b1d64e74d52d72f68e2887da6b44f8eb57cbb1
Fixed logic for Default Sort on Grid by referencing the correct columns from the config to be sorted

Change-Id: Ie22494511f9a76e29df204bf2a3712a228496010
Merge "Once postCallback is set and forceRefresh is set as false, then the response does not come back to callback handler. Fix: Corrected the logic to handle the response back to the handler."
Closes-Bug : #1394467 - Baremetal : Need to create Subnet and set Virtual Machine Interface reference to it while creating Logical interface of type L3

Change-Id: Iffbf1c7585aa66bd1145871ce825e846dea9ff06
Merge "Fixed logic for Default Sort on Grid by referencing the correct columns from the config to be sorted"
Added uuid, action in the results grid in Flow Records query.
(Fixes bug id 1343501) Added a vrouter= option in the where clause for Flow series and Flow records queries.
Fixed issue where UI sent invalid protocol value in Flow Series. (Fixes bug id 1382004)

Change-Id: Iaf390df148faecec0b46c2ebe4f645495dbd566e