deploy splunk-nozzle to system org, splunk-nozzle-space

[anishp55]

Currently the splunk-nozzle is deployed to a splunk-nozzle-org and a dedicated space in there. I propose that the splunk-nozzle go into the system org, and into a splunk-nozzle-space.

[aegershman]

Respectfully disagree; I'm not a fan of touching anything within the system org from third-party vendors. I'm partial to keeping the orgs separated. By keeping the org separate, users are able to leverage tools like cf-mgmt to manage users within a third-party org (e.g. any ops folks who want to keep an eye on the nozzle), without having to setup configuration to also handle the rest of the system org, as it can be whitelisted. I'm partial to making the deployment target customizable. Personally I'm a fan of having a nozzles org with spaces inside each such as splunk-nozzle for any system-wide / admin-used nozzles on the platform. Don't mean to completely shun the idea, just pointed out my discomfort with letting things, namely third-party vendors, touching the system org. Thoughts?

EDIT: on second thought, it wouldn't be the worst to have the option to put it in the system org rather than it's own, because in envs which leverage NSX-T, you have to allocate a full subnet of internal IPs per-org... so it would be a massive waste to have an entire subnet just for the splunk firehose nozzle...

[luckyj5]

@anishp55 Did you mean to file this issue against https://github.com/cloudfoundry-community/splunk-firehose-nozzle repo? Thanks!

[anishp55]

@luckyj5 possibly.
@aegershman a nozzle org would work