At the beginning of the staging process, you'll notice lines like the following:
Creating package "my_app"... done
Uploading package contents... 100.0% (891.5/891.5 KiB)
[package] -- Uploading -- received all bytes from client, start upload to storage backend
[package] -- Uploading -- uploaded resource "46400dc0-aeda-435e-8e7b-33c6f25092c6" to storage backend successfully in 0.313s
[package] -- Uploading -- updated package "c21cd843-97b6-452a-981e-3daab40f90ef" with new resource
Deciphering this, the following process takes place:
- The APC CLI packages up (basically as a tarball) your app's source bits and uploads it to the Apcera deployment. Note the 1st resource UUID "46400dc0...". This interaction is with the Package Manager role, which is one of the roles the Central VM has. The Storage Backend for Apcera CE is on local storage, specifically in
/var/lib/continuum/packages. This is different than with Apcera EE where the Storage Backend can be S3 or GlusterFS.
- A package object is created. Note its UUID "c21cd843...".
- The package is associated with the uploaded content.
Hope this helps.