Re: [Openstack-operators] [openstack-dev] Poll: S Release Naming

[Sławomir Kapłoński]

Indeed. I now tried from different IP address and I was able to vote. Thx a lot 
for help.

— 
Best regards
Slawek Kaplonski
sla...@kaplonski.pl

> Wiadomość napisana przez Thierry Carrez <thie...@openstack.org> w dniu 
> 14.03.2018, o godz. 10:05:
> 
> Jens Harbott wrote:
>> 2018-03-14 9:21 GMT+01:00 Sławomir Kapłoński <sla...@kaplonski.pl>:
>>> Hi,
>>> 
>>> Are You sure this link is good? I just tried it and I got info that 
>>> "Already voted" which isn't true in fact :)
>> 
>> Comparing with previous polls, these should be personalized links that
>> need to be sent out to each voter individually, so I agree that this
>> looks like a mistake.
> 
> We crashed CIVS for the last naming with a private poll sent to all the
> Foundation membership, so the TC decided to use public (open) polling
> this time around. Anyone with the link can vote, nothing was sent to
> each of the voters individually.
> 
> The "Already voted" error might be due to CIVS limiting public polling
> to one entry per IP, and a colleague of yours already voted... Maybe try
> from another IP address ?
> 
> -- 
> Thierry Carrez (ttx)
> 
> __
> 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

Re: [Openstack-operators] [openstack-dev] Poll: S Release Naming

[Sławomir Kapłoński]

Hi,

Are You sure this link is good? I just tried it and I got info that "Already 
voted" which isn't true in fact :)

— 
Best regards
Slawek Kaplonski
sla...@kaplonski.pl

> Wiadomość napisana przez Paul Belanger  w dniu 
> 14.03.2018, o godz. 00:58:
> 
> Greetings all,
> 
> It is time again to cast your vote for the naming of the S Release. This time
> is little different as we've decided to use a public polling option over per
> user private URLs for voting. This means, everybody should proceed to use the
> following URL to cast their vote:
> 
>  
> https://civs.cs.cornell.edu/cgi-bin/vote.pl?id=E_40b95cb2be3fcdf1=8cfdc1f5df5fe4d3
> 
> Because this is a public poll, results will currently be only viewable by 
> myself
> until the poll closes. Once closed, I'll post the URL making the results
> viewable to everybody. This was done to avoid everybody seeing the results 
> while
> the public poll is running.
> 
> The poll will officially end on 2018-03-21 23:59:59[1], and results will be
> posted shortly after.
> 
> [1] 
> http://git.openstack.org/cgit/openstack/governance/tree/reference/release-naming.rst
> ---
> 
> According to the Release Naming Process, this poll is to determine the
> community preferences for the name of the R release of OpenStack. It is
> possible that the top choice is not viable for legal reasons, so the second or
> later community preference could wind up being the name.
> 
> Release Name Criteria
> 
> Each release name must start with the letter of the ISO basic Latin alphabet
> following the initial letter of the previous release, starting with the
> initial release of "Austin". After "Z", the next name should start with
> "A" again.
> 
> The name must be composed only of the 26 characters of the ISO basic Latin
> alphabet. Names which can be transliterated into this character set are also
> acceptable.
> 
> The name must refer to the physical or human geography of the region
> encompassing the location of the OpenStack design summit for the
> corresponding release. The exact boundaries of the geographic region under
> consideration must be declared before the opening of nominations, as part of
> the initiation of the selection process.
> 
> The name must be a single word with a maximum of 10 characters. Words that
> describe the feature should not be included, so "Foo City" or "Foo Peak"
> would both be eligible as "Foo".
> 
> Names which do not meet these criteria but otherwise sound really cool
> should be added to a separate section of the wiki page and the TC may make
> an exception for one or more of them to be considered in the Condorcet poll.
> The naming official is responsible for presenting the list of exceptional
> names for consideration to the TC before the poll opens.
> 
> Exact Geographic Region
> 
> The Geographic Region from where names for the S release will come is Berlin
> 
> Proposed Names
> 
> Spree (a river that flows through the Saxony, Brandenburg and Berlin states of
>   Germany)
> 
> SBahn (The Berlin S-Bahn is a rapid transit system in and around Berlin)
> 
> Spandau (One of the twelve boroughs of Berlin)
> 
> Stein (Steinstraße or "Stein Street" in Berlin, can also be conveniently
>   abbreviated as )
> 
> Steglitz (a locality in the South Western part of the city)
> 
> Springer (Berlin is headquarters of Axel Springer publishing house)
> 
> Staaken (a locality within the Spandau borough)
> 
> Schoenholz (A zone in the Niederschönhausen district of Berlin)
> 
> Shellhaus (A famous office building)
> 
> Suedkreuz ("southern cross" - a railway station in Tempelhof-Schöneberg)
> 
> Schiller (A park in the Mitte borough)
> 
> Saatwinkel (The name of a super tiny beach, and its surrounding neighborhood)
>   (The adjective form, Saatwinkler is also a really cool bridge but
>   that form is too long)
> 
> Sonne (Sonnenallee is the name of a large street in Berlin crossing the former
>   wall, also translates as "sun")
> 
> Savigny (Common place in City-West)
> 
> Soorstreet (Street in Berlin restrict Charlottenburg)
> 
> Solar (Skybar in Berlin)
> 
> See (Seestraße or "See Street" in Berlin)
> 
> Thanks,
> Paul
> 
> __
> 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

Re: [Openstack-operators] Openstack operational configuration improvement.

[Sławomir Kapłoński]

Hi,

Isn't Fuel or TripleO something what You are looking for?

— 
Best regards
Slawek Kaplonski
sla...@kaplonski.pl



> Wiadomość napisana przez Flint WALRUS  w dniu 
> 18.12.2017, o godz. 14:28:
> 
> Hi everyone, I don't really know if this list is the good one, but I'll have 
> my bet on it :D
> 
> Here I go.
> 
> Since many times now, I'm managing  Openstack platforms, and one things that 
> always amazed me is its lack of comprehensive configuration management for 
> services within Horizon.
> 
> Indeed, you can set and adapt pretty much everything within Horizon or the 
> CLI except for the services configuration.
> 
> So here is a proposal regarding this issue:
> 
> I think of it as a rework of the already existing system information panel 
> from the admin dashboard such as:
> 
> Within the services tab, each service line would now be a clickable drop down 
> containing an additional subarray named configuration and listing the whole 
> available configurations options for this service with information such as:
> - Current value: default or value. (Dynamically editable by simply clicking 
> on it, write the new value on the INI file).
> - Default value: the default sane value. (Not editable default value of the 
> option).
> - Reload / Restart button. (a button enforcing the service to reload its 
> configuration).
> - Description: None or a short excerpt. (Not editable information about the 
> option meaning).
> - Documentation: None or a link to the option documentation. (Not editable).
> 
> What do you think of it?
> 
> PS: If this discussion should go with the horizon team rather than the 
> operational team, could someone help with this one as I didn't find any 
> mailing list related endpoint?
> 
> Thanks a lot.
> 
> 
> ___
> 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