cloudstack-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From anshul1886 <>
Subject [GitHub] cloudstack issue #1278: CLOUDSTACK-9198: Virtual router gets deployed in dis...
Date Tue, 07 Mar 2017 06:56:38 GMT
Github user anshul1886 commented on the issue:
    @rafaelweingartner, Basically CallContext.current().getCallingAccount(); is setting the
proper context which is later used. If you have observed in code all the api calls have a
similar call before proceeding further. One random example:
     @ActionEvent(eventType = EventTypes.EVENT_VOLUME_UPLOAD, eventDescription = "uploading
volume", async = true)
        public VolumeVO uploadVolume(UploadVolumeCmd cmd) throws ResourceAllocationException
            Account caller = CallContext.current().getCallingAccount(); 
    For more details refer
and commits 7928963 and 11e1e58  which I have mentioned earlier.
    Hopefully this clears your doubts.

If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at or file a JIRA ticket
with INFRA.

View raw message