Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Explore options to support application grouping #99

Closed
sabbyanandan opened this issue Aug 7, 2016 · 1 comment
Closed

Explore options to support application grouping #99

sabbyanandan opened this issue Aug 7, 2016 · 1 comment
Assignees
@markfisher
Labels
for/spike For spike
Milestone
1.2.0.M1

Comments

@sabbyanandan
Copy link
Contributor

sabbyanandan commented Aug 7, 2016 •
edited

As a developer, I'd like to investigate the approach to support application grouping, so I can use it to partition multiple applications into manageable sets.

Goals:

  • we could support deploying arbitrary set of apps that has no messaging-middleware relevance and the stream/task applications (in SCDF) becomes a specialization

Acceptance:

  • deploy, undeploy, status, and delete operations in the context of "application grouping" is included in this study
  • design proposal for review
@sabbyanandan sabbyanandan added this to the 1.1.0.M1 milestone Aug 7, 2016
@markfisher markfisher self-assigned this Aug 8, 2016
@markfisher markfisher mentioned this issue Aug 22, 2016
Open
@sabbyanandan sabbyanandan modified the milestone: 1.1.0.M1 Sep 19, 2016
@sabbyanandan sabbyanandan mentioned this issue Oct 2, 2016
Closed
@sabbyanandan sabbyanandan modified the milestones: 1.1.0.M1, 1.1.0.M2 Oct 12, 2016
@sabbyanandan sabbyanandan removed this from the 1.1.0.RC1 milestone Oct 26, 2016
@sabbyanandan sabbyanandan added this to the 1.2.0.M1 milestone Dec 11, 2016
@sabbyanandan
Copy link
Contributor Author

The finalized design proposal is here for review. We will be addressing the feature capabilities in incremental chunks and the first step in the process will be tackled via spring-cloud/spring-cloud-dataflow#1122 and spring-cloud/spring-cloud-dataflow#1123. The scope of this spike is complete; closing it.

corneil pushed a commit that referenced this issue Mar 22, 2023
@trisberg @ilayaperumalg
Add support for enabling hostNetwork for pods.
2d50d61 
- this allows us to deploy a stream using something like:
  stream deploy ticktock --properties "app.time.server.port=8281,app.log.server.port=8282,app.*.spring.cloud.deployer.kubernetes.hostNetwork=true"

- when using "minikube" we can now access the deployed apps on http://192.168.99.100:8281/health and http://192.168.99.100:8282/health respectively

- see https://kubernetes.io/docs/api-reference/v1/definitions/#_v1_podspec

Resolves #99

Adding hostNetwork to KubernetesDeployerProperties
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@markfisher markfisher

Labels
for/spike For spike
Projects
None yet
Milestone
1.2.0.M1
Development

No branches or pull requests
2 participants
@markfisher @sabbyanandan