March 2019 - openstack-discuss - lists.openstack.org

keystone 15.0.0.0rc1 (stein)
by no-reply＠openstack.org 21 Mar '19

21 Mar '19

Hello everyone, A new release candidate for keystone for the end of the Stein cycle is available! You can find the source code tarball at: https://tarballs.openstack.org/keystone/ Unless release-critical issues are found that warrant a release candidate respin, this candidate will be formally released as the final Stein release. You are therefore strongly encouraged to test and validate this tarball! Alternatively, you can directly test the stable/stein release branch at: https://git.openstack.org/cgit/openstack/keystone/log/?h=stable/stein Release notes for keystone can be found at: https://docs.openstack.org/releasenotes/keystone/

1 0

[dev][keystone] RC tracking
by Lance Bragstad 21 Mar '19

21 Mar '19

Hey all, We have a few things left to track for RC. We started building a list [0] during the keystone meeting on Tuesday. As such, we have a few calls to action. First, if you have *anything* (pending it's acceptable to merge at this point) you'd like to get into Stein, please add it to the etherpad. Second, if you're a reviewer please have a look at the list. Patches will need to be merged by next week if we want them to ship in Stein. Finally, be sure to keep an eye out for any release-blocking items and raise awareness if you think you see something. Thanks, Lance [0] https://etherpad.openstack.org/p/keystone-stein-rc2-tracking

1 0

[dev][tc][ptl] Continuing Evaluating projects in relation to OpenStack cloud vision
by Chris Dent 21 Mar '19

21 Mar '19

Yesterday at the TC meeting [1] we decided that the in-progress task to make sure the technical vision document [2] has been fully evaluated by project teams needs a bit more time, so this message is being produced as a reminder. Back in January Julia produced a message [3] suggesting that each project consider producing a document where they compare their current state with an idealized state if they were in complete alignment with the vision. There were two hoped for outcomes: * A useful in-project document that could help guide future development. * Patches to the vision document to clarify or correct the vision where it is discovered to be not quite right. A few projects have started that process (see, for example, melwitt's recent message for some links [4]) resulting in some good plans as well as some improvements to the vision document [5]. In the future the TC would like to use the vision document to help evaluate projects applying to be "official" as well as determining if projects are "healthy". As such it is important that the document be constantly evolving toward whatever "correct" means. The process described in Julia's message [3] is a useful to make it so. Please check it out. Thanks. [1] http://eavesdrop.openstack.org/meetings/tc/2019/tc.2019-02-07-14.00.html [2] https://governance.openstack.org/tc/reference/technical-vision.html [3] http://lists.openstack.org/pipermail/openstack-discuss/2019-January/001417.… [4] http://lists.openstack.org/pipermail/openstack-discuss/2019-February/002501… [5] https://review.openstack.org/#/q/project:openstack/governance+file:referenc… -- Chris Dent ٩◔̯◔۶ https://anticdent.org/ freenode: cdent tw: @anticdent

5 4

[tc] constellations
by Mohammed Naser 21 Mar '19

21 Mar '19

Hi everyone. For quite sometime, there has been work on an effort of moving forward with building 'constellations' however this effort has stalled out for a few months since. It looks like we've tried a few times to get this document done https://review.openstack.org/#/c/180112/ [3y9m ago, creating compute starter kit, by sdague] https://review.openstack.org/#/c/565466/ [7m ago, draft for scientific computing but in `governance`] https://review.openstack.org/#/c/586212/3 [6m ago, draft for compute starter constillation, by dims] Do we want to continue this effort (do we see value in it right now)? Does the community find it a useful document to publish and does anyone feel like they can pick it up? Thanks, Mohammed

5 6

[tc] joint leadership meeting
by Mohammed Naser 21 Mar '19

21 Mar '19

Hi everyone: I can't seriously keep a straight face talking about a joint leadership meeting in Denver since Sean brought it up, so i'll make sure everyone also thinks of it by bringing it up now. You'll never be able to unsee it :) Anyhow, the upcoming joint leadership meeting is happening a day before the summit starts in Denver. The logistics haven't yet been confirmed however the day of Sunday (before summit) seems to be confirmed. During the joint leadership meeting, the TC has time where we can bring up a certain agenda of topics to discuss and report about OpenStack to the board in the technical scope of things. The agenda that we had for Berlin was: - Rocky retrospective, Sean McGinnis - Stein update, Doug Hellmann - TC operational changes, Doug Hellmann - Peer review culture initiative, Julia Kreger - Technical vision initiative, Zane Bitter I think it would be good to start coming up with subjects for it. This question is also open to all community members that feel we should bring something up from the technical committee onto the board as well. Thank you Mohammed -- Mohammed Naser — vexxhost ----------------------------------------------------- D. 514-316-8872 D. 800-910-1726 ext. 200 E. mnaser(a)vexxhost.com W. http://vexxhost.com

2 3

[placement] Train PTG planning
by Chris Dent 21 Mar '19

21 Mar '19

>From discussion at today's nova-scheduler/placement meeting: For the sake of brainstorming, and to see how much (if any) time we'll want to devote to placement at the PTG, I've started an etherpad [1], also linked from the wiki [2]. The "if any" is because we haven't started out with any official space at the PTG, but we may be able to acquire some (or a room here and there) if we need to, but it is also assumed that many of us will be required in other rooms (nova, cyborg, blazar, others) and there are only 3 short days. We'll make more detailed plans after the etherpad has had some time to mature. [1] https://etherpad.openstack.org/p/placement-ptg-train [2] https://wiki.openstack.org/wiki/PTG/Train/Etherpads -- Chris Dent ٩◔̯◔۶ https://anticdent.org/ freenode: cdent tw: @anticdent

1 1

[kolla] Disabling haproxy does not work
by vladimir franciz blando 21 Mar '19

21 Mar '19

I have a 2 node deployment and I disabled haproxy in globals.yml but for some reason it does not doing what it's supposed to do. An error on the deployment run reveals that MariaDB is trying to connect to a VIP --- TASK [mariadb : Waiting for MariaDB service to be ready through VIP] ******************************************************************************************************************************** FAILED - RETRYING: Waiting for MariaDB service to be ready through VIP (6 retries left). FAILED - RETRYING: Waiting for MariaDB service to be ready through VIP (5 retries left). FAILED - RETRYING: Waiting for MariaDB service to be ready through VIP (4 retries left). FAILED - RETRYING: Waiting for MariaDB service to be ready through VIP (3 retries left). FAILED - RETRYING: Waiting for MariaDB service to be ready through VIP (2 retries left). FAILED - RETRYING: Waiting for MariaDB service to be ready through VIP (1 retries left). fatal: [192.168.0.115]: FAILED! => {"attempts": 6, "changed": false, "cmd": ["docker", "exec", "mariadb", "mysql", "-h", "192.168.0.199", "-P", "3306", "-u", "haproxy", "-e", "show databases;"], "delta": "0:00:03.093026", "end": "2019-03-20 02:11:02.423933", "msg": "non-zero return code", "rc": 1, "start": "2019-03-20 02:10:59.330907", "stderr": "ERROR 2003 (HY000): Can't connect to MySQL server on '192.168.0.199' (113 \"No route to host\")", "stderr_lines": ["ERROR 2003 (HY000): Can't connect to MySQL server on '192.168.0.199' (113 \"No route to host\")"], "stdout": "", "stdout_lines": []} --- - Vlad

3 2

python-watcher 2.0.0.0rc1 (stein)
by no-reply＠openstack.org 21 Mar '19

21 Mar '19

Hello everyone, A new release candidate for python-watcher for the end of the Stein cycle is available! You can find the source code tarball at: https://tarballs.openstack.org/watcher/ Unless release-critical issues are found that warrant a release candidate respin, this candidate will be formally released as the final Stein release. You are therefore strongly encouraged to test and validate this tarball! Alternatively, you can directly test the stable/stein release branch at: https://git.openstack.org/cgit/openstack/python-watcher/log/?h=stable/stein Release notes for python-watcher can be found at: https://docs.openstack.org/releasenotes/python-watcher/ If you find an issue that could be considered release-critical, please file it at: https://bugs.launchpad.net/watcher and tag it *stein-rc-potential* to bring it to the python-watcher release crew's attention.

1 0

blazar 3.0.0.0rc1 (stein)
by no-reply＠openstack.org 21 Mar '19

21 Mar '19

Hello everyone, A new release candidate for blazar for the end of the Stein cycle is available! You can find the source code tarball at: https://tarballs.openstack.org/blazar/ Unless release-critical issues are found that warrant a release candidate respin, this candidate will be formally released as the final Stein release. You are therefore strongly encouraged to test and validate this tarball! Alternatively, you can directly test the stable/stein release branch at: https://git.openstack.org/cgit/openstack/blazar/log/?h=stable/stein Release notes for blazar can be found at: https://docs.openstack.org/releasenotes/blazar/ If you find an issue that could be considered release-critical, please file it at: https://launchpad.net/blazar and tag it *stein-rc-potential* to bring it to the blazar release crew's attention.

1 0

zaqar-ui 6.0.0.0rc1 (stein)
by no-reply＠openstack.org 21 Mar '19

21 Mar '19

Hello everyone, A new release candidate for zaqar-ui for the end of the Stein cycle is available! You can find the source code tarball at: https://tarballs.openstack.org/zaqar-ui/ Unless release-critical issues are found that warrant a release candidate respin, this candidate will be formally released as the final Stein release. You are therefore strongly encouraged to test and validate this tarball! Alternatively, you can directly test the stable/stein release branch at: https://git.openstack.org/cgit/openstack/zaqar-ui/log/?h=stable/stein Release notes for zaqar-ui can be found at: https://docs.openstack.org/releasenotes/zaqar-ui/ If you find an issue that could be considered release-critical, please file it at: https://bugs.launchpad.net/zaqar-ui and tag it *stein-rc-potential* to bring it to the zaqar-ui release crew's attention.

1 0