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

Support for the Elastic Stack #134

Closed
morgango opened this issue May 12, 2020 · 4 comments
Closed

Support for the Elastic Stack #134

morgango opened this issue May 12, 2020 · 4 comments
Labels
comp/node Issue of node component status/need-to-review Need to review

Comments

@morgango
Copy link

morgango commented May 12, 2020 •
edited
Loading

Where would you recommend putting icons for a SaaS service that runs on one of the major providers? For example, Elastic has Elastic Cloud which can run on Google, Azure, Alibaba, or AWS.

Thanks.
@mingrammer
Copy link
Owner

mingrammer commented May 15, 2020 •
edited
Loading

There are already some elastic services on onprem provider:

And we have a plan for adding the saas provider for some saas services. (maybe user facing services will be located on this provider) When saas provider is added, we should decide whether to move the elastic stack to saas provider or keep them in onprem provider.

Here is saas related issue: #89

@mingrammer mingrammer added comp/node Issue of node component status/need-to-review Need to review labels May 15, 2020
@gabriel-tessier gabriel-tessier mentioned this issue May 24, 2020
Closed
@gabriel-tessier
Copy link
Collaborator

I'll push a PR to add elastic as provider as discussed in the 168 PR (as I already have the resources).
It will make more sense to isolate elastic, this will prevent duplication with onprem as (nearly) all the service they provide can be saas or onprem.

mingrammer pushed a commit that referenced this issue May 31, 2020
@gabriel-tessier
Add elastic stack (#134) (#174)
1eed336 
* Add elastic stack (#134)

* (#134) Fix Upper case
nlamirault added a commit to nlamirault/diagrams that referenced this issue Jun 4, 2020
@nlamirault
Merge branch 'master' into feature/elasticstack
bc3d020 
* master: (23 commits)
  Added generic itens and blank cluster (mingrammer#171)
  bump: up to version 0.13.1
  fix: add missing firebase base class
  docs: fix i18n
  docs(web): add sponsoring
  docs: fix Saas to SaaS
  docs: add more badges
  docs: add a sponsorship link :)
  docs: add firebase, elastic, and saas categories
  bump: up to version 0.13.0
  AWS: Added more DynamoDB and IAM resources (mingrammer#180)
  Add elastic stack (mingrammer#134) (mingrammer#174)
  Add Rust programming language (mingrammer#179)
  Add flux and flagger (mingrammer#147)
  Add Saas v2 (mingrammer#89) (mingrammer#173)
  Add nodes for Firebase (mingrammer#167)
  Add ZuulCI as onprem CI resource (mingrammer#145)
  bump: up to version 0.12.0
  Add GitlabCI to onprem.ci section (mingrammer#166)
  Add Sentry to onperm.monitoring (mingrammer#165)
  ...

Signed-off-by: Nicolas Lamirault <nicolas.lamirault@gmail.com>
nlamirault added a commit to nlamirault/diagrams that referenced this issue Jun 4, 2020
@nlamirault
Merge branch 'master' into feature/tekton
4557141 
* master: (23 commits)
  Added generic itens and blank cluster (mingrammer#171)
  bump: up to version 0.13.1
  fix: add missing firebase base class
  docs: fix i18n
  docs(web): add sponsoring
  docs: fix Saas to SaaS
  docs: add more badges
  docs: add a sponsorship link :)
  docs: add firebase, elastic, and saas categories
  bump: up to version 0.13.0
  AWS: Added more DynamoDB and IAM resources (mingrammer#180)
  Add elastic stack (mingrammer#134) (mingrammer#174)
  Add Rust programming language (mingrammer#179)
  Add flux and flagger (mingrammer#147)
  Add Saas v2 (mingrammer#89) (mingrammer#173)
  Add nodes for Firebase (mingrammer#167)
  Add ZuulCI as onprem CI resource (mingrammer#145)
  bump: up to version 0.12.0
  Add GitlabCI to onprem.ci section (mingrammer#166)
  Add Sentry to onperm.monitoring (mingrammer#165)
  ...
@gabriel-tessier
Copy link
Collaborator

gabriel-tessier commented Jul 4, 2020 •
edited
Loading

@mingrammer

What about this issue?
As now there's an elastic provider can I remove the resources from onprem?
but need to add a note in the readme as it will be a breaking change.

I can push a PR for this change.

mingrammer pushed a commit that referenced this issue Jul 7, 2020
@gabriel-tessier
(#134) Clean onprem elastic (#223)
d02c4d9 
* (#134) Clean onprem elastic

* [Fix] Move to Changelog

* Update Changelog
@mingrammer
Copy link
Owner

It is currently supporting the elastic provider.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
comp/node Issue of node component status/need-to-review Need to review
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@gabriel-tessier @morgango @mingrammer