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.

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

Seperate on-prem dalco cluster into two #912

Open
1 of 3 tasks
mrnicegyu11 opened this issue Dec 16, 2024 · 1 comment
Open
1 of 3 tasks

Seperate on-prem dalco cluster into two #912

mrnicegyu11 opened this issue Dec 16, 2024 · 1 comment
Assignees
Labels
EPIC p:high-prio t:infra-ops Adjustments to the way or resources with that microservices are run
Milestone

Comments

@mrnicegyu11
Copy link
Member

mrnicegyu11 commented Dec 16, 2024

Tasks

Preview Give feedback
@mrnicegyu11 mrnicegyu11 self-assigned this Dec 16, 2024
@mrnicegyu11 mrnicegyu11 added p:high-prio t:infra-ops Adjustments to the way or resources with that microservices are run EPIC labels Dec 16, 2024
@mrnicegyu11 mrnicegyu11 added this to the Event Horizon milestone Dec 16, 2024
@mrnicegyu11
Copy link
Member Author

mrnicegyu11 commented Dec 16, 2024

Proposal - 16dec2024

Proposal new dalco-staging:

new-machine --> Manager --> osparc-staging-srv01
former osparc-srv08 --> simcore - worker --> osparc-staging-srv02
former osparc-srv09 --> ops  - worker--> osparc-staging-srv03
former osparc-srv07 --> GPU machine --> osparc-staging-srv04

Proposal new dalco-prod:

former ospars-srv01 - manager - new-name osparc-srv01
former ospars-srv02 - manager + ops + simcore - new-name osparc-srv02
former ospars-srv03 - manager + simcore + simcore - new-name osparc-srv03
former ospars-srv04 [this machine has 754 Gb RAM] - worker - new-name osparc-srv04
former ospars-srv05 [this machine has 128 Gb RAM, GPU]  - worker - new-name osparc-srv05
former ospars-srv06 [this machine has 64 Gb RAM, GPU]  - worker - new-name osparc-srv06
former ospars-srv10 [this machine has 128 Gb RAM, GPU]  - worker - new-name osparc-srv07

Proposal master

new server-machine, manager & ops --> osparc01.speag.com
new server-machine - 02, simcore & ops --> osparc02.speag.com
old osparc03 -> mounted into rack chassis by speag IT --> osparc03.speag.com
old osparc04 -> mounted into rack chassis by speag IT  --> osparc04.speag.com
old osparc06 -> mounted into rack chassis  by speag IT --> osparc06.speag.com

Proposal master-k8s:

new machine --> kubernetes manager --> osparc-master-k8s-01
former master01 --> desktop chassis, potentially keep in A120 office in desktop chassis as second k8s machines, osparc-master-k8s-02

probably to remove:

former master02: Has reported issues by the devs, services running there show weird behavior --> trash?
master05 --> trash?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
EPIC p:high-prio t:infra-ops Adjustments to the way or resources with that microservices are run
Projects
None yet
Development

No branches or pull requests

1 participant