Lakmal, We took a quick look at this issue , and it is not simple. The jclouds class stratos uses has no concept of network interfaces. Maybe there is anther jclouds class that stratos can use ? Otherwise we need to extent the current compute class.
What we are looking to do is to be able to select a subset of available network to connect to a cartridge. Currently in stratos-M6 what happens is that all interfaces are always assigned to all cartridges in RANDOM order. The problem of pre-assigning IP addresses to cartridges is a bit different. I am not convinced that it is just a stratos issue. Is there a way to do that in Jclouds ? I know that it can be done in openstack. Thanks. Luca On 01/29/2014 10:04 AM, Lakmal Warusawithana wrote: > Hi devs, > > Last couple of days I worked with some stratos use-case which running top of > OpenStacks. I have identified some limitation when OpenStack provide multiple > network interfaces. Here some scenarios we should support IMO > > * If multiple network available in IaaS layer, we should give which network > interface assign IP addresses. > * Also some cases, User need to assign pre assign IP addresses (IP pool) for > particular cartridge type. > > > Also, even Stratos architecture support to identifying fine-grain IaaS > resource > locations (for a e.g Region, zone, cell, host ..etc) with the jclouds > limitation, we could not control IaaS that far. we need to check how we can > overcome that. > > -- > Lakmal Warusawithana > Software Architect; WSO2 Inc. > Mobile : +94714289692 > Blog : http://lakmalsview.blogspot.com/ >
