-
Notifications
You must be signed in to change notification settings - Fork 116
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
[gov][pcac]: Correcting the document title #3119
base: master
Are you sure you want to change the base?
[gov][pcac]: Correcting the document title #3119
Conversation
Based on the discussion in anuket-project#3045 Signed-off-by: Gergely Csatari <[email protected]>
I would rather ask an Anuket clean and basically to remove common and gov. |
Signed-off-by: Gergely Csatari <[email protected]>
I agree that on the long run we should consolidate these, but I would not just remove them as there are lots of valuable things there. |
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.
Approved
Signed-off-by: Gergely Csatari <[email protected]>
Signed-off-by: Gergely Csatari <[email protected]>
Signed-off-by: Gergely Csatari <[email protected]>
doc/common/chapter00.rst
Outdated
3. **Separation of concerns:** to promote lifecycle independence of | ||
different architectural layers and modules (e.g., disaggregation of | ||
software from hardware). | ||
4. **Automated lifecycle management:** to minimise the |
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.
LCM of what? If workloads, then "target zero downtime" is reasonable but if infrastructure then that is not.
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.
@pgoyal01 This is about the RM, therefore about infrastructure. Maybe we should remove the zero downtime requirement?
Co-authored-by: Pankaj Goyal <[email protected]>
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.
Because of RTD forcing the use of .readthedocs.yaml, we don't have another choice than splitting the git repository per stream. This PR must be applied on next RM's git repository and not here.
Everything is already ready on my own repositories but sadly I don't have the rights needed on anuket-project organization. Please give me them to complete the migration.
Be free to ask for any detail about the migration during a Weekly Technical meeting.
Based on the discussion in #3045