Re: [Openstack-operators] about the R release name

[Melvin Hillsman]

This cracked me up! "Mountain Dew learned the hard way when 4 Chan took
control of a vote

to name a new flavor, and the joke was on Taylor Swift and VH1 when the
Internet chose a school for the deaf

as a concert location."

On Mon, Apr 10, 2017 at 4:11 PM, Matt Joyce  wrote:

> +2
>
> On Mon, Apr 10, 2017 at 5:07 PM, Monty Taylor 
> wrote:
>
>> On 04/10/2017 02:10 PM, Amrith Kumar wrote:
>>
>>> The naming is based on community input and there's good reason to
>>> believe that in this round of voting both of these values will get a low
>>> score.
>>>
>>> But, we could have a repeat of the Boaty McBoatface debacle 
>>>
>>
>> I would totally vote for OpenStack Boaty McBoatface. Maybe we can switch
>> from place names to names of the form "{foo}y Mc{foo}face" for all releases
>> after Z ...
>>
>>
>> https://www.nytimes.com/2016/03/22/world/europe/boaty-mcboat
>>> face-what-you-get-when-you-let-the-internet-decide.html?_r=0
>>>
>>> -amrith
>>>
>>> --
>>> Amrith Kumar
>>> amrith.ku...@gmail.com
>>>
>>>
>>> -Original Message-
 From: Saverio Proto [mailto:ziopr...@gmail.com]
 Sent: Monday, April 10, 2017 3:02 PM
 To: OpenStack Operators 
 Subject: [Openstack-operators] about the R release name

 Hello Ops,

 I got the mail about the Poll for OpenStack R Release Naming

 I am shocked that there are proposed names like Raspberry or Root !

 Think about troubleshooting and searching on google:

 Openstack Raspberry "string of log file"

 The Raspberry or Root words are anti-google words that will pollute the
 search with a lot of results from other context domain 

 Please be smart when voting ! We need names that can identify easily the
 releases when using search engines !!!

 thank you

 Saverio

 ___
 OpenStack-operators mailing list
 OpenStack-operators@lists.openstack.org
 http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators

>>>
>>>
>>> ___
>>> OpenStack-operators mailing list
>>> OpenStack-operators@lists.openstack.org
>>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators
>>>
>>>
>>
>> ___
>> OpenStack-operators mailing list
>> OpenStack-operators@lists.openstack.org
>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators
>>
>
>
> ___
> OpenStack-operators mailing list
> OpenStack-operators@lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators
>
>


-- 
Kind regards,

Melvin Hillsman
Ops Technical Lead
OpenStack Innovation Center

mrhills...@gmail.com
phone: (210) 312-1267
mobile: (210) 413-1659
http://osic.org

Learner | Ideation | Belief | Responsibility | Command
___
OpenStack-operators mailing list
OpenStack-operators@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators

Re: [Openstack-operators] about the R release name

[Matt Joyce]

+2

On Mon, Apr 10, 2017 at 5:07 PM, Monty Taylor  wrote:

> On 04/10/2017 02:10 PM, Amrith Kumar wrote:
>
>> The naming is based on community input and there's good reason to believe
>> that in this round of voting both of these values will get a low score.
>>
>> But, we could have a repeat of the Boaty McBoatface debacle 
>>
>
> I would totally vote for OpenStack Boaty McBoatface. Maybe we can switch
> from place names to names of the form "{foo}y Mc{foo}face" for all releases
> after Z ...
>
>
> https://www.nytimes.com/2016/03/22/world/europe/boaty-mcboat
>> face-what-you-get-when-you-let-the-internet-decide.html?_r=0
>>
>> -amrith
>>
>> --
>> Amrith Kumar
>> amrith.ku...@gmail.com
>>
>>
>> -Original Message-
>>> From: Saverio Proto [mailto:ziopr...@gmail.com]
>>> Sent: Monday, April 10, 2017 3:02 PM
>>> To: OpenStack Operators 
>>> Subject: [Openstack-operators] about the R release name
>>>
>>> Hello Ops,
>>>
>>> I got the mail about the Poll for OpenStack R Release Naming
>>>
>>> I am shocked that there are proposed names like Raspberry or Root !
>>>
>>> Think about troubleshooting and searching on google:
>>>
>>> Openstack Raspberry "string of log file"
>>>
>>> The Raspberry or Root words are anti-google words that will pollute the
>>> search with a lot of results from other context domain 
>>>
>>> Please be smart when voting ! We need names that can identify easily the
>>> releases when using search engines !!!
>>>
>>> thank you
>>>
>>> Saverio
>>>
>>> ___
>>> OpenStack-operators mailing list
>>> OpenStack-operators@lists.openstack.org
>>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators
>>>
>>
>>
>> ___
>> OpenStack-operators mailing list
>> OpenStack-operators@lists.openstack.org
>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators
>>
>>
>
> ___
> OpenStack-operators mailing list
> OpenStack-operators@lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators
>
___
OpenStack-operators mailing list
OpenStack-operators@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators

Re: [Openstack-operators] about the R release name

[Monty Taylor]

On 04/10/2017 02:10 PM, Amrith Kumar wrote:

The naming is based on community input and there's good reason to believe that 
in this round of voting both of these values will get a low score.

But, we could have a repeat of the Boaty McBoatface debacle 


I would totally vote for OpenStack Boaty McBoatface. Maybe we can switch 
from place names to names of the form "{foo}y Mc{foo}face" for all 
releases after Z ...



https://www.nytimes.com/2016/03/22/world/europe/boaty-mcboatface-what-you-get-when-you-let-the-internet-decide.html?_r=0

-amrith

--
Amrith Kumar
amrith.ku...@gmail.com



-Original Message-
From: Saverio Proto [mailto:ziopr...@gmail.com]
Sent: Monday, April 10, 2017 3:02 PM
To: OpenStack Operators 
Subject: [Openstack-operators] about the R release name

Hello Ops,

I got the mail about the Poll for OpenStack R Release Naming

I am shocked that there are proposed names like Raspberry or Root !

Think about troubleshooting and searching on google:

Openstack Raspberry "string of log file"

The Raspberry or Root words are anti-google words that will pollute the
search with a lot of results from other context domain 

Please be smart when voting ! We need names that can identify easily the
releases when using search engines !!!

thank you

Saverio

___
OpenStack-operators mailing list
OpenStack-operators@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators



___
OpenStack-operators mailing list
OpenStack-operators@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators




___
OpenStack-operators mailing list
OpenStack-operators@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators

Re: [Openstack-operators] FW: [quotas] Unified Limits Conceptual Spec RFC

[Lance Bragstad]

Sending out a heads up that the initial spec [0] merged.

[0] https://review.openstack.org/#/c/440815/

On Thu, Mar 30, 2017 at 1:44 PM, Tim Bell  wrote:

