On 02/03/14 22:37, Nirmal Fernando wrote:
>
>
> On Monday, February 3, 2014, Lakmal Warusawithana <[email protected]
> <mailto:[email protected]>> wrote:
>
> Hi Nirmal,
>
> I think this is exactly what Jeffrey also mention in this mailing
> thread. How can we patch CC with this?
>
> So, we need to patch relevant IaaS provider implementation.
>
>
> Then next question is how can pass these information to CC. IMO we
> need to put some information into cartridge definition, to select
> subnet when it spinning up.
>
> Yes, this again can be an optional property in cartridge definition.
This sounds like it has potential. One thing we should look into is how
to make it user friendly.
UUIDs are not very nice when you try to add interfaces to a cartridge.
Maybe there is a way to pick by name ?
Luca
>
>
>
> On Mon, Feb 3, 2014 at 10:17 PM, Nirmal Fernando
> <[email protected]> wrote:
>
> Absolutely!
>
> Hi Luca,
>
> So what you expect is to provide a sub-set of network UUIDs to
> a Cartridge instance that will start by Stratos, right? And am
> I correct to assume that you as the creator of your IaaS is
> aware of the UUIDs of all network interfaces in your IaaS? If
> this is what you expect, I think jClouds' server API is
> already support this feature via CreateServerOptions#networks.
>
>
>
>
> On Mon, Feb 3, 2014 at 10:01 PM, Lakmal Warusawithana
> <[email protected]> wrote:
>
> Hi Nirmal,
>
> Since you are closely working on jclouds, you can work
> with Luca and team on this. We are highly appreciate more
> contributors coming on-board with Stratos :)
>
>
> On Mon, Feb 3, 2014 at 9:53 PM, Nirmal Fernando
> <[email protected]> wrote:
>
> Hi All,
>
> Yes, I'll start looking into this.
>
>
> On Mon, Feb 3, 2014 at 9:50 PM, Lakmal Warusawithana
> <[email protected]> wrote:
>
> Hi Luca,
>
> True, we should look into extending jclouds,
> Nirmal also going to start working on this.
>
> thanks
>
>
> On Mon, Feb 3, 2014 at 9:00 PM, Luca Martini
> <[email protected]> wrote:
>
>
> Lakmal,
>
> 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.
> Luca
>
>
> 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 protected]
> > <mailto:[email protected]>> wrote:
> >
> > 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
> >
>
>
>
> --
> Best Regards,
> Nirmal
>
> Nirmal Fernando.
> PPMC Member & Committer of Apache Stratos,
> Senior Software Engineer, WSO2 Inc.
>
> Blog: http://nirmalfdo.blogspot.com/
>
