date:20180305

Re: GSoC ideas for the 2018 edition

2018-03-05 Thread Khosrow Moossavi

Cool! +1


On Mon, Mar 5, 2018 at 4:13 PM, Daan Hoogland 
wrote:

> fixed
>
> On Mon, Mar 5, 2018 at 7:43 PM, Khosrow Moossavi 
> wrote:
>
> > Hi Daan
> >
> > I just noticed filter for issues on gsoc2018 [1] doesn't show all of them
> > when filtered by CLOUDSTACK
> > project, if you haven't logged in. Is there a security setting somewhere
> to
> > make them public?
> >
> > I guess it would be better for anyone to see the list, and not make them
> to
> > register first.
> >
> > [1]: http://s.apache.org/gsoc2018ideas
> >
> > Khosrow Moossavi
> >
> > 
> >
> >
> >
> > On Mon, Jan 22, 2018 at 4:21 AM, Daan Hoogland 
> > wrote:
> >
> > > devs,
> > >
> > > Google Summer of Code is coming again. Apache is applying as
> organisation
> > > and we can hitch on that.
> > > I know we have a lot of ideas with varying probability of success for
> > which
> > > we have no time ourselves.
> > > Let me share some relevant information:
> > >
> > >
> > > Google Summer of Code [1] is a program sponsored by Google allowing
> > > students to spend their summer
> > > working on open source software. Students will receive stipends for
> > > developing open source software
> > > full-time for three months. Projects will provide mentoring and project
> > > ideas, and in return have
> > > the chance to get new code developed and - most importantly - to
> identify
> > > and bring in new committers.
> > >
> > > The ASF will apply as a participating organization meaning individual
> > > projects don't have to apply
> > > separately.
> > >
> > > If you want to participate with your project we ask you to do the
> > following
> > > things as soon as
> > > possible but please no later than 2017-01-30:
> > >
> > > 1. understand what it means to be a mentor [2].
> > >
> > > 2. record your project ideas.
> > >
> > > Just create issues in JIRA, label them with gsoc2018, and they will
> show
> > up
> > > at [3]. Please be as
> > > specific as possible when describing your idea. Include the programming
> > > language, the tools and
> > > skills required, but try not to scare potential students away. They are
> > > supposed to learn what's
> > > required before the program starts.
> > >
> > > Mark those projects with the label GSoC2018 and
> > > u
> > > se
> > >  additional
> > > labels, e.g. for the programming language (java, c, c++, erlang,
> python,
> > > brainfuck, ...) or
> > > technology area (cloud, xml, web, foo, bar, ...)
> > > Share those label with the rest of us devs, for instance on this
> thread.
> > >
> > >
> > > 
> > > [4] contains some additional information (will be updated for 2017
> > > shortly).
> > >
> > > 3. subscribe to ment...@community.apache.org; restricted to potential
> > > mentors, meant to be used as a
> > > private list - general discussions on the public
> > d...@community.apache.org
> > > list as much as possible
> > > please). Use a recognized address when subscribing (@apache.org or one
> > of
> > > your alias addresses on
> > > record).
> > >
> > > Note that the ASF isn't accepted as a participating organization yet,
> > > nevertheless you *have to*
> > > start recording your ideas now or we will not get accepted.
> > >
> > > Over the years we were able to complete hundreds of projects
> > successfully.
> > > Some of our prior
> > > students are active contributors now! Let's make this year a success
> > again!
> > >
> > >
> > > [1] https://summerofcode.withgoogle.com/
> > > [2] http://community.apache.org/guide-to-being-a-mentor.html
> > > [3] http://s.apache.org/gsoc2018ideas
> > > [4] http://community.apache.org/gsoc.html
> > >
> > > --
> > > Daan
> > >
> >
>
>
>
> --
> Daan
>

Re: GSoC ideas for the 2018 edition

2018-03-05 Thread Daan Hoogland

fixed

On Mon, Mar 5, 2018 at 7:43 PM, Khosrow Moossavi 
wrote:

