Reporting utilities don't all work in Azure

Consonance / consonance

Core consonance utilities for scheduling, reporting on, and provisioning VMs for workflows

GNU General Public License v3.0

14 stars 5 forks source link

Reporting utilities don't all work in Azure #84

Open SolomonShorser-OICR opened 9 years ago

SolomonShorser-OICR commented 9 years ago

reports status and reports provisioned seem to rely on AWS libraries, they don't work in azure:

$ java -cp reporting.jar  info.pancancer.arch3.reportcli.ReportCLI --config config/masterConfig.ini status 
Sep 24, 2015 4:28:17 PM com.amazonaws.auth.profile.internal.ProfilesConfigFileLoader onProfileProperty
INFO: Skip unsupported property name region in profile [default].
Sep 24, 2015 4:28:17 PM com.amazonaws.auth.profile.internal.ProfilesConfigFileLoader onProfileProperty
INFO: Skip unsupported property name output in profile [default].

denis-yuen commented 9 years ago

They probably don't work at all. I could not decipher how to get back private ip addresses from the Azure API and we rely upon that a lot in the reporting tools.

gmihaiescu commented 9 years ago

Can you obtain the ip address locally? I would use something like facter that can cleanly display a lot of useful info.

denis-yuen commented 9 years ago

It would probably be better to explore their API further. The reporting utilities are stateless in the sense that they get all their information from the cloud APIs, the worker daemon running on the actual VM would need to report its own ip address to Azure which would be weird.