Project

General

Profile

Actions
Copy link

Task #2011

closed

Access to Floyd.

Added by Jan Iversen over 7 years ago. Updated over 7 years ago.

Status:
Closed
Priority:
Normal
Assignee:
Christian Lohmaier
Category:
-
Target version:
Team - Pool
Start date:
Due date:
% Done:

0%

Tags:
URL:

Description

Once the current move/cleanup from gitlab has been done, I would like to (if possible) to have access to floyd, so I can activate salt changes.

Actions
Copy link
 #1

Updated by Florian Effenberger over 7 years ago

  • Assignee set to Christian Lohmaier
  • Target version set to Pool
Actions
Copy link
 #2

Updated by Jan Iversen over 7 years ago

If we stay with gitlab (I did not really understand the reasons to change), then it would of course be practical to have access before.

Cloph@, would be nice if we could 10 minutes on walking through the SALT setup on floyd.

Actions
Copy link
 #3

Updated by Jan Iversen over 7 years ago

I have added myself to default_users, which floyd uses, but floyd needs to be updated.

I have no problem, with not having access (actually it is better), but then we need to have some automatic update, when commits for vms are pushed. For now I have ~8 commits that are pushed but not activated (missing update on floyd)

Actions
Copy link
 #4

Updated by Florian Effenberger over 7 years ago

I have added myself to default_users, which floyd uses, but floyd needs
to be updated.

What do you mean by updated? Salt histate run?

Actions
Copy link
 #5

Updated by Jan Iversen over 7 years ago

I assume that, but I am not a specialist in the floyd setup.

Cloph is busy with the virtualization problems, but it is a theme for tonights infra call.

Actions
Copy link
 #6

Updated by Florian Effenberger over 7 years ago

  • Status changed from New to Closed
Actions
Copy link

Also available in: Atom PDF