[rdo-list] openstack-ec2-api on Pike
by Belmiro Moreira
Hi,
I'm starting to look at RDO packages for Pike and noticed that
openstack-ec2-api
with tag "cloud7-openstack-pike-release" is version 4.1.0.
For Pike shouldn't it be 5.0.1?
thanks,
Belmiro
7 years, 2 months
[rdo-list] [Meeting] RDO meeting (2017-09-06) Minutes
by Javier Pena
==============================
#rdo: RDO meeting - 2017-09-06
==============================
Meeting started by jpena at 15:00:38 UTC. The full logs are available
at
http://eavesdrop.openstack.org/meetings/rdo_meeting___2017_09_06/2017/rdo...
.
Meeting summary
---------------
* roll call (jpena, 15:01:01)
* rdopkg-0.45.0 (jpena, 15:04:38)
* changelog in release commit message:
https://softwarefactory-project.io/r/#/c/9503/1//COMMIT_MSG
(jruzicka, 15:08:14)
* Python 3 support available with python3-rdopkg (jruzicka, 15:08:33)
* Fedora review is ready for approval after 2 years \o/
https://bugzilla.redhat.com/show_bug.cgi?id=1246199 (jruzicka,
15:09:19)
* Defining core contributors policies (jpena, 15:17:43)
* LINK:
https://docs.openstack.org/contributor-guide/docs-review.html#achieving-c...
(PagliaccisCloud, 15:21:48)
* ACTION: hguemar prepare a proposal to define how to become on
individual packages and distro (hguemar, 15:24:00)
* open floor (jpena, 15:26:23)
* Chair for the next meeting (jpena, 15:34:08)
* ACTION: chandankumar to chair the next meeting (jpena, 15:36:47)
Meeting ended at 15:39:05 UTC.
Action items, by person
-----------------------
* chandankumar
* chandankumar to chair the next meeting
* hguemar
* hguemar prepare a proposal to define how to become on individual
packages and distro
People present (lines said)
---------------------------
* hguemar (28)
* jpena (27)
* jruzicka (22)
* chandankumar (16)
* PagliaccisCloud (10)
* openstack (10)
* rdogerrit (2)
* Duck (2)
* rdobot (1)
* dmsimard (1)
* myoung (1)
Generated by `MeetBot`_ 0.1.4
7 years, 2 months
[rdo-list] RDO at the OpenStack PTG
by David Moreau Simard
Hi!
The RDO community project [1] provides RPM OpenStack packages for deploying
on RHEL and CentOS.
RDO is analogous to Ubuntu Cloud Archive (UCA) which provides OpenStack
packages for installing on Ubuntu.
I'm no marketing or sales guy, I'm part of the RDO engineering team in
charge of building, packaging, testing and shipping RDO.
If you happen to be at the PTG and would like to chat about RDO, please let
me know off-thread so we can set aside some time. I'm always excited to
talk with users and operators !
Thanks and see you there !
[1]: http://rdoproject.org
David Moreau Simard
Senior Software Engineer | Openstack RDO
dmsimard = [irc, github, twitter]
7 years, 2 months
[rdo-list] Requesting submit rights for rdoproject.org config & ci-config for Gabriele & Sagi
by Attila Darazs
We're working on the TripleO promotion pipeline and it would be useful
if these two core tripleo-ci/quickstart members could submit changes to
the rdoproject config & ci-config repos
I'd also like to get explicit permission to submit stuff to "config" as
I was previously granted the permission by Alan, but it was only for
experimenting on something else a while ago.
I think our restrictions on these repos could be "only submit if it's
tripleo related".
Please let me know what you think.
Best regards,
Attila
7 years, 2 months
[rdo-list] RPM (minimum version) dependencies (pike)
by iain MacDonnell
Experimenting with upgrading RDO Ocata to Pike in my lab, and have run
into a couple of RPM minimum version dependency issues.
1) neutron-server and agents fail to start, with:
# neutron-server
Guru meditation now registers SIGUSR1 and SIGUSR2 by default for
backward compatibility. SIGUSR1 will no longer be registered in a
future release, so please use SIGUSR2 to generate reports.
Traceback (most recent call last):
File "/usr/bin/neutron-server", line 6, in <module>
from neutron.cmd.eventlet.server import main
File "/usr/lib/python2.7/site-packages/neutron/cmd/eventlet/__init__.py",
line 15, in <module>
eventlet_utils.monkey_patch()
File "/usr/lib/python2.7/site-packages/neutron/common/eventlet_utils.py",
line 25, in monkey_patch
p_c_e = importutils.import_module('pyroute2.config.asyncio')
File "/usr/lib/python2.7/site-packages/oslo_utils/importutils.py",
line 73, in import_module
__import__(import_str)
ImportError: No module named asyncio
I have:
# rpm -q python2-pyroute2
python2-pyroute2-0.4.8-1.el7.noarch
which meets the dependency:
# rpm -qR python-neutron-11.0.0-1.el7.noarch | grep pyroute2
python-pyroute2 >= 0.4.3
but the latest version (in the openstack-pike repo) is 0.4.19 (and
neutron works after explicitly updating to that). Seems that the
"Requires" in python-neutron needs to be bumped up.
2) Horizon fails to start due to https://bugs.launchpad.net/horizon/+bug/1701765
Per comments in that bug, python-XStatic-Bootstrap-SCSS >= 3.3.7.1 is
required., but we have:
# rpm -qR openstack-dashboard-12.0.0-1.el7.noarch | grep SCSS
python-XStatic-Bootstrap-SCSS
So it seems that the minimum version needs to be added to that "Requires".
I can file a bug (or two) on this if it'd be helpful... ?
~iain
7 years, 2 months
[rdo-list] RDO Pike released
by Rich Bowen
The RDO community is pleased to announce the general availability of the
RDO build for OpenStack Pike for RPM-based distributions, CentOS Linux 7
and Red Hat Enterprise Linux. RDO is suitable for building private,
public, and hybrid clouds. Pike is the 16th release from the OpenStack
project, which is the work of more than 2300 contributors from around
the world.
The release is making its way out to the CentOS mirror network, and
should be on your favorite mirror site momentarily.
The RDO community project curates, packages, builds, tests and maintains
a complete OpenStack component set for RHEL and CentOS Linux and is a
member of the CentOS Cloud Infrastructure SIG. The Cloud Infrastructure
SIG focuses on delivering a great user experience for CentOS Linux users
looking to build and maintain their own on-premise, public or hybrid clouds.
All work on RDO, and on the downstream release, Red Hat OpenStack
Platform, is 100% open source, with all code changes going upstream first.
New and Improved
Interesting things in the Pike release include:
* Ironic now supports booting from Cinder volumes, rolling upgrades and
Redfish protocol.
* We added OVN support to Packstack.
* We added support to install the Horizon plugins for several services
in Packstack.
Added/Updated packages
The following packages and services were added or updated in this release:
* Kuryr and Kuryr-kubernetes: an integration between OpenStack and
Kubernetes networking.
* Senlin: a clustering service for OpenStack clouds.
* Shade: a simple client library for interacting with OpenStack clouds,
used by Ansible among others.
* python-pankoclient: a client library for the event storage and REST
API for Ceilometer.
* python-scciclient: a ServerView Common Command Interface Client
Library, for the FUJITSU iRMC S4 - integrated Remote Management Controller.
Other additions include:
Python Libraries
* os-xenapi
* ovsdbapp (deps)
* python-daiquiri (deps)
* python-deprecation (deps)
* python-exabgp
* python-json-logger (deps)
* python-netmiko (deps)
* python-os-traits
* python-paunch
* python-scciclient
* python-scrypt (deps)
* python-sphinxcontrib-actdiag (deps) (pending)
* python-sphinxcontrib-websupport (deps)
* python-stestr (deps)
* python-subunit2sql (deps)
* python-sushy
* shade (SDK)
* update XStatic packages (update)
* update crudini to 0.9 (deps) (update)
* upgrade liberasurecode and pyeclib libraries to 1.5.0 (update) (deps)
Tempest Plugins
* python-barbican-tests-tempest
* python-keystone-testst-tempest
* python-kuryr-tests-tempest
* python-patrole-tests-tempest
* python-vmware-nsx-tests-tempest
* python-watcher-tests-tempest
Puppet-Modules
* puppet-murano
* puppet-veritas_hyperscale
* puppet-vitrage
OpenStack Projects
* kuryr
* kuryr-kubernetes
* openstack-glare
* openstack-panko
* openstack-senlin
* OpenStack Clients
* mistral-lib
* python-glareclient
* python-pankoclient
* python-senlinclient
Contributors
During the Pike cycle, we started the EasyFix initiative, which has
resulted in several new people joining our ranks. These include:
* Christopher Brown
* Anthony Chow
* T. Nicole Williams
* Ricardo Arguello
But, we wouldn't want to overlook anyone. Thank you to all 172
contributors who participated in producing this release:
Aditya Prakash Vaja, Alan Bishop, Alan Pevec, Alex Schultz, Alexander
Stafeyev, Alfredo Moralejo, Andrii Kroshchenko, Anil, Antoni Segura
Puimedon, Arie Bregman, Assaf Muller, Ben Nemec, Bernard Cafarelli,
Bogdan Dobrelya, Brent Eagles, Brian Haley, Carlos Gonçalves, Chandan
Kumar, Christian Schwede, Christopher Brown, Damien Ciabrini, Dan Radez,
Daniel Alvarez, Daniel Farrell, Daniel Mellado, David Moreau Simard,
Derek Higgins, Doug Hellmann, Dougal Matthews, Edu Alcañiz, Eduardo
Gonzalez, Elise Gafford, Emilien Macchi, Eric Harney, Eyal, Feng Pan,
Frederic Lepied, Frederic Lepied, Garth Mollett, Gaël Chamoulaud, Giulio
Fidente, Gorka Eguileor, Hanxi Liu, Harry Rybacki, Honza Pokorny, Ian
Main, Igor Yozhikov, Ihar Hrachyshka, Jakub Libosvar, Jakub Ruzicka,
Janki, Jason E. Rist, Jason Joyce, Javier Peña, Jeffrey Zhang, Jeremy
Liu, Jiří Stránský, Johan Guldmyr, John Eckersberg, John Fulton, John R.
Dennis, Jon Schlueter, Juan Antonio Osorio, Juan Badia Payno, Julie
Pichon, Julien Danjou, Karim Boumedhel, Koki Sanagi, Lars
Kellogg-Stedman, Lee Yarwood, Leif Madsen, Lon Hohberger, Lucas Alvares
Gomes, Luigi Toscano, Luis Tomás, Luke Hinds, Martin André, Martin
Kopec, Martin Mágr, Matt Young, Matthias Runge, Michal Pryc, Michele
Baldessari, Mike Burns, Mike Fedosin, Mohammed Naser, Oliver Walsh,
Parag Nemade, Paul Belanger, Petr Kovar, Pradeep Kilambi, Rabi Mishra,
Radomir Dopieralski, Raoul Scarazzini, Ricardo Arguello, Ricardo
Noriega, Rob Crittenden, Russell Bryant, Ryan Brady, Ryan Hallisey,
Sarath Kumar, Spyros Trigazis, Stephen Finucane, Steve Baker, Steve
Gordon, Steven Hardy, Suraj Narwade, Sven Anderson, T. Nichole Williams,
Telles Nóbrega, Terry Wilson, Thierry Vignaud, Thomas Hervé, Thomas
Morin, Tim Rozet, Tom Barron, Tony Breeds, Tristan Cacqueray, afazekas,
danpawlik, dnyanmpawar, hamzy, inarotzk, j-zimnowoda, kamleshp, marios,
mdbooth, michaelhenkel, mkolesni, numansiddique, pawarsandeepu,
prateek1192, ratailor, shreshtha90, vakwetu, vtas-hyperscale-ci, yrobla,
zhangguoqing, Vladislav Odintsov, Xin Wu, XueFengLiu, Yatin Karel,
Yedidyah Bar David, adriano petrich, bcrochet, changzhi, diana, djipko,
dprince, dtantsur, eggmaster, eglynn, elmiko, flaper87, gpocentek,
gregswift, hguemar, jason guiditta, jprovaznik, mangelajo, marcosflobo,
morsik, nmagnezi, sahid, sileht, slagle, trown, vkmc, wes hayutin,
xbezdick, zaitcev, and zaneb.
Getting Started
There are three ways to get started with RDO.
To spin up a proof of concept cloud, quickly, and on limited hardware,
try an All-In-One Packstack installation. You can run RDO on a single
node to get a feel for how it works.
https://www.rdoproject.org/install/packstack/
For a production deployment of RDO, use the TripleO Quickstart and
you'll be running a production cloud in short order.
https://www.rdoproject.org/tripleo/
Finally, if you want to try out OpenStack, but don't have the time or
hardware to run it yourself, visit TryStack, where you can use a free
public OpenStack instance, running RDO packages, to experiment with the
OpenStack management interface and API, launch instances, configure
networks, and generally familiarize yourself with OpenStack. (TryStack
is not, at this time, running Pike, although it is running RDO.)
http://packstack.org/
Getting Help
The RDO Project participates in a Q&A service at ask.openstack.org, for
more developer-oriented content we recommend joining the rdo-list
mailing list. Remember to post a brief introduction about yourself and
your RDO story. You can also find extensive documentation on the RDO
docs site.
The #rdo channel on Freenode IRC is also an excellent place to find help
and give help.
We also welcome comments and requests on the CentOS mailing lists and
the CentOS and TripleO IRC channels (#centos, #centos-devel, and
#tripleo on irc.freenode.net), however we have a more focused audience
in the RDO venues.
Getting Involved
To get involved in the OpenStack RPM packaging effort, see the RDO
community pages and the CentOS Cloud SIG page. See also the RDO
packaging documentation.
Join us in #rdo on the Freenode IRC network, and follow us at
@RDOCommunity on Twitter. If you prefer Facebook, we're there tooi (
http://facebook.com/RDOCommunity ), and also Google+ (
http://tm3.org/rdogplus )
7 years, 2 months