> Hi Daan
>
> I just noticed filter for issues on gsoc2018 [1] doesn't show all of them
> when filtered by CLOUDSTACK
> project, if you haven't logged in. Is there a security setting somewhere to
> make them public?
>
> I guess it would be better for anyone to see the list, and not make them to
> register first.
>
> [1]: http://s.apache.org/gsoc2018ideas
>
> Khosrow Moossavi
>
> 
>
>
>
> On Mon, Jan 22, 2018 at 4:21 AM, Daan Hoogland 
> wrote:
>
> > devs,
> >
> > Google Summer of Code is coming again. Apache is applying as organisation
> > and we can hitch on that.
> > I know we have a lot of ideas with varying probability of success for
> which
> > we have no time ourselves.
> > Let me share some relevant information:
> >
> >
> > Google Summer of Code [1] is a program sponsored by Google allowing
> > students to spend their summer
> > working on open source software. Students will receive stipends for
> > developing open source software
> > full-time for three months. Projects will provide mentoring and project
> > ideas, and in return have
> > the chance to get new code developed and - most importantly - to identify
> > and bring in new committers.
> >
> > The ASF will apply as a participating organization meaning individual
> > projects don't have to apply
> > separately.
> >
> > If you want to participate with your project we ask you to do the
> following
> > things as soon as
> > possible but please no later than 2017-01-30:
> >
> > 1. understand what it means to be a mentor [2].
> >
> > 2. record your project ideas.
> >
> > Just create issues in JIRA, label them with gsoc2018, and they will show
> up
> > at [3]. Please be as
> > specific as possible when describing your idea. Include the programming
> > language, the tools and
> > skills required, but try not to scare potential students away. They are
> > supposed to learn what's
> > required before the program starts.
> >
> > Mark those projects with the label GSoC2018 and
> > u
> > se
> >  additional
> > labels, e.g. for the programming language (java, c, c++, erlang, python,
> > brainfuck, ...) or
> > technology area (cloud, xml, web, foo, bar, ...)
> > Share those label with the rest of us devs, for instance on this thread.
> >
> >
> > 
> > [4] contains some additional information (will be updated for 2017
> > shortly).
> >
> > 3. subscribe to ment...@community.apache.org; restricted to potential
> > mentors, meant to be used as a
> > private list - general discussions on the public
> d...@community.apache.org
> > list as much as possible
> > please). Use a recognized address when subscribing (@apache.org or one
> of
> > your alias addresses on
> > record).
> >
> > Note that the ASF isn't accepted as a participating organization yet,
> > nevertheless you *have to*
> > start recording your ideas now or we will not get accepted.
> >
> > Over the years we were able to complete hundreds of projects
> successfully.
> > Some of our prior
> > students are active contributors now! Let's make this year a success
> again!
> >
> >
> > [1] https://summerofcode.withgoogle.com/
> > [2] http://community.apache.org/guide-to-being-a-mentor.html
> > [3] http://s.apache.org/gsoc2018ideas
> > [4] http://community.apache.org/gsoc.html
> >
> > --
> > Daan
> >
>



-- 
Daan

Include resource tags in the usage record for chargebacks

2018-03-05 Thread Syed Ahmed

Hi Guys,

Currently the usage record in CloudStack doesn't include the resource tags
and we are having more and more use cases where we feel like including tags
will immensely help with the chargeback logic. Currently, we go back and
query Cloudstack to give us the tags associated with a resource. What do
you guys think about adding tags as a field in the usage record?

Thanks,
-Syed

Re: GSoC ideas for the 2018 edition

2018-03-05 Thread Khosrow Moossavi

Hi Daan

I just noticed filter for issues on gsoc2018 [1] doesn't show all of them
when filtered by CLOUDSTACK
project, if you haven't logged in. Is there a security setting somewhere to
make them public?

I guess it would be better for anyone to see the list, and not make them to
register first.

[1]: http://s.apache.org/gsoc2018ideas

Khosrow Moossavi





On Mon, Jan 22, 2018 at 4:21 AM, Daan Hoogland 
wrote:

