- openstack-discuss - lists.openstack.org

[tripleo][ironic] What I had to do to get standalone ironic working with ovn enabled
by Lars Kellogg-Stedman 25 Feb '19

25 Feb '19

I'm using the tripleo standalone install to set up an Ironic test environment. With recent tripleo master, the deploy started failing because the DockerOvn*Image parameters weren't defined. Here's what I did to get everything working: 1. I added to my deploy: -e /usr/share/tripleo-heat-templates/environment/services/neutron-ovn-standalone.yaml With this change, `openstack tripleo container image prep` correctly detected that ovn was enabled and generated the appropriate image parameters. 2. environments/services/ironic.yaml sets: NeutronMechanismDrivers: ['openvswitch', 'baremetal'] Since I didn't want openvswitch enabled in this deployment, I explicitly set the mechanism drivers in a subsequent environment file: NeutronMechanismDrivers: ['ovn', 'baremetal'] 3. The neutron-ovn-standalone.yaml environment explicitly disables the non-ovn neutron services. Ironic requires the services of the neutron_dhcp_agent, so I had to add: OS::TripleO::Services::NeutronDhcpAgent: /usr/share/openstack-tripleo-heat-templates/deployment/neutron/neutron-dhcp-container-puppet.yaml With this in place, the ironic nodes were able to receive dhcp responses and were able to boot. 3. In order to provide the baremetal nodes with a route to the nova metadata service, I added the following to my deploy: NeutronEnableForceMetadata: true This provides the baremetal nodes with a route to 169.254.169.254 via the neutron dhcp namespace. 4. In order get the metadata service to respond correctly, I also had to enable the neutron metadata agent: OS::TripleO::Services::NeutronMetadataAgent: /usr/share/openstack-tripleo-heat-templates/deployment/neutron/neutron-metadata-container-puppet.yaml This returned my Ironic deployment to a functioning state: I can successfully boot baremetal nodes and provide them with configuration information via the metadata service. I'm curious if this was the *correct* solution, or if there was a better method of getting things working. -- Lars Kellogg-Stedman <lars(a)redhat.com> | larsks @ {irc,twitter,github} http://blog.oddbit.com/ |

4 5

[tc][election] candidate question: managing change
by Doug Hellmann 23 Feb '19

23 Feb '19

We are consistently presented with the challenges of trying to convince our large community to change direction, collaborate across team boundaries, and work on features that require integration of several services. Other threads with candidate questions include discussions of some significant technical changes people would like to see in OpenStack's implementation. Taking one of those ideas, or one of your own idea, as inspiration, consider how you would make the change happen if it was your responsibility to do so. Which change management approaches that we have used unsuccessfully in the past did you expect to see work? Why do you think they failed? Which would you like to try again? How would you do things differently? What new suggestions do you have for addressing this recurring challenge? -- Doug

4 3

Re: [release] Release countdown for week R-15, May 14-18
by rocky700 23 Feb '19

23 Feb '19

The details which you have given will be very useful for the stack developers as they can know the basic process of it and developing a full stack-based programme will be easy for the developers. ----- apple ipad support -- Sent from: http://openstack.10931.n7.nabble.com/Developer-f2.html

1 0

[nova][dev] 2 weeks until feature freeze
by melanie witt 23 Feb '19

23 Feb '19

Howdy all, We've about 2 weeks left until feature freeze milestone s-3 on March 7: https://wiki.openstack.org/wiki/Nova/Stein_Release_Schedule Non-client library freeze is in 1 week February 28, so if you need changes released in Stein for os-vif, os-traits, or os-resource-classes, they need to be merged by Feb 28 and the releases will be proposed on Feb 28. Ping us if you need review. The blueprint status tracking etherpad is up-to-date: https://etherpad.openstack.org/p/nova-stein-blueprint-status For our Cycle Themes: Multi-cell operational enhancements: The patch series for the API microversion for handling of down cells (nova side and novaclient side) is complete with one admin docs patch remaining. It is actively being reviewed. Counting quota usage from placement has its implementation done and WIP on test coverage. Cross-cell resize is still making good progress with active code review. Compute nodes able to upgrade and exist with nested resource providers for multiple vGPU types: The libvirt driver reshaper patch is up-to-date and passing CI. There's a comment on the patch pointing out a bit of missing test coverage which needs to be added. Volume-backed user experience and API improvement: The detach boot volume and volume-backed server rebuild patches are active WIP. If you are the owner of an approved blueprint, please: * Add the blueprint if I've missed it * Update the status if it is not accurate * If your blueprint is in the "Wayward changes" section, please upload and update patches as soon as you can, to allow maximum time for review * If your patches are noted as Merge Conflict or WIP or needing an update, please update them and update the status on the etherpad * Add a note under your blueprint if you're no longer able to work on it this cycle Let us know if you have any questions or need assistance with your blueprint. Cheers, -melanie

2 1

[all][tc] Denver Forum session brainstorming
by Ghanshyam Mann 23 Feb '19

23 Feb '19

Hi, TC, Stackers, TC has started the etherpad to brainstorm the topis ideas for Denver Summit Forum. You can add TC related sessions or cross community or something which target wider community discussion as whole and does not fit under any specific project/SIG group. Please add your ideas at: https://etherpad.openstack.org/p/DEN-Train-TC-brainstorming March 8th is the dealine to submit the forum sessions. More details on dates, refer - http://lists.openstack.org/pipermail/openstack-discuss/2019-February/003073… -gmann

1 0

[openstack-dev][tripleo] TripleO CI Summary: Sprint 26
by Rafael Folco 22 Feb '19

22 Feb '19

Greetings, The TripleO CI team has just completed Sprint 26 / Unified Sprint 5 (Jan 31 thru Feb 20). The following is a summary of completed work during this sprint cycle: - Added support to Fedora on build containers job, including tripleo-repos. Updated the promotion pipeline jobs to use the same workflow for building containers on CentOS 7 and Fedora 28. Container builds on Fedora-28 are still a work in progress. - Converted scenario 12 to standalone. - Investigated the use of Standalone and OpenShift deployments. We determined to continue using a multinode topology for OpenShift. - Improved usability of Zuul container reproducer with launcher and user documentation. - Completed support of additional OVB node in TripleO jobs and implemented a FreeIPA deployment via CI tooling for TLS deployments. The planned work for the next sprint [1] are: - Get the Fedora 28 containers build job running in RDO and reporting failures. - Enable real bare metal testing in upstream promotion jobs - Test and provide feedback on Zuul reproducer with bugs and fixes. - Use ovb to enable an environment for CI testing of TLS. - Continue work on TLS deployments with nova migration tests. - Close out remaining OpenStack-Ansible tempest integration for a first cut or mvp. The Ruck and Rover for this sprint are Rafael Folco (rfolco) and Gabriele Cerami (panda). Please direct questions or queries to them regarding CI status or issues in #tripleo, ideally to whomever has the ‘|ruck’ suffix on their nick. Notes are recorded on etherpad [2]. Thanks, rfolco [1] https://tree.taiga.io/project/tripleo-ci-board/taskboard/unified-sprint-6 [2] https://review.rdoproject.org/etherpad/p/ruckrover-unisprint6

1 0

[baremetal-sig] Bare metal white paper (volunteers needed)
by Chris Hoge 22 Feb '19

22 Feb '19

One of the first goals of the Bare Metal SIG will be to publish a white paper for the Denver Open Infrastructure Summit, similar to the document we produced last year for container integrations. We're looking for volunteers to help organize and write the paper. I've started a planning etherpad with a basic time-line and proposed outline: https://etherpad.openstack.org/p/bare-metal-whitepaper Time line: * February 22: White paper Kick Off Feedback from SIG on proposed outline, content, and schedule * March 4: High-level outline and content assignments Writing begins with weekly check-ins on progress and assistance * March 25: Initial content completed Design requests for figures and diagrams Editing and revisions on content for length, style, and correctness * April 8: Final copy to design and web teams for layout and publication * April 29: Publication at Open Infrastructure Summit, Denver Proposed Outline: * Introduction * High Level Overview of Bare Metal provisioning * Integrations into management tools * Case Studies * Conclusion * Glossary * Authors If we're going to have a successful launch for the summit, we'll need to organize writing efforts around this. Right now we need volunteers to help write the different sections of the document, as well as massage the outline into its final form. In particular we need deployers and users to write a variety of case studies to demonstrate the flexibility and power of Ironic in production. I'd like to get some feedback on the outline in the mailing list, and also have volunteers sign up for different parts of the paper in the planning etherpad. I've also started writing some introduction text to help everyone get started on thinking about how to frame this work in a compelling way. Thanks, and I'm excited to get started on this work with everyone. -Chris

1 0

[tc][election] candidate question: strategic leadership
by Doug Hellmann 22 Feb '19

22 Feb '19

With the changes at the Foundation level, adding new OIPs, a few board members have suggested that this is an opportunity for the TC to evolve from providing what some have seen as tactical management through dealing with day-to-day issues to more long-term strategic leadership for the project. This theme has also come up in the recent discussions of the role of the TC, especially when considering how to make community-wide technical decisions and how much influence the TC should have over the direction individual projects take. What do you think OpenStack, as a whole, should be doing over the next 1, 3, and 5 years? Why? -- Doug

4 3

[dev][keystone] Keystone Team Update - Week of 18 February 2019
by Colleen Murphy 22 Feb '19

22 Feb '19

# Keystone Team Update - Week of 18 February 2019 ## News ### Scope 101 Melanie started a nova thread [0] that highlighted an API in nova that would benefit from leveraging different scopes in keystone and scope_types in oslo.policy. This thread ultimately kicked up a long discussion in IRC [1] about the concept of authorization scope and how it's actually useful to other OpenStack developers. While we document various token scopes in our admin guide [2], contributor guide [3], and explain how to get them in our API reference [4], we don't do a great job of breaking it down for other developers. Specifically, we don't help connect the dots for developers working on other parts of OpenStack that would benefit from the work we've done in keystone, keystonemiddleware, oslo.policy, and oslo.context to protect APIs they write. This is apparent in discussions we have with experienced OpenStack developers. What we need is a concise and digestable document that clearly explains how other developers in OpenStack can use these tools to provide more of the work they do to end users in a secure way. Lance has a WIP patch [5] up to our contributor guide that attempts to outline the questions people have about authorization scopes and how to consume them. If you have unanswered questions about authorization scopes or just want to learn more about it, please add your perspective to the review and we'll work on smoothing out the wrinkles. [0] http://lists.openstack.org/pipermail/openstack-discuss/2019-February/002740… [1] http://eavesdrop.openstack.org/irclogs/%23openstack-keystone/%23openstack-k… [2] https://docs.openstack.org/keystone/latest/admin/tokens-overview.html#autho… [3] https://docs.openstack.org/keystone/latest/contributor/services.html#author… [4] https://developer.openstack.org/api-ref/identity/v3/index.html?expanded=pas… [5] https://review.openstack.org/#/c/638563/ ### Forum, PTG and Summit Sessions Lance posted a call for forum topics for the Denver summit[6]. As the PTG will be in the same place immediately following it, we also need to start thinking about PTG topics too. The presentation schedule has been finalized and posted[7], so make sure to check out all the keystone breakout sessions! [6] http://lists.openstack.org/pipermail/openstack-discuss/2019-February/003021… [7] https://www.openstack.org/summit/denver-2019/summit-schedule ### App Creds Update I posted an update on our progress on the fine-grained-access-control feature for application credentials[8] and we had a brief discussion about it on IRC[9]. Please respond on that thread if you have opinions about. I am expecting we will not meet the feature freeze deadline, which means it's perfectly okay to have a naming bikeshed. [8] http://lists.openstack.org/pipermail/openstack-discuss/2019-February/003031… [9] http://eavesdrop.openstack.org/irclogs/%23openstack-keystone/%23openstack-k… ### Outreachy Applications Open You may have noticed some activity from Outreachy applicants on the mailing list. The next round is open for both project and intern applications until March 26[10]. As you can tell, interns are already searching for and applying for projects, so best to submit project ideas ASAP. If you have an idea for an Outreachy project and would like to be a mentor, feel free to ask me about it: I can give you an idea of what the process is like, what the time commitment is, and other things you should know. [10] https://www.outreachy.org/communities/cfp/openstack/ ## Recently Merged Changes Search query: https://bit.ly/2pquOwT We merged 37 changes this week. ## Changes that need Attention Search query: https://bit.ly/2tymTje There are 44 changes that are passing CI, not in merge conflict, have no negative reviews and aren't proposed by bots. ## Bugs Just after I sent my report last week, we converted several old blueprints to RFE bug reports, so I altered my filter this week to include those: Bugs opened (23) Bug #1816833 (keystone:High) opened by Lance Bragstad https://bugs.launchpad.net/keystone/+bug/1816833 Bug #1817313 (keystone:High) opened by Colleen Murphy https://bugs.launchpad.net/keystone/+bug/1817313 Bug #1816927 (keystone:Low) opened by Lance Bragstad https://bugs.launchpad.net/keystone/+bug/1816927 Bug #1817047 (keystone:Low) opened by André Luis Penteado https://bugs.launchpad.net/keystone/+bug/1817047 Bug #1816054 (keystone:Wishlist) opened by Lance Bragstad https://bugs.launchpad.net/keystone/+bug/1816054 Bug #1816059 (keystone:Wishlist) opened by Lance Bragstad https://bugs.launchpad.net/keystone/+bug/1816059 Bug #1816066 (keystone:Wishlist) opened by Lance Bragstad https://bugs.launchpad.net/keystone/+bug/1816066 Bug #1816076 (keystone:Wishlist) opened by Lance Bragstad https://bugs.launchpad.net/keystone/+bug/1816076 Bug #1816097 (keystone:Wishlist) opened by Lance Bragstad https://bugs.launchpad.net/keystone/+bug/1816097 Bug #1816099 (keystone:Wishlist) opened by Lance Bragstad https://bugs.launchpad.net/keystone/+bug/1816099 Bug #1816105 (keystone:Wishlist) opened by Lance Bragstad https://bugs.launchpad.net/keystone/+bug/1816105 Bug #1816107 (keystone:Wishlist) opened by Lance Bragstad https://bugs.launchpad.net/keystone/+bug/1816107 Bug #1816109 (keystone:Wishlist) opened by Lance Bragstad https://bugs.launchpad.net/keystone/+bug/1816109 Bug #1816112 (keystone:Wishlist) opened by Lance Bragstad https://bugs.launchpad.net/keystone/+bug/1816112 Bug #1816115 (keystone:Wishlist) opened by Lance Bragstad https://bugs.launchpad.net/keystone/+bug/1816115 Bug #1816120 (keystone:Wishlist) opened by Lance Bragstad https://bugs.launchpad.net/keystone/+bug/1816120 Bug #1816158 (keystone:Wishlist) opened by Lance Bragstad https://bugs.launchpad.net/keystone/+bug/1816158 Bug #1816160 (keystone:Wishlist) opened by Lance Bragstad https://bugs.launchpad.net/keystone/+bug/1816160 Bug #1816163 (keystone:Wishlist) opened by Lance Bragstad https://bugs.launchpad.net/keystone/+bug/1816163 Bug #1816164 (keystone:Wishlist) opened by Lance Bragstad https://bugs.launchpad.net/keystone/+bug/1816164 Bug #1816165 (keystone:Wishlist) opened by Lance Bragstad https://bugs.launchpad.net/keystone/+bug/1816165 Bug #1816166 (keystone:Wishlist) opened by Lance Bragstad https://bugs.launchpad.net/keystone/+bug/1816166 Bug #1816167 (keystone:Wishlist) opened by Lance Bragstad https://bugs.launchpad.net/keystone/+bug/1816167 Bugs fixed (8) Bug #1811605 (keystone:High) fixed by Guang Yee https://bugs.launchpad.net/keystone/+bug/1811605 Bug #1814589 (keystone:High) fixed by Guang Yee https://bugs.launchpad.net/keystone/+bug/1814589 Bug #1815539 (keystone:High) fixed by Guang Yee https://bugs.launchpad.net/keystone/+bug/1815539 Bug #1757000 (keystone:Medium) fixed by erus https://bugs.launchpad.net/keystone/+bug/1757000 Bug #1804292 (keystone:Medium) fixed by Lance Bragstad https://bugs.launchpad.net/keystone/+bug/1804292 Bug #1804516 (keystone:Medium) fixed by Lance Bragstad https://bugs.launchpad.net/keystone/+bug/1804516 Bug #1804519 (keystone:Medium) fixed by Lance Bragstad https://bugs.launchpad.net/keystone/+bug/1804519 Bug #1804521 (keystone:Medium) fixed by Lance Bragstad https://bugs.launchpad.net/keystone/+bug/1804521 ## Milestone Outlook https://releases.openstack.org/stein/schedule.html The final release of non-client libraries is next week. As bnemec pointed out, this doesn't include the oslo libraries, for which the freeze is this week. Luckily it doesn't look like we have anything major in flight for oslo.policy and oslo.limit currently. Feature freeze for keystone and final release of client libraries is in two weeks. ## Help with this newsletter Help contribute to this newsletter by editing the etherpad: https://etherpad.openstack.org/p/keystone-team-newsletter

1 0

Re: [Release-job-failures][ansible] Release of openstack/openstack-ansible failed
by Doug Hellmann 22 Feb '19

22 Feb '19

zuul(a)openstack.org writes: > Build failed. > > - announce-release http://logs.openstack.org/14/1426df14f2bec09521dbf85486537250b8865fbc/relea… : FAILURE in 3m 33s > > _______________________________________________ > Release-job-failures mailing list > Release-job-failures(a)lists.openstack.org > http://lists.openstack.org/cgi-bin/mailman/listinfo/release-job-failures This looks like a transient failure installing pbr (another job for the same repo at a different version worked fine). I ran tools/announce.sh in the releases repo by hand to send the announcement instead of requeuing the job [1]. That script did report a warning: No bug url found in 'openstack/openstack-ansible/README.rst' It just means that the script couldn't find the pattern it was looking for to be able to link to the bug tracker in the generated email. When that happens it just leaves the section out of the message body. I don't know how important that is to the OSA team. [1] http://lists.openstack.org/pipermail/release-announce/2019-February/006474.… -- Doug

2 2