April 2019 - openstack-discuss - lists.openstack.org

[ceilometer] Add Ceph disk usage for images and instances
by Gilles Mocellin 25 Apr '19

25 Apr '19

Hello, I've seen that it's possible to add polsters to ceilometer to gather additional metrics. I need to measure storage usage of my users, specially image usage (instance snapshots), where we still cannot have quotas. Does someone have already done something similar, where can I start to investigate ? I've seen some documentation to add Ceph RadosGW usage to Ceilometer, but it's not adaptable to my use case.

1 0

[manila][ptg] manila retrospective
by Tom Barron 25 Apr '19

25 Apr '19

We will kick off Manila PTG session next Thursday with a retrospective on the Stein cycle -- what went well, what we should improve, etc. So I set up an etherpad [1] that we will use to organize the discussion. Please go ahead and add items to the etherpad as they occur to you. Thanks, -- Tom Barron (tbarron) [1] https://etherpad.openstack.org/p/manila-stein-retrospective

1 0

Migrating git repos to OpenDev
by corvus＠inaugust.com 24 Apr '19

24 Apr '19

Hi, As discussed in November[1], the OpenStack project infrastructure is being rebranded as "OpenDev" to better support a wider community of projects. We are nearly ready to perform the part of this transition with the largest impact: moving the authoritative git repositories for existing projects. In this email, I'd like to introduce the new hosting system we are preparing, discuss the transition, and invite projects to work with us on the logistics of the change. Gerrit ====== Gerrit is the core of our system and it will remain so in OpenDev. As part of this move, we will rename the gerrit server from review.openstack.org to review.opendev.org. As part of the transition, we will automatically merge appropriate changes to all branches of all repositories updating .gitreview and Zuul configuration files. Any further changes (README files, etc.) we expect to be made by individual project contributors. Repository Browsing =================== Currently our canonical *public* repository system is the cgit server at https://git.openstack.org/ (and git.airshipit.org, git.starlingx.io, and git.zuul-ci.org) This is a load balanced cluster of several servers which is designed to handle all the public git repository traffic, as it scales much better than Gerrit (and has a more friendly domain name). >From a technical standpoint, it's excellent, but its usability could be improved. Therefore, as part of this transition, we will replace the cgit servers with a new system based on Gitea. Gitea is a complete development collaboration system, but it's very flexible and will allow us to disable components which we aren't using. We will operate it in a read-only configuration where it will act as the public mirror for Gerrit. The advantages it has over the current system are: * Shorter domain name in project URLs: https://git.openstack.org/openstack/nova vs https://opendev.org/openstack/nova * Clone and browsing URLs are the same (with cgit, the browsing URL has an extra path component) * More visually pleasing code browsing * Integrated code searching * Ability to highlight multiple lines in links When we perform the transition we will install redirects from git.openstack.org (and the other git sites) to opendev.org, and will maintain those redirects for the foreseeable future. We will construct them so that even existing deep links to individual files in individual commits to cgit will redirect to the correct location on opendev.org. This system is up and running now with a live mirror of data from Gerrit, and you can start testing it out today at https://opendev.org/ Please let us know if you encounter any problems. If you would like to read more about the design of this system and the transition, see the infra-spec[2]. GitHub ====== Currently all OpenStack projects are replicated to GitHub. We do not plan on changing that during the transition, however, any projects outside of the openstack*/ namespaces will not automatically be replicated to GitHub, and we do not plan on adding that in the future. We do, however, support projects using Zuul to run post-merge jobs to push updates to GitHub or any other third-party mirrors with their own credentials. We will be happy to work with anyone interested in that to help set up jobs to do so. We are adopting this approach so that individual projects can have more control over how they are represented in social media, and to give us more flexibility in supporting our own organizational namespaces on OpenDev without assuming they map directly to GitHub. Eventually we plan on moving the OpenStack project to that system as well and retiring direct replication from Gerrit to GitHub completely. But we will defer that work until after this transition. Logistics ========= We can prepare much of the system in advance (as we have for the hosting system on opendev.org) but the actual transition and renaming of the Gerrit server will need to happen at once during an outage window. We need to schedule that outage and begin preparing for it. Since all of the project git URLs are going to change (to replace git.openstack.org with opendev.org and review.openstack.org with review.opendev.org) we can additionally take the opportunity to reorganize projects into different organizations. For example, during the transition we will rename Zuul, and it's associated projects, from the "openstack-infra" org to "zuul". So their new names will be "zuul/zuul", "zuul/nodepool", etc. This is an excellent time for the rest of the OpenStack Foundation pilot projects to do the same. If the OpenStack project desires this, it would also be a good time to move unofficial projects out of the openstack/ namespace. Therefore, we need your help: Action Items ============ We need each of the following projects: * OpenStack * Airship * StarlingX * Zuul To nominate a single point of contact to work with us on the transition. It would be helpful for that person to attend the next (and possibly next several) openstack infra team meetings in IRC [3]. We will work with those people on scheduling the transition, as well as finalizing the list of projects which should be renamed as part of the transition. If you manage an unofficial project and would like to take the opportunity to move or rename your project, please add it to this ethercalc[4]. [1] http://lists.openstack.org/pipermail/openstack-dev/2018-November/136403.html [2] http://specs.openstack.org/openstack-infra/infra-specs/specs/opendev-gerrit… [3] http://eavesdrop.openstack.org/#Project_Infrastructure_Team_Meeting [4] https://ethercalc.openstack.org/opendev-transition

19 39

[publiccloud]Bi-weekly Meeting Thursday Apr 25th
by Zhipeng Huang 24 Apr '19

24 Apr '19

Hi All, We will have our bi-weekly meeting today starting UTC1400, please checkout the agenda at https://etherpad.openstack.org/p/publiccloud-wg Lokk forward to your -- Zhipeng (Howard) Huang Principle Engineer OpenStack, Kubernetes, CNCF, LF Edge, ONNX, Kubeflow, OpenSDS, Open Service Broker API, OCP, Hyperledger, ETSI, SNIA, DMTF, W3C

1 0

[release] Release countdown for week R-26 and R-25, April 15-26
by Tony Breeds 24 Apr '19

24 Apr '19

Here we go again! The Train cycle will about normal at 26 weeks. Please take a couple of minutes to look over the schedule for this release: https://releases.openstack.org/train/schedule.html We also have the same data available as an ics: https://releases.openstack.org/train/schedule.ics it's a good idea for interested parties (for example PTLs and liaisons) to subscribe to it so upcoming deadlines are visible. Development Focus ----------------- Focus should be on optimizing the time at the PTG and following up after the event to jump start Train development and spec planning Action Required --------------- PTLs will receive a direct email from me establishing contact and setting communication expectations. Be on the lookout! General Information ------------------- All teams should review their release liaison information and make sure it is up to date [1]. While reviewing liaisons, this would also be a good time to make sure your declared release model matches the project's plans for Train (e.g. [2]). This should be done prior to the first milestone and can be done by proposing a change to the Stein deliverable file for the project(s) affected [3]. Now would be a good time to start brainstorming Forum topics while some of the PTG discussions are fresh. Just a couple months until the Summit and Forum in Berlin. Upcoming Deadlines & Dates -------------------------- Train-1 milestone: Jun 03 (R-19 week) Forum at OpenInfrastructure Summit in Denver: April 29 - May 1 PTG right after the OpenInfrastructure Summit in Denver: May 2 - 4 Yours Tony (tonyb). [1] https://wiki.openstack.org/wiki/CrossProjectLiaisons [2] https://opendev.org/openstack/releases/src/branch/master/deliverables/train… [3] https://opendev.org/openstack/releases/src/branch/master/deliverables/train

2 2

gitweb link broken after OpenDev migration
by Nadathur, Sundar 24 Apr '19

24 Apr '19

The gitweb link seen in the diffs in review.openstack.org is broken - it still points to git.openstack.org in all the diffs I looked at, and that returns a 404. E.g. https://drive.google.com/file/d/1XVEyLnDOeJ0UUY16EfmDmV8029Ktp6HS/view?usp=… Regards, Sundar

3 4

[cyborg] [ironic] [ptg] Cyborg-Ironic cross-project etherpad available
by Nadathur, Sundar 24 Apr '19

24 Apr '19

Please see https://etherpad.openstack.org/p/ptg-train-xproj-ironic-cyborg . It has been linked to: https://etherpad.openstack.org/p/DEN-train-ironic-brainstorming Line 162 https://etherpad.openstack.org/p/DEN-train-ironic-ptg Line 198 https://etherpad.openstack.org/p/cyborg-ptg-train Line 20 https://wiki.openstack.org/wiki/PTG/Train/Etherpads Regards, Sundar

1 0

[all][qa][ptg][forum] QA PTG Schedule and Related Forum Sessions
by Ghanshyam Mann 24 Apr '19

24 Apr '19

Hello Everyone, I have prepared the QA schedule for Denver Open Infrastructure Summit and PTG. We will be meeting for two days in PTG which is divided into two parts 1. topic discussions for one and half days 2. Code Sprint & Open Discussion. * PTG: QA 2nd May- 3rd May 2019: Room 105 PTG Scheduled is flexible and we can adjust it based on request. QA Stein PTG Schedule - https://ethercalc.openstack.org/Train-PTG-QA-Schedule Details of each session can be found in this etherpad - https://etherpad.openstack.org/p/qa-train-ptg * Summit: QA Forum sessions: Along with project updates & onboarding sessions, QA team will host QA feedback sessions . 1. OpenStack QA - Project Update: Tuesday, April 30, 2:35pm-2:55pm [1] 2. OpenStack QA - Project Onboarding : Wednesday, May 1, 9:00am-9:40am [2] 3. Users / Operators adoption of QA tools / plugins : Wednesday, May 1, 10:50am-11:30am [3] [1] https://www.openstack.org/summit/denver-2019/summit-schedule/events/23703/o… [2] https://www.openstack.org/summit/denver-2019/summit-schedule/events/23728/o… [3] https://www.openstack.org/summit/denver-2019/summit-schedule/events/23660/u… -gmann

1 0

[all][qa][forum] Etherpad for Users / Operators adoption of QA tools / plugins sessions
by Ghanshyam Mann 24 Apr '19

24 Apr '19

Hello Everyone, I've created the etherpad for the QA feedback sessions[1] which is scheduled on Wednesday, May 1, 10:50am-11:30am. I have added a few basic feedback questions there and If you have any additional items to add or modify, please feel free to do that. In case, you are not able to attend this session, you can still write your feedback with your irc/name contact. Etherpad: https://etherpad.openstack.org/p/Den-forum-qa-ops-user-feedback [1] https://www.openstack.org/summit/denver-2019/summit-schedule/events/23660/u… -gmann

1 0

[self-healing][PTG][Forum] Self-healing SIG sessions at Denver Forum and PTG
by Adam Spiers 24 Apr '19

24 Apr '19

Hi there, This is a last call for topics for discussion at either of the two self-healing SIG sessions scheduled next week in Denver. Everyone is warmly invited to add topics they are interested in to the etherpad: https://etherpad.openstack.org/p/DEN-self-healing-SIG As always, we are particularly interested to hear feedback from operators: - Are you already implementing any self-healing functionality in your OpenStack clouds? - If so, how are you doing it, and what's working and not working? - What self-healing functionality would you like to see which is currently missing? The Birds of a Feather session on Wednesday May 1, 9:50am-10:30am is the best time to provide that feedback: https://www.openstack.org/summit/denver-2019/summit-schedule/events/23743/s… However we also have a PTG session the whole afternoon of Thursday May 2nd: https://www.openstack.org/ptg#tab_schedule and while it will certainly cover developer-oriented topics, operator feedback is very welcome there too. Looking forward to seeing you all! Regards, Adam and Eric

1 0