[Rdo-list] RDO Liberty and Fedora
by Alan Pevec
Hi all,
Fedora/RDO relationship topic came up few months ago on the rdo-list and
in the meantime details have been refined in a Trello card
https://trello.com/c/wzdl1IlZ/52-openstack-in-fedora which I'll try to
summarize in this post.
High level overview (aka tl;dr) is that RDO Liberty repository will be
providing EL7 packages, hosted on CentOS mirrors and built as a part
of CentOS CloudSIG.
For developers using Fedora latest trunk builds of openstack-* packages
will be available from Delorean Trunk.
OpenStack service packages (openstack-*) will be retired in Fedora
master while Oslo and OpenStack clients stay in Fedora proper to allow
using Fedora as a client of OpenStack based cloud providers.
Reasoning is that Fedora user population are developers who always
need latest and greatest version and Delorean Trunk packages are the
best match. We were trying to follow 1:1 mapping between Fedora and
OpenStack release but it is getting out of sync now (current f22 is
Juno, unreleased f23 is Kilo) and it's getting impossible to keep up
with required dependency versions in the current stable Fedora without
breaking older OpenStack release.
There is also wasted overhead of pushing OpenStack stable updates in
Fedora when stable builds are not interesting for the target
population.
For production setup EL7 platform is preferred and that's where we are
going to provide stable updates in released RDO versions.
Cheers,
Alan
8 years, 8 months
[Rdo-list] Liberty RDO Manager Failing to install
by Graeme Gillies
Hi,
I'm attempting to get Liberty RDO Manager up and running.
I've manually compiled python-keystoneauth1 using the spec from the
delorean repos and installed that, and have installed
python-openstackclient. Now when I attempt to run
openstack undercloud install
I get the following error
$ openstack undercloud install
The plugin osc_password could not be found
Is another packaging missing, or is this more likely a missing
dependency that should be getting pulled in by python-openstackclient?
Regards,
Graeme
--
Graeme Gillies
Principal Systems Administrator
Openstack Infrastructure
Red Hat Australia
8 years, 8 months
[Rdo-list] RDO Test Day, Sep 23-24
by Rich Bowen
We are planning to do a test day of Liberty RDO next week, September
23rd and 24th. The test day notes are shaping up at
https://www.rdoproject.org/RDO_test_day_Liberty and should be fleshed
out more by the end of the week. As usual, we'll coordinate on #rdo (on
Freenode) for questions and discussion.
The packages that we will be testing have been through CI, so we should
be able to have a fairly successful day.
If you have things that you'd like to see tested, please add these to
the test case matrix.
We're aware that a number of people will be out during this time, but
it's been difficult to find days that work for everyone. So we're
planning to have another test day in the weeks to come. Announcement to
come soon.
--
Rich Bowen - rbowen(a)redhat.com
OpenStack Community Liaison
http://rdoproject.org/
8 years, 8 months
[Rdo-list] Question about Restart=always in systemd
by Liping Mao (limao)
Hi all,
We find some of the openstack systemd config contain "Restart=always", but some other do not have this, is this a bug or this is just what we want?
Thanks for your help.
For example:
We have "Restart=always" in keystone:
[cid:image002.jpg@01D0DBFD.205589F0]
But we do not have "Restart=always" in neutron-server:
[cid:image004.jpg@01D0DBFD.205589F0]
Thanks.
Regards,
Liping Mao
8 years, 8 months
[Rdo-list] [delorean] Planned maintenance for Delorean instance - September 14-15
by Javier Pena
Dear all,
Due to a planned maintenance of the infrastructure supporting the Delorean instance (trunk.rdoproject.org), it is expected to be offline between September 14 (~ 9PM EDT) and September 15 (~ 9PM EDT).
We will be sending updates to the list if there is any additional information or change in the plans, and keep you updated on the status.
Please let us know if you have any questions or concerns.
Regards,
Javier
----
Javier Peña, RHCA email: javier.pena(a)redhat.com
Senior Software Engineer phone: +34 914148872
EMEA OpenStack Engineering
8 years, 8 months
[Rdo-list] Delorean-rdo-management.repo missing
by Eduardo Gonzalez
Hi,
Today, i have tried to create overcloud images with the following command:
openstack overcloud image build --all
The process keeps stuck while adding and updating system packages with
delorean-rdo-management-repo.
Yesterday, some problems related with delorean repository maintenance
happened, so my question is:
The missing repo file is supposed to be there or there is a bug that are
searching the file in the wrong location?
Here is the output related with the issue:
+ echo dib-run-parts Wed Sep 16 21:08:51 UTC 2015 00-centos-cloud-repo
completed
dib-run-parts Wed Sep 16 21:08:51 UTC 2015 00-centos-cloud-repo completed
+ for target in '$targets'
+ output 'Running /tmp/in_target.d/pre-install.d/00-delorean-rdo-management'
++ date
+ echo dib-run-parts Wed Sep 16 21:08:51 UTC 2015 Running
/tmp/in_target.d/pre-install.d/00-delorean-rdo-management
dib-run-parts Wed Sep 16 21:08:51 UTC 2015 Running
/tmp/in_target.d/pre-install.d/00-delorean-rdo-management
+ target_tag=00-delorean-rdo-management
+ date +%s.%N
+ /tmp/in_target.d/pre-install.d/00-delorean-rdo-management
+ export DELOREAN_TRUNK_MGT_REPO=
http://trunk.rdoproject.org/centos7/current/
+ DELOREAN_TRUNK_MGT_REPO=http://trunk.rdoproject.org/centos7/current/
+ curl -o /etc/yum.repos.d/delorean-rdo-management.repo
http://trunk.rdoproject.org/centos7/current//delorean-rdo-management.repo
% Total % Received % Xferd Average Speed Time Time Time
Current
Dload Upload Total Spent Left
Speed
100 243 100 243 0 0 427 0 --:--:-- --:--:-- --:--:--
428
+ target_tag=00-delorean-rdo-management
+ date +%s.%N
+ output '00-delorean-rdo-management completed'
++ date
+ echo dib-run-parts Wed Sep 16 21:08:52 UTC 2015
00-delorean-rdo-management completed
dib-run-parts Wed Sep 16 21:08:52 UTC 2015 00-delorean-rdo-management
completed
+ for target in '$targets'
+ output 'Running /tmp/in_target.d/pre-install.d/00-enable-cr-repo'
++ date
+ echo dib-run-parts Wed Sep 16 21:08:52 UTC 2015 Running
/tmp/in_target.d/pre-install.d/00-enable-cr-repo
dib-run-parts Wed Sep 16 21:08:52 UTC 2015 Running
/tmp/in_target.d/pre-install.d/00-enable-cr-repo
+ target_tag=00-enable-cr-repo
+ date +%s.%N
+ /tmp/in_target.d/pre-install.d/00-enable-cr-repo
+ set -o pipefail
+ yum -y update
Loaded plugins: fastestmirror
File contains no section headers.
file: file:///etc/yum.repos.d/delorean-rdo-management.repo, line: 1
'<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 2.0//EN">\n'
Regards.
Eduardo Gonzalez
8 years, 8 months
[Rdo-list] nova cells with neutron network
by Sha Li
Hi,
I am try to test the nova cells function with Juno release.
My test deployment consits of one api-cell node, one child-cell node and
one compute node.
api-cell node: nova-api, nova-cells, nova-cert, nova-condoleauth,
nova-novncproxy
child-cell node: nova-cells, nova-conductor, nova-scheduler
compute node: nova-compute
I found most deployment example is using nova-network with nova-cells. I
want to use neutron. So I had keystone , glance, and neutron-server,
neutron-dhcp, neutron-l3 shared between all cells and deployed all on the
api-cell node.
I encounterd similar problem as described in this bug report
https://bugs.launchpad.net/nova/+bug/1348103
When boot a new instance, nova-compute fails to get the network-vif-plugged
notification and get time out waiting for the call back.
But on the neutron server side, it looks like the notification had been
successfully sent and get the 200 response code from nova-api server
I had to set
vif_plugging_is_fatal = False
Then the instnace can be spawned normally
I am wondering how people use neutron with nova-cells, is this going to
cause any trouble in large scale production deployment.
Cheers,
Sha
--- neutron server log file
2015-08-22 00:20:35.464 16812 DEBUG neutron.notifiers.nova [-] Sending
events: [{'status': 'completed', 'tag':
u'2839ca4d-b632-4d64-a174-ecfe34a7a746', 'name': 'network-vif-plugged',
'server_uuid': u'092c8bc4-3643-44c0-b79e-ad5caac18b3d'}] send_events
/usr/lib/python2.7/site-packages/neutron/notifiers/nova.py:232
2015-08-22 00:20:35.468 16812 INFO urllib3.connectionpool [-] Starting new
HTTP connection (1): 192.168.81.221
2015-08-22 00:20:35.548 16812 DEBUG urllib3.connectionpool [-] "POST
/v2/338aad513c604880a6a0dcc58b88b905/*os**-server-external-events *HTTP/1.1"
200 183 _make_request /usr/lib/python2.7/site-packages/urllib3/connectionp
ool.py:357
2015-08-22 00:20:35.550 16812 INFO neutron.notifiers.nova [-] Nova event
*response*: {u'status': u'completed', u'tag':
u'2839ca4d-b632-4d64-a174-ecfe34a7a746', u'name': u'network-vif-plugged',
u'server_uuid': u'092c8bc4-3643-44c0-b79e-ad5caac18b3d', u'code': 200}
8 years, 8 months
[Rdo-list] RDO Liberty and Fedora - details for openstack-* maintainers
by Alan Pevec
Subject: RDO Liberty and Fedora - details for openstack-* maintainers
As a followup, here are few notes for the package maintainers, until
rdo-packaging documentation is updated with this workflow.
distgit will be rdo-liberty branch on gerrithub/openstack-packages,
create it from Fedora master and squash merge rpm-master:
git remote add -f gerrit
ssh://review.gerrithub.io:29418/openstack-packages/$PROJECT # skip if
already present
git-review -s
git remote add -f fedora
git://pkgs.fedoraproject.org/openstack-$PROJECT.git # skip if already
present
git branch rdo-liberty fedora/master
git checkout rdo-liberty
git merge --squash gerrit/rpm-master
git reset HEAD .gitignore sources .gitreview
git checkout .gitignore sources
Resolve conflicts in .spec file
Set correct Liberty Version: for your project
Release: field should be pre-release 0.N until GA
e.g. openstack-keystone.spec
%global release_name liberty
%global pypi_name keystone
%global milestone .0b3
%{!?upstream_version: %global upstream_version %{version}%{?milestone}}
Name: openstack-keystone
Epoch: 1
Version: 8.0.0
Release: 0.3%{?milestone}%{?dist}
Get the source tarball for the current milestone e.g. milestone 3:
Source0:
http://launchpad.net/%{pypi_name}/%{release_name}/%{release_name}-3/+down...
If Source0: is like above, rdopkg new-version --bump-only
$UPSTREAM_VERSION should work.
Preserve Kilo patches if any: ideally, RDO packages are pure upstream
and don't need any patches in RPM
-patches branches are as before in github/redhat-openstack/$PROJECT
but since there isn't Fedora:OpenStack 1:1 anymore, branch name for
RDO Liberty RPM patches will be liberty-patches.
You might want to archive old changelog entries in ChangeLog.old like
done for Kilo GA
http://pkgs.fedoraproject.org/cgit/openstack-nova.git/commit/ChangeLog.ol...
When done:
git commit -m "Update to Liberty"
git push -u gerrit rdo-liberty:rdo-liberty
For packages already in Fedora, build Liberty versions in Rawhide and
ping apevec or number80 on Freenode #rdo for CloudSIG EL7 build.
If you get stuck, please ping us on IRC and/or reply to this thread!
Cheers,
Alan
8 years, 8 months
[Rdo-list] [meeting] RDO packaging meeting (2015-09-16)
by Chandan kumar
========================================
#rdo: RDO packaging meeting (2015-09-16)
========================================
Meeting started by chandankumar at 15:01:27 UTC. The full logs are
available at
http://meetbot.fedoraproject.org/rdo/2015-09-16/rdo.2015-09-16-15.01.log....
.
Meeting summary
---------------
* LINK: https://etherpad.openstack.org/p/RDO-Packaging (rbowen,
15:03:37)
* RDO website (chandankumar, 15:03:48)
* beta version of RDO website is up http://beta.rdoproject.org/
(chandankumar, 15:04:05)
* LINK:
https://www.redhat.com/archives/rdo-list/2015-September/msg00077.html
(chandankumar, 15:04:13)
* LINK: https://github.com/redhat-openstack/website/ (chandankumar,
15:05:08)
* RDO DOC hack day on 12/13 Oct, 2015. (chandankumar, 15:05:46)
* start cloning and poking around at RDO website (number80, 15:06:07)
* RDO Liberty and Fedora (chandankumar, 15:07:57)
* LINK:
https://www.redhat.com/archives/rdo-list/2015-September/msg00090.html
(chandankumar, 15:08:24)
* ACTION: all maintainers are requested to prepare liberty release for
their packages (number80, 15:08:40)
* LINK:
https://www.redhat.com/archives/rdo-list/2015-September/msg00113.html
(chandankumar, 15:08:51)
* LINK: https://trello.com/c/GPqDlVLs/63-liberty-3-rpms
(chandankumar, 15:11:05)
* ACTION: apevec send another followup to rdo-list explaining
workflow for new RDO packages (apevec, 15:13:53)
* ACTION: number80 create package-review component (number80,
15:14:33)
* Needs version Bumps for following packages (chandankumar, 15:16:43)
* LINK: https://etherpad.openstack.org/p/RDO-Packaging (apevec,
15:33:48)
* New Package scm request (chandankumar, 15:35:04)
* LINK: python-oslo-reports -
https://bugzilla.redhat.com/show_bug.cgi?id=1241088 (chandankumar,
15:35:14)
* LINK: python-castellan -
https://bugzilla.redhat.com/show_bug.cgi?id=1259919 (chandankumar,
15:35:27)
* LINK: openstack-barbican
https://bugzilla.redhat.com/show_bug.cgi?id=1190269 (chandankumar,
15:36:43)
* LINK:
https://admin.fedoraproject.org/pkgdb/package/python-barbicanclient/
(chandankumar, 15:38:11)
* Status of maintenance works on Delorean instance (chandankumar,
15:39:12)
* f21 Delorean worker deprecation (chandankumar, 15:40:52)
* LINK:
https://www.redhat.com/archives/rdo-list/2015-September/msg00119.html
(chandankumar, 15:41:24)
* LINK: https://trunk.rdoproject.org/f22/status_report.html (apevec,
15:42:27)
* RDO Liberty Test day - September 23/24 (chandankumar, 15:45:31)
* LINK: RDO liberty test day
https://www.redhat.com/archives/rdo-list/2015-September/msg00114.html
(chandankumar, 15:46:04)
* LINK: https://www.rdoproject.org/RDO_test_day_Liberty was not
migrated (apevec, 15:47:48)
* Delorean CI:
https://prod-rdojenkins.rhcloud.com/view/RDO-Liberty-Delorean-Trunk/
(chandankumar, 15:51:11)
* LINK:
https://www.redhat.com/archives/rdo-list/2015-September/msg00105.html
(dmsimard, 15:51:38)
* LINK: https://bugzilla.redhat.com/show_bug.cgi?id=1249685
(dmsimard, 15:52:54)
* LINK: https://review.gerrithub.io/#/c/246606/ (dmsimard, 15:54:49)
* Fedora client import (chandankumar, 15:55:46)
* open floor (chandankumar, 16:00:34)
* chair rotation for next meeting (chandankumar, 16:01:38)
* ACTION: jpena to chair next meeting (chandankumar, 16:02:03)
Meeting ended at 16:02:47 UTC.
Action Items
------------
* all maintainers are requested to prepare liberty release for their
packages
* apevec send another followup to rdo-list explaining workflow for new
RDO packages
* number80 create package-review component
* jpena to chair next meeting
Action Items, by person
-----------------------
* apevec
* apevec send another followup to rdo-list explaining workflow for
new RDO packages
* jpena
* jpena to chair next meeting
* number80
* number80 create package-review component
* **UNASSIGNED**
* all maintainers are requested to prepare liberty release for their
packages
People Present (lines said)
---------------------------
* chandankumar (87)
* apevec (72)
* number80 (32)
* rbowen (25)
* dmsimard (15)
* zodbot (14)
* elmiko (10)
* jpena (9)
* jruzicka (9)
* eggmaster (6)
* ihrachys (6)
* lon (3)
* xaeth (3)
* kfox1111 (2)
* trown (1)
* dtantsur (1)
* kashyap (1)
* social (1)
* csim (1)
Generated by `MeetBot`_ 0.1.4
.. _`MeetBot`: http://wiki.debian.org/MeetBot
Thanks,
Chandan Kumar
8 years, 8 months
