Re: GSoC ideas for the 2018 edition

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

Re: GSoC ideas for the 2018 edition

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

Include resource tags in the usage record for chargebacks

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.

Re: GSoC ideas for the 2018 edition

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.

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

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

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