>
> For those that are interested in nested quotas, there is proposal on how
> to address this forming in openstack-dev (and any comments on the review
> should be made to https://review.openstack.org/#/c/363765).
>
> This proposal has the benefits (if I can summarise) that
>
> - Quota limits will be centrally managed in Keystone so the quota data
> will be close to the project for creation/deletion/admin.
> - The usage data remains within each project avoiding dependencies and
> risks of usage data getting out of sync.
> - With a central store for quotas, there is increased opportunity for
> consistency. Given the complexity of quotas and nested projects, this would
> improve operator and end user understanding. The exact model is still for
> confirmation though.
>
> We’ll have a forum discussion (http://forumtopics.openstack.
> org/cfp/details/9) in Boston too but feel free to give input to
> https://review.openstack.org/#/c/363765 so we can use Boston as the
> opportunity to agree on the approach and next steps.
>
> Tim
>
> On 30.03.17, 19:52, "Sean Dague"  wrote:
>
> The near final draft of the unified limits spec is up now -
> https://review.openstack.org/#/c/440815/
>
> If you have not yet wandered in, now is the time, we're going to make
> the final go / no go the end of this week.
>
> -Sean
>
> On 03/17/2017 06:36 AM, Sean Dague wrote:
> > Background:
> >
> > At the Atlanta PTG there was yet another attempt to get hierarchical
> > quotas more generally addressed in OpenStack. A proposal was put
> forward
> > that considered storing the limit information in Keystone
> > (https://review.openstack.org/#/c/363765/). While there were some
> > concerns on details that emerged out of that spec, the concept of the
> > move to Keystone was actually really well received in that room by a
> > wide range of parties, and it seemed to solve some interesting
> questions
> > around project hierarchy validation. We were perilously close to
> having
> > a path forward for a community request that's had a hard time making
> > progress over the last couple of years.
> >
> > Let's keep that flame alive!
> >
> >
> > Here is the proposal for the Unified Limits in Keystone approach -
> > https://review.openstack.org/#/c/440815/. It is intentionally a high
> > level spec that largely lays out where the conceptual levels of
> control
> > will be. It intentionally does not talk about specific quota models
> > (there is a follow on that is doing some of that, under the
> assumption
> > that the exact model(s) supported will take a while, and that the
> > keystone interfaces are probably not going to substantially change
> based
> > on model).
> >
> > We're shooting for a 2 week comment cycle here to then decide if we
> can
> > merge and move forward during this cycle or not. So please
> > comment/question now (either in the spec or here on the mailing
> list).
> >
> > It is especially important that we get feedback from teams that have
> > limits implementations internally, as well as any that have started
> on
> > hierarchical limits/quotas (which I believe Cinder is the only one).
> >
> > Thanks for your time, and look forward to seeing comments on this.
> >
> >   -Sean
> >
>
>
> --
> Sean Dague
> http://dague.net
>
> 
> __
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:
> unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
>
> ___
> OpenStack-operators mailing list
> OpenStack-operators@lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators
>
___
OpenStack-operators mailing list
OpenStack-operators@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators

Re: [Openstack-operators] about the R release name

[Matt Joyce]

Legit point.  +1

Vote Rambler.  No one's owned a rambler in like 50 years.  =P

On Mon, Apr 10, 2017 at 3:02 PM, Saverio Proto  wrote:

> Hello Ops,
>
> I got the mail about the Poll for OpenStack R Release Naming
>
> I am shocked that there are proposed names like Raspberry or Root !
>
> Think about troubleshooting and searching on google:
>
> Openstack Raspberry "string of log file"
>
> The Raspberry or Root words are anti-google words that will pollute
> the search with a lot of results from other context domain 
>
> Please be smart when voting ! We need names that can identify easily
> the releases when using search engines !!!
>
> thank you
>
> Saverio
>
> ___
> OpenStack-operators mailing list
> OpenStack-operators@lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators
>
___
OpenStack-operators mailing list
OpenStack-operators@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators

[Openstack-operators] about the R release name

[Saverio Proto]

Hello Ops,

I got the mail about the Poll for OpenStack R Release Naming

I am shocked that there are proposed names like Raspberry or Root !

Think about troubleshooting and searching on google:

Openstack Raspberry "string of log file"

The Raspberry or Root words are anti-google words that will pollute
the search with a lot of results from other context domain 

Please be smart when voting ! We need names that can identify easily
the releases when using search engines !!!

thank you

Saverio

___
OpenStack-operators mailing list
OpenStack-operators@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators

[Openstack-operators] UC Meeting 04/10/17 Cancelled

[Melvin Hillsman]

Hey everyone,

Apologies for the late notice. We are cancelling the meeting today. We have
moved to a weekly cadence with meetings being subject to new agenda items
having to be proposed/added by the Friday before the meeting. In other
words, for UC meeting scheduled for 04/17/17 agenda items will need to be
proposed/added by this Friday 04/14/17

Thanks very much,

OpenStack UC
___
OpenStack-operators mailing list
OpenStack-operators@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators

[Openstack-operators] [HA] HA Discussion at Boston Forum

[Sam P]

Hi All,

 I proposed a session [1] to Boston Forum and it is now at incomplete state.
 This is good opportunity for all of us to get together and discuss
our HA related issues.
 I need your help to reform this session.
 Please put comments on [1] or replay to this with your comments.

[1] http://forumtopics.openstack.org/cfp/details/117

--- Regards,
Sampath

___
OpenStack-operators mailing list
OpenStack-operators@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators

[Openstack-operators] [telecom-nfv] Boston Summit Working Group Session

[Curtis]

Hi All,

Just FYI, we do have a session time at the summit:

http://www.openstack.org/summit/boston-2017/summit-schedule/events/17636/openstack-operators-telecomnfv-working-group-session

It's possible I missed being alerted to the fact that our request was
accepted. I didn't notice it until the speaker email came out last
week. Apologies for that.

More to come on this topic. :)

Thanks,
Curtis.

___
OpenStack-operators mailing list
OpenStack-operators@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators

[Openstack-operators] Reminder User Committee Meeting

[Melvin Hillsman]

Hey everyone,

User Committee will meet today in #openstack-meeting @ 1900UTC. If you have
any requests for agenda items you can reply to this email or message any of
the UC members via email as well as IRC - #openstack-uc

-- 
Kind regards,

OpenStack UC
___
OpenStack-operators mailing list
OpenStack-operators@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators