Pivotal/Cloud Foundry/Apps - Revision history

R00t at 17:34, 16 August 2018

2018-08-16T17:34:51Z

R00t at 13:45, 6 August 2018

2018-08-06T13:45:31Z

R00t at 15:10, 23 May 2018

2018-05-23T15:10:27Z

R00t at 17:35, 22 May 2018

2018-05-22T17:35:31Z

R00t at 16:18, 22 May 2018

2018-05-22T16:18:33Z

R00t at 16:05, 22 May 2018

2018-05-22T16:05:35Z

R00t: Created page with "Cloud Foundry | Cloud Foundry CLI | Apps"

2018-05-22T14:32:24Z

Created page with "Cloud Foundry | Cloud Foundry CLI | Apps"

New page

@@ Line 1: / Line 1: @@
-[[Pivotal/Cloud_Foundry|Cloud Foundry]] | [[Pivotal/Cloud_Foundry/CLI|Cloud Foundry CLI]] | [[Pivotal/Cloud_Foundry/Apps|Apps]] | [[Pivotal/Cloud_Foundry/Tasks|Tasks]] | [[Pivotal/Cloud_Foundry/Logs|Logs]]
+[[Pivotal/Cloud_Foundry|Cloud Foundry]] | [[Pivotal/Cloud_Foundry/CLI|Cloud Foundry CLI]] | [[Pivotal/Cloud_Foundry/Apps|Apps]] | [[Pivotal/Cloud_Foundry/Tasks|Tasks]] | [[Pivotal/Cloud_Foundry/Logs|Logs]] | [[Pivotal/Cloud_Foundry/OpsManager|OpsManager]]
 =App Deployment Overview=
 This is just a quick overview of what happens during app deployment.  The steps were obtained by using TRACE during an app deployment and then reviewing the corresponding log file.

@@ Line 1: / Line 1: @@
-[[Pivotal/Cloud_Foundry|Cloud Foundry]] | [[Pivotal/Cloud_Foundry/CLI|Cloud Foundry CLI]] | [[Pivotal/Cloud_Foundry/Apps|Apps]] | [[Pivotal/Cloud_Foundry/Tasks|Tasks]]
+[[Pivotal/Cloud_Foundry|Cloud Foundry]] | [[Pivotal/Cloud_Foundry/CLI|Cloud Foundry CLI]] | [[Pivotal/Cloud_Foundry/Apps|Apps]] | [[Pivotal/Cloud_Foundry/Tasks|Tasks]] | [[Pivotal/Cloud_Foundry/Logs|Logs]]
 =App Deployment Overview=
 This is just a quick overview of what happens during app deployment.  The steps were obtained by using TRACE during an app deployment and then reviewing the corresponding log file.

@@ Line 1: / Line 1: @@
-[[Pivotal/Cloud_Foundry|Cloud Foundry]] | [[Pivotal/Cloud_Foundry/CLI|Cloud Foundry CLI]] | [[Pivotal/Cloud_Foundry/Apps|Apps]]
+[[Pivotal/Cloud_Foundry|Cloud Foundry]] | [[Pivotal/Cloud_Foundry/CLI|Cloud Foundry CLI]] | [[Pivotal/Cloud_Foundry/Apps|Apps]] | [[Pivotal/Cloud_Foundry/Tasks|Tasks]]
 =App Deployment Overview=
 This is just a quick overview of what happens during app deployment.  The steps were obtained by using TRACE during an app deployment and then reviewing the corresponding log file.

@@ Line 39: / Line 39: @@
 This appears to be where we upgrade the connection protocol to SSL/TLS
 ==16: GET app data/status==
-quick looped GET request to obtain current app status, we are looking for a change from PENDING to
+quick looped GET request to obtain current app status, we are looking for a change from PENDING to STAGED.  Appears to loop every 2-3 seconds.

@@ Line 39: / Line 39: @@
 This appears to be where we upgrade the connection protocol to SSL/TLS
 ==16: GET app data/status==
-quick GET request to obtain current app status, we are looking for a change from STARTED to PENDING
+quick looped GET request to obtain current app status, we are looking for a change from PENDING to
-==17: GET app data/status==
-another quick GE request to obtain current app status, we are looking for a change from PENDING to

← Older revision		Revision as of 16:05, 22 May 2018
Line 1:		Line 1:
	[[Pivotal/Cloud_Foundry\|Cloud Foundry]] \| [[Pivotal/Cloud_Foundry/CLI\|Cloud Foundry CLI]] \| [[Pivotal/Cloud_Foundry/Apps\|Apps]]		[[Pivotal/Cloud_Foundry\|Cloud Foundry]] \| [[Pivotal/Cloud_Foundry/CLI\|Cloud Foundry CLI]] \| [[Pivotal/Cloud_Foundry/Apps\|Apps]]
		+	=App Deployment Overview=
		+	This is just a quick overview of what happens during app deployment. The steps were obtained by using TRACE during an app deployment and then reviewing the corresponding log file.
		+	<nowiki>~$CF_TRACE=/Users/User/web-app/trace.log cf push web-app</nowiki>
		+	==1: HTTP request for json info==
		+	Simple HTTP request for json info to the server. Server will reply back with information such as:
		+	*api version and minimum requirement
		+	*addresses for services
		+	==2: Login==
		+	Next up is to log into the CF Service. Submit another HTTP request for json data pertaining to login services. This will provide login information such as:
		+	*login URL
		+	*forgot password link
		+	*registration
		+	==3: Check if the application exists==
		+	We want to see if the application already exists in the environment. This will determine whether we are pushing an update or if we are pushing a whole new app.
		+	==4: Get list of shared domains==
		+	Get a list of all the shared domains that are available to us.
		+	==5: Get list of private domains==
		+	Get a list of all the private domains that are available to us
		+	==6: Push the app package==
		+	If the app is not deployed already, we will push what i'm calling the "package". it is essentially the settings defined in the app manifest to begin prepping CF for the app. CF will respond back with a ton of information regarding the app settings and package configuration.
		+	==7: Push the app route==
		+	Push the app route, if specified, otherwise the server will create a random route and reply back with the details and settings.
		+	==8: Update the app route==
		+	With the information provided in the last step, we can make updates and finalize the route.
		+	==9: Update Resources (?)==
		+	The next step was brief for me, although it appears to be a function to update resources and match their requirements to the app.
		+	==10: application update (?)==
		+	An application update, very brief, not sure what its for other than to get the current package build status, but unsure why it would be a PUT request instead of a GET request. Seems like something is being updated.
		+	==11: GET job status==
		+	Determine what the current job status is, probably to determine the build status. In my case, the response came back queued.
		+	==12: Another GET job status==
		+	Same as above, most likely a looped function to check on status until it returns a Finished result. Mine now finished.
		+	==13: Start the application==
		+	It seems we are now ready to start the application! We will also get back alot of information regarding the application, however, the next (3) steps may complete before the response is returned. We will get back a response stated STARTED
		+	==14: Request an access token (?)==
		+	I assume this is an access token for the application, not quite sure what its used for yet.
		+	==15: perform a websocket upgrade request==
		+	This appears to be where we upgrade the connection protocol to SSL/TLS
		+	==16: GET app data/status==
		+	quick GET request to obtain current app status, we are looking for a change from STARTED to PENDING
		+	==17: GET app data/status==
		+	another quick GE request to obtain current app status, we are looking for a change from PENDING to