sodafoundation / controller Goto Github PK

Issue/Feature Description:
This Issue tracks the Analysis and Design of Overall User Management encompassing all the components of SODA [Including Defin , Catalog Services, Backend Secret Services etc.]

Why this issue to fixed / feature is needed(give scenarios or use cases):
To provide robust, user and identity management for SODA.

How to reproduce, in case of a bug:

Other Notes / Environment Information: (Please give the env information, log link or any useful information for this issue)
https://docs.google.com/document/d/1AStnHyht46BsISaxeIBsLiV7IBQYLL1tNyLskzOKNqM/edit

Issue/Feature Description:

• P3 : Roles to be created for
  - Multicloud User
  - On-Prem User
  - Admin User
  - CXO USer [optional]
  -
  Why this issue to fixed / feature is needed(give scenarios or use cases):

How to reproduce, in case of a bug:

Other Notes / Environment Information: (Please give the env information, log link or any useful information for this issue)

Issue/Feature Description:
Rename docker images to sodafoundation/controller

Why this issue to fixed / feature is needed(give scenarios or use cases):

How to reproduce, in case of a bug:

Other Notes / Environment Information: (Please give the env information, log link or any useful information for this issue)

Issue/Feature Description:
When the controller calls multiple docks, the dock selected by 'edp' may not be used to connect, but rather the previously connected dock.
This is the code:
pkg/controller/dockcontroller/client/client.go (func (c *DockClient) Connect(edp string) error)

Why this issue to fixed / feature is needed(give scenarios or use cases):
When I use multiple soda docks, only one dock is connected, that is not what I expected.

How to reproduce, in case of a bug:
When I start two soda docks, only one dock that was started first is connected.

Other Notes / Environment Information: (Please give the env information, log link or any useful information for this issue)
https://github.com/sodafoundation/controller/blob/30f5f72c23b5d770bc65fa18a75d3ff69be1f412/pkg/controller/dockcontroller/client/client.go#L53C4-L53C4

Is this a BUG REPORT or FEATURE REQUEST?:

Uncomment only one, leave it on its own line:

/kind feature

What happened:
Need to automate the Controller test cases for optimisation

What you expected to happen:
Automated test cases instead of manual

How to reproduce it (as minimally and precisely as possible):

Anything else we need to know?:

Environment:

• Hotpot(release/branch) version:
• OS (e.g. from /etc/os-release):
• Kernel (e.g. uname -a):
• Install tools:
• Others:

Issue/Feature Description:
Update Keystone to use latest release (18.xx)
Sanity of existing Features after upgrade.

Why this issue to fixed / feature is needed(give scenarios or use cases):

How to reproduce, in case of a bug:

Other Notes / Environment Information: (Please give the env information, log link or any useful information for this issue)

Open Qs. : Do we migrate users from previous Releases.

Issue/Feature Description:
Add unit tests and achieve coverage >70%

Why this issue to fixed / feature is needed(give scenarios or use cases):
To imporove code quality and covergae

How to reproduce, in case of a bug:

Other Notes / Environment Information: (Please give the env information, log link or any useful information for this issue)

Issue/Feature Description:

• Explore Resouce consumption and Performance monitoring APIs for various Cloud Backend providers.
• Try to use Real time APIs offered by Vendors as Agent based monitoring has vast scope.
• Data Collection and Storage is in Delfin Future Scope.
• Yig, Ceph : No resource utilization and performance monitoring methods defined.
• Explore tools like AWS Cloud Watch.

Why this issue to fixed / feature is needed(give scenarios or use cases):

How to reproduce, in case of a bug:

Other Notes / Environment Information: (Please give the env information, log link or any useful information for this issue)

Issue/Feature Description:
Add unit tests and achieve coverage >70%

Why this issue to fixed / feature is needed(give scenarios or use cases):
To imporove code quality and covergae

How to reproduce, in case of a bug:

Other Notes / Environment Information: (Please give the env information, log link or any useful information for this issue)

Issue/Feature Description:
Add unit tests and achieve coverage >70%

Why this issue to fixed / feature is needed(give scenarios or use cases):
To imporove code quality and covergae

How to reproduce, in case of a bug:

Other Notes / Environment Information: (Please give the env information, log link or any useful information for this issue)

Issue/Feature Description:
Add unit tests and achieve coverage >70%

Why this issue to fixed / feature is needed(give scenarios or use cases):
To imporove code quality and covergae

How to reproduce, in case of a bug:

Other Notes / Environment Information: (Please give the env information, log link or any useful information for this issue)

Is this a BUG REPORT or FEATURE REQUEST?:
Currently DB is accessed by two module, soda-apiserver and soda-controller. soda-controller usses DB just to update the status of provisioning service(For ex: after volume,fileshare creation, it update the status).

Since we are making hotpot to three seperate and independent project, let's remove the controller interaction with DB. And to update the status controller should sent the reuest to APISERVER only. And only API Server will update the status/anyother things. This way DB will be completly mange by API Server.
Let's do the POC.
i.e scenario 2 from below diagram

Uncomment only one, leave it on its own line:

/kind bug
/kind feature

What happened:

What you expected to happen:

How to reproduce it (as minimally and precisely as possible):

Anything else we need to know?:

Environment:

• Hotpot(release/branch) version:
• OS (e.g. from /etc/os-release):
• Kernel (e.g. uname -a):
• Install tools:
• Others:

Issue/Feature Description:
Identify Integration points with Delfin , Hotpot with Independent Identity Service

• Explore the integration points with all the other services of SODA .
• Seperate Identity and Usermanagement into a new Repository in SODA

Expected Output : Analysis doc , Integration Sample code

Why this issue to fixed / feature is needed(give scenarios or use cases):

• Modularization of Identity service
• Add integration points to Backend Credential Service Vault [Future]
• Make Identity Service Configurable.

How to reproduce, in case of a bug:

Other Notes / Environment Information: (Please give the env information, log link or any useful information for this issue)

Issue/Feature Description:
Add unit tests and achieve coverage >70%

Why this issue to fixed / feature is needed(give scenarios or use cases):
To imporove code quality and covergae

How to reproduce, in case of a bug:

Other Notes / Environment Information: (Please give the env information, log link or any useful information for this issue)

Issue/Feature Description:
Add unit tests and achieve coverage >70%

Why this issue to fixed / feature is needed(give scenarios or use cases):
To imporove code quality and covergae

How to reproduce, in case of a bug:

Other Notes / Environment Information: (Please give the env information, log link or any useful information for this issue)

Is this a BUG REPORT or FEATURE REQUEST?:

Uncomment only one, leave it on its own line:

/kind bug

What happened: Build is failed due to different protoc Versions

What you expected to happen: Build should be successful

How to reproduce it (as minimally and precisely as possible):

Anything else we need to know?:

Environment:

• Hotpot(release/branch) version:
• OS (e.g. from /etc/os-release):
• Kernel (e.g. uname -a):
• Install tools:
• Others:

Is this a BUG REPORT or FEATURE REQUEST?:

Uncomment only one, leave it on its own line:

/kind bug
/kind feature

What happened:
Add all the required test cases for Controller
What you expected to happen:

How to reproduce it (as minimally and precisely as possible):

Anything else we need to know?:

Environment:

• Hotpot(release/branch) version:
• OS (e.g. from /etc/os-release):
• Kernel (e.g. uname -a):
• Install tools:
• Others:

Issue/Feature Description:
Perform sanity of User Management Features w.r.t Admin and User Roles.
Fix any issues found.

Why this issue to fixed / feature is needed(give scenarios or use cases):

How to reproduce, in case of a bug:

Other Notes / Environment Information: (Please give the env information, log link or any useful information for this issue)

Sanity for User and Admin Roles for All the APIs [Backend CRUD, Bucket CRUD, Migration, Lifecycle, Hotpot functionality]
- Verify all the functionality for these roles
- User should have limited rights [mostly READ, Execute]

Issue/Feature Description:
If go version is 1.12, the build fails on proto file compile. This is can be fixed by exporting GO111MODULE=on from make file

Why this issue to fixed / feature is needed(give scenarios or use cases):
We need to support GO version 1.12

How to reproduce, in case of a bug:
run command 'make all' in a machine with GO version 1.12 installed

Other Notes / Environment Information: (Please give the env information, log link or any useful information for this issue)

Issue/Feature Description:
Add unit tests and achieve coverage >70%

Why this issue to fixed / feature is needed(give scenarios or use cases):
To imporove code quality and covergae

How to reproduce, in case of a bug:

Other Notes / Environment Information: (Please give the env information, log link or any useful information for this issue)

Issue/Feature Description:
Add unit tests and achieve coverage >70%

Why this issue to fixed / feature is needed(give scenarios or use cases):
To imporove code quality and covergae

How to reproduce, in case of a bug:

Other Notes / Environment Information: (Please give the env information, log link or any useful information for this issue)

Issue/Feature Description: Latest Libraries Check for the project

Why this issue to fixed / feature is needed(give scenarios or use cases): To check any dependency lag for the latest deployment frameworks

Issue/Feature Description:
Add unit tests and achieve coverage >70%

Why this issue to fixed / feature is needed(give scenarios or use cases):
To imporove code quality and covergae

How to reproduce, in case of a bug:

Other Notes / Environment Information: (Please give the env information, log link or any useful information for this issue)

Issue/Feature Description:
Add unit tests and achieve coverage >70%

Why this issue to fixed / feature is needed(give scenarios or use cases):
To imporove code quality and covergae

How to reproduce, in case of a bug:

Other Notes / Environment Information: (Please give the env information, log link or any useful information for this issue)

Issue/Feature Description:
Analysis of new services in Controller.

• Identity Service.
• Catalog service.
• Logging & Audit Service.
• Tiering Service.
• Config Service.

Why this issue to fixed / feature is needed(give scenarios or use cases):

• Dedicated independent services should be created for the core functionalities in the Controller layer, which can cater to the various domains i.e on-prem , cloud, container storages.

How to reproduce, in case of a bug:

Other Notes / Environment Information: (Please give the env information, log link or any useful information for this issue)

Is this a BUG REPORT or FEATURE REQUEST?:

/kind feature

What happened:
After separation of Hotpot project into SODA API/DOCK/CONTROLLER we need to update CI accordingly so that project can be run independently

What you expected to happen:
CI for Controller should run properly and independently

How to reproduce it (as minimally and precisely as possible):

Anything else we need to know?:

Environment:

• Hotpot(release/branch) version:
• OS (e.g. from /etc/os-release):
• Kernel (e.g. uname -a):
• Install tools:
• Others:

Issue/Feature Description:
The current CI across SODA Projects is being run using Travis CI. With the changes made to the free tier of Travis CI we are moving the CI for all the projects under SODA Foundation to GitHub Actions.
As part of this we need to move the CI for the Controller project to GitHub Actions

Why this issue to fixed / feature is needed(give scenarios or use cases):
Currently the CI jobs are getting queued across the SODA Organisation and this is causing delays in the CI's being run if there are many PRs raised across projects. This delays PR reviews and merging. Moving to Github actions will run the CI independently.

How to reproduce, in case of a bug:

Other Notes / Environment Information: (Please give the env information, log link or any useful information for this issue)