Over the last couple of months, it has become apparent that the process
for releasing new versions of the two TripleO UI RPMs
(openstack-tripleo-ui and openstack-tripleo-ui-deps) relies on manual
work done by humans. As a result, making changes to the specs of the
said RPMs takes a long time, and causes delays in upstream CI.
>From my point of view (read: I'm not familiar with the finer details of
the inner workings of RDO), there are three manual tasks that need to be
performed when a change to a spec is required (most often it's a new
1. Licensing review
Obviously this step cannot be done by machines. It has been suggested
to us that it would simplify things for reviewers if we included
transient dependency diffs as well --- we plan to do that going forward.
2. openstack-tripleo-ui-deps PR merge
This step also cannot be done by machines. However, we could streamline
this work by handling the reviewing and merging by using the RDO Gerrit
instead of GitHub. I suspect that reviewers will be more likely to
review these kinds of patches faster than by having to go to GitHub
given that many of the other RDO projects are handled by Gerrit.
3. Rebuilding RPM and publishing it
This step is the most opaque to the TripleO UI team. Usually, we have
to ask someone on IRC to rebuild the package. Then, it seems to be
published in two different places: CBS, which I understand to be a
staging environment of some kind, and the other place is unknown to me
but it's the place where the upstream CI can pick it up. I have
repeatedly asked to gain to some read-only access to the progress of
these builds but have received none. In order to speed up this work, I
would love to see some more automation of the build process, and more
visibility of the progress.
It's very likely that my understanding of the problem is misguided, and
I very much welcome your correction! If you have suggestions on how the
TripleO UI team can make RDO's life easier, I'm all ears.
Hi all -
doing a tripleo-quickstart, the delorean repo is returning a 403 for
openstack-tripleo-ui, which it is looking for when it installs the
undercloud. Not sure if I'm missing something or working with a stale
repo or what, though this is fresh tripleo-quickstart from today,
referred to by config/release/newton.yml, and the repo claims it has
this package and then reports 403 for just the one package. The repo is:
[stack@undercloud ~]$ cat /etc/yum.repos.d/delorean.repo
trying a manual install shows that it sees it but can't install (I did a
yum clear cache also, but again this is from the undercloud image at
. Hitting the directory listing shows all the other packages there
and other directory listings under different hashes also show
See yum output below, not sure if I'm just missing something silly.
[stack@undercloud ~]$ sudo yum install openstack-tripleo-ui
Loaded plugins: fastestmirror, priorities
Loading mirror speeds from cached hostfile
* base: mirrors.centos.webair.com
* extras: mirrors.cmich.edu
* updates: mirrors.tripadvisor.com
644 packages excluded due to repository priority protections
--> Running transaction check
---> Package openstack-tripleo-ui.noarch
0:1.1.0-0.20170201184830.36b0b58.el7.centos will be installed
--> Finished Dependency Resolution
delorean 2.4 M
Install 1 Package
Total download size: 2.4 M
Installed size: 11 M
Is this ok [y/d/N]: y
Delta RPMs disabled because /usr/bin/applydeltarpm not installed.
: [Errno 14] HTTPS Error 403 - Forbidden
Trying other mirror.
To address this issue please refer to the below knowledge base article
If above article doesn't help to resolve this issue please create a bug
Error downloading packages:
[Errno 256] No more mirrors to try.
In case any of you are anywhere near Seoul, they're looking for speakers.
-------- Forwarded Message --------
Subject: [openstack-community] OpenStack Days Korea 2017 is looking for
Sponsors and Speakers
Date: Mon, 17 Apr 2017 21:57:37 -0700
From: Jaesuk Ahn <bluejay.ahn(a)gmail.com>
To: community(a)lists.openstack.org <community(a)lists.openstack.org>,
CC: Nalee Jang <nalee999(a)gmail.com>
Dear OpenStack Community Members,
OpenStack Korea User Group is excited to announce that OpenStack Days
Korea 2017 will be in Seoul, Korea, for two days (July 13^th and July
The two day event will have a focus on what is coming “NEXT” for
OpenStack, including containerization, DevOps practices, orchestration,
operations, software defined storage and network, AI infrastructure, and
This is the forth OpenStack Days Korea event since 2014. Each three
previous events had a huge success and attracted lots of interest among
IT expert, engineers, developers and Executives. The OpenStack Days
Korea is certainly one of the biggest Open Source Technology event in
The event will be held at Jamsil Lotte Hotel World (the first day) and
COEX (the second day). In order to successfully execute this event, we
will need your help on both sponsoring and participating the event.
In the above event webpage, you will find link for both “Sponsorship”
and “Call for Speakers”. Please kindly review and consider it, and get
back to us. If you have any question, you can contact one of organizers
in OpenStack Days Korea 2017 event stated at the end of this email. In
addition, if you are interested in speaking at the event, please fill
the form at “Call for Speakers” link.
Thank you very much in advance, and we look forward to working with you.
User Group Leader – Ian Y. Choi (ianyrchoi(a)gmail.com)
Program Chair – Jaesuk Ahn (bluejay.ahn(a)gmail.com)
Event Organizing Chair – Jungwon Ku (jwon.ku(a)gmail.com)
Please note that we've currently taken the Jenkins public interface
offline as we evaluate the Jenkins security advisory that came out
Jobs will still run as usual but the Jenkins console will not be available.
If you're in a bind or have an urgent need to look at review logs,
please ping me (dmsimard) on #rdo.
David Moreau Simard
Senior Software Engineer | Openstack RDO
dmsimard = [irc, github, twitter]
It is the reminder email.
Our next RDO community weekly meeting is scheduled on 26th Apr 2017,
1500 UTC at #rdo channel on Freenode server.
What happened in Last RDO community meeting [2017-04-19]?
* RDO Test days prepration updates:
-> promote current-passed-ci and current-tripleo-rdo to
-> update image symlinks to point to
* Call for testing of DLRN API testing
* RDO Pike Milestone testday happened on April 20, 21 , 2017
What exciting things coming in upcoming meeting [2017-04-26]?
* Separate module name suggestion for moving rdoinfo parser from
rdoinfo/rdopkg into a separate module
* upstream openstack/rpm-packaging spec templates
* Tempest-16.0.0 tag update in RDO
Feel free to add your meeting agenda to the etherpad:
https://etherpad.openstack.org/p/RDO-Meeting So we can make RDO
meeting more awesome.
Dear RDO Enthusiast,
We have some important news this week about what’s shifting in the RDO
As you may know, Rich Bowen has been serving in the role of Community
Liaison for the last 4 years. In that capacity, he’s done a variety of
things for the community, including event coordination, social media,
podcasts and videos, managing the website, and so on.
Starting next week, this role is going to include Rain Leander as
TripleO Community Liaison. Rain has been working with the RDO community,
and, more generally, with Red Hat’s upstream OpenStack development
efforts, for the past 18 months. She’s helped out at a number of events,
including two OpenStack Summits, numerous OpenStack Days and Meetups.
And she’s been a passionate advocate of TripleO in the community at large.
You may have seen her at some of these events and you’ve probably seen
her on IRC as leanderthal. Please give her all the support that you’ve
given Rich as she moves into this role.
If you have any questions about how this is going to work, what Rain’s
priorities will be in the coming months, or concerns about getting stuff
done in the next few months, please don’t hesitate to contact either one
of us via email (rain(a)redhat.com and rbowen(a)redhat.com), on IRC
(leanderthal and rbowen) or via Twitter (@rainleander and @rbowen).
Rich Bowen and Rain Leander