-
Notifications
You must be signed in to change notification settings - Fork 14
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
feat(openstack-aws): Add owner/lifetime info in VM's metadata #207
feat(openstack-aws): Add owner/lifetime info in VM's metadata #207
Conversation
1e875ef
to
4353266
Compare
First of all thanks for the PR very much. Let us re-visit changes. Just a note also a title of PR must comply with commit message check i have changed it a bit. |
500c9bb
to
1718a4f
Compare
Updated code in two commits |
1718a4f
to
ae35a3f
Compare
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.
Comments added, but in general:
- I'd avoid excessive writes on "info" level. We could be more chatty on debug level, but still on the extend that it is usable for somebody who is investigating an issue.
- methods should not only what their name says
- unit tests needs fixing (I didn't look to deep in it, but probably global context is not initialized)
- you might check with @Tiboris about the gssapi import - it being optional
bd1753d
to
4aaa042
Compare
b2e9b63
to
91bde71
Compare
@kaleemsiddiqu could you please also add line (with some comment)
to the https://github.com/neoave/mrack/blob/main/src/mrack/data/mrack.conf ? |
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.
I've tested various scenarios and it works well.
So the only remaining part is the mrack.spec
discussion. Otherwise it is good from my PoV.
Doc changes can be done in a separate MR.
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.
Please add
Requires: python3-gssapi
after line https://github.com/neoave/mrack/blob/main/mrack.spec#L46
Owner and lifetime info will be added into VM's metadata for Openstack provider. This info will give info who owns the VM and what is the lifetime of the VM which will be used for notifying owners and cleaning up the resources based on lifetime of the VMs. If owner info not fetched, user notified with custom error message for follow up action to take up. Signed-off-by: ksiddiqu <[email protected]>
Owner and lifetime info will be added into VM's metadata for AWS provider. This info will give info who owns the VM and what is the lifetime of the VM which will be used for notifying owners and cleaning up the resources based on lifetime of the VMs. If owner info not fetched, user notified with custom error message for follow up action to take up. Signed-off-by: ksiddiqu <[email protected]>
Integration test test_actions.py failing due to introduction of new option(require-owner) in mrack.conf as global_context was not set which is now being set using a fixture in test_actions.py Signed-off-by: ksiddiqu <[email protected]>
91bde71
to
4f681b5
Compare
Thanks @kaleemsiddiqu for all the changes you did and updates. I would like to kindly ask you to change the spec file to add:
after line https://github.com/neoave/mrack/blob/main/mrack.spec#L46 which will create weak dependency on the package. With addition to setup.py (https://github.com/neoave/mrack/blob/main/setup.py#L56 ) :
|
gssapi pkg now required for new added mrack feature to add owner/lifetime info into the VM Signed-off-by: ksiddiqu <[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.
Thanks for the patch @kaleemsiddiqu fixes and patience lets ship this ! :)
Owner and lifetime info will be added into VM's metadata for Openstack/AWS providers. This info will give info who owns the VM and what is the lifetime of the VM which will be used for notifying owners and cleaning up the resources based on lifetime of the VMs.
If owner info not fetched, user notified with custom error message for follow up action to take up.
Signed-off-by: ksiddiqu [email protected]