Offline buildpacks

[hamzahamidi]

Deployment type

• Cloud Foundry Application (cf push)
• Kubernetes, using a helm chart
• Docker, using docker compose
• Docker, single container deploying all components
• [x ] Other (please provide below)

Is there a support for Packaging Dependencies for Offline Buildpacks? If not, are you planning to do it in the future ? Any information you can provide me would be greatly appreciated, thank you.

Expected behaviour

Actual behaviour

Steps to reproduce the behavior

Log output covering before error and any error statements

Insert log here

[richard-cox]

We currently have no support for this. It is something we'd be interested in but it's not on our current road map. If this is something that you work on your side let us know and we can see about getting those changes to master. Thanks!

[gberche-orange]

@richard-cox

One of our colleague (@ArthurHlt ) worked on an offline packager to support offline CF deployments
https://github.com/orange-cloudfoundry/stratos-ui-cf-packager

Please let us know if this could be useful.

[ArthurHlt]

thanks @gberche-orange to push me to talk about this, I should talk about it.

I did the work https://github.com/orange-cloudfoundry/stratos-ui-cf-packager to package stratos-ui for cloud foundry without internet connection and without stratos-buildpack. It packages stratos-ui through travis and build binaries inside it.

Maybe it could be on the main repo because stratos-ui only need nodejs and gulp for building and package assets and one of the good part of the project use golang as backend. On golang, this project use the plugin experimental concept from go which only works on linux (neither mac and windows and like we can see here this is not a priority).
I have no special bad feelings about it on stratos because how it is used make things really better and highly pluggable.

So, as it is tied to linux I don't think there is a high value to be able to build stratos when staging on Cloud Foundry. I'm maybe wrong but the only thing I can see is security issues from golang which can be handled by bumping the version when packaging in a CI. I can do a pull request if there is an interest to package in this way

In https://github.com/orange-cloudfoundry/stratos-ui-cf-packager there is another component inside which is a plugin, it was made to be able to register multiple endpoints inside stratos-ui by only use user provided service. It uses gautocloud which give the ability to do the same for kubernetes or cloud foundry. This project can also maybe leverage some issues on stratos-ui to be cloud agnostic (I'm thinking about populate databases, pre-configuration and so on).

BTW, You have made a great work, stratos-ui is already awesome and when I see that it's still in beta, i can't imagine how it will be when it be the first release. Thank you to fill this huge gap in cloud foundry open source.

[richard-cox]

Sorry @gberche-orange and @ArthurHlt , I managed to miss these two comments. We'll take a look and get back to you. I know @nwmac has been looking in to building the back end on different OSs and currently has an open PR #1366 which might help you out.

[aad]

just update that we are able to build the binary that be able to run on cf using https://github.com/cloudfoundry-incubator/stratos/tree/2.0.1