Infrastructure/ansible
3
0
Fork 0
Code Issues Pull requests 6 Projects Releases Packages Wiki Activity Actions

data_reports: create a new data-reports vm #1369

Merged
ryanlerch merged 1 commit from data-reports01 into main 2023-04-11 17:46:34 +00:00
Conversation 9 Commits 1 Files changed 4 +65
kevin commented 2023-04-10 19:48:36 +00:00
Contributor
Copy link

This vm is to allow the creation of reports about contibutor numbers
from datanommer db. It should be short lived. Once the reports are
developed, they can be moved to openshift or some other place.

Signed-off-by: Kevin Fenzi kevin@scrye.com

This vm is to allow the creation of reports about contibutor numbers from datanommer db. It should be short lived. Once the reports are developed, they can be moved to openshift or some other place. Signed-off-by: Kevin Fenzi <kevin@scrye.com>
kevin commented 2023-04-10 19:48:55 +00:00
Author
Contributor
Copy link

Metadata Update from @kevin:

  • Pull-request tagged with: freeze-break-request
**Metadata Update from @kevin**: - Pull-request tagged with: freeze-break-request
zuul commented 2023-04-10 19:54:10 +00:00
First-time contributor
Copy link

Build succeeded.
https://fedora.softwarefactory-project.io/zuul/buildset/491d8019947b4d55878389486088d460

Build succeeded. https://fedora.softwarefactory-project.io/zuul/buildset/491d8019947b4d55878389486088d460 - [fi-ansible-lint-diff ](https://fedora.softwarefactory-project.io/zuul/build/748915be97fc437a8cdce15f8a0abce8) : SUCCESS in 5m 05s - [fi-yamllint-diff ](https://fedora.softwarefactory-project.io/zuul/build/326c757d56ee430696d33b9eabb83f47) : SUCCESS in 3m 12s
nb commented 2023-04-10 21:51:30 +00:00
Contributor
Copy link

+1, although I was wondering if this was something that could be done in AWS?

+1, although I was wondering if this was something that could be done in AWS?
kevin commented 2023-04-10 22:07:08 +00:00
Author
Contributor
Copy link

It needs to be able to connect to db-datanommer02 via psql... so I don't think aws is practical. Otherwise that would work fine. ;)

It needs to be able to connect to db-datanommer02 via psql... so I don't think aws is practical. Otherwise that would work fine. ;)
smooge commented 2023-04-11 09:42:12 +00:00
Contributor
Copy link

+1 should not break anything

+1 should not break anything
kevin commented 2023-04-11 17:45:55 +00:00
Author
Contributor
Copy link

rebased onto ee244ae706

rebased onto ee244ae706b65e132bd8d23f86b160b75cbf01f0
kevin commented 2023-04-11 17:46:02 +00:00
Author
Contributor
Copy link

rebased onto ee244ae706

rebased onto ee244ae706b65e132bd8d23f86b160b75cbf01f0
kevin commented 2023-04-11 17:46:35 +00:00
Author
Contributor
Copy link

Pull-Request has been merged by kevin

Pull-Request has been merged by kevin
zuul commented 2023-04-11 17:52:24 +00:00
First-time contributor
Copy link

Build succeeded.
https://fedora.softwarefactory-project.io/zuul/buildset/70a8296ff5694b34816906cdc580eb83

Build succeeded. https://fedora.softwarefactory-project.io/zuul/buildset/70a8296ff5694b34816906cdc580eb83 - [fi-ansible-lint-diff ](https://fedora.softwarefactory-project.io/zuul/build/8ffa761f13334081a6e7f266e132ab54) : SUCCESS in 5m 44s - [fi-yamllint-diff ](https://fedora.softwarefactory-project.io/zuul/build/3150b3bb406c491c899ea97b685aa342) : SUCCESS in 3m 49s
Sign in to join this conversation.
Reviewers
No reviewers
Labels
Clear labels   
freeze-break-request

   
post-freeze
  
blocked

Indicates the work cannot proceed. There is a dependency or an issue that is preventing the team from completing the task. This is a flag for the Scrum Master to help unblock the team.

  
Bug

The software is not behaving as expected. It could be an error, a crash, or an incorrect result. Bugs often need to be prioritized based on their severity and business impact

  
Chore

Tasks that are necessary but don't directly deliver new value to the end-user. These are internal tasks like updating a library, managing user accounts, or setting up a new service.

  
Feature

It's something that a user would be able to see or interact with, such as a new button, a new page, or an improved workflow.

  
in-progress

This label is for work that a developer is actively working on. This is usually what you'll see on the "In Progress" column of your project board.

  
points:1

A task that is simple, small, and has very little uncertainty. It should be easy enough for any team member to pick up and complete quickly, without a lot of discussion or research.

  
points:13

Any task that feels like it's a "13" or more is considered an Epic. These are too large and uncertain to be worked on in a single sprint.

  
points:2

This is a task that is slightly more complex or larger than a "1." It might involve two or three simple steps, but the outcome is still very clear and there's little uncertainty.

  
points:3

medium-sized task with some noticeable complexity. It might require a bit more thought or collaboration. The steps are well-defined, but it's not a trivial change.

  
points:5

a significant piece of work. It has more complexity and a higher degree of uncertainty than smaller tasks. It might require some research, a design discussion, or collaboration across multiple teams.

  
points:8

complex task with a lot of uncertainty. It's often the largest size that a team will consider for a single sprint. It likely requires a detailed breakdown and multiple team members to complete.

  
priority:high

This is for work that is critical and needs to be addressed in the next sprint. It's often for urgent bugs, important features, or a major piece of technical debt that is blocking other work.

  
priority:low

This is for work that is good to do but not urgent. It's a candidate for being worked on when there's extra time or when it rises in importance. It can stay in the backlog for a longer period.

  
priority:medium

This is for important work that should be done soon, but isn't as urgent as a high-priority item. It will likely be considered for the next 1-2 sprints.

  
ready

indicates that an issue has been fully refined, has a story point value, and is ready to be pulled into a sprint. It has all the information needed for a developer to start working on it immediately.

  
review

This indicates that the work is complete, but it is now in a review state. This could mean a peer code review, a QA check, or a review by the Product Owner.

  
Technical Debt

work that improves the codebase without adding new features. It's work that pays down the "debt" you've accumulated, such as refactoring a messy piece of code, improving test coverage.

No labels
freeze-break-request
post-freeze
blocked
Bug
Chore
Feature
in-progress
points:1
points:13
points:2
points:3
points:5
points:8
priority:high
priority:low
priority:medium
ready
review
Technical Debt
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
4 participants
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference: Infrastructure/ansible#1369
No description provided.
Delete branch "data-reports01"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?