[Openstack-operators] Poll: S Release Naming

[Paul Belanger]

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-operators mailing list
OpenStack-operators@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators

Re: [Openstack-operators] How are you handling billing/chargeback?

[Mike Lowe]

Ceilometer (now panko) vm exists events coerced to look like jobs from a HPC 
batch system.

Sent from my iPad

> On Mar 13, 2018, at 6:11 PM, Simon Leinen  wrote:
> 
> Lars Kellogg-Stedman writes:
>> I'm curious what folks out there are using for chargeback/billing in
>> your OpenStack environment.
> 
> We use a homegrown billing system that periodically samples utilization
> of billable resources.
> 
> (We turned off Ceilometer a few years ago because we weren't really
> using it and found that it caused us trouble.)
> -- 
> Simon.
> 
>> Are you doing any sort of chargeback (or showback)?  Are you using (or
>> have you tried) CloudKitty?  Or some other existing project?  Have you
>> rolled your own instead?
> 
>> I ask because I am helping out some folks get a handle on the
>> operational side of their existing OpenStack environment, and they are
>> interested in but have not yet deployed some sort of reporting
>> mechanism.
> 
> ___
> 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] How are you handling billing/chargeback?

[Simon Leinen]

Lars Kellogg-Stedman writes:
> I'm curious what folks out there are using for chargeback/billing in
> your OpenStack environment.

We use a homegrown billing system that periodically samples utilization
of billable resources.

(We turned off Ceilometer a few years ago because we weren't really
using it and found that it caused us trouble.)
-- 
Simon.

> Are you doing any sort of chargeback (or showback)?  Are you using (or
> have you tried) CloudKitty?  Or some other existing project?  Have you
> rolled your own instead?

> I ask because I am helping out some folks get a handle on the
> operational side of their existing OpenStack environment, and they are
> interested in but have not yet deployed some sort of reporting
> mechanism.

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

[Openstack-operators] [publiccloud-wg] Poll new meeting time and bi-weekly meeting

[Tobias Rydberg]

Hi folks,

We have under some time had requests of changing the current time for 
our bi-weekly meetings. Not very many suggestions of new time slots have 
ended up in my inbox, so have added a few suggestions my self.


The plan is to have this set and do final voting at tomorrows meeting. 
Reply to this email if you have other suggestions and I can add those as 
well. Please mark the alternatives that works for you no later than 
tomorrow 1400UTC.


Doodle link: https://doodle.com/poll/2kv4h79xypmathac

Tomorrows meeting will be held as planned in #openstack-meeting-3 at 
1400 UTC.


Agenda can be found at: https://etherpad.openstack.org/p/publiccloud-wg

S

--
Tobias Rydberg
Senior Developer
Mobile: +46 733 312780

www.citynetwork.eu | www.citycloud.com

INNOVATION THROUGH OPEN IT INFRASTRUCTURE
ISO 9001, 14001, 27001, 27015 & 27018 CERTIFIED




smime.p7s
Description: S/MIME Cryptographic Signature
___
OpenStack-operators mailing list
OpenStack-operators@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators

Re: [Openstack-operators] How are you handling billing/chargeback?

[Christophe Sauthier]

Le 2018-03-13 10:03, Tomáš Vondra a écrit :

Hi!

We at Homeatcloud have rolled our own engine taking data from
Ceilometer events. However, CloudKitty didn‘t exist back then. Now we
would probably use it to calculate the rating AND roll our own engine
for billing and invoice printing.


The case you are mentionning is clearly the scope of cloudkitty. So if 
you are willing to have some informations I'd be happy to exchange with 
you (by mail or huats on IRC).


Regards

 Christophe Sauthier




Christophe Sauthier
CEO

Objectif Libre : Au service de votre Cloud

+33 (0) 6 16 98 63 96 | christophe.sauth...@objectif-libre.com

www.objectif-libre.com | @objectiflibre | 
www.linkedin.com/company/objectif-libre

Recevez la Pause Cloud Et DevOps : olib.re/abo-pause

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

Re: [Openstack-operators] How are you handling billing/chargeback?

[Benedikt Trefzer]

Hi 

same here, despite we do not use events but audit data from ceilometer.

Benedikt


On 13.03.2018 10:03, Tomáš Vondra wrote:
>
> Hi!
>
> We at Homeatcloud have rolled our own engine taking data from
> Ceilometer events. However, CloudKitty didn‘t exist back then. Now we
> would probably use it to calculate the rating AND roll our own engine
> for billing and invoice printing.
>
> Tomas
>
>  
>
> *From:*Flint WALRUS [mailto:gael.ther...@gmail.com]
> *Sent:* Monday, March 12, 2018 9:41 PM
> *To:* Lars Kellogg-Stedman
> *Cc:* openstack-operators@lists.openstack.org
> *Subject:* Re: [Openstack-operators] How are you handling
> billing/chargeback?
>
>  
>
> Hi lars, personally using an internally crafted service.
>
> It’s one of my main regret with Openstack, lack of a decent billing
> system.
>
> Le lun. 12 mars 2018 à 20:22, Lars Kellogg-Stedman  > a écrit :
>
> Hey folks,
>
> I'm curious what folks out there are using for chargeback/billing in
> your OpenStack environment.
>
> Are you doing any sort of chargeback (or showback)?  Are you using (or
> have you tried) CloudKitty?  Or some other existing project?  Have you
> rolled your own instead?
>
> I ask because I am helping out some folks get a handle on the
> operational side of their existing OpenStack environment, and they are
> interested in but have not yet deployed some sort of reporting
> mechanism.
>
> Thanks,
>
> --
> Lars Kellogg-Stedman > |
> larsks @ {irc,twitter,github}
> http://blog.oddbit.com/                |
>
> ___
> 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] No Ops Meetups team meeting this week

[Chris Morgan]

There will be no team meeting this week for the Ops Meetups team this week
as those of us who made it to the Tokyo meetup last week catch up on other
things. Normal meetings will resume next week and we will also put together
a Meetup recap/lessons-learned note to be shared here shortly.

Chris

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

Re: [Openstack-operators] How are you handling billing/chargeback?

[Tomáš Vondra]

Hi!

We at Homeatcloud have rolled our own engine taking data from Ceilometer 
events. However, CloudKitty didn‘t exist back then. Now we would probably use 
it to calculate the rating AND roll our own engine for billing and invoice 
printing.

Tomas

 

From: Flint WALRUS [mailto:gael.ther...@gmail.com] 
Sent: Monday, March 12, 2018 9:41 PM
To: Lars Kellogg-Stedman
Cc: openstack-operators@lists.openstack.org
Subject: Re: [Openstack-operators] How are you handling billing/chargeback?

 

Hi lars, personally using an internally crafted service.

It’s one of my main regret with Openstack, lack of a decent billing system.

Le lun. 12 mars 2018 à 20:22, Lars Kellogg-Stedman  a écrit :

Hey folks,

I'm curious what folks out there are using for chargeback/billing in
your OpenStack environment.

Are you doing any sort of chargeback (or showback)?  Are you using (or
have you tried) CloudKitty?  Or some other existing project?  Have you
rolled your own instead?

I ask because I am helping out some folks get a handle on the
operational side of their existing OpenStack environment, and they are
interested in but have not yet deployed some sort of reporting
mechanism.

Thanks,

--
Lars Kellogg-Stedman  | larsks @ {irc,twitter,github}
http://blog.oddbit.com/|

___
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