December 2017 - 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...

5 years, 3 months

6
6
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

5 years, 4 months

3
4
0 / 0

Update TripleO bookmarks

by Rich Bowen

TL;DR: Please help update the TripleO bookmarks at https://github.com/ccamacho/tripleo-graphics/tree/master/cheatsheets While at OpenStack Summit, I printed and handed out the bookmarks that are listed here: https://www.rdoproject.org/use/bookmarks/ Specifically, the RDO one and the Deploying with TripleO one. Towards the end of the event, someone pointed out that the TripleO bookmark is outdated, incorrect, and only deploys on RHEL. So, we could use some help updating that to reflect the current state of the art, and to deploy on CentOS. The "source" for these bookmarks is at https://github.com/ccamacho/tripleo-graphics/tree/master/cheatsheets -- Rich Bowen: Community Architect rbowen(a)redhat.com @rbowen // @RDOCommunity // @CentOSProject 1 859 351 9166

5 years, 5 months

2
3
0 / 0

Opendaylight Openstack Routing

by Donny Davis

I am sure i am just misunderstanding how this all works, but I have opendaylight running on RDO Pike and all seems to work well. My issue is when I try to connect to a floating ip that is on a provider vlan from a machine that is not on that network. IE < Edge Router > | < Provider Vlan> | < Opendaylight Router> | < Floating IP> | < VM> This works. When I ssh or ping from my edge router which is on the same vlan as my external network in opendaylight (openstack), I have no issue. So Traffic is being labeled and routed properly at this point However when I ssh from my client machines that are also connected to the same edge router it does not. IE < Client Machine> | < Internal Vlan | < Edge Router > | < Provider Vlan> | < Opendaylight Router> | < Floating IP> | < VM> I cannot understand, traffic makes it to the edge router, and is not being dropped by the firewall. This process works fine without Opendaylight. I am sure I am just doing something wrong Please let me know if this is an appropriate list, or if I should move this to an opendaylight list

5 years, 5 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 2017-12-26 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/

5 years, 5 months

2
1
0 / 0

[tripleo]network isolation

by qinglong.dong＠horebdata.cn

Hi, all I want to deploy an baremetal environment(pike) with network isolation. I have three controller nodes and one compute node. Each node has 3 nics. If I set external network as a vlan I succeed. But If I set external network on the bridge(using native vlan on the trunked interface) I fail. Anyone can help? Thanks! Here are some config of controller nodes. Compute node does not have external network and storage management network. Controller NICs Bonded Interface Bond Slaves bond1eth1, eth2 Networks NIC Provisioning eth0 External bond1 / br-ex Internal bond1 / vlan201 Tenant bond1 / vlan204 Storage bond1 / vlan202 Storage Management bond1 / vlan203 network-environment.yaml resource_registry: OS::TripleO::Compute::Net::SoftwareConfig: ../network/config/bond-with-vlans/compute.yaml OS::TripleO::Controller::Net::SoftwareConfig: ../network/config/bond-with-vlans/controller.yaml parameter_defaults: ControlPlaneSubnetCidr: '24' ControlPlaneDefaultRoute: 192.168.24.1 EC2MetadataIp: 192.168.24.1 InternalApiNetCidr: 172.17.0.0/24 StorageNetCidr: 172.18.0.0/24 StorageMgmtNetCidr: 172.19.0.0/24 TenantNetCidr: 172.16.0.0/24 ExternalNetCidr: 192.168.1.0/24 InternalApiNetworkVlanID: 201 StorageNetworkVlanID: 202 StorageMgmtNetworkVlanID: 203 TenantNetworkVlanID: 204 InternalApiAllocationPools: [{'start': '172.17.0.10', 'end': '172.17.0.200'}] StorageAllocationPools: [{'start': '172.18.0.10', 'end': '172.18.0.200'}] StorageMgmtAllocationPools: [{'start': '172.19.0.10', 'end': '172.19.0.200'}] TenantAllocationPools: [{'start': '172.16.0.10', 'end': '172.16.0.200'}] ExternalAllocationPools: [{'start': '192.168.1.223', 'end': '192.168.1.235'}] ExternalInterfaceDefaultRoute: 192.168.1.1 DnsServers: ["192.168.1.1"] NeutronNetworkType: 'vlan' NeutronTunnelTypes: '' NeutronNetworkVLANRanges: 'datacentre:1:1000' BondInterfaceOvsOptions: "bond_mode=active-backup" NeutronMechanismDrivers: linuxbridge controller.yaml [...] resources: OsNetConfigImpl: type: OS::Heat::SoftwareConfig properties: group: script config: str_replace: template: get_file: ../../scripts/run-os-net-config.sh params: $network_config: network_config: - type: interface name: nic1 use_dhcp: false addresses: - ip_netmask: list_join: - / - - get_param: ControlPlaneIp - get_param: ControlPlaneSubnetCidr routes: - ip_netmask: 169.254.169.254/32 next_hop: get_param: EC2MetadataIp - type: linux_bridge name: bridge_name dns_servers: get_param: DnsServers use_dhcp: false addresses: - ip_netmask: get_param: ExternalIpSubnet routes: - default: true next_hop: get_param: ExternalInterfaceDefaultRoute members: - type: linux_bond name: bond1 bonding_options: mode=1 members: - type: interface name: nic2 primary: true - type: interface name: nic3 - type: vlan device: bond1 vlan_id: get_param: InternalApiNetworkVlanID addresses: - ip_netmask: get_param: InternalApiIpSubnet - type: vlan device: bond1 vlan_id: get_param: StorageNetworkVlanID addresses: - ip_netmask: get_param: StorageIpSubnet - type: vlan device: bond1 vlan_id: get_param: StorageMgmtNetworkVlanID addresses: - ip_netmask: get_param: StorageMgmtIpSubnet - type: vlan device: bond1 vlan_id: get_param: TenantNetworkVlanID addresses: - ip_netmask: get_param: TenantIpSubnet outputs: OS::stack_id: description: The OsNetConfigImpl resource. value: get_resource: OsNetConfigImpl

5 years, 5 months

1
0
0 / 0

Maintenance on review.rdoproject.org *tonight* December 20th 23:00 UTC

by David Moreau Simard

Hi, Our apologies for the short notice but review.rdoproject.org will be undergoing maintenance tonight at 23:00 UTC in order to update to operating system and software factory packages to the latest versions. We are planning one hour for the maintenance but it could take longer if we run into unexpected complications. There may brief moments of downtime as we will need to reboot the different instances of the cluster at least once. Please note that while this update will enable us to activate Zuul v3, it will *not* be implemented tonight. Zuul v3 will be installed at a later date, at the very least after the upcoming holiday period. If you have any questions or notice any unexpected issues, please reach out to us on #rdo on IRC or by replying to this thread. Thanks ! David Moreau Simard Senior Software Engineer | OpenStack RDO dmsimard = [irc, github, twitter]

5 years, 5 months

1
1
0 / 0

Add your things which make RDO awesome in year 2017

by Chandan kumar

Hello, We are planning to do a blog post on the 2017 year in review for RDO. Lots of awesome things have happened this year in RDO land. Feel free to reply to the mailing list stating the same. * What good things have happened this year and what needs to be improved? * If someone helped you in some way, feel free to drop a comment about that, and what you appreciate. * If you have photos from some RDO gathering, please share those Thanks, Chandan Kumar

5 years, 5 months

1
0
0 / 0

[Meeting] RDO meeting (2017-12-20) minutes

by Alfredo Moralejo Alonso

============================== #rdo: RDO meeting - 2017-12-20 ============================== Meeting started by amoralej at 15:05:39 UTC. The full logs are available athttp://eavesdrop.openstack.org/meetings/rdo_meeting___2017_12_20/2017/r... . Meeting summary --------------- * rollcall (amoralej, 15:05:52) * CBS certificate renewal on Dec, 31/Jan, 1 (amoralej, 15:07:30) * ACTION: dmsimard to reach out to #centos-devel about getting a service account like paas (dmsimard, 15:16:28) * ACTION: amoralej to install new certificate for CBS task (amoralej, 15:18:23) * Upgrading review.rdoproject.org to software factory to 2.7 (amoralej, 15:24:07) * AGREED: review.rdoproject.org to be updated tonight december 20th at 23:00UTC (dmsimard, 15:35:38) * ACTION: dmsimard to send an email to notify about the upgrade (dmsimard, 15:35:45) * Update about status of infra (amoralej, 15:36:37) * Test day (amoralej, 15:42:47) * ACTION: dmsimard to discuss the test day cloud idea with the TC (dmsimard, 15:47:00) * Cancelling 27th Dec and 03rd Jan meeting due to holidays (amoralej, 15:48:41) * AGREED: the meeting on december 27th will be cancelled (amoralej, 15:51:56) * 27th Dec, 2017 RDO meeting is cancelled, Happy Holidays :-) (chandankumar, 15:52:01) * AGREED: the meeting on january on 3rd is kept (amoralej, 15:52:10) * ACTION: chandankumar will chair the RDO meeting on January the 3rd (amoralej, 15:52:27) * the office hour on december 26th is cancelled (amoralej, 15:53:37) * open floor (amoralej, 15:54:06) Meeting ended at 15:59:48 UTC. Action items, by person ----------------------- * amoralej * amoralej to install new certificate for CBS task * chandankumar * chandankumar will chair the RDO meeting on January the 3rd * dmsimard * dmsimard to reach out to #centos-devel about getting a service account like paas * dmsimard to send an email to notify about the upgrade * dmsimard to discuss the test day cloud idea with the TC People present (lines said) --------------------------- * amoralej (107) * dmsimard (71) * apevec (19) * chandankumar (17) * rbowen (12) * jpena (9) * openstack (9) * number80 (7) * weshay (3) * rlandy|rover (2) * rdogerrit (2) * ykarel (2) * rdobot (1) * mary_grace (1) Generated by `MeetBot`_ 0.1.4

5 years, 5 months

1
0
0 / 0

RDO meeting on 27th Dec, 2017 and RDO Office hour on 26th Dec, 2017 are cancelled

by Chandan kumar

Hello, RDO meeting on 27th Dec, 2017 and RDO Office hour on 26th Dec, 2017 are canceled due to holidays. We will again meet in New year 2018. Till then Happy Holidays RDOers :-) Thanks, Chandan Kumar

5 years, 5 months

1
0
0 / 0

2023

2022

2021

2020

2019

2018

2017

users December 2017