> devs,
>
> Google Summer of Code is coming again. Apache is applying as organisation
> and we can hitch on that.
> I know we have a lot of ideas with varying probability of success for which
> we have no time ourselves.
> Let me share some relevant information:
>
>
> Google Summer of Code [1] is a program sponsored by Google allowing
> students to spend their summer
> working on open source software. Students will receive stipends for
> developing open source software
> full-time for three months. Projects will provide mentoring and project
> ideas, and in return have
> the chance to get new code developed and - most importantly - to identify
> and bring in new committers.
>
> The ASF will apply as a participating organization meaning individual
> projects don't have to apply
> separately.
>
> If you want to participate with your project we ask you to do the following
> things as soon as
> possible but please no later than 2017-01-30:
>
> 1. understand what it means to be a mentor [2].
>
> 2. record your project ideas.
>
> Just create issues in JIRA, label them with gsoc2018, and they will show up
> at [3]. Please be as
> specific as possible when describing your idea. Include the programming
> language, the tools and
> skills required, but try not to scare potential students away. They are
> supposed to learn what's
> required before the program starts.
>
> Mark those projects with the label GSoC2018 and
> u
> se
>  additional
> labels, e.g. for the programming language (java, c, c++, erlang, python,
> brainfuck, ...) or
> technology area (cloud, xml, web, foo, bar, ...)
> Share those label with the rest of us devs, for instance on this thread.
>
>
> 
> [4] contains some additional information (will be updated for 2017
> shortly).
>
> 3. subscribe to ment...@community.apache.org; restricted to potential
> mentors, meant to be used as a
> private list - general discussions on the public d...@community.apache.org
> list as much as possible
> please). Use a recognized address when subscribing (@apache.org or one of
> your alias addresses on
> record).
>
> Note that the ASF isn't accepted as a participating organization yet,
> nevertheless you *have to*
> start recording your ideas now or we will not get accepted.
>
> Over the years we were able to complete hundreds of projects successfully.
> Some of our prior
> students are active contributors now! Let's make this year a success again!
>
>
> [1] https://summerofcode.withgoogle.com/
> [2] http://community.apache.org/guide-to-being-a-mentor.html
> [3] http://s.apache.org/gsoc2018ideas
> [4] http://community.apache.org/gsoc.html
>
> --
> Daan
>

Re: Refusing to design this network, the physical isolation type is not BCF_SEGMENT

2018-03-05 Thread Nux!

And thank you for fixing it!

--
Sent from the Delta quadrant using Borg technology!

Nux!
www.nux.ro

- Original Message -
> From: "Nicolas Vazquez" 
> To: "dev" 
> Sent: Monday, 5 March, 2018 11:16:44
> Subject: Re: Refusing to design this network, the physical isolation type is 
> not BCF_SEGMENT

> Solved, thanks for testing and raising the issue! This will be included on
> 4.11.1
> 
> 
> From: Nux! 
> Sent: Thursday, February 8, 2018 1:03:29 PM
> To: dev
> Subject: Re: Refusing to design this network, the physical isolation type is 
> not
> BCF_SEGMENT
> 
> Tested, now I can add L2 network on the back of vxlan phsyical network, but I
> have found a problem.
> 
> It doesn't seem to like VNI ids higher than those for VLANs which is 4096,
> however VXLAN's max id is about 16 millions, so this is a problem that needs a
> fix.
> 
> Here are some logs:
> 
> 2018-02-08 15:50:00,738 WARN  [resource.wrapper.LibvirtStartCommandWrapper]
> (agentRequest-Handler-4:null) (logid:bd9fbea5) InternalErrorException
> com.cloud.exception.InternalErrorException: Failed to create vnet 3:
> RTNETLINK answers: Numerical result out of rangeCannot find device
> "bond0.3"Failed to create vlan 3 on pif: bond0.
> 
> --
> Sent from the Delta quadrant using Borg technology!
> 
> Nux!
> www.nux.ro
> 
> 
> nicolas.vazq...@shapeblue.com
> www.shapeblue.com
> ,
> @shapeblue
>  
> 
> 
> - Original Message -
>> From: "Nux!" 
>> To: "dev" 
>> Sent: Thursday, 8 February, 2018 14:29:36
>> Subject: Re: Refusing to design this network, the physical isolation type is 
>> not
>> BCF_SEGMENT
> 
>> Thanks! Any idea where blueorangutan keeps the rpms?
>>
>> --
>> Sent from the Delta quadrant using Borg technology!
>>
>> Nux!
>> www.nux.ro
>>
>> - Original Message -
>>> From: "Nicolas Vazquez" 
>>> To: "dev" 
>>> Sent: Wednesday, 7 February, 2018 12:12:00
>>> Subject: Re: Refusing to design this network, the physical isolation type 
>>> is not
>>> BCF_SEGMENT
>>
>>> I have pushed a fix for this on PR 2448. Can you please test it?
>>>
>>> 
>>> From: Nux! 
>>> Sent: Tuesday, February 6, 2018 10:25:07 AM
>>> To: dev
>>> Subject: Re: Refusing to design this network, the physical isolation type 
>>> is not
>>> BCF_SEGMENT
>>>
>>> Thanks Nicolas, much appreciated.
>>> Once you have a patch, feel free to ping me so I can test.
>>>
>>> --
>>> Sent from the Delta quadrant using Borg technology!
>>>
>>> Nux!
>>> www.nux.ro
>>>
>>>
>>> nicolas.vazq...@shapeblue.com
>>> www.shapeblue.com
>>> ,
>>> @shapeblue
>>>
>>>
>>>
>>> - Original Message -
 From: "Nicolas Vazquez" 
 To: "dev" 
 Sent: Tuesday, 6 February, 2018 13:23:54
 Subject: Re: Refusing to design this network, the physical isolation type 
 is not
 BCF_SEGMENT
