|
Re: [release] Telling our users about what is in Helium
I'm late to the party (as usual), but this looks fine to me.
release-bounces@... wrote on 09/24/2014 02:49:31 PM:
> From: Phil Robb <probb@...>
> To: Colin Dixon <colin@...>
> Cc: "tsc@..." <tsc@...>,
I'm late to the party (as usual), but this looks fine to me.
release-bounces@... wrote on 09/24/2014 02:49:31 PM:
> From: Phil Robb <probb@...>
> To: Colin Dixon <colin@...>
> Cc: "tsc@..." <tsc@...>,
|
By
Ryan Moats <rmoats@...>
·
#1775
·
|
|
Re: Telling our users about what is in Helium
If my memory services right, FRM hasn't been spelled out since hydrogen. -:)Sent from Huawei MobilePhil Robb <probb@...> wrote:
Yea, spelling it out makes it look cluttered Colin.
I think it's best if
If my memory services right, FRM hasn't been spelled out since hydrogen. -:)Sent from Huawei MobilePhil Robb <probb@...> wrote:
Yea, spelling it out makes it look cluttered Colin.
I think it's best if
|
By
George Zhao
·
#1774
·
|
|
Re: Telling our users about what is in Helium
Yea, spelling it out makes it look cluttered Colin.
I think it's best if we leave it in the legend.
Phil.
--
Phil Robb
Director - Networking Solutions
The Linux Foundation
(O) 970-229-5949
(M)
Yea, spelling it out makes it look cluttered Colin.
I think it's best if we leave it in the legend.
Phil.
--
Phil Robb
Director - Networking Solutions
The Linux Foundation
(O) 970-229-5949
(M)
|
By
Phil Robb
·
#1773
·
|
|
Re: Telling our users about what is in Helium
Yes - looks nice.
By
Abhijit Kumbhare
·
#1772
·
|
|
Re: Telling our users about what is in Helium
Very nice work Phil. --dmm
Very nice work Phil. --dmm
|
By
David Meyer <dmm@...>
·
#1771
·
|
|
Re: Telling our users about what is in Helium
I like it a lot.
I'm assuming there's not space to spell out FRM in "Base Network Services"?
--Colin
I like it a lot.
I'm assuming there's not space to spell out FRM in "Base Network Services"?
--Colin
|
By
Colin Dixon
·
#1770
·
|
|
Dev Design Forum / Schedule Live and Last Chance to Register
ODL Community,
If you have not already registered for the Developer Design Forum, please do so ASAP at http://events.linuxfoundation.org/events/opendaylight-developer-design-forum
In addition, the
ODL Community,
If you have not already registered for the Developer Design Forum, please do so ASAP at http://events.linuxfoundation.org/events/opendaylight-developer-design-forum
In addition, the
|
By
Todd Benzies <tbenzies@...>
·
#1769
·
|
|
Re: Telling our users about what is in Helium
1) OK, ARP Handler is gone.
2) I reduced the GBP Renderers box to now only cover half of the OF and OVSDB boxes
3) No better phrase that I know of and that's what we used in the Hydrogen diagram as
1) OK, ARP Handler is gone.
2) I reduced the GBP Renderers box to now only cover half of the OF and OVSDB boxes
3) No better phrase that I know of and that's what we used in the Hydrogen diagram as
|
By
Phil Robb
·
#1768
·
|
|
Re: Telling our users about what is in Helium
Hi Srini:
As I understand it,the renderers actually do sit below the SAL, so I want to show them that way.
On the data plane icons, I would like to keep these consistent with the Hydrogen diagram and
Hi Srini:
As I understand it,the renderers actually do sit below the SAL, so I want to show them that way.
On the data plane icons, I would like to keep these consistent with the Hydrogen diagram and
|
By
Phil Robb
·
#1767
·
|
|
release reviews from 9/24 and 9/23
The meeting minutes from today (9/24) are
The meeting minutes from today (9/24) are
|
By
Colin Dixon
·
#1766
·
|
|
Re: [openflowplugin-dev] Bug 2026
It seems as though we had to respin to avoid the -RC2 version suffix anyway. I *thnk* this patch will end up in those artifacts as a consequence.
--Colin
It seems as though we had to respin to avoid the -RC2 version suffix anyway. I *thnk* this patch will end up in those artifacts as a consequence.
--Colin
|
By
Colin Dixon
·
#1765
·
|
|
Re: [openflowplugin-dev] Bug 2026
I agree, AFAIK this is not a blocking issue.
I agree, AFAIK this is not a blocking issue.
|
By
Luis Gomez
·
#1764
·
|
|
Re: [openflowplugin-dev] Bug 2061
OK - this looks like it has been merged - so if we wind up respinning it will be included. Fixed the bug number in the thread title (2061 not 2026). I agree that this would not be something that we
OK - this looks like it has been merged - so if we wind up respinning it will be included. Fixed the bug number in the thread title (2061 not 2026). I agree that this would not be something that we
|
By
Abhijit Kumbhare
·
#1763
·
|
|
Re: [openflowplugin-dev] Bug 2026
My gut reaction would be that this is the kind of thing which we won't respin the release artifacts for, but if we wind up respinning the release artifacts should be included.
I'm open to other
My gut reaction would be that this is the kind of thing which we won't respin the release artifacts for, but if we wind up respinning the release artifacts should be included.
I'm open to other
|
By
Colin Dixon
·
#1762
·
|
|
Bug 2026
Hi Openflow Committers -
Luis discovered a bug (2026) in openflow and I pushed a patch (https://git.opendaylight.org/gerrit/11511). The fix was straight forward but since the test also tested for the
Hi Openflow Committers -
Luis discovered a bug (2026) in openflow and I pushed a patch (https://git.opendaylight.org/gerrit/11511). The fix was straight forward but since the test also tested for the
|
By
Devin Avery <davery@...>
·
#1761
·
|
|
Re: Topics and agenda for the Developer Design Forum
+1
I wasn't suggesting it to save time, but instead to make sure people can attend all 3 and that we have them in the right order.
--Colin
On Sep 23, 2014 4:36 PM, "Robert Varga" <nite@...> wrote:
+1
I wasn't suggesting it to save time, but instead to make sure people can attend all 3 and that we have them in the right order.
--Colin
On Sep 23, 2014 4:36 PM, "Robert Varga" <nite@...> wrote:
|
By
Colin Dixon
·
#1760
·
|
|
Re: Lithium schedule and timeline
So, moving that date to October 23rd is something which I believe is just fixing the document to be internally consistent and gives an extra (almost) week. I just made that change [0]. I think that
So, moving that date to October 23rd is something which I believe is just fixing the document to be internally consistent and gives an extra (almost) week. I just made that change [0]. I think that
|
By
Colin Dixon
·
#1759
·
|
|
Re: Telling our users about what is in Helium
For Colin's point #2, how about pulling up the GBP into the green rectangle and carving out a portion of the SAL to make it all fit?
With the devices in the bottom, how about changing it to these
For Colin's point #2, how about pulling up the GBP into the green rectangle and carving out a portion of the SAL to make it all fit?
With the devices in the bottom, how about changing it to these
|
By
Srini Seetharaman
·
#1758
·
|
|
Re: Telling our users about what is in Helium
A few questions/suggestions:
1.) can we remove the ARP Handler or move it into the l2switch where I think it resides now. That will actually save space.
2.) If anyone has a suggestion for how to make
A few questions/suggestions:
1.) can we remove the ARP Handler or move it into the l2switch where I think it resides now. That will actually save space.
2.) If anyone has a suggestion for how to make
|
By
Colin Dixon
·
#1757
·
|
|
Re: Telling our users about what is in Helium
Hello again TSC and members of the Helium Release:
Thanks to all for the great feedback on the Helium diagram. It has all been incorporated into the pretty version of the diagram you see
Hello again TSC and members of the Helium Release:
Thanks to all for the great feedback on the Helium diagram. It has all been incorporated into the pretty version of the diagram you see
|
By
Phil Robb
·
#1756
·
|