Re: [openstack-dev] [kolla] add service discovery, proxysql, vault, fabio and FQDN endpoints

[Christian Berendt]

> On 8. Oct 2018, at 19:48, Jay Pipes  wrote:
> 
> Why not send all read and all write traffic to a single haproxy endpoint and 
> just have haproxy spread all traffic across each Galera node?
> 
> Galera, after all, is multi-master synchronous replication... so it shouldn't 
> matter which node in the Galera cluster you send traffic to.

Probably because of MySQL deadlocks in Galera:

—snip—
Galera cluster has known limitations, one of them is that it uses cluster-wide 
optimistic locking. This may cause some transactions to rollback. With an 
increasing number of writeable masters, the transaction rollback rate may 
increase, especially if there is write contention on the same dataset. It is of 
course possible to retry the transaction and perhaps it will COMMIT in the 
retries, but this will add to the transaction latency. However, some designs 
are deadlock prone, e.g sequence tables.
—snap—

Source: 
https://severalnines.com/resources/tutorials/mysql-load-balancing-haproxy-tutorial

Christian.

-- 
Christian Berendt
Chief Executive Officer (CEO)

Mail: bere...@betacloud-solutions.de
Web: https://www.betacloud-solutions.de

Betacloud Solutions GmbH
Teckstrasse 62 / 70190 Stuttgart / Deutschland

Geschäftsführer: Christian Berendt
Unternehmenssitz: Stuttgart
Amtsgericht: Stuttgart, HRB 756139


__
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

Re: [openstack-dev] [kolla] Proposing Chason Chan (chason) as kolla-ansible core

[Christian Berendt]

+1

> On 25. Sep 2018, at 17:47, Eduardo Gonzalez  wrote:
> 
> Hi,
> 
> I would like to propose Chason Chan to the kolla-ansible core team.
> 
> Chason is been working on addition of Vitrage roles, rework VpnaaS service, 
> maintaining
> documentation as well as fixing many bugs.
> 
> Voting will be open for 14 days (until 9th of Oct).
> 
> Kolla-ansible cores, please leave a vote.
> Consider this mail my +1 vote
> 
> Regards,
> Eduardo
> __
> 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

-- 
Christian Berendt
Chief Executive Officer (CEO)

Mail: bere...@betacloud-solutions.de
Web: https://www.betacloud-solutions.de

Betacloud Solutions GmbH
Teckstrasse 62 / 70190 Stuttgart / Deutschland

Geschäftsführer: Christian Berendt
Unternehmenssitz: Stuttgart
Amtsgericht: Stuttgart, HRB 756139


__
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

Re: [openstack-dev] [kolla][vote] Nominating Steve Noyes for kolla-cli core reviewer

[Christian Berendt]

+1

> On 31. May 2018, at 19:02, Borne Mace  wrote:
> 
> Greetings all,
> 
> I would like to propose the addition of Steve Noyes to the kolla-cli core 
> reviewer team.  Consider this nomination as my personal +1.
> 
> Steve has a long history with the kolla-cli and should be considered its 
> co-creator as probably half or more of the existing code was due to his 
> efforts.  He has now been working diligently since it was pushed upstream to 
> improve the stability and testability of the cli and has the second most 
> commits on the project.
> 
> The kolla core team consists of 19 people, and the kolla-cli team of 2, for a 
> total of 21.  Steve therefore requires a minimum of 11 votes (so just 10 more 
> after my +1), with no veto -2 votes within a 7 day voting window to end on 
> June 6th.  Voting will be closed immediately on a veto or in the case of a 
> unanimous vote.
> 
> As I'm not sure how active all of the 19 kolla cores are, your attention and 
> timely vote is much appreciated.
> 
> Thanks!
> 
> -- Borne
> 
> 
> __
> 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

-- 
Christian Berendt
Chief Executive Officer (CEO)

Mail: bere...@betacloud-solutions.de
Web: https://www.betacloud-solutions.de

Betacloud Solutions GmbH
Teckstrasse 62 / 70190 Stuttgart / Deutschland

Geschäftsführer: Christian Berendt
Unternehmenssitz: Stuttgart
Amtsgericht: Stuttgart, HRB 756139


__
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

Re: [openstack-dev] [kolla][vote]Core nomination for Mark Goddard (mgoddard) as kolla core member

[Christian Berendt]

+1

> On 26. Apr 2018, at 17:31, Jeffrey Zhang <zhang.lei@gmail.com> wrote:
> 
> Kolla core reviewer team,
> 
> It is my pleasure to nominate ​mgoddard for kolla core team.
> ​
> Mark has been working both upstream and downstream with kolla and
> kolla-ansible for over two years, building bare metal compute clouds with
> ironic for HPC. He's been involved with OpenStack since 2014. He started
> the kayobe deployment project which complements kolla-ansible. He is 
> also the most active non-core contributor for last 90 days[1]
> ​​
> Consider this nomination a +1 vote from me
> 
> A +1 vote indicates you are in favor of ​mgoddard as a candidate, a -1 
> is a ​​veto. Voting is open for 7 days until ​May ​4​th, or a unanimous
> response is reached or a veto vote occurs.
> 
> [1] http://stackalytics.com/report/contribution/kolla-group/90
> 
> -- 
> Regards,
> Jeffrey Zhang
> Blog: http://xcodest.me
> __
> 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

-- 
Christian Berendt
Chief Executive Officer (CEO)

Mail: bere...@betacloud-solutions.de
Web: https://www.betacloud-solutions.de

Betacloud Solutions GmbH
Teckstrasse 62 / 70190 Stuttgart / Deutschland

Geschäftsführer: Christian Berendt
Unternehmenssitz: Stuttgart
Amtsgericht: Stuttgart, HRB 756139


__
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

Re: [openstack-dev] [kolla][vote]Retire kolla-kubernetes project

[Christian Berendt]

+1

> On 18. Apr 2018, at 03:51, Jeffrey Zhang <zhang.lei@gmail.com> wrote:
> 
> Since many of the contributors in the kolla-kubernetes project are moved to 
> other things. And there is no active contributor for months.  On the other 
> hand, there is another comparable project, openstack-helm, in the community.  
> For less confusion and disruptive community resource, I propose to retire the 
> kolla-kubernetes project.
> 
> More discussion about this you can check the mail[0] and patch[1]
> 
> please vote +1 to retire the repo, or -1 not to retire the repo. The vote 
> will be open until everyone has voted, or for 1 week until April 25th, 2018.
> 
> [0] http://lists.openstack.org/pipermail/openstack-dev/2018-March/128822.html
> [1] https://review.openstack.org/552531
> 
> -- 
> Regards,
> Jeffrey Zhang
> Blog: http://xcodest.me
> __
> 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

-- 
Christian Berendt
Chief Executive Officer (CEO)

Mail: bere...@betacloud-solutions.de
Web: https://www.betacloud-solutions.de

Betacloud Solutions GmbH
Teckstrasse 62 / 70190 Stuttgart / Deutschland

Geschäftsführer: Christian Berendt
Unternehmenssitz: Stuttgart
Amtsgericht: Stuttgart, HRB 756139


__
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

Re: [openstack-dev] [kolla] kolla-ansible cli proposal

[Christian Berendt]

In my opinion, a separate repository would be most suitable for this. So we do 
not mix the ansible roll with a frontend for ansible itself and are independent.

Importing the project into the OpenStack namespace is probably easier this way.

Christian.

> On 20. Mar 2018, at 18:02, Borne Mace <borne.m...@oracle.com> wrote:
> 
> Greetings all,
> 
> One of the discussions we had at the recent PTG was in regards to the
> blueprint to add support for a kolla-ansible cli [0].  I would like to
> propose that to satisfy this blueprint the thus far Oracle developed
> kollacli be completely upstreamed and made a community guided project.
> 
> The source for the project is available already [1] and it is known to
> work against the Queens codebase.  My suggestion would be that either a
> new repository be created for it or it be included in the
> kolla-ansible repository.  Either way my hope is that it be under
> kolla project control, as far as PTL guidance and core contributors.
> 
> The kollacli is documented here [2] for your review, and along with
> any discussion that folks want to have on the mailing list I will make
> sure to be around for the next couple of wednesday kolla meetings so
> that it can be discussed there as well.
> 
> Thanks much for taking the time to read this,
> 
> -- Borne Mace
> 
> [0]: https://blueprints.launchpad.net/kolla/+spec/kolla-multicloud-cli
> [1]: https://oss.oracle.com/git/gitweb.cgi?p=openstack-kollacli.git;a=summary
> [2]: https://docs.oracle.com/cd/E90981_01/E90982/html/kollacli.html
> 
> 
> __
> 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

-- 
Christian Berendt
Chief Executive Officer (CEO)

Mail: bere...@betacloud-solutions.de
Web: https://www.betacloud-solutions.de

Betacloud Solutions GmbH
Teckstrasse 62 / 70190 Stuttgart / Deutschland

Geschäftsführer: Christian Berendt
Unternehmenssitz: Stuttgart
Amtsgericht: Stuttgart, HRB 756139


__
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

Re: [openstack-dev] [kolla][vote] core nomination for caoyuan

[Christian Berendt]

+1

> On 12. Mar 2018, at 03:06, Jeffrey Zhang <zhang.lei@gmail.com> wrote:
> 
> It is my pleasure to nominate caoyuan for kolla core team.

-- 
Christian Berendt
Chief Executive Officer (CEO)

Mail: bere...@betacloud-solutions.de
Web: https://www.betacloud-solutions.de

Betacloud Solutions GmbH
Teckstrasse 62 / 70190 Stuttgart / Deutschland

Geschäftsführer: Christian Berendt
Unternehmenssitz: Stuttgart
Amtsgericht: Stuttgart, HRB 756139


__
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

Re: [openstack-dev] [kolla][ptg] Team dinner

[Christian Berendt]

+1

Thanks for the organisation.

> On 26. Feb 2018, at 20:39, Paul Bourke <paul.bou...@oracle.com> wrote:
> 
> Hey Kolla,
> 
> Hope you're all enjoying Dublin so far :) Some have expressed interest in 
> getting together for a team meal, how does Thursday sound? Please reply to 
> this with +1/-1 and I can see about booking something.
> 
> Cheers,
> -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

-- 
Christian Berendt
Chief Executive Officer (CEO)

Mail: bere...@betacloud-solutions.de
Web: https://www.betacloud-solutions.de

Betacloud Solutions GmbH
Teckstrasse 62 / 70190 Stuttgart / Deutschland

Geschäftsführer: Christian Berendt
Unternehmenssitz: Stuttgart
Amtsgericht: Stuttgart, HRB 756139


__
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

Re: [openstack-dev] [kolla] Rocky PTL candidacy

[Christian Berendt]

Hello Paul.

> On 5. Feb 2018, at 11:12, Paul Bourke <paul.bou...@oracle.com> wrote:
> 
> This does not mean I don't have a vision for Kolla - no project is perfect


Regardless of that, I would be interested in your visions. What specifically do 
you want to tackle in the next cycle in kolla? What should be the focus?

Christian.

-- 
Christian Berendt
Chief Executive Officer (CEO)

Mail: bere...@betacloud-solutions.de
Web: https://www.betacloud-solutions.de

Betacloud Solutions GmbH
Teckstrasse 62 / 70190 Stuttgart / Deutschland

Geschäftsführer: Christian Berendt
Unternehmenssitz: Stuttgart
Amtsgericht: Stuttgart, HRB 756139


__
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

Re: [openstack-dev] [kolla][kolla-ansible] Proposing Surya (spsurya) for core

[Christian Berendt]

+1 

> On 14. Jun 2017, at 17:46, Michał Jastrzębski <inc...@gmail.com> wrote:
> 
> Hello,
> 
> With great pleasure I'm kicking off another core voting to
> kolla-ansible and kolla teams:) this one is about spsurya. Voting will
> be open for 2 weeks (till 28th Jun).
> 
> Consider this mail my +1 vote, you know the drill:)
> 
> Regards,
> Michal
> 
> __
> 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

-- 
Christian Berendt
Chief Executive Officer (CEO)

Mail: bere...@betacloud-solutions.de
Web: https://www.betacloud-solutions.de

Betacloud Solutions GmbH
Teckstrasse 62 / 70190 Stuttgart / Deutschland

Geschäftsführer: Christian Berendt
Unternehmenssitz: Stuttgart
Amtsgericht: Stuttgart, HRB 756139


__
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

Re: [openstack-dev] [kolla] Which distros are used as base ones?

[Christian Berendt]

> On 27. Apr 2017, at 11:46, Marcin Juszkiewicz <marcin.juszkiew...@linaro.org> 
> wrote:
> 
> Does someone care about Ubuntu?

Yes, we do. We are using the Ubuntu source images with the Newton and Ocata 
branches from kolla/kolla-ansible.

Christian.

-- 
Christian Berendt
Chief Executive Officer (CEO)

Mail: bere...@betacloud-solutions.de
Web: https://www.betacloud-solutions.de

Betacloud Solutions GmbH
Teckstrasse 62 / 70190 Stuttgart / Deutschland

Geschäftsführer: Christian Berendt
Unternehmenssitz: Stuttgart
Amtsgericht: Stuttgart, HRB 756139


__
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

Re: [openstack-dev] [OpenStack-docs] [openstack-docs] [dev] What's up, Doc?

[Christian Berendt]

> On 24 Feb 2017, at 13:32, Alexandra Settle <a.set...@outlook.com> wrote:
> 
> Please vote for your fellow documenter below:

The community voting for Boston already closed.

Christian.

-- 
Christian Berendt
Chief Executive Officer (CEO)

Mail: bere...@betacloud-solutions.de
Web: https://www.betacloud-solutions.de

Betacloud Solutions GmbH
Teckstrasse 62 / 70190 Stuttgart / Deutschland

Geschäftsführer: Christian Berendt
Unternehmenssitz: Stuttgart
Amtsgericht: Stuttgart, HRB 756139


__
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

Re: [openstack-dev] [kolla] Structuring the documentation on all repositories

[Christian Berendt]

> On 20 Feb 2017, at 11:52, Paul Bourke <paul.bou...@oracle.com> wrote:
> 
> I'm a little confused on the final outcome, it sounds like most of what 
> you've written is currently the case.
> 
> Besides a more user friendly deploy guide appearing under 
> https://docs.openstack.org/project-deploy-guide/ocata/, what is changing?

* all deploy instructions will be moved from doc directory in the deploy-guide 
directory
* all generic information will be removed from kolla-ansible/kolla-k8s 
repositories and will be provided in the kolla repository
* the generic information in the kolla repository will be extented

Christian.

-- 
Christian Berendt
Chief Executive Officer (CEO)

Mail: bere...@betacloud-solutions.de
Web: https://www.betacloud-solutions.de

Betacloud Solutions GmbH
Teckstrasse 62 / 70190 Stuttgart / Deutschland

Geschäftsführer: Christian Berendt
Unternehmenssitz: Stuttgart
Amtsgericht: Stuttgart, HRB 756139


__
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-dev] [kolla] Structuring the documentation on all repositories

[Christian Berendt]

This is a summary about structuring the documentation on all repositories as 
discussed at the PTG (https://etherpad.openstack.org/p/kolla-pike-ptg-docs).

The doc directory:

kolla/doc — kolla developer documentation (about our docker images) and generic 
documentation
kolla-ansible/doc — kolla-ansible developer documentation
kolla-k8s/doc — kolla-k8s developer documentation

Contents will be published to https://docs.openstack.org/developer/kolla…/

The doc directory in the kolla repositories will be splitted into 2 parts and 
will keep the generic kolla documentation (landing page, mission, philosophy, 
explanation of deliverables, overview of deployment guides (previous QSG), bug 
triage, how to contribute, ...) and the development documentation related to 
kolla images.

The central entry point (landing page) for the kolla project will be 
https://docs.openstack.org/developer/kolla.

The deploy-guide directory:

kolla-ansible/deploy-guide — Kolla deployment guide for Ansible, how to deploy 
with kolla-ansible (previous name: quick start guide)
kolla-k8s/deploy-guide — Kolla deployment guide for K8S, how to deploy with 
kolla-k8s (previous name: quick start guide)

We will add 2 links to https://docs.openstack.org/project-deploy-guide/ocata/:

* Kolla deployment guide for Ansible
* Kolla deployment guide for K8S

Sample split for kolla-ansible prepared at 
https://review.openstack.org/#/c/427965/.

The guides itself will be published at 
https://docs.openstack.org/project-deploy-guide/ocata/kolla-ansible and 
https://docs.openstack.org/project-deploy-guide/ocata/kolla-k8s.

Christian.

-- 
Christian Berendt
Chief Executive Officer (CEO)

Mail: bere...@betacloud-solutions.de
Web: https://www.betacloud-solutions.de

Betacloud Solutions GmbH
Teckstrasse 62 / 70190 Stuttgart / Deutschland

Geschäftsführer: Christian Berendt
Unternehmenssitz: Stuttgart
Amtsgericht: Stuttgart, HRB 756139


__
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

Re: [openstack-dev] [kolla] Mascot

[Christian Berendt]

> On 14 Feb 2017, at 17:27, Steven Dake (stdake) <std...@cisco.com> wrote:
> 
> The mascot is absolutely fantastic!  Nice work to all involved!

Woot! Awesome!

-- 
Christian Berendt
Chief Executive Officer (CEO)

Mail: bere...@betacloud-solutions.de
Web: https://www.betacloud-solutions.de

Betacloud Solutions GmbH
Teckstrasse 62 / 70190 Stuttgart / Deutschland

Geschäftsführer: Christian Berendt
Unternehmenssitz: Stuttgart
Amtsgericht: Stuttgart, HRB 756139


__
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

Re: [openstack-dev] [vote][kolla] deprecation for Debian distro support

[Christian Berendt]

As discussed in todays team meeting [0]:

* the vote is closed
* the deprecation is delayed

http://eavesdrop.openstack.org/meetings/kolla/2017/kolla.2017-01-25-16.01.log.html

Christian.

-- 
Christian Berendt
Chief Executive Officer (CEO)

Mail: bere...@betacloud-solutions.de
Web: https://www.betacloud-solutions.de

Betacloud Solutions GmbH
Teckstrasse 62 / 70190 Stuttgart / Deutschland

Geschäftsführer: Christian Berendt
Unternehmenssitz: Stuttgart
Amtsgericht: Stuttgart, HRB 756139


__
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-dev] [vote][kolla] deprecation for Debian distro support

[Christian Berendt]

As discussed in one of the last team meetings I want to propose the deprecation 
(this cycle) and removal (next cycle) of the Debian support in Kolla.

More than 1 week ago I sent a pre warning mail to the openstack-operators 
mailing list, without any reply [0].

Kolla core reviewers, please vote now. The vote will be open for 7 days 
(26.01.2017).

1. Kolla needs support for Debian, it should not be deprecated

2. Kolla should deprecate support for Debian

[0] 
http://lists.openstack.org/pipermail/openstack-operators/2017-January/012427.html

-- 
Christian Berendt
Chief Executive Officer (CEO)

Mail: bere...@betacloud-solutions.de
Web: https://www.betacloud-solutions.de

Betacloud Solutions GmbH
Teckstrasse 62 / 70190 Stuttgart / Deutschland

Geschäftsführer: Christian Berendt
Unternehmenssitz: Stuttgart
Amtsgericht: Stuttgart, HRB 756139


__
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

Re: [openstack-dev] [kolla] kolla-build building images that are known not to work for a given base/type

[Christian Berendt]

Hello David.

Sounds reasonable. I transferred your mail into a Launchpad bug:

https://bugs.launchpad.net/kolla/+bug/1656753

Christian.

-- 
Christian Berendt
Chief Executive Officer (CEO)

Mail: bere...@betacloud-solutions.de
Web: https://www.betacloud-solutions.de

Betacloud Solutions GmbH
Teckstrasse 62 / 70190 Stuttgart / Deutschland

Geschäftsführer: Christian Berendt
Unternehmenssitz: Stuttgart
Amtsgericht: Stuttgart, HRB 756139


__
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

Re: [openstack-dev] [docs] Stepping down from core

[Christian Berendt]

Matt, I wish you the best and much success on your further journey. In the past 
I was able to learn a lot from you and I always appreciated your work.

Christian.

-- 
Christian Berendt
Chief Executive Officer (CEO)

Mail: bere...@betacloud-solutions.de
Web: https://www.betacloud-solutions.de

Betacloud Solutions GmbH
Teckstrasse 62 / 70190 Stuttgart / Deutschland

Geschäftsführer: Christian Berendt
Unternehmenssitz: Stuttgart
Amtsgericht: Stuttgart, HRB 756139


__
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-dev] [kolla] Bugs cleanup dashboard

[Christian Berendt]

Hello everybody.

Based on the dashboard which is used for the Nova project I have created one 
for Kolla. The dashboard gets updated hourly.

http://kolla.betacloud.io/bugs-dashboard.html

Christian.

-- 
Christian Berendt
Chief Executive Officer (CEO)

Mail: bere...@betacloud-solutions.de
Web: https://www.betacloud-solutions.de

Betacloud Solutions GmbH
Teckstrasse 62 / 70190 Stuttgart / Deutschland

Geschäftsführer: Christian Berendt
Unternehmenssitz: Stuttgart
Amtsgericht: Stuttgart, HRB 756139


__
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

Re: [openstack-dev] [kolla] Question about config cinder volume

[Christian Berendt]

> On 2 Dec 2016, at 14:49, Jason HU <huzhiji...@gmail.com> wrote:
> 1. Will Glance use Cinder volume as storage automatically when I enable 
> Cinder?

The default store for Glance is “file" when not using Ceph.

https://github.com/openstack/kolla-ansible/blob/master/ansible/roles/glance/templates/glance-api.conf.j2#L68-L71

You can change this by using custom configurations 
(http://docs.openstack.org/developer/kolla/advanced-configuration.html#openstack-service-configuration-in-kolla).

> 2. I heard that kolla has a third party plugin method which can be used to do 
> some setup on target node. Can it be used to setup the cinder-volume vg? Is 
> there any example on doing this?

http://docs.openstack.org/developer/kolla/image-building.html#plugin-functionality

We support a plugin functionality for our Docker templates.

I think it is better to create the required volume group with a custom Ansible 
playbook during the bootstrap of your storage node.

> 3. The storage system is HDS AMS2300 which seems do not supported by any 
> Cinder driver. So I have to use LVM backend. According to the cinder/glance 
> bug mentioned in Kolla doc, does it mean that I can not deploy 
> multi-controller scenario, unless using Ceph?

Check if you can use the HDS AMS2300 as external iSCSI storage 
(http://docs.openstack.org/developer/kolla/cinder-guide.html#cinder-back-end-with-external-iscsi-storage).

I think the use of LVM2 / iSCSI as a layer before the storage backend is not a 
good idea.

HTH, Christian.

-- 
Christian Berendt
Chief Executive Officer (CEO)

Mail: bere...@betacloud-solutions.de
Web: https://www.betacloud-solutions.de

Betacloud Solutions GmbH
Teckstrasse 62 / 70190 Stuttgart / Deutschland

Geschäftsführer: Christian Berendt
Unternehmenssitz: Stuttgart
Amtsgericht: Stuttgart, HRB 756139


__
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

Re: [openstack-dev] [kolla][kolla-ansible][kolla-kubernetes] Kolla core election policy change - vote

[Christian Berendt]

+1

> On 16 Nov 2016, at 19:23, Michał Jastrzębski <inc...@gmail.com> wrote:
> 
> Hello,
> 
> In light of recent events (kolla-kubernetes becoming thriving project,
> kolla-ansible being split) I feel we need to change of core reviewer
> election process.
> 
> Currently Kolla was single core team. That is no longer the case, as
> right now we have 3 distinct core teams (kolla, kolla-ansible and
> kolla-kubernetes), although for now with big overlap in terms of
> people in them.
> 
> For future-proofing, as we already have difference between teams, I
> propose following change to core election process:
> 
> 
> Core reviewer voting rights are reserved by core team in question.
> Which means if someone propose core reviewer to kolla-kubernetes, only
> kolla-kubernetes cores has a voting right (not kolla or kolla-ansible
> cores).
> 
> 
> Voting will be open until 30 Nov '16 end of day. Reviewers from all
> core teams in kolla has voting rights on this policy change.
> 
> Regards
> Michal
> 
> __
> 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

-- 
Christian Berendt
Chief Executive Officer (CEO)

Mail: bere...@betacloud-solutions.de
Web: https://www.betacloud-solutions.de

Betacloud Solutions GmbH
Teckstrasse 62 / 70190 Stuttgart / Deutschland

Geschäftsführer: Christian Berendt
Unternehmenssitz: Stuttgart
Amtsgericht: Stuttgart, HRB 756139


__
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

Re: [openstack-dev] [kolla] Vote to add zhubingbing to core team

[Christian Berendt]

> On 29 Nov 2016, at 17:21, Michał Jastrzębski <inc...@gmail.com> wrote:
> 
> I'd like to propose to add zhubingbing to kolla (and kolla-ansible)
> core teams. He did great job reviewing code during last couple of
> months.

+1

-- 
Christian Berendt
Chief Executive Officer (CEO)

Mail: bere...@betacloud-solutions.de
Web: https://www.betacloud-solutions.de

Betacloud Solutions GmbH
Teckstrasse 62 / 70190 Stuttgart / Deutschland

Geschäftsführer: Christian Berendt
Unternehmenssitz: Stuttgart
Amtsgericht: Stuttgart, HRB 756139


__
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

Re: [openstack-dev] [kolla] Notes on Ansible fact gathering

[Christian Berendt]

> On 23 Nov 2016, at 12:12, Paul Bourke <paul.bou...@oracle.com> wrote:
> 
> In the cases where users have 500 control nodes and want to add five more 
> sequentially (the value of doing more than one sequentially is still not 
> clear to me), we could look into turning on fact caching.

At https://betacloud.io/speedup-kolla-with-ansible-fact-caching/ I documented a 
few months ago how to enable fact caching for Kolla or for ansible in general. 
Possibly it is helpful for someone who wants to test it.

-- 
Christian Berendt
Chief Executive Officer (CEO)

Mail: bere...@betacloud-solutions.de
Web: https://www.betacloud-solutions.de

Betacloud Solutions GmbH
Teckstrasse 62 / 70190 Stuttgart / Deutschland

Geschäftsführer: Christian Berendt
Unternehmenssitz: Stuttgart
Amtsgericht: Stuttgart, HRB 756139


__
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

Re: [openstack-dev] [kolla] the alternative of log processing tool

[Christian Berendt]

> On 27 Nov 2016, at 06:55, Jeffrey Zhang <zhang.lei@gmail.com> wrote:
> 
> * Fluentd
> * Logstash

I do not have a strong behaviour.

At the moment we use the E and K of the ELK stack. Because of that I think it 
makes sense to go with Logstash. In this way, we have a stack developed by one 
community and which is tuned to each other.

Christian.

-- 
Christian Berendt
Chief Executive Officer (CEO)

Mail: bere...@betacloud-solutions.de
Web: https://www.betacloud-solutions.de

Betacloud Solutions GmbH
Teckstrasse 62 / 70190 Stuttgart / Deutschland

Geschäftsführer: Christian Berendt
Unternehmenssitz: Stuttgart
Amtsgericht: Stuttgart, HRB 756139


__
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

Re: [openstack-dev] [kolla] Propose removal of TrivialFix requirement

[Christian Berendt]

> On 3 Nov 2016, at 14:33, Mauricio Lima  wrote:
> 
> I Agree. +1

+1

__
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

Re: [openstack-dev] Deprecation Policies (related to Heka)

[Christian Berendt]

> On 29 Sep 2016, at 06:26, Steven Dake (stdake)  wrote:
> 
> If you have a different parsing of the deprecation policy, feel free to chime 
> in.

Heka is only used as an internal component of Kolla and is not provided as a 
service for the operators. It should be sufficient to replace Heka by something 
else without deprecating it.

Christian.


signature.asc
Description: Message signed with OpenPGP using GPGMail
__
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

Re: [openstack-dev] [kolla] the user in container should NOT have write permission for configuration file

[Christian Berendt]

> On 26 Sep 2016, at 16:43, Sam Yaple  wrote:
> 
> So this actually makes it _less_ secure. The 0600 permissions were chosen for 
> a reason.  The nova.conf file has passwords to the DB and rabbitmq. If the 
> configuration files are world readable then those passwords could leak to an 
> unprivileged user on the host.

Confirmed. Please do not make configuration files world readable.

We use volumes for the configuration file directories. Why do we not simply use 
read only volumes? This way we do not have to touch the current implementation 
(files are owned by the service user with 0600 permissions) and can make the 
configuration files read only.

Christian.


signature.asc
Description: Message signed with OpenPGP using GPGMail
__
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

Re: [openstack-dev] [vote][kolla] deprecation for debian distro support

[Christian Berendt]

> On 22 Sep 2016, at 17:16, Ryan Hallisey  wrote:
> 
> I agree with Michal and Martin. I was a little reluctant to respond here 
> because the Debian additions are new, while Fedora has been around since the 
> beginning and never got a ton of testing.
> 
> Berendt what's your take here?

It is fine for me to keep Debian if someone committed to continue working on it.

Christian.


signature.asc
Description: Message signed with OpenPGP using GPGMail
__
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

Re: [openstack-dev] [vote][kolla] deprecation for debian distro support

[Christian Berendt]

Thanks for moving this forward.

> On 19 Sep 2016, at 19:44, Jeffrey Zhang  wrote:
> 
> Please vote:
> 
> 1. Kolla needs support Debian( if so, we need some guys to set up the
> gate and fix all the issues ASAP in O cycle)
> 2. Kolla should deprecate Debian support

+1 on option 2.


signature.asc
Description: Message signed with OpenPGP using GPGMail
__
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

Re: [openstack-dev] [vote][kolla] deprecation for fedora distro support

[Christian Berendt]

Thanks for moving this forward.

> On 19 Sep 2016, at 19:40, Jeffrey Zhang  wrote:
> 
> 1. Kolla needs support fedora( if so, we need some guys to set up the
> gate and fix all the issues ASAP in O cycle)
> 2. Kolla should deprecate fedora support

+1 on option 2.


signature.asc
Description: Message signed with OpenPGP using GPGMail
__
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

Re: [openstack-dev] [vote][kolla] Core Nomination for Christian Berendt (berendt on irc)

[Christian Berendt]

> On 16 Sep 2016, at 02:06, Steven Dake (stdake) <std...@cisco.com> wrote:
> 
> Welcome to the core review team!

Thank you for being added to the group of core reviewers of Kolla. Looking 
forward to work with all of you.

Christian.

--
Christian Berendt
Chief Executive Officer (CEO)

Mail: bere...@betacloud-solutions.de
Web: https://www.betacloud-solutions.de

Betacloud Solutions GmbH
Teckstrasse 62 / 70190 Stuttgart / Deutschland

Geschäftsführer: Christian Berendt
Unternehmenssitz: Stuttgart
Amtsgericht: Stuttgart, HRB 756139



signature.asc
Description: Message signed with OpenPGP using GPGMail
__
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

Re: [openstack-dev] [vote][kolla] Splitting out Ansible into a separate deliverable

[Christian Berendt]

> On 15 Sep 2016, at 08:12, Steven Dake (stdake)  wrote:
> 
> c)   Split the repository shortly after tagging 3.0.0 – creating a 
> kolla-ansible deliverable for Ocata.

+1

Christian.


signature.asc
Description: Message signed with OpenPGP using GPGMail
__
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

Re: [openstack-dev] [kolla] Problem regarding named volume data location

[Christian Berendt]

> On 02 Sep 2016, at 19:04, Jeffrey Zhang  wrote:
> 
> I think the right solution should warn the end-user: you need configure a 
> large partition for /var/lib/docker.

Confirmed. The volumes of Mongodb and of Mariadb are getting pretty big as 
well. Using /var/lib/nova (or /var/lib/mariadb, ..) on the local filesystem 
instead of a named volume will change nothing.

I think it is the best to stay with named volumes and to document the host 
requirements.

While using named volumes it is also possible to use alternative Docker volume 
plugins like Convoy.

Christian.


signature.asc
Description: Message signed with OpenPGP using GPGMail
__
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

Re: [openstack-dev] [kolla] Requirement for bug when reno is present

[Christian Berendt]

> On 30 Aug 2016, at 12:42, Paul Bourke  wrote:
> 
> Do people feel we still want to require a bug-id in the commit message for 
> features, when reno notes are present? My understanding is that till now 
> we've required people to add bugs for non trivial features in order to track 
> them as part of releases. Does/should reno supersede this?

I think it makes sense to keep the bug/blueprint id because some of our 
features are distributed in several reviews and only one of the reviews 
includes the release note. When removing the bug/blueprint ids from the commit 
message when a reno note will be added with one of the reviews it will be 
difficult to track the relations.

Christian.


signature.asc
Description: Message signed with OpenPGP using GPGMail
__
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-dev] [kolla] future of Debian images

[Christian Berendt]

Hello everybody.

With this mail I want to propose the deprecation and removal of Debian images 
from the Kolla project.

* On the gates we only test the build of binary images for the following 
distributions: centos,  oraclelinux, ubuntu-trusty, ubuntu-xenial 
(https://github.com/openstack-infra/project-config/blob/master/jenkins/jobs/projects.yaml#L5485-L5510)

* The most Dockerfile templates do not handle Debian for binary images (only 37 
templates handle base_distro type debian, 108 templates handle base_distro type 
ubuntu)

Christian.

--
Christian Berendt
Chief Executive Officer (CEO)

Mail: bere...@betacloud-solutions.de
Web: https://www.betacloud-solutions.de

Betacloud Solutions GmbH
Teckstrasse 62 / 70190 Stuttgart / Deutschland

Geschäftsführer: Christian Berendt
Unternehmenssitz: Stuttgart
Amtsgericht: Stuttgart, HRB 756139



signature.asc
Description: Message signed with OpenPGP using GPGMail
__
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-dev] Call for papers already closed?

[Christian Berendt]

Hello.

I am a little bit confused, according to openstack.org:

FEBRUARY 1 IS THE DEADLINE TO SUBMIT A TALK (11:59PM PST)

I tried to edit a submitted talk and got the following message:

Call for speaker closed!

Also I have the following note in my interface:

Warning! You reached presentations submissions limit (3).

Is it not possible to submit more than 3 talks? Anyway, at the moment I 
only have 2 talks (1 submitted be my, 1 submitted by a other person). I 
am submitting the talks for all of my colleagues and we prepared more 
than 3 talks.


Christian.

--
Christian Berendt
Cloud Solution Architect
Mail: bere...@b1-systems.de

B1 Systems GmbH
Osterfeldstraße 7 / 85088 Vohburg / http://www.b1-systems.de
GF: Ralph Dehner / Unternehmenssitz: Vohburg / AG: Ingolstadt,HRB 3537

__
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

Re: [openstack-dev] Call for papers already closed?

[Christian Berendt]

On 02/01/2016 08:46 AM, Wang, Shane wrote:

Yes, I was confused too. The time is yet up.


It should not be closed, but it is at the moment :/ I forwarded my 
previous mail to sum...@openstack.org and hope that somebody can take 
care of this issue.


Christian.

--
Christian Berendt
Cloud Solution Architect
Mail: bere...@b1-systems.de

B1 Systems GmbH
Osterfeldstraße 7 / 85088 Vohburg / http://www.b1-systems.de
GF: Ralph Dehner / Unternehmenssitz: Vohburg / AG: Ingolstadt,HRB 3537

__
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-dev] [nova] do not account compute resource of instances in state SHELVED_OFFLOADED

[Christian Berendt]

After offloading a shelved instance the freed compute resources are 
still accounted.


I think it makes sense to make this behavior configurable. We often have 
the request to not account the freed compute resources after an 
instances was offloaded to be able to spawn new instances or to 
unshelved offloaded instances even the assigned compute resource quota 
was archieved.


Because the instance are shelved and offloaded they do not occupy 
compute resource and it is often safe to allow the freed compute 
resources for other inststances. Of coure it has to be checked if there 
are enough free compute resource when trying to unshelve an offloaded 
instance.


What do you thin about this use case? If it make sense to you I want to 
propose to write a spec for this feature.


Christian.

--
Christian Berendt
Cloud Solution Architect
Mail: bere...@b1-systems.de

B1 Systems GmbH
Osterfeldstraße 7 / 85088 Vohburg / http://www.b1-systems.de
GF: Ralph Dehner / Unternehmenssitz: Vohburg / AG: Ingolstadt,HRB 3537

__
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

Re: [openstack-dev] How to get the current stable release

[Christian Berendt]

On 01/12/2016 08:55 AM, Christian Berendt wrote:

Sorry if this is a stupid question and I waste your time. I am looking
for a file that speicifes the name and version number of the latest
stable release.


As a use case the following example:

We have a sitemap generator that builds a sitemap.xml file for docs.o.o. 
Now we want to set a higher priority for URLs related to the current 
stable release ( https://review.openstack.org/#/c/266241/ ). At the 
moment I have to hard code the name of the current stable release to be 
able to check for it and have to remember this and update it with every 
upcoming release. I think it is more intuitive to have this piece of 
information in a central file.


Christian.

--
Christian Berendt
Cloud Solution Architect
Mail: bere...@b1-systems.de

B1 Systems GmbH
Osterfeldstraße 7 / 85088 Vohburg / http://www.b1-systems.de
GF: Ralph Dehner / Unternehmenssitz: Vohburg / AG: Ingolstadt,HRB 3537

__
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-dev] How to get the current stable release

[Christian Berendt]

Sorry if this is a stupid question and I waste your time. I am looking 
for a file that speicifes the name and version number of the latest 
stable release.