>>>
 Hi Lucian,


 Thanks for posting this issue. I have checked the canHandle() method on
 VxlanGuestNetworkGuru and it is not considering L2 network offerings, only
 Isolated, so it refuses to design the network. I'll make sure to include a 
 fix
 for it on 4.11.1.


 Thanks,

 Nicolas

 
 From: Nux! 
 Sent: Tuesday, February 6, 2018 8:30:03 AM
 To: dev
 Subject: [L2 network] [VXLAN] Refusing to design this network, the physical
 isolation type is not BCF_SEGMENT

 Hi,

 I'm trying to add an L2 network based on a VXLAN physical network and I am
 getting the error in the subject.

 If I use a VLAN based physical network all completes successfully and I 
 end up
 with an L2 network in green "Setup" state.

 Here are some more logs:

 2018-02-06 11:20:27,748 DEBUG [c.c.n.NetworkServiceImpl]
 (qtp788117692-390:ctx-f1a980be ctx-61be30e8) (logid:0ca0c866) Found 
 physical
 network id=201 based on requested tags mellanoxvxlan
 2018-02-06 11:20:27,749 DEBUG [c.c.n.NetworkServiceImpl]
 (qtp788117692-390:ctx-f1a980be ctx-61be30e8) (logid:0ca0c866) Found 
 physical
 network id=201 based on requested tags mellanoxvxlan
 2018-02-06 11:20:27,766 DEBUG [c.c.n.g.BigSwitchBcfGuestNetworkGuru]
 (qtp788117692-390:ctx-f1a980be ctx-61be30e8) (logid:0ca0c866) Refusing to
 design this network, the physical isolation type is not BCF_SEGMENT
 2018-02-06 11:20:27,766 DEBUG [o.a.c.n.c.m.ContrailGuru]
 (qtp788117692-390:ctx-f1a980be ctx-61be30e8) (logid:0ca0c866) Refusing to
 design this network
 2018-02-06 11:20:27,767 DEBUG [c.c.n.g.NiciraNvpGuestNetworkGuru]
 (qtp788117692-390:ctx-f1a980be ctx-61be30e8) (logid:0ca0c866) Refusing to

Re: Refusing to design this network, the physical isolation type is not BCF_SEGMENT

2018-03-05 Thread Nicolas Vazquez

Solved, thanks for testing and raising the issue! This will be included on 
4.11.1


From: Nux! 
Sent: Thursday, February 8, 2018 1:03:29 PM
To: dev
Subject: Re: Refusing to design this network, the physical isolation type is 
not BCF_SEGMENT

Tested, now I can add L2 network on the back of vxlan phsyical network, but I 
have found a problem.

It doesn't seem to like VNI ids higher than those for VLANs which is 4096, 
however VXLAN's max id is about 16 millions, so this is a problem that needs a 
fix.

Here are some logs:

2018-02-08 15:50:00,738 WARN  [resource.wrapper.LibvirtStartCommandWrapper] 
(agentRequest-Handler-4:null) (logid:bd9fbea5) InternalErrorException
com.cloud.exception.InternalErrorException: Failed to create vnet 3: 
RTNETLINK answers: Numerical result out of rangeCannot find device 
"bond0.3"Failed to create vlan 3 on pif: bond0.

--
Sent from the Delta quadrant using Borg technology!

Nux!
www.nux.ro


nicolas.vazq...@shapeblue.com 
www.shapeblue.com
,   
@shapeblue
  
 

- Original Message -
> From: "Nux!" 
> To: "dev" 
> Sent: Thursday, 8 February, 2018 14:29:36
> Subject: Re: Refusing to design this network, the physical isolation type is 
> not BCF_SEGMENT

