Hi Luca,True, we should look into extending jclouds, Nirmal also going to start working on this.thanksOn Mon, Feb 3, 2014 at 9:00 PM, Luca Martini <firstname.lastname@example.org> wrote:
We really need to look at extending jclouds , otherwise will will have
the same issue with multiple IaaS in the future.
We are looking into this now.
On 01/29/14 11:29, Lakmal Warusawithana wrote:
> Hi Luca,
> What I realized that, some functionality which provide by OpenStack,
> we cant call from jclouds. First will see how easy to extent jclouds
> to provide them. Otherwise we need to think about how we can directly
> support OpenStack API IMO.
> On Wed, Jan 29, 2014 at 11:07 PM, Luca Martini <email@example.com
> <mailto:firstname.lastname@example.org>> wrote:
> 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
> 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
> > 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/
> Lakmal Warusawithana
> Software Architect; WSO2 Inc.
> Mobile : +94714289692
> Blog : http://lakmalsview.blogspot.com/