[rdo-list] [infra] images.rdoproject server cleanup changes
by Gabriele Cerami
Hi,
to allow rdophase2 cache servers to have the time to download the images
for caching purposes, we are stopping the automatic removal of all
previous promoted images at each promotion. We'll change the cleanup
process to delete images after a configurable threshold in days/images
numbers.
This will probably impact the storage space needed, but it's essential
for downstream, even more since now potentially the rhythm of promotions
upstream is going to increase.
Thanks.
7 years
[rdo-list] Where and how should the DLRN API based promotion run?
by Attila Darazs
I want to follow up this conversation from this review:
https://review.rdoproject.org/r/9846
For reference, we're talking about the way we will do promotions based
on DLRN API using this piece of script I called dlrnapi_promoter[1].
> Attila, John, Wes, I'm not convinced we need a dedicated machine
> for this.
> Can we take some time to discuss if a cron on a machine is the
> right approach in the first place ?
>
> I feel there's a lot of different options available but we haven't
> had the opportunity to discuss them.
>
> For example, a jenkins job that would trigger periodically or
> through content change on the DLRN API result pages ? I'm sure we
> could come up with different ideas.
These are the most obvious other options (for me):
1. Make this promotion logic part of DLRN -- I would have preferred this
but didn't see interest in this from Javier or from any of you when I
pitched it a while ago -- probably too late in the design process of the
API. Even the promotion API that we really needed was an afterthought
for DLRN API, so we didn't really cooperate on the design to begin with.
Adding this logic would have been my preference. We should do better
next time.
2. Run this separately but *on* the DLRN server. I couldn't even get a
proper approval for me and Gabriele and Sagi to get submit rights in the
'config' repo after a month[2]. I didn't even try to force this -- seems
like our communication and cooperation is inflexible enough for now to
not try to force this level of cohabitation to save the resources to run
a single VM. I think it makes sense to run this separately.
3. Run this in a zuul job constantly polling: we would use the same
amount of resources as having a dedicated machine, there's no good
reason for doing it.
4. Run this based on some triggers: We want to be able to rerun failed
jobs (RDO Phase1 & Phase2) and have the promotion succeed. We will have
a ton of jobs that would trigger these scripts when they finish and
there's no point in doing it after every single job, time based check
seems to be more useful. If we don't run it after every single job
finishes, it might miss a possible window for promotion.
So in summary, the point of using DLRN API was not relying on random
places changing/triggers/etc. The source of truth should be the DLRN API
for promotion and the most straightforward way to check for results now
is polling.
I wouldn't mind if we eventually integrate this functionality in
DLRN/DLRN API and when the promotion conditions are true, it could
trigger jobs. Though we couldn't trigger stuff on intranet -- polling
there still makes sense, but we could poll some DLRN page for sure.
This script[1] and VM instance is what we have now due to 1) and 2) not
going through. It would be definitely a lot more sane and cheaper
resource and maintenance-wise to do these calculations for promotions in
DLRN API and have DLRN trigger some jobs when they are true for a given
hash, but I didn't feel capable of adding this to DLRN, it was simpler
to use the API as it was designed.
I'm happy to help start integrating this into DLRN, but as of now we
should poll the API, and for polling the most reasonable solution is to
have this on a constantly running machine vs. a long running job that
does polling.
Let me know what you think!
Attila
[1]
https://github.com/rdo-infra/ci-config/tree/master/ci-scripts/dlrnapi_pro...
[2] https://www.redhat.com/archives/rdo-list/2017-September/msg00008.html
7 years
[rdo-list] RDO booth at OpenStack Summit: Help needed
by Rich Bowen
As always, RDO will have a presence within the Red Hat booth at
OpenStack Summit. We will have the usual stuff: ducks, stickers, and
RDO/OpenStack cheatsheet bookmarks.
As you begin to look at the Summit schedule and plan out your days,
please consider spending one or more of your free sessions answering
questions at the RDO booth. We need friendly people who are willing to
answer questions all the way from "What's RDO?" to "I found a bug in
Neutron and need help troubleshooting it."
The schedule is at
https://etherpad.openstack.org/p/rdo-sydney-summit-booth and I'll be
reminding you of it over the coming weeks. The times are (roughly) in
sync with sessions so you should be able to do a shift and make it to
the next session.
Thanks!
--
Rich Bowen: Community Architect
rbowen(a)redhat.com
@rbowen // @RDOCommunity // @CentOSProject
1 859 351 9166
7 years
[rdo-list] Upcoming meetups, October 2, 2017
by Rich Bowen
The following are the meetups I'm aware of in the next two weeks where
OpenStack and/or RDO enthusiasts are likely to be present. If you know
of others, please let me know, and/or add them to
http://rdoproject.org/events
If there's a meetup in your area, please consider attending. If you
attend, please consider taking a few photos, and possibly even writing
up a brief summary of what was covered.
--Rich
* Monday October 02 in Istanbul, TR: Ankara 12. Meetup - Ceph ve OpenStack
- https://www.meetup.com/Turkey-OpenStack-Meetup/events/243543715/
* Tuesday October 03 in Sunnyvale, CA, US: OpenStack Pike Release Update &
Redefining Protection in the Cloud -
https://www.meetup.com/openstack/events/243811056/
* Wednesday October 04 in Prague, CZ: OpenStack - Zkušenosti s
implementacemi a provozem -
https://www.meetup.com/OpenStack-Czech-User-Group-Meetup/events/240756834/
* Wednesday October 04 in Helsinki, FI: OpenStackOperators Finland Video
Call - https://www.meetup.com/OpenStack-Finland-User-Group/events/243462697/
* Saturday October 07 in Littleton, CO, US: OpenStack by David Willson
10-07-2017 - https://www.meetup.com/sofreeus/events/243043418/
* Saturday October 07 in Ha Noi, VN: OpenStack PTG Denver Recap Meetup #16
- VietOpenStack - https://www.meetup.com/VietOpenStack/events/243769562/
* Tuesday October 10 in Sydney, AU: Canberra OpenStack meetup -
https://www.meetup.com/Australian-OpenStack-User-Group/events/243693862/
* Wednesday October 11 in Istanbul, TR: İstanbul 13. Meetup, Konu: Ceph
Yapıtaşları, OpenStack Entegrasyonu -
https://www.meetup.com/Turkey-OpenStack-Meetup/events/243543951/
* Thursday October 12 in San Diego, CA, US: From the Experts: Cloud
Computing - A Panel Discussion -
https://www.meetup.com/OpenStackSanDiego/events/242450015/
* Saturday October 14 in Denver, CO, US: Learn OpenStack -
https://www.meetup.com/it-ntl/events/243488239/
* Saturday October 14 in Bangalore, IN: OpenStack Mini-Conf at OSI Days
India 2017 -
https://www.meetup.com/Indian-OpenStack-User-Group/events/243384587/
* Monday October 16 in Tel Aviv-Yafo, IL: ONAP VNF Onboarding Hack Day -
https://www.meetup.com/OpenStack-Israel/events/243488892/
7 years, 1 month
[rdo-list] Triangle OpenStack Meetup group needs a leader
by Rich Bowen
Hi, folks,
Since I know that a number of you are in or around the Raleigh, RTP area, I
hope that one of you is willing to step up to lead the Triangle OpenStack
Meetup group. The current leader has stepped back, and the group will be
discontinued (ie, the registration on Meetup.com will lapse) in about a
week unless someone is willing to take over.
Please let me know if you're willing to do this, and I'll forward the email
where you can take over.
Thanks!
7 years, 1 month