> Thanks! Any idea where blueorangutan keeps the rpms?
>
> --
> Sent from the Delta quadrant using Borg technology!
>
> Nux!
> www.nux.ro
>
> - Original Message -
>> From: "Nicolas Vazquez" 
>> To: "dev" 
>> Sent: Wednesday, 7 February, 2018 12:12:00
>> Subject: Re: Refusing to design this network, the physical isolation type is 
>> not
>> BCF_SEGMENT
>
>> I have pushed a fix for this on PR 2448. Can you please test it?
>>
>> 
>> From: Nux! 
>> Sent: Tuesday, February 6, 2018 10:25:07 AM
>> To: dev
>> Subject: Re: Refusing to design this network, the physical isolation type is 
>> not
>> BCF_SEGMENT
>>
>> Thanks Nicolas, much appreciated.
>> Once you have a patch, feel free to ping me so I can test.
>>
>> --
>> Sent from the Delta quadrant using Borg technology!
>>
>> Nux!
>> www.nux.ro
>>
>>
>> nicolas.vazq...@shapeblue.com
>> www.shapeblue.com
>> ,
>> @shapeblue
>>
>>
>>
>> - Original Message -
>>> From: "Nicolas Vazquez" 
>>> To: "dev" 
>>> Sent: Tuesday, 6 February, 2018 13:23:54
>>> Subject: Re: Refusing to design this network, the physical isolation type 
>>> is not
>>> BCF_SEGMENT
>>
>>> Hi Lucian,
>>>
>>>
>>> Thanks for posting this issue. I have checked the canHandle() method on
>>> VxlanGuestNetworkGuru and it is not considering L2 network offerings, only
>>> Isolated, so it refuses to design the network. I'll make sure to include a 
>>> fix
>>> for it on 4.11.1.
>>>
>>>
>>> Thanks,
>>>
>>> Nicolas
>>>
>>> 
>>> From: Nux! 
>>> Sent: Tuesday, February 6, 2018 8:30:03 AM
>>> To: dev
>>> Subject: [L2 network] [VXLAN] Refusing to design this network, the physical
>>> isolation type is not BCF_SEGMENT
>>>
>>> Hi,
>>>
>>> I'm trying to add an L2 network based on a VXLAN physical network and I am
>>> getting the error in the subject.
>>>
>>> If I use a VLAN based physical network all completes successfully and I end 
>>> up
>>> with an L2 network in green "Setup" state.
>>>
>>> Here are some more logs:
>>>
>>> 2018-02-06 11:20:27,748 DEBUG [c.c.n.NetworkServiceImpl]
>>> (qtp788117692-390:ctx-f1a980be ctx-61be30e8) (logid:0ca0c866) Found physical
>>> network id=201 based on requested tags mellanoxvxlan
>>> 2018-02-06 11:20:27,749 DEBUG [c.c.n.NetworkServiceImpl]
>>> (qtp788117692-390:ctx-f1a980be ctx-61be30e8) (logid:0ca0c866) Found physical
>>> network id=201 based on requested tags mellanoxvxlan
>>> 2018-02-06 11:20:27,766 DEBUG [c.c.n.g.BigSwitchBcfGuestNetworkGuru]
>>> (qtp788117692-390:ctx-f1a980be ctx-61be30e8) (logid:0ca0c866) Refusing to
>>> design this network, the physical isolation type is not BCF_SEGMENT
>>> 2018-02-06 11:20:27,766 DEBUG [o.a.c.n.c.m.ContrailGuru]
>>> (qtp788117692-390:ctx-f1a980be ctx-61be30e8) (logid:0ca0c866) Refusing to
>>> design this network
>>> 2018-02-06 11:20:27,767 DEBUG [c.c.n.g.NiciraNvpGuestNetworkGuru]
>>> (qtp788117692-390:ctx-f1a980be ctx-61be30e8) (logid:0ca0c866) Refusing to
>>> design this network
>>> 2018-02-06 11:20:27,767 DEBUG [o.a.c.n.o.OpendaylightGuestNetworkGuru]
>>> (qtp788117692-390:ctx-f1a980be ctx-61be30e8) (logid:0ca0c866) Refusing to
>>> design this network
>>> 2018-02-06 11:20:27,767 DEBUG [c.c.n.g.OvsGuestNetworkGuru]
>>> (qtp788117692-390:ctx-f1a980be ctx-61be30e8) (logid:0ca0c866) Refusing to
>>> design this network
>>> 2018-02-06 11:20:27,769 DEBUG [o.a.c.n.g.SspGuestNetworkGuru]
>>> (qtp788117692-390:ctx-f1a980be ctx-61be30e8) (logid:0ca0c866) SSP not
>>> configured to be active
>>> 2018-02-06

Re: GSoC ideas for the 2018 edition

Re: GSoC ideas for the 2018 edition

Include resource tags in the usage record for chargebacks

Re: GSoC ideas for the 2018 edition

Re: Refusing to design this network, the physical isolation type is not BCF_SEGMENT

Re: Refusing to design this network, the physical isolation type is not BCF_SEGMENT

6 matches

Site Navigation

Mail list logo

Footer information