[rdo-list] Error While Installing Openstack Newton using RDO packstack
by Pradeep Antil
Hi Folks ,
I am trying to install 3 node openstack newton on CentOS 7 using packstack.
But getting below error. In the answer file i have mentioned that packstack
script will create selfsign certificate at the mentioned location.
Preparing Nova VNC Proxy entries [ ERROR ]
ERROR : [Errno 2] No such file or directory:
'/etc/pki/tls/certs/selfcert.crt'
~]# tail -f /var/tmp/packstack/20161008-104443-u_wbaC/openstack-setup.log
File "/usr/lib/python2.7/site-packages/packstack/modules/ospluginutils.py",
line 101, in generate_ssl_cert ca_file =
open(config['CONFIG_SSL_CACERT_FILE'], 'rt').read() IOError: [Errno 2] No
such file or directory: '/etc/pki/tls/certs/selfcert.crt'
2016-10-08 10:56:33::INFO::shell::94::root:: [192.168.43.70] Executing
script: rm -rf /var/tmp/packstack/8a47dc48454c40a0a8c7856728604812
2016-10-08 10:56:34::INFO::shell::94::root:: [192.168.43.80] Executing
script: rm -rf /var/tmp/packstack/844988cf4be74a6cb5b95a22c7eab220
2016-10-08 10:56:34::INFO::shell::94::root:: [192.168.43.90] Executing
script: rm -rf /var/tmp/packstack/d2e704b6b353457aac455dca91efc2d6
Any idea how to resolve this issue so that i can latest version of
openstack. It also seems to be a bug in the script.
--
Best Regards
Pradeep Kumar
8 years, 3 months
[rdo-list] Maintaining os-*-config in Fedora
by James Slagle
os-*-config (apply, cloud, collect, refresh, net) are still maintained in
Fedora (despite that the maintainers, myself included, have not been doing
regular builds).
I've been asked by a couple people from Fedora to update these packages to
build python 3 packages, and some other things like removing outdated Requires
on python libraries that are now in the stdlib (argparse, etc).
This raised the question for me though if we still want to maintain these
packages in Fedora at all. Aiui, they were not retired when the rest of the
core OpenStack packages were retired because os-*-config is useful when using
Fedora as an instance orchestarted via Heat on OpenStack.
However, we haven't been properly maintaining these packages in Fedora by doing
updated builds to pick up new releases, not to mention that these packages and
use case are entirely untested on Fedora to the best of my knowledge.
os-cloud-config I think we can retire from Fedora without any concern since it
is specific to TripleO.
For the others, is there anyone who wants to take them over to continue to work
on the "Fedora as an instance orchestrated via Heat" use case? If not, I
propose to retire the others as well.
Note that diskimage-builder and dib-utls are also still in Fedora but it
appears that pabelanger has been keeping those updated, so is likely using
them.
--
-- James Slagle
--
8 years, 3 months
Re: [rdo-list] No maintainer for networking-arista
by Ihar Hrachyshka
Hi Sukhdev,
I think designating another interested maintainer for the package that
would take it over and help solve RDO folks any integration issues with the
package will be enough.
Ihar
Sukhdev Kapur <sukhdev(a)arista.com> wrote:
> Hey Ihar,
> We obviously would not want networking-arista be dropped from RDO. What
> do you suggest we do to ensure this package does not get dropped?
>
> Regards
> Sukhdev
>
>
>> On Oct 5, 2016, at 5:05 AM, Ihar Hrachyshka <ihrachys(a)redhat.com> wrote:
>>
>> Hi all,
>>
>> current maintainers for the package (me and Miguel) want to step down.
>> Unless someone replaces us, or give us a reason to keep maintaining the
>> package, we may need to drop it from RDO.
>>
>> Anyone interested in keeping it available?
>> Ihar
8 years, 3 months
[rdo-list] Third party DLRN CI and the need for a "-head" builder
by David Moreau Simard
Hi,
So with the help of Paul Belanger, we've identified the issue that
prevented the "openstack-check-verified" pipeline from working.
The Zuul openstack-check-verified pipeline [1] from
review.rdoproject.org can be used to trigger builds on upstream
projects on each patchset, only when Jenkins has +1'd it.
The goal with this pipeline is to do third party CI with DLRN in order
to try and build projects' patches to warn us for failure to build
errors ahead of time, even before the change merges.
We're not planning on voting on the Gerrit changes, it's solely to
check if there are any issues building the project with that
particular patch.
So we really have two Ocata DLRN instances now, one that is pinned to
upper-constraints [2] and one that builds the "master of everything"
[3].
I was thinking... If we're able to do third party CI against upstream
with DLRN do we need that "head" instance ?
The "head" instance exists, as far as I know, to let us know if
anything from unpinned projects fails to build.
The third party CI will let us know that -- and even before, ahead of
time, before the change causing the failure even merges.
Thoughts ?
[1]: https://review.rdoproject.org/r/gitweb?p=config.git;a=blob;f=zuul/upstrea...
[2]: https://trunk.rdoproject.org/centos7-master/
[3]: https://trunk.rdoproject.org/centos7-master-head/
David Moreau Simard
Senior Software Engineer | Openstack RDO
dmsimard = [irc, github, twitter]
8 years, 3 months
[rdo-list] [release] RDO Newton packages released
by Alan Pevec
The RDO community is pleased to announce the general availability of
the RDO build for OpenStack Newton for RPM-based distributions -
CentOS Linux 7 and Red Hat Enterprise Linux. RDO is suitable for
building private, public, and hybrid clouds. Newton is the 14th
release from the OpenStack project ( http://openstack.org ), which is
the work of more than 2700 contributors from around the world.
(Source http://stackalytics.com/ )
The RDO community project ( https://www.rdoproject.org/ ) 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 (
https://wiki.centos.org/SpecialInterestGroup/Cloud ). 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. At latest count, RDO contains 1157 packages (
https://www.rdoproject.org/documentation/package-list/ ).
All work on RDO, and on the downstream release, Red Hat OpenStack
Platform, is 100% open source, with all code changes going upstream
first.
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 the RDO QuickStart ( http://rdoproject.org/Quickstart ) You can
run RDO on a single node to get a feel for how it works.
For a production deployment of RDO, use the TripleO Quickstart (
https://www.rdoproject.org/tripleo/ ) and you'll be running a
production cloud in short order.
Finally, if you want to try out OpenStack, but don't have the time or
hardware to run it yourself, visit TryStack ( http://trystack.org/ ),
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
Getting Help
The RDO Project participates in a Q&A service at ask.openstack.org (
http://ask.openstack.org ), for more developer oriented content we
recommend joining the rdo-list mailing list (
https://www.redhat.com/mailman/listinfo/rdo-list ). Remember to post a
brief introduction about yourself and your RDO story. You can also
find extensive documentation on the RDO docs site (
https://www.rdoproject.org/documentation ).
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 (
https://lists.centos.org/ ) and the CentOS IRC Channels (#centos, and
#centos-devel, 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 ( https://www.rdoproject.org/community/ ) and the
CentOS Cloud SIG page (
https://wiki.centos.org/SpecialInterestGroup/Cloud ). See also the RDO
packaging documentation ( https://www.rdoproject.org/packaging/ ).
Join us in #rdo on the Freenode IRC network, and follow us at
@RDOCommunity ( http://twitter.com/rdocommunity ) on Twitter. If you
prefer Facebook, we're there too ( http://facebook.com/rdocommunity ),
and also Google+ ( http://tm3.org/rdogplus ).
And, if you're going to be in Barcelona for the OpenStack Summit (
http://openstack.org/summit/ ) two weeks from now, join us on Tuesday
evening at the Barcelona Princess, 5pm - 8pm, for an evening with the
RDO and Ceph communities. If you can't make it in person, we'll be
streaming it on YouTube ( https://www.youtube.com/watch?v=ji-WqEXZRTY
).
Cheers,
Alan
8 years, 3 months
[rdo-list] [Meeting] RDO meeting (2016-10-05) Minutes
by Javier Pena
==============================
#rdo: RDO meeting - 2016-10-05
==============================
Meeting started by jpena at 15:00:53 UTC. The full logs are available at
https://meetbot.fedoraproject.org/rdo/2016-10-05/rdo_meeting_-_2016-10-05...
.
Meeting summary
---------------
* roll call (jpena, 15:01:27)
* DLRN Ocata branch (jpena, 15:04:27)
* LINK:
http://logs.openstack.org/51/382351/2/check/gate-puppet-openstack-integra...
(EmilienM, 15:07:23)
* LINK:
https://github.com/openstack/instack-undercloud/commits/stable/newton
(trown, 15:25:37)
* ACTION: trown submit test patch to tripleo-ci to test ocata repo
(trown, 15:38:43)
* ACTION: jpena to move centos-master to ocata worker as soon as
tripleo-ci and puppet ci jobs are ok (jpena, 15:39:03)
* Preparation for CentOS outage October 10th (jpena, 15:41:41)
* no new packages built by DLRN during the CentOS outage (jpena,
15:46:15)
* Preparation for RCIP-DEV move October 17th (jpena, 15:49:14)
* GA rebuilds tomorrow (jpena, 15:50:34)
* LINK:
https://git.openstack.org/cgit/openstack/puppet-heat/commit/?h=9.4.1&id=7...
is in there (trown, 15:53:03)
* ACTION: apevec to make sure puppet 9.4.1 are in newton-testing
(apevec, 15:54:15)
* Newton GA test day Oct 13/14 -
https://www.rdoproject.org/testday/newton/final/ (jpena, 15:57:52)
* Announcements (jpena, 15:59:56)
* chair for next meeting (jpena, 16:00:55)
* ACTION: jruzicka to chair next meeting (jpena, 16:01:54)
Meeting ended at 16:02:13 UTC.
Action Items
------------
* trown submit test patch to tripleo-ci to test ocata repo
* jpena to move centos-master to ocata worker as soon as tripleo-ci and
puppet ci jobs are ok
* apevec to make sure puppet 9.4.1 are in newton-testing
* jruzicka to chair next meeting
Action Items, by person
-----------------------
* apevec
* apevec to make sure puppet 9.4.1 are in newton-testing
* jpena
* jpena to move centos-master to ocata worker as soon as tripleo-ci
and puppet ci jobs are ok
* jruzicka
* jruzicka to chair next meeting
* trown
* trown submit test patch to tripleo-ci to test ocata repo
* **UNASSIGNED**
* (none)
People Present (lines said)
---------------------------
* apevec (62)
* jpena (62)
* EmilienM (51)
* dmsimard (46)
* trown (44)
* ihrachys (18)
* rbowen (14)
* rdogerrit (10)
* zodbot (9)
* jruzicka (6)
* jschlueter (6)
* weshay (5)
* flepied (3)
* openstack (3)
* amoralej (3)
* Duck (3)
* coolsvap (2)
* number80 (2)
* tosky (1)
* rdobot (1)
* imcsk8 (1)
* mburned (1)
* f0o (1)
Generated by `MeetBot`_ 0.1.4
.. _`MeetBot`: http://wiki.debian.org/MeetBot
8 years, 3 months