I have not found this information in the governance repository (I only 
found a hard coded variable called latest_stable_branch in the 
tool/stable.py script, using kilo as the current value 
(https://github.com/openstack/governance/blob/master/tools/stable.py#L21-L24)).


In the releases repository is a note in the doc/source/index.rst file (I 
think this is the source of http://docs.openstack.org/releases/) that 
releases/liberty is the current stable release.


Christian.

--
Christian Berendt
Cloud Solution Architect
Mail: bere...@b1-systems.de

B1 Systems GmbH
Osterfeldstraße 7 / 85088 Vohburg / http://www.b1-systems.de
GF: Ralph Dehner / Unternehmenssitz: Vohburg / AG: Ingolstadt,HRB 3537

__
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

Re: [openstack-dev] [all][docs] Incorrect '/p' in Project Source URLs on docs.openstack.org/developer

[Christian Berendt]

On 10/16/2015 01:46 PM, Neil Jerram wrote:
> I'd be happy to submit a fix for this, but I haven't yet found which
> project generates this URL.  Can someone advise?

The developer documentations use the oslosphinx
theme.(http://git.openstack.org/cgit/openstack/oslosphinx). The
mentioned URL is generated in
https://github.com/openstack/oslosphinx/blob/master/oslosphinx/__init__.py#L20-L36.
Probably there is something wrong.

Christian.

-- 
Christian Berendt
Cloud Solution Architect
Mail: bere...@b1-systems.de

B1 Systems GmbH
Osterfeldstraße 7 / 85088 Vohburg / http://www.b1-systems.de
GF: Ralph Dehner / Unternehmenssitz: Vohburg / AG: Ingolstadt,HRB 3537

__
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

Re: [openstack-dev] [tc] naming N and O releases nowish

[Christian Berendt]

On 10/07/2015 02:57 PM, Thierry Carrez wrote:
> ...which if I read it correctly means we could pick N now, but not O. We
> might want to change that (again) first.

Is this list correct?

M = Tokyo
N = Atlanta
O = Barcelona
P = ?

Christian.

-- 
Christian Berendt
Cloud Solution Architect
Mail: bere...@b1-systems.de

B1 Systems GmbH
Osterfeldstraße 7 / 85088 Vohburg / http://www.b1-systems.de
GF: Ralph Dehner / Unternehmenssitz: Vohburg / AG: Ingolstadt,HRB 3537

__
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

Re: [openstack-dev] [heat] perfomance benchmark metrics of heat-api

[Christian Berendt]

On 10/06/2015 05:20 AM, ESWAR RAO wrote:

Has anyone done any performance tests on heat-api servers on any
standard setup so as to know how many stack requests it can handle
before it can stumble so that we can deploy scaling of heat-servers ??


It depends on your environment and you should run your own tests. Have a 
look at 
https://github.com/openstack/rally/tree/master/samples/tasks/scenarios/heat 
for a lot of prepared scenarios for Heat.


HTH, Christian.

--
Christian Berendt
Cloud Solution Architect
Mail: bere...@b1-systems.de

B1 Systems GmbH
Osterfeldstraße 7 / 85088 Vohburg / http://www.b1-systems.de
GF: Ralph Dehner / Unternehmenssitz: Vohburg / AG: Ingolstadt,HRB 3537

__
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

Re: [openstack-dev] [OpenStack-docs] [docs][ptl] Docs PTL Candidacy

[Christian Berendt]

On 09/14/2015 04:31 AM, Lana Brindley wrote:

I'd love to have your support for the PTL role for Mitaka, and I'm
looking forward to continuing to grow the documentation team.


You have my support. Thanks for your great work during the current cycle.

Christian.

--
Christian Berendt
Cloud Solution Architect
Mail: bere...@b1-systems.de

B1 Systems GmbH
Osterfeldstraße 7 / 85088 Vohburg / http://www.b1-systems.de
GF: Ralph Dehner / Unternehmenssitz: Vohburg / AG: Ingolstadt,HRB 3537

__
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-dev] [keystone] creating new users with invalid mail addresses possible

[Christian Berendt]

At the moment it is possible to create new users with invalid mail 
addresses. I pasted the output of my test at 
http://paste.openstack.org/show/456642/. (the listing of invalid mail 
addresses is available at 
http://codefool.tumblr.com/post/15288874550/list-of-valid-and-invalid-email-addresses).


Is it intended that addresses are not be validated?

Does it makes sense to validate addresses (e.g. with 
https://github.com/mailgun/flanker)?


Christian.

--
Christian Berendt
Cloud Solution Architect
Mail: bere...@b1-systems.de

B1 Systems GmbH
Osterfeldstraße 7 / 85088 Vohburg / http://www.b1-systems.de
GF: Ralph Dehner / Unternehmenssitz: Vohburg / AG: Ingolstadt,HRB 3537

__
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-dev] [nova] installation of requirements not possible because of wrong pip version

[Christian Berendt]

According to requirements.txt we require pip=6.0. Trying to install the 
requirements for nova with pip 6.1.1 is not possible at the moment 
because of the following issue:


$ virtualenv .venv
$ source .venv/bin/activate
$ pip install -r requirements.txt
You are using pip version 6.1.1, however version 7.1.0 is available.
You should consider upgrading via the 'pip install --upgrade pip' command.
Double requirement given: Routes!=2.0,=1.12.3 (from -r requirements.txt 
(line 14)) (already in Routes!=2.0,!=2.1,=1.12.3 (from -r 
requirements.txt (line 13)), name='Routes')


It looks like pip 6.1.1 cannot handle the following 2 lines in 
requirements.txt:


Routes=1.12.3,!=2.0,!=2.1;python_version=='2.7'
Routes=1.12.3,!=2.0;python_version!='2.7'

After upgrading pip to the latest available version (7.1.0) with pip 
install --upgrade pip everything is working like expected.


Does this mean that we have to require at least pip=7.1.0 in the global 
requirements?


Christian.

--
Christian Berendt
Cloud Solution Architect
Mail: bere...@b1-systems.de

B1 Systems GmbH
Osterfeldstraße 7 / 85088 Vohburg / http://www.b1-systems.de
GF: Ralph Dehner / Unternehmenssitz: Vohburg / AG: Ingolstadt,HRB 3537

__
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

Re: [openstack-dev] [nova] installation of requirements not possible because of wrong pip version

[Christian Berendt]

On 08/07/2015 10:52 PM, Robert Collins wrote:

I don't know why Nova has a requirement expressed on pip, since
requirements.txt is evaluated by pip its too late. Does Nova actually
consume pip itself?


pip is not listed in the requirements.txt file of nova. pip is listed in 
the global requirements:


https://github.com/openstack/requirements/blob/master/global-requirements.txt#L112

My understanding is that it is possible to use pip=6.0. Is that wrong?

Is there an other place where we documented which version of pip can be 
used with the requirement.txt files (based on global-requirements.txt)?


Christian.

--
Christian Berendt
Cloud Solution Architect
Mail: bere...@b1-systems.de

B1 Systems GmbH
Osterfeldstraße 7 / 85088 Vohburg / http://www.b1-systems.de
GF: Ralph Dehner / Unternehmenssitz: Vohburg / AG: Ingolstadt,HRB 3537

__
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

Re: [openstack-dev] Improving OpenStack documentation around RabbitMQ

[Christian Berendt]

Hello Michael.

Just moving your thread to the correct mailling list.

Christian.

On 04/28/2015 02:58 PM, Michael Klishin wrote:
 Hi, 
 
 I'm a RabbitMQ engineering team member and we'd like to help improve 
 OpenStack docs
 around it.
 
 I've been reading the docs and making notes of what can be improved. We'd be 
 happy
 to contribute the changes. However, we're not very familiar with the 
 OpenStack development
 process and have a few questions before we start.
 
 As far as I understand, OpenStack Kilo is about to ship. Does this mean we 
 can only contribute
 documentation improvements for the release after it? Are there maintenance 
 releases that doc improvements
 could go into? If so, how is this reflected in repository  branches?
 
 Should the changes we propose be discussed on this list or in GitHub issues 
 [1]?
 
 Finally, we are considering adding a doc guide dedicated to OpenStack on 
 rabbitmq.com (we have one for EC2,
 for instance). Note that we are not looking
 to replace what's on docs.openstack.org, only provide a guide that can go 
 into more details.
 Does this sound like a good idea to the OpenStack community? Should we keep 
 everything on docs.openstack.org?
 Would it be OK if we link to rabbitmq.com guides in any changes we 
 contribute? I don't think OpenStack Juno
 docs have a lot of external links: is that by design?
 
 Thanks.
 
 1. https://github.com/openstack/openstack-manuals 
 --  
 MK  
 
 Staff Software Engineer, Pivotal/RabbitMQ  
 
 
 
 __
 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
 


-- 
Christian Berendt
Cloud Solution Architect
Mail: bere...@b1-systems.de

B1 Systems GmbH
Osterfeldstraße 7 / 85088 Vohburg / http://www.b1-systems.de
GF: Ralph Dehner / Unternehmenssitz: Vohburg / AG: Ingolstadt,HRB 3537

__
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

Re: [openstack-dev] Improving OpenStack documentation around RabbitMQ

[Christian Berendt]

Hello Michael.

Just moving your thread to the correct mailling list.

Sorry for my previous mail. Thunderbird autocompletion used the
unsubscribe alias and not the correct mailinglist :(

Christian.

On 04/28/2015 02:58 PM, Michael Klishin wrote:
 Hi, 
 
 I'm a RabbitMQ engineering team member and we'd like to help improve 
 OpenStack docs
 around it.
 
 I've been reading the docs and making notes of what can be improved. We'd be 
 happy
 to contribute the changes. However, we're not very familiar with the 
 OpenStack development
 process and have a few questions before we start.
 
 As far as I understand, OpenStack Kilo is about to ship. Does this mean we 
 can only contribute
 documentation improvements for the release after it? Are there maintenance 
 releases that doc improvements
 could go into? If so, how is this reflected in repository  branches?
 
 Should the changes we propose be discussed on this list or in GitHub issues 
 [1]?
 
 Finally, we are considering adding a doc guide dedicated to OpenStack on 
 rabbitmq.com (we have one for EC2,
 for instance). Note that we are not looking
 to replace what's on docs.openstack.org, only provide a guide that can go 
 into more details.
 Does this sound like a good idea to the OpenStack community? Should we keep 
 everything on docs.openstack.org?
 Would it be OK if we link to rabbitmq.com guides in any changes we 
 contribute? I don't think OpenStack Juno
 docs have a lot of external links: is that by design?
 
 Thanks.
 
 1. https://github.com/openstack/openstack-manuals 
 --  
 MK  
 
 Staff Software Engineer, Pivotal/RabbitMQ  
 
 
 
 __
 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
 


-- 
Christian Berendt
Cloud Computing Solution Architect
Mail: bere...@b1-systems.de

B1 Systems GmbH
Osterfeldstraße 7 / 85088 Vohburg / http://www.b1-systems.de
GF: Ralph Dehner / Unternehmenssitz: Vohburg / AG: Ingolstadt,HRB 3537

__
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

Re: [openstack-dev] nominating Nathaniel Dillon for security-doc core

[Christian Berendt]

On 03/05/2015 10:14 PM, Bryan D. Payne wrote:
 I'd like to bring him on as a core member of security-doc so that he can
 help with the review and approval process for new changes to the book. 
 Please chime in with your agreement or concerns.

+1.

Christian.

__
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-dev] Removal of copyright statements above the Apache 2.0 license header

[Christian Berendt]

Is it safe to remove copyright statements above the Apache 2.0 license
headers stated in a lot of files?

We recenctly removed all @author tags and added a hacking check to not
longer add @author tags in the future. Can we do the same for the
copyright statements above the Apache 2.0 license headers?

Christian.

__
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

Re: [openstack-dev] Removal of copyright statements above the Apache 2.0 license header

[Christian Berendt]

On 02/17/2015 12:05 PM, Daniel P. Berrange wrote:
 In section 4.(c) the LICENSE text says
 
   (c) You must retain, in the Source form of any Derivative Works
   that You distribute, all copyright, patent, trademark, and
   attribution notices from the Source form of the Work,
   excluding those notices that do not pertain to any part of
   the Derivative Works; and
 
 So based on that, I think it would be a violation to remove any of the
 Copyright acmeco lines in the file header.

Section 4 is about the redistribution of the code. In my understanding
this means that I am not allowed to remove the license header if I
redistribute a source file (e.g. in a package or in my own software).

If I add code to OpenStack I have to sign the CLA. The CLA includes:

   2. Grant of Copyright License. Subject to the terms and conditions of
  this License, each Contributor hereby grants to You a perpetual,
  worldwide, non-exclusive, no-charge, royalty-free, irrevocable
  copyright license to reproduce, prepare Derivative Works of,
  publicly display, publicly perform, sublicense, and distribute the
  Work and such Derivative Works in Source or Object form.

Does this not mean that it is not necessary to explicitly add a
copyright statement above the license headers?

According to
http://www.apache.org/dev/apply-license.html#contributor-copyright and
http://www.apache.org/legal/src-headers.html copyright statements should
not be added to the headers in source files.

Christian.

__
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

Re: [openstack-dev] Missing column in Gerrit overview page showing a -1 review after/with a +2 review

[Christian Berendt]

On 02/14/2015 04:46 PM, Anita Kuno wrote:
 Using gerrit queries might come in handy here.
 
 https://review.openstack.org/Documentation/user-search.html
 
 For a start, this gets me all reviews that are open for which I am not
 the author, where I voted +1 (or better) and someone else voted -1 (or
 lower). I just gave it a quick test to try it out, it might need refining.
 
 NOT owner:self status:open label:Code-Review=+1,self label:Code-Review=-1

This way I can display review requests with -1 reviews, yes. On the
overview page a +2 review will still hide any -1 reviews. But a -1
review will hide all +1 reviews. I think -1 reviews should be visible
regardless of +2 reviews.

Christian.

__
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

Re: [openstack-dev] [docs] rethinking docs jobs in the gate

[Christian Berendt]

On 02/16/2015 04:29 PM, Andreas Jaeger wrote:
 For documentation projects we should discuss this separately as well,

Is it possible to keep all environments like they are and to add a meta
environment (called docs) calling the existing environments? This way we
can reduce the number of jobs on the gates (entry point for the gates is
the meta environment) but can keep the existing environments for local
tests.

Christian.

__
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-dev] Missing column in Gerrit overview page showing a -1 review after/with a +2 review

[Christian Berendt]

At the moment there are three columns in the Gerrit overiew page showing
the status of a review request:

* CR (Code-Review)
* V (Verified)
* Workflow (WF).

After a core reviewer +2 (CR) a review request there will be a green
hook in the CR column in the overview page, regardless of -1 reviews.

Sometimes I do not have the time to have a look in my Gerrit mail
folder. Sometimes I do not have the time to manually monitor pending
review requests. This is why I sometimes miss a new -1 of a reviewer
because it is not shown in the Gerrit overview page when there is
already a +2 of a core reviewer. Also a +2 of a core reviewer will
overwrite an existing -1 in the Gerrit overview page. Sometimes I do
not have the time to remove my +2 after a new -1 (at the moment it is
necessary to remove a +2 after a new -1 to be able to see the new -1 on
the Gerrit overview page).

I would really like to have a fourth column in the Gerrit overview page
showing a -1 on a review request even if there is already a +2 of a core
reviewer.

What do you think about this?

And if this idea is appreciated how can this fourth column be added to
the Gerrit overview page?

Christian.

__
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

Re: [openstack-dev] [bashate] towards inbox zero on bashate changes, release?

[Christian Berendt]

On 10/14/2014 07:03 AM, Ian Wienand wrote:
 1) changes for auto-detection.  IMO, we should drop all these and just
leave bashate as taking a list of files to check, and let
test-harnesses fix it.  Everyone using it at the moment seems fine
without them

I am fine with this and abandoned the Introduce directories as possible
arguements review request. This way we can use already exisiting tools
like find and do not have to re-implement this.

Christian.

-- 
Christian Berendt
Cloud Solution Architect
Mail: bere...@b1-systems.de

B1 Systems GmbH
Osterfeldstraße 7 / 85088 Vohburg / http://www.b1-systems.de
GF: Ralph Dehner / Unternehmenssitz: Vohburg / AG: Ingolstadt,HRB 3537

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

[openstack-dev] RSS feeds for gerrit projects

[Christian Berendt]

Is it possible to directly access RSS feeds for gerrit projects or is
the only way to do this to use a wrapper like openstackwatch in jeepyb?

Christian.

-- 
Christian Berendt
Cloud Solution Architect
Mail: bere...@b1-systems.de

B1 Systems GmbH
Osterfeldstraße 7 / 85088 Vohburg / http://www.b1-systems.de
GF: Ralph Dehner / Unternehmenssitz: Vohburg / AG: Ingolstadt,HRB 3537

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

[openstack-dev] Usage of @author tags in the header of Python files

[Christian Berendt]

After proposing a change to Horizon to remove the @author tags from the
header of Python files (https://review.openstack.org/#/c/126656/)
Matthias Runge proposed to discuss this first on the mailing list.

Is it necessary to track the authorship of a file inside the file using
@author tags?

The copyright statement itself is unchanged and intact after the removal
of the @author tags.

The copyright statement is not addicted to the authorship of a file so
it should be safe to remove the @author tags.

The @author tag is not used in other projects. Neutron removed all
@author tags some time ago and there are no @author tags e.g. in Nova,
or Cinder. There are even local hacking checks in Nova, and Neutron to
not use @author tags.

Christian.

-- 
Christian Berendt
Cloud Solution Architect
Mail: bere...@b1-systems.de

B1 Systems GmbH
Osterfeldstraße 7 / 85088 Vohburg / http://www.b1-systems.de
GF: Ralph Dehner / Unternehmenssitz: Vohburg / AG: Ingolstadt,HRB 3537

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

[openstack-dev] Add a hacking check to not use Python Source Code Encodings (PEP0263)

[Christian Berendt]

Hello.

There are some files using the Python source code encodings as the first
line. That's normally not necessary and I want propose to introduce a
hacking check to check for the absence of the source code encodings.

Best, Christian.

-- 
Christian Berendt
Cloud Computing Solution Architect
Mail: bere...@b1-systems.de

B1 Systems GmbH
Osterfeldstraße 7 / 85088 Vohburg / http://www.b1-systems.de
GF: Ralph Dehner / Unternehmenssitz: Vohburg / AG: Ingolstadt,HRB 3537

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

Re: [openstack-dev] [horizon] mocking policy

[Christian Berendt]

On 06/04/2014 02:56 PM, Ana Krivokapic wrote:
 +1 for adding Mock to the requirements (test-requirements.txt rather
 than requirements.txt, right?) and using it in newly written tests.

+1 for the usage of mock.

Also the use of mox3 should be preferred. mox is not compatible with
Python3 and it's not under an active development.

Christian.

-- 
Christian Berendt
Cloud Computing Solution Architect
Mail: bere...@b1-systems.de

B1 Systems GmbH
Osterfeldstraße 7 / 85088 Vohburg / http://www.b1-systems.de
GF: Ralph Dehner / Unternehmenssitz: Vohburg / AG: Ingolstadt,HRB 3537

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

Re: [openstack-dev] A proposal for code reduction

[Christian Berendt]

On 05/21/2014 01:34 PM, Clark, Robert Graham wrote:
 If you weren’t already aware of it there’s some great content here: 
 https://wiki.openstack.org/wiki/Oslo

https://github.com/openstack/oslo.test

-- 
Christian Berendt
Cloud Computing Solution Architect
Mail: bere...@b1-systems.de

B1 Systems GmbH
Osterfeldstraße 7 / 85088 Vohburg / http://www.b1-systems.de
GF: Ralph Dehner / Unternehmenssitz: Vohburg / AG: Ingolstadt,HRB 3537

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

Re: [openstack-dev] [oslo] Logging exceptions and Python 3

[Christian Berendt]

On 05/15/2014 11:20 PM, Igor Kalnitsky wrote:
 Example:
 
 LOG.error(e.message)

According to http://legacy.python.org/dev/peps/pep-0352/ the message
attribute of BaseException is deprecated since Python 2.6 and was
dropped in Python 3.0.

Christian.

-- 
Christian Berendt
Cloud Computing Solution Architect
Mail: bere...@b1-systems.de

B1 Systems GmbH
Osterfeldstraße 7 / 85088 Vohburg / http://www.b1-systems.de
GF: Ralph Dehner / Unternehmenssitz: Vohburg / AG: Ingolstadt,HRB 3537

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

[openstack-dev] [Horizon] pre-running lesscpy

[Christian Berendt]

Hi.

Is it possible to pre-run lesscpy? When accessing Horizon in my devstack
environment the first time lesscpy is always running several seconds in
the background.

Tried to run python manage.py compress (setting COMPRESS_OFFLINE=True in
the settings.py), but afterwards lesscpy is still running in the
background when accessing Horizon the first time.

Christian.

-- 
Christian Berendt
Cloud Computing Solution Architect
Mail: bere...@b1-systems.de

B1 Systems GmbH
Osterfeldstraße 7 / 85088 Vohburg / http://www.b1-systems.de
GF: Ralph Dehner / Unternehmenssitz: Vohburg / AG: Ingolstadt,HRB 3537

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

Re: [openstack-dev] [Ceilometer][QA][Tempest][Infra] Ceilometer tempest testing in gate

[Christian Berendt]

On 03/20/2014 01:27 PM, Nadya Privalova wrote:
 Tim, yep. If you use one db for Ceilometer and Nova then nova's
 performance may be affected.

If I understood it correctly the problem is not the higher load produced
directly by Ceilometer on the database. The problem is that the
Ceilometer compute agent sends a lot of Nova API calls and this results
in a higher load on the nova-api services. Tim mentioned a factor of 16.

Christian.

-- 
Christian Berendt
Cloud Computing Solution Architect
Mail: bere...@b1-systems.de

B1 Systems GmbH
Osterfeldstraße 7 / 85088 Vohburg / http://www.b1-systems.de
GF: Ralph Dehner / Unternehmenssitz: Vohburg / AG: Ingolstadt,HRB 3537

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

[openstack-dev] Ceilometer visualization in Horizon

[Christian Berendt]

Hello folks.

I started playing with Horizon and Ceilometer. I already added the 
client to openstack_dashboard/api/ and added some pure data tables 
(cpu/network/storage utilization) to the instance detail panel. Now I 
want to have some nice graphs there, but at the moment I'm not sure 
about the graphing library I should use.


I gave http://www.chartjs.org/ a try and it's working fine. But I'm not 
sure about the license (MIT license). Is it possible to add Chart.js to 
the horizon repository? Or are there any other suggestions?


Christian.

--
Christian Berendt
Cloud Computing Solution Architect
Mail: bere...@b1-systems.de

B1 Systems GmbH
Osterfeldstraße 7 / 85088 Vohburg / http://www.b1-systems.de
GF: Ralph Dehner / Unternehmenssitz: Vohburg / AG: Ingolstadt,HRB 3537

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