-
Notifications
You must be signed in to change notification settings - Fork 17
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
Conversation
As an early access phase has ended, remove the documentation for it. Signed-off-by: Jeny Sadadia <[email protected]>
doc/staging.md
Outdated
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 |
There was a problem hiding this comment.
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?
There was a problem hiding this comment.
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.
There was a problem hiding this comment.
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?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
yes
There was a problem hiding this comment.
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
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" |
There was a problem hiding this comment.
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.
There was a problem hiding this comment.
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).
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Okay, thanks for confirming.
db955a3
to
ca6909c
Compare
Add documentation for requesting user account on staging instance and related information to use it. Signed-off-by: Jeny Sadadia <[email protected]>
ca6909c
to
61bd32c
Compare
early-access
doc