[
https://issues.apache.org/jira/browse/CLOUDSTACK-6826?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14169611#comment-14169611
]
Nitin Mehta commented on CLOUDSTACK-6826:
-----------------------------------------
Issue1 - When download urls expire (after extract.url.expiration.interval) the
deletion was sent to a random ssvm in the zone instead of the ssvm on which the
symlink for the url was created
Fix - Improving the download url expiration where the expiration work would be
handled by the ssvm that has the corresponding symlink created on it. This is
done by figuring out the ssvm from the public ip of the url created and then
while cleaning up the url send command to the right ssvm. In case the ssvm
doesnt exist send it to any ssvm and cleanup any artifacts if any (like volume).
Issue 2 - When ssvm is destroyed download urls were not expired immediately and
they were not usable
Fix - When any ssvm is destroyed expire all the urls in the zone but setting
the download url created time in store ref tables.
QA Notes -
You can create multiple ssvm in the zone and make sure url expiration is sent
to right ssvm
In case ssvm is in alert state make sure there is right error there.
In case ssvm is destroyed or doesnt exist make sure artifacts (like volume)
are still cleaned up
Try this for http and https urls.
When ssvm is destroyed make sure urls get expired all of them cleaned up in
next cycle.
> Ability to gracefully expire urls and clean them up when ssvm is destroyed
> --------------------------------------------------------------------------
>
> Key: CLOUDSTACK-6826
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6826
> Project: CloudStack
> Issue Type: Improvement
> Security Level: Public(Anyone can view this level - this is the
> default.)
> Affects Versions: 4.4.0
> Reporter: Nitin Mehta
> Assignee: Nitin Mehta
> Fix For: 4.5.0
>
>
> There should be ability to gracefully expire urls and clean them up before
> ssvm is destroyed. Currently ssvm can be destroyed even if the agent is in
> alert state. Also the cleanup mechanism needs to be enahanced to take care of
> multiple ssvms and sending the cleaning up command to the right ssvm.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
