Thanks Akila. Yes. InstanceType works as well based on cartridge json. I have a small example in the testing doc [1]. [2] lists the machine types. I did not test all of them. However, f1-micro, g1-small didn't work since their memory is low, and jclouds API complained about that. If needed we can circumvent this by specifying low memory requirement in GCEIaaS.java Rest of the types should work.
Yes. I guess GCE jclouds regions & zones should match well with stratos. One issue would be that zone name actually includes region (us-central1-f, etc). The jclouds apis just take the region name. DiskApi, InstanceApi, etc in [3] Let me know of any other clarification. [1] https://docs.google.com/document/d/1_UyglvcuNASxFbC6YK4zDoKohx9xiiqBNZqMiezkhzo [2] https://developers.google.com/compute/docs/machine-types [3] https://github.com/suriyapriya/stratos/blob/gce-4.0.0/components/org.apache.stratos.cloud.controller/src/main/java/org/apache/stratos/cloud/controller/iaases/GCEIaas.java Thanks Suriya On Wed, Aug 13, 2014 at 11:50 AM, Akila Ravihansa Perera <[email protected] > wrote: > Awesome work, Suriya! > > Sorry I couldn't join the live Hangout but I watched the demo and it's > really nice to see Stratos running on GCE. I would like to share few > things :) > > Does current implementation support GCE instance type given in > cartridge json? I didn't see the instanceType section in your demo > video. (please ignore if I missed that). If not, you could create a > support JIRA for that as well. > > GCE also has the concept of regions and availability zones. So I think > we can easily integrate Stratos partitions and network partitions > model with that of GCE. Any limitations from Jclouds API that > prohibits us from doing this? > > Again, very nice work...thank you for all your hard work. >
