January 2018 - users - Rdo List Archives

[all] Revisiting RDO Technical Definition of Done

by Alan Pevec

Hi all, we as a community last discussed RDO definition of done more than a year ago and it was documented[1] In the meantime we have multiple changes in the RDO promotion process, most significant is that we do not run all the CI promotion jobs in the single Jenkins pipeline, instead there is now an increasing number of periodic Zuul jobs in review.rdoproject.org reporting to DLRN API database. Promotion is performed asynchronously when all the required jobs report success. At the same time, TripleO as the deployment project with the most coverage in the promotion CI, has moved to be completely containerized in Queens. While RDO does provide container registry which is used with RDO Trunk, there aren't currently plans to provide containers built from the stable RPM builds as discussed on this list [2] around Pike GA. Even if we do all the work listed in [2] problem stays that containers are currently installer specific and we cannot realistically provide separate set of containers for each of TripleO, Kolla, OSA... Proposal would be to redefine DoD as follows: - RDO GA release delivers RPM packages via CentOS Cloud SIG repos, built from pristine upstream source tarballs - CI promotion GA criteria is changed from Jenkins pipeline to the list of jobs running with RPM packages directly, initial set would be all weirdo jobs running in [3] - TripleO jobs would not be part of RDO GA criteria since TripelO now requires containers which RDO will not ship.TripleO promotion CI will continue running with containers built with RDO Trunk packages. I'm adding this topic on the agenda for the RDO meeting today, I won't be able to join but we need to get that discussion going so we have updated DoD ready for Queens GA. Cheers, Alan [1] https://www.rdoproject.org/blog/2016/05/technical-definition-of-done/ [2] https://www.redhat.com/archives/rdo-list/2017-August/msg00069.html [3] https://ci.centos.org/view/rdo/view/promotion-pipeline/job/rdo_trunk-prom...

6 years, 2 months

6
6
0 / 0

RHOSP 10 failed registration of the overcloud nodes

by Anda Nicolae

Hello, I am trying to deploy OpenStack 10 using OpenStack Platform Director 10. I am using a bare-metal server with RedHat 7.4, on which I have created 3 VMs: 1st VM is the undercloud node, 2nd VM is the overcloud controller node and the 3rd VM is the overcloud compute node. The bare-metal server I am using is also my KVM hypervisor for the overcloud. The bare-metal server has 2 interfaces: an external interface used in instackenv.json for registering the overcloud nodes and a provisioning interface which will be used for provisioning the overcloud nodes. My 1st question is: Is it mandatory that the KVM hypervisor for the overcloud VMs and the undercloud are the same machine? As you can see, in my case the undercloud VM and the KVM hypervisor are different machines. I saw a blog post which used a topology similar to mine: https://keithtenzer.com/2017/04/20/red-hat-openstack-platform-10-newton-i... The error I am getting while running: openstack baremetal import -- json ~/.instackenv.json is in ironic_conductor.log: Failed to validate power driver interface for node <uuid>. Error: SSH connection cannot be established: Failed to establish SSH connection to host <kvm_hypervisor_external_ip_address > I have created the instackenv.json file which looks similar to this: "arch": "x86_64", "host-ip": "<kvm_hypervisor_external_ip_address>", "power_manager": "nova.virt.baremetal.virtual_power_driver.VirtualPowerManager", "ssh-user": "stack", "ssh-key": "$(cat ~/.ssh/id_rsa)", "nodes": [ { "mac": [ "<overcloud_controller_provisioning_interface_mac_address>" ], "name": "overcloud-controller", "capabilities" : "profile:control", "cpu": "4", "memory": "6000", "disk": "50", "arch": "x86_64", "pm_user": "stack", "pm_addr": "<kvm_hypervisor_external_ip_address>", "pm_password": "$(cat ~/.ssh/id_rsa)", "pm_type": "pxe_ssh" } , { "mac": [ "<overcloud_compute_provisioning_interface_mac_address>" ], "name": "overcloud-compute", "capabilities" : "profile:compute", "cpu": "4", "memory": "6000", "disk": "50", "arch": "x86_64", "pm_user": "stack", "pm_addr": "<kvm_hypervisor_external_ip_address>", "pm_password": "$(cat ~/.ssh/id_rsa)", "pm_type": "pxe_ssh" } ] } Do you have any idea what might have gone wrong and how can I progress with my overcloud node registration? Thanks, Anda

6 years, 2 months

2
1
0 / 0

RHOSP 10 failed overcloud deployment

by Anda Nicolae

Hello, As previously stated in my previous mail on this list , I am trying to deploy OpenStack 10 using OpenStack Platform Director 10. I am using a bare-metal server with RedHat 7.4, on which I have created 3 VMs: 1st VM is the undercloud node, 2nd VM is the overcloud controller node and the 3rd VM is the overcloud compute node. The bare-metal server I am using is also my KVM hypervisor for the overcloud. I managed to provision my overcloud nodes and now I am stuck at performing overcloud deployment. The command I am running is: openstack --debug overcloud deploy --templates ~/templates --control-scale 1 --compute-scale 1 --control-flavor control --compute-flavor compute -e ~/templates/environments/network-isolation.yaml -e ~/templates/environments/network-environment.yaml --ntp-server pool.ntp.org --neutron-network-type vxlan --neutron-tunnel-types vxlan. I connected via ssh with heat-admin user on my controller and compute nodes. I've run the following command to gather logs: sudo journalctl -u os-collect-config I think the problem is on my controller node, because I've noticed the following messages in the output of the above command: os-collect-config[2996]: Source [ec2] Unavailable. os-collect-config[2996]: /var/lib/os-collect-config/local-data not found. Skipping os-collect-config[2996]: No local metadata found (['/var/lib/os-collect-config/local-data'] These messages repeat for various times in the output of the above command. On my underclud VM, I've noticed that overcloud deployment remains stuck when running wait_for_stack_ready function from /usr/lib/python2.7/site-packages/tripleoclient/utils.py. I also intend to add some logs in /usr/lib/python2.7/site-packages/os_collect_config/collect.py to see what causes the error message: Source [ec2] Unavailable I think I have an error in my templates, but I don't figure out which yet. Do you know what may cause this? Thanks, Anda

6 years, 2 months

4
13
0 / 0

[Meeting] RDO meeting (2018-01-31) minutes

by Javier Pena

============================== #rdo: RDO meeting - 2018-01-31 ============================== Meeting started by jpena at 15:01:19 UTC. The full logs are available at http://eavesdrop.openstack.org/meetings/rdo_meeting___2018_01_31/2018/rdo... . Meeting summary --------------- * roll call (jpena, 15:01:49) * Plan to provide VM images for Octavia (jpena, 15:05:56) * AGREED: Build images for Octavia using a periodic job on review.rdoproject.org, store on images.rdoproject.org (jpena, 15:22:58) * ACTION: jpena to send email to dev@lists with results of Octavia image discussion (jpena, 15:23:31) * Discuss Power CI for RDO (jpena, 15:24:16) * LINK: http://trunk.rdoproject.org/centos7-master/current-tripleo (amoralej, 15:40:12) * Preparation for queens release (jpena, 15:42:22) * ACTION: maintainers to send final updates for specs with requirements updates (amoralej, 15:45:55) * we will pin non-OpenStack puppet modules for queens with the builds in next promotion (amoralej, 15:49:28) * Chair for the next meeting (jpena, 15:53:25) * ACTION: amoralej to chair the next meeting (jpena, 15:53:49) * open floor (jpena, 15:53:54) Meeting ended at 16:00:48 UTC. Action items, by person ----------------------- * amoralej * amoralej to chair the next meeting * jpena * jpena to send email to dev@lists with results of Octavia image discussion People present (lines said) --------------------------- * amoralej (60) * jpena (37) * mjturek (26) * bcafarel (13) * number80 (8) * rdogerrit (6) * openstack (6) * EmilienM (5) * pabelanger (4) * ykarel (2) * mary_grace (2) * mnaser (1) * tosky (1) * chandankumar (1) Generated by `MeetBot`_ 0.1.4

6 years, 2 months

1
0
0 / 0

[RDO] Queens Milestone 3 test day, Feb 8, 9

by Rich Bowen

We will be testing the RDO OpenStack Queens Milestone 3 packages on February 8th and 9th. Details are at http://rdoproject.org/testday/queens/milestone3/ We will be congregating on the #RDO channel on Freenode IRC for questions, commentary, and so on. We will also be deploying a test cloud, like last time, so that you can test without having to deploy it yourself. Details, and signups, are at https://etherpad.openstack.org/p/rdo-queens-m3-cloud If you have any questions, please bring them to the users(a)lists.rdoproject.org mailing list. You can subscribe to this list at http://lists.rdoproject.org/ -- Rich Bowen: Community Architect rbowen(a)redhat.com @rbowen // @RDOCommunity // @CentOSProject 1 859 351 9166

6 years, 2 months

1
0
0 / 0

Newbie question: CentOS Cloud SIG vs RDO vs "centos-release-openstack-xxx"

by Jan Gutter

Hi, Apologies for asking an obviously newbie question here, but I got a bit confused by the relationship between the CentOS Cloud SIG, RDO and the repos enabled by installing "centos-release-openstack-<x>". For example, I'm aware that upstream OpenStack is no longer supporting Newton, but RHEL has support for RHOSP10 (based on Newton). I do see that Newton's still listed on https://trunk.rdoproject.org/ Am I correct in assuming that the repos pointed to when a CentOS user installs centos-release-openstack-<x> points to a set of packages that was emitted from the RDO pipeline? Is this process manual or automated to some degree? In a semi-related question: I've hit an issue with an outdated puppet-pacemaker package in the centos-release-openstack-newton repo that prevents deployment. There's an "easy fix" available by promoting the pike version of said package to the same repo, but if Newton's been sunset then this question is moot. Apologies for the meandering ramble, if you need more details on the last issue I can provide them. -- Jan Gutter Embedded Networking Software Engineer Netronome | First Floor Suite 1, Block A, Southdowns Ridge Office Park, Cnr Nellmapius and John Vorster St, Irene, Pretoria, 0157 Phone: +27 (12) 665-4427 | Skype: jangutter | www.netronome.com

6 years, 3 months

3
4
0 / 0

Removing mongodb from RDO

by Alfredo Moralejo Alonso

Hi, During previous OpenStack releases, projects using mongodb as backend (as telemetry or zaqar) have moved to other technologies for data persistence and mongo is not longer the default or preferred backend. In this cycle (Queens), mongodb packages will be retired from RDO repositories under the assumption that users have implemented any of the alternatives for each affected service (or are in the process of doing it). This will happen in next weeks and will not affect previous releases. If you have any question or you think that mongo should be maintained in RDO, please feel free to let us know in this thread or reach us in #rdo so that we can consider all implications of this decision. Best regards, Alfredo

6 years, 3 months

3
4
0 / 0

[Minutes] RDO Office Hour 2018-01-09

by Chandan kumar

================================ #rdo: RDO Office Hour 2018-01-09 ================================ Meeting started by chandankumar at 13:32:30 UTC. The full logs are available at http://eavesdrop.openstack.org/meetings/rdo_office_hour_2018_01_09/2018/r... . Meeting summary --------------- * Roll Call (chandankumar, 13:32:44) * LINK: package review queue -> http://bit.ly/rdo_pkg_rvw (chandankumar, 13:34:53) * LINK: https://bugzilla.redhat.com/show_bug.cgi?id=1528360 -> closed (jpena, 13:45:04) * LINK: https://bugzilla.redhat.com/show_bug.cgi?id=1527427 -> closed (jpena, 13:45:44) * LINK: https://bugzilla.redhat.com/show_bug.cgi?id=1494119 -> closed (jpena, 13:47:42) * LINK: https://bugzilla.redhat.com/show_bug.cgi?id=1531613 -> closed (jpena, 13:48:11) * LINK: https://bugzilla.redhat.com/show_bug.cgi?id=1527448 -> closed (jpena, 13:54:16) * LINK: https://bugzilla.redhat.com/show_bug.cgi?id=1530991 -> closed (jpena, 13:55:13) Meeting ended at 14:31:33 UTC. People present (lines said) --------------------------- * chandankumar (25) * openstack (11) * jpena (9) * rdogerrit (7) * tristanC (5) * weshay|rover (4) * number80 (4) * rbowen (1) * lon (1) * rdobot (1) * EmilienM (1) * sfbender (1) Generated by `MeetBot`_ 0.1.4

6 years, 3 months

1
0
0 / 0

[Fedocal] Reminder meeting : RDO Office Hours

by chkumar246＠gmail.com

Dear all, You are kindly invited to the meeting: RDO Office Hours on 2018-01-23 from 13:30:00 to 14:30:00 UTC The meeting will be about: The meeting will be about RDO Office Hour. Aim: To keep up with increasing participation, we'll host office hours to add more easy fixes and provide mentoring to newcomers. [Agenda at RDO Office Hour easyfixes](https://review.rdoproject.org/etherpad/p/rdo-office-hour-easyf... Source: https://apps.fedoraproject.org/calendar/meeting/6374/

6 years, 3 months

1
0
0 / 0

Problem with OVS configuration in packstack

by Nathan Butcher

I've been experimenting with a particular configuration from a commercial course on OpenStack, but I've hit an error in packstack pike. Essentially the idea is to have an eth0 as an external interface out to the wider internet, and eth1 for all the internal traffic between nodes. Both eth0 and eth1 have been given valid IP addresses(eth0: 10.0.2.9, eth1: 192.168.2.9), and the hostname of the host has been put into /etc/hosts with the IP address of the external interface. I tested my answer file to see that it worked properly as an all-in-one - which it did, but when I make these OVS changes, packstack doesn't finish up properly CONFIG_NEUTRON_OVS_BRIDGE_MAPPINGS=physnet1:br-eth1 CONFIG_NEUTRON_OVS_BRIDGE_IFACES=br-eth1:eth1 CONFIG_NEUTRON_OVS_TUNNEL_IF=eth1 The error I see happens during the compute.pp part of applying the puppet manifests. ERROR : Error appeared during Puppet run: 10.0.2.9_compute.pp Error: Evaluation Error: Error while evaluating a Function Call, no address for at /var/tmp/packstack/<code>/modules/packstack/manifests/neutron/ovs_agent.pp:50:27 on node rdotest.gateway I've tried to dig through the trace log, but no smoking gun is showing up. I can post log files and the answer file if needed. Thanks,

6 years, 3 months

2
1
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

users January 2018