April 2019 - Starlingx-discuss - lists.starlingx.io

[Starlingx-discuss] [build-report] STX_build_master_master - Build # 72 - Still Failing!
by build.starlingx＠gmail.com 21 Apr '19

21 Apr '19

Project: STX_build_master_master Build #: 72 Status: Still Failing Timestamp: 20190421T013001Z Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/20190421T01… -------------------------------------------------------------------------------- Parameters BUILD_CONTAINERS_DEV: false BUILD_CONTAINERS_STABLE: false

1 0

[Starlingx-discuss] Post OpenDev Repo Migration Issues
by Clark Boylan 20 Apr '19

20 Apr '19

Hello, There are two quick things we want to point out that we've noticed after the OpenDev Gerrit manuevers. First, any commit Depends-On footers for unmerged changes will need to use https://review.opendev.org urls instead of https://review.openstack.org urls. This is due to a limitation in Zuul and how it sees the Gerrit server. Any Depends-On footers that use https://review.openstack.org are currently non-functional and they will not enforce the dependency relationship. Second, while we have fairly robust http(s) redirects in place for old urls (including those from cgit to gitea) any ssh repo urls will need to be updated to use the new canonical paths if a repo has moved. We are unable to redirect incoming ssh requests against Gerrit. If you need to know what the canonical path is go to the corresponding https repo url and the resulting destination is the canonical location. Again thank you for your patience, Clark

1 0

[Starlingx-discuss] Migrating git repos to OpenDev
by corvus＠inaugust.com 20 Apr '19

20 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

4 7

[Starlingx-discuss] [build-report] STX_build_master_master - Build # 71 - Failure!
by build.starlingx＠gmail.com 20 Apr '19

20 Apr '19

Project: STX_build_master_master Build #: 71 Status: Failure Timestamp: 20190420T013001Z Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/20190420T01… -------------------------------------------------------------------------------- Parameters BUILD_CONTAINERS_DEV: false BUILD_CONTAINERS_STABLE: false

1 0

[Starlingx-discuss] stx-nova numa aware live migration
by Kopec, Gerald (Gerry) 19 Apr '19

19 Apr '19

I've created a stx-nova PR for the backport of the upstream numa aware live migration feature: https://github.com/starlingx-staging/stx-nova/pull/23 It's the 7 open nova reviews from https://review.openstack.org/#/q/topic:bp/numa-aware-live-migration plus a temporary change to address some of the review comments related to live migration and resource tracking. Please review and comment, Thanks, Gerry

2 1

[Starlingx-discuss] Does rabbitmq listener work in NFV module
by Liu, ZhipengS 19 Apr '19

19 Apr '19

Hi all, >From nfv-vim.log I see below 2019-04-12T08:38:11.409 controller-0 VIM_Thread[31835] INFO rpc_listener.py.127 RPC-Listener not connected to exchange nova, queue=notifications.nfvi_nova_listener_queue. It seems NFV could not get notifications from nova now. Have we enabled rabbitmq listener in NFV after containerized version? Thanks! zhipeng

2 4

[Starlingx-discuss] [TSC] Minutes - 4/11 meeting
by Jolliffe, Ian 19 Apr '19

19 Apr '19

Release Plan Update (release team) options at https://docs.google.com/spreadsheets/d/1HUwbsaSerzFRuvXVB_qvoGdI0Chx1YiiA2W… We discussed the 2 options in detail for 30 min. In the end we didn’t reach consensus on which option to select and a third compromise option came up. This will be on the agenda for the TSC call on 4/18 – tomorrow @TSC members – please make every effort to be on the TSC call. We will be making a decision on the release plan tomorrow. Project mission statement - https://etherpad.openstack.org/p/stx-mission-statement (ildikov) TSC please review proposal needs to be done soon Review next week Raised on community call as well How do we revalidate? Writing visions is a more involved process. There is a framework that can be used for this - use time as a way to frame - Vision, mission, goals. Add to PTG agenda Small team to work on a proposal for how to move this forward. Dean, Ian, PTG lunch slot presentation? (ildikov) the idea is a 5 minutes long presentation about the project to give an overview and what's new sign up for the team photo in PTG(shuquan): https://ethercalc.openstack.org/3qd1fj5f3tt3 Need a volunteer for this - presentation - feel free to sign up - Bruce has slides - OSF Board meeting update (ildikov) F2F Board meeting is in Denver, April 28 - This is the Sunday 10-15 minute overview presentation Need a TSC member - likely afternoon need to discuss what messages we want to send to the board Packet projects Curtis - MOU has been signed by both packet.com and the openstack foundation I sent an email to all the TSC members with the signed MOU attached Do we store these kinds of agreements anywhere? Eg. CENGN hosting agreement? - Is the latter signed by the Foundation as well? OSF has likely stored the MOU in some fashion May want to look into ensuring the CENGN hosting MOU/whatever is also stored in the same fashion Where to store these kinds of community agreements? Next step is to try to get STX booting on bare metal They use iPXE causing some issues Work being done here: https://etherpad.openstack.org/p/stx-packet-baremetal-boot

2 1

[Starlingx-discuss] Minutes: StarlingX Release Meeting - April 18/2019
by Khalil, Ghada 19 Apr '19

19 Apr '19

Agenda/Minutes are posted at: https://etherpad.openstack.org/p/stx-releases Release meeting agenda / notes Apr 18 2019 - TSC approved (by consensus) the release plan option without Dist Cloud - Chosen option updated on release plan in google docs - Action: Ghada to update release dates on Release Planning Wiki: https://wiki.openstack.org/wiki/StarlingX/Release_Plan - Execution / Delivery time! - Patch Elimination Update: - NUMA live migration patch backport should complete within 1-2 weeks. We have a f/stein.X branch that will be re-branched when 1) new content is merged to upstream stable Stein or 2) we backport additional code. - Status of other long poll items? - Went through all the features and updated the status. - See: https://docs.google.com/spreadsheets/d/1HUwbsaSerzFRuvXVB_qvoGdI0Chx1YiiA2W… - Test team not covered (Ada/Numan are out). Will get an update in the next community meeting. - Release plan proposal for PTG - Brucej: Want to move toward continuous integration - want to catch more bugs and do more testing at code check in time. - would like to move toward more frequent releases with less excitement :) - Significant challenges in doing builds and running system level tests - need some creative thinking - Need to make a distinction between the type of release we are delivering - Release with foundational changes - Like stx.2.0 which introduced support for containers and containerization openstack - Lessons from stx.2.0: Under-estimated the complexity and the scale of the changes and the time/effort it would take to test it - Release with a number of smaller indepdent features - This would be more deterministic to align on time-based releases moving forward - For stx.3.0, we feel this will be the case. - Need to plan in more automation and CI/CD pipe-line work - Issue with having systems out in the public - Leverage virtual env testing - Bugs - We want to do a scrub of the stx.2.0 bugs. Schedule in the release planning meeting for May 9 or later. - Ask the domain owners to do a pre-review and make recommendations

1 0

[Starlingx-discuss] Minutes: StarlingX Networking Meeting - 04/18
by Khalil, Ghada 19 Apr '19

19 Apr '19

Meeting minutes/agenda are captured at: https://etherpad.openstack.org/p/stx-networking Networking Test Status - TC Definition for Regression (update by Elio, Matt and Chris) - Still working on this. - Elio is working on comments provided by Matt by email. - Lots of changes are required. Elio coordinating with the rest of the test team. - Expect to have a new version for review in the next two weeks - 1st wk of May - Link to work in progress documents: - https://drive.google.com/drive/folders/1LS-gSj0Obfa9Qle2Ver2j5dZjmQJ9etB - Regression Execution (update by Elio) - Agreed to include some networking TCs in the automated sanity - Still not able to ping testing between 2 VMs on virtual env -- this was a limitation with ovs-dpdk. With the use of ovs in virtual env, this should no longer be an issue. - For automated sanity in virtual env, test with OVS. For automated sanity on baremetal, use OVS-DPDK - Action: Elio to share the TCs planned for sanity with the team. Send to starlingx-discuss mailing list. - Elio to provide time-line for adding TCs to sanity by next week. - Feature Testing for ovs-dpdk upversion (update by Ricardo and Elio) Testing on two systems: - Duplex (config 4) - No issues found with testing. Trunk re-test successful. Still need to re-test dns. - 2+2 (config 4) - Facing issues potentially with connectivity - https://bugs.launchpad.net/starlingx/+bug/1824923 - Given testing is successful on Duplex & 2+2 with another set of NICs, this points more to a networking configuration issue. - Christopher will look into the switch configuration to see if there is an issue there - Feature Testing for ovs-dpdk firewall (update by Elio) - TC creation is about 50%. Will work to incorporate Matt and Kailun's feedback - Expect to start execution next week - OVS process monitoring and alarming (update by Chenjie) - Code has been merged: - https://review.openstack.org/#/c/648330/ - https://review.openstack.org/#/c/648367/ - Ready for test verification - Containerized OVS Integration - Remaining item: Follow-up on version of ovs used in the container image. - Right now, the default docker image (with ovs 2.8.0) is used. - Agreed to align with the openvswitch version of the host. Target is 2.11.0 once the ovs-dpdk upversion feature is merged. - This means that we need to build/update the ovs docker image in starlingx - Need to get more information from Don on how to do this -- is a build required? or can we specify the ovs version via manifest? - Agreed to wait until the openvswitch 2.11 is merged in stx master and gets some soak first before proceeding with changing the version in the container - Bugs - All bugs are now assigned and being worked by Forrest's team - Expect to be able to address the current backlog in 2-3wks

1 0

[Starlingx-discuss] Update on sanity status
by Miller, Frank 18 Apr '19

18 Apr '19

This week has seen a number of issues that impacted sanity. Two of the issues were addressed by commits earlier in the week as well as this morning. It looks like at least one issue remains that is preventing the stx-openstack application from successfully coming up on some platforms. This issue is being tracked by https://bugs.launchpad.net/starlingx/+bug/1825423 Until a solution is merged and sanity results are good, I suggest you revert to the most recent sane loads which were from the April 10 and April 11 builds: Apr 11: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/20190411T01… Apr 10: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/20190410T01… An update will be sent on Monday. Frank P.S. The most recent sanity report is indicating LP https://bugs.launchpad.net/starlingx/+bug/1825045 is causing failures but while the symptoms look the same we do not feel this is actually the LP that is causing sanity to fail.

1 0