Mitigate confilict between cc1, cc2 and cg1

erans / ec2instancespricing

Quick and dirty Python API and CLI to get EC2 instance pricing for On-Demand and Reserved Instances

Other

175 stars 89 forks source link

Mitigate confilict between cc1, cc2 and cg1 #4

Closed CitizenOfRome closed 11 years ago

CitizenOfRome commented 11 years ago

cc1 and cc2 shared the same ID and therefore their data was getting mixed up. Also, I had wrongly identified clusterGPUI as cc2 when it should've been cg1 Reference: http://stackoverflow.com/a/9840802/937891

erans commented 11 years ago

Thanks. When I started this I don't think there was cg1 and all... :-)

CitizenOfRome commented 11 years ago

:) There wasn't They apparently renamed the older cc2 as cg1 And what they now call cc2 is actually a part of cc1 Really strange ...

erans commented 11 years ago

I see. That's really weird.

Eran

On Wed, Nov 21, 2012 at 3:39 PM, Sathvik Ponangi notifications@github.comwrote:

:) There wasn't They apparently renamed the older cc2 as cg1 And what they now call cc2 is actually a part of cc1 Really strange ...

— Reply to this email directly or view it on GitHubhttps://github.com/erans/ec2instancespricing/pull/4#issuecomment-10597110.