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

Add instructions for accessing staging instance #542

Merged
merged 2 commits into from
Sep 23, 2024

Conversation

JenySadadia
Copy link
Collaborator

  • Add documentation for requesting a user account on staging instance and related information to use it
  • Remove early-access doc

As an early access phase has ended, remove
the documentation for it.

Signed-off-by: Jeny Sadadia <[email protected]>
@JenySadadia JenySadadia added the documentation Improvements or additions to documentation label Aug 15, 2024
doc/staging.md Outdated
Comment on lines 126 to 131
File storage is managed separately from the API services. An AzureFiles token is provided to each user to be able to upload
artifacts. It is one of the storage solutions supported by KernelCI, you may
also use SSH or soon any S3-compatible storage. There is a quota, currently
5TiB for all the Early Access files. Old files will be deleted after a while
5TiB for all the staging files. Old files will be deleted after a while
Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Hi @nuclearcat
I am not sure if this part is true for staging configs.
Could you please provide some insights?

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We dont have any policy right now (by request of @padovan ), still have to decide on that after LPC.

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Okay, then should I discard this?

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

yes

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Okay, thanks. As per our discussion today, I have dropped storage section and added details related to accessing staging containers.

doc/staging.md Outdated
Comment on lines 138 to 143
staging-azure-<your-username>:
storage_type: azure
base_url: https://kciapistagingstorage1.file.core.windows.net/
sas_public_token: "?sv=2022-11-02&ss=f&srt=sco&sp=r&se=2024-10-17T19:19:12Z&st=2023-10-17T11:19:12Z&spr=https&sig=sLmFlvZHXRrZsSGubsDUIvTiv%2BtzgDq6vALfkrtWnv8%3D"
Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@nuclearcat The same question as above for this.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yes, whole point probably is to rework concept of staging. I dont think we will give separate API accounts anymore (and especially storage).

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Okay, thanks for confirming.

@JenySadadia JenySadadia force-pushed the add-staging-doc branch 3 times, most recently from db955a3 to ca6909c Compare August 15, 2024 09:16
Add documentation for requesting user account on
staging instance and related information to use
it.

Signed-off-by: Jeny Sadadia <[email protected]>
@nuclearcat nuclearcat added this pull request to the merge queue Sep 23, 2024
Merged via the queue into kernelci:main with commit 823a31c Sep 23, 2024
6 checks passed
@JenySadadia JenySadadia deleted the add-staging-doc branch September 23, 2024 07:33
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
documentation Improvements or additions to documentation
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants