Hi,
We are planning to run a patch maintenance on dlrn-db.rdoproject.org on
Tuesday, November 21 at 9:00 UTC. The maintenance is expected to last for
approximately 1 hour.
During this maintenance, no new packages will be built and any call to the DLRN
API will fail.
Please do not hesitate to
> Hi,
>
> We are planning to run a patch maintenance on dlrn-db.rdoproject.org on
> Tuesday, November 21 at 9:00 UTC. The maintenance is expected to last for
> approximately 1 hour.
>
> During this maintenance, no new packages will be built and any call to the
> DLRN API will fail.
>
Hi,
The m
==
#rdo: RDO meeting - 2017-11-22
==
Meeting started by jpena at 15:00:21 UTC. The full logs are available
at
http://eavesdrop.openstack.org/meetings/rdo_meeting___2017_11_22/2017/rdo_meeting___2017_11_22.2017-11-22-15.00.log.html
.
Meet
Hi all,
We are planning to run a patch maintenance on images.rdoproject.org on Tuesday,
November 28 at 9:00 UTC. The maintenance is expected to last for approximately
1 hour.
During this maintenance, any CI job fetching or uploading images may fail.
Please do not hesitate to contact us if you
Hi all,
The maintenance has finished. If you find any issue, please do not hesitate to
contact us.
Regards,
Javier
- Original Message -
> Hi all,
>
> We are planning to run a patch maintenance on images.rdoproject.org on
> Tuesday, November 28 at 9:00 UTC. The maintenance is expected t
- Original Message -
> Hi all,
>
> we as a community last discussed RDO definition of done more than a
> year ago and it was documented[1]
>
> In the meantime we have multiple changes in the RDO promotion
> process, most significant is that we do not run all the CI promotion
> jobs in
Hi all,
We are planning to run a patch maintenance on master.monitoring.rdoproject.org
on Thursday, November 30 at 9:00 UTC. The maintenance is expected to last for
approximately 1 hour.
No direct impact is expected, other than the lack of monitoring (or a spammy
rdobot in a worst case).
Plea
> Hi all,
>
> We are planning to run a patch maintenance on
> master.monitoring.rdoproject.org on Thursday, November 30 at 9:00 UTC. The
> maintenance is expected to last for approximately 1 hour.
>
> No direct impact is expected, other than the lack of monitoring (or a spammy
> rdobot in a worst
Hi all,
We had another nodepool outage this morning. Around 9:00 UTC, amoralej noticed
that no new jobs were being processed. He restarted nodepool, and I helped him
later with some stale node cleanup. Nodepool started creating VMs successfully
around 10:00 UTC.
On a first look at the logs, we
- Original Message -
> On Sat, Dec 02, 2017 at 01:57:08PM +0100, Alfredo Moralejo Alonso wrote:
> > On Sat, Dec 2, 2017 at 11:56 AM, Javier Pena wrote:
> >
> > > Hi all,
> > >
> > > We had another nodepool outage this morning. Around 9:00 UT
- Original Message -
> On December 3, 2017 9:27 pm, Paul Belanger wrote:
> [snip]
> > Please reach out to me the next time you restart it, something is seriously
> > wrong is we have to keep restarting nodepool every few days.
> > At this rate, I would even leave nodepool-launcher is the
> Hi RDO developers,
>
> After installing watcher Ocata version by install document[1],
> I tried to install python-watcherclient.
>
> But the package was not found. I found other Openstack project
> clients such as neutron.
>
> Is there any special reason not to package python-watcherclient?
>
Hi all,
The RDO Cloud is being upgraded. As a result, we can expect outages in multiple
RDO Infra services to happen until the upgrade is finished. For example,
currently nodepool is failing to create new VMs, so CI jobs are being delayed.
We are in contact with the RDO Cloud team, and will wor
> Hi all,
>
> The RDO Cloud is being upgraded. As a result, we can expect outages in
> multiple RDO Infra services to happen until the upgrade is finished. For
> example, currently nodepool is failing to create new VMs, so CI jobs are
> being delayed.
>
Hi all,
The RDO Cloud upgrade is still on
Hi,
The RDO Cloud is now going through its major upgrade. This may also impact our
CI jobs and most of our infrastructure services, please stay tuned for updates.
As a preventive measure, we have stopped builds on the RDO Trunk server (DLRN).
We will work with the RDO Cloud to ensure services a
> Hi,
>
> The RDO Cloud is now going through its major upgrade. This may also impact
> our CI jobs and most of our infrastructure services, please stay tuned for
> updates.
>
> As a preventive measure, we have stopped builds on the RDO Trunk server
> (DLRN). We will work with the RDO Cloud to en
- Original Message -
> On 10 January 2018 at 14:41, Assaf Muller wrote:
> > On Wed, Jan 10, 2018 at 8:10 AM, Alan Pevec wrote:
> >> Hi Bernard,
> >>
> >> I've added this as a topic for the
> >> https://etherpad.openstack.org/p/RDO-Meeting today,
> >> with some initial questions to explo
- Original Message -
> On Wed, Jan 10, 2018 at 7:50 PM, Javier Pena wrote:
> > If we want to deliver via RPM and build on each Octavia change, we could
> > try to add it to the octavia spec and build it using DLRN. Does the script
> > require many external resour
> Greetings,
>
> As discussed in the RDO meeting today, I am proposing rlandy as core for [1].
> I'm not 100% sure how the access is divided up so I'm specifying the repo
> itself. Ronelle has proven herself to be a quality reviewer and her
> submissions are also up to the standards of core.
>
> Th
Hello,
We are going to update the RDO Trunk builders to the latest DLRN version on
January 30th, starting at 9:00 AM UTC.
The update is expected to last for one hour, and no packages will be built
during that time. RDO Trunk repos and the DLRN API will remain accessible.
If you have any questi
, storing images in a new path under
images.rdoproject.org.
Regards,
Javier
>
> [0] https://review.openstack.org/#/c/522626/
>
> On 12 January 2018 at 13:05, Bernard Cafarelli wrote:
> > On 11 January 2018 at 11:53, Javier Pena wrote:
> >> - Original Message
==
#rdo: RDO meeting - 2018-01-31
==
Meeting started by jpena at 15:01:19 UTC. The full logs are available
at
http://eavesdrop.openstack.org/meetings/rdo_meeting___2018_01_31/2018/rdo_meeting___2018_01_31.2018-01-31-15.01.log.html
.
Meet
s used in gate jobs, we will have to
revisit the concept and make sure we add some tests before publishing an image.
Now it is time to implement it. All help is welcome :).
Regards,
Javier
[1] - https://lists.rdoproject.org/pipermail/dev/2018-January/008521.html
> Regards,
> Javier
>
>
> >
&
- Original Message -
> Hi,
>
> We're currently a bit behind in terms of trunk repository promotions
> for the m3 queens milestone.
> We are not very confident that we can get all the issues sorted out in
> time for the test day so I would like to suggest we push the test days
> next week
Hi,
I see no issues in nodepool. Looking at the current Zuul queue, we have a
single job stuck for ~90 hours, queued on
"gate-tripleo-ci-centos-7-ovb-3ctlr_1comp-featureset035-queens".
When that happens, it's usually a configuration issue, and this is the case
here: we have no definition for t
- Original Message -
> On 02/15/2018 04:40 PM, Michael Turek wrote:
> > Hey all,
> >
> > I'll be attending the Dublin PTG and was wondering if anyone would be
> > interested in a birds of a feather lunch around RDO. Specifically I'd
> > like to talk about RDO CI for Power but I'm open to
Hi all,
Today at about 16:20 UTC we had to restart zuul-server on
review.rdoproject.org. The RDO Cloud had a network outage, and that was
affecting Zuul, which was not queueing new changes to be reviewed.
All queued changes have been restored. However, if you sent a change for review
between 1
==
#rdo: RDO meeting - 2018-02-21
==
Meeting started by jpena at 15:00:15 UTC. The full logs are available
at
http://eavesdrop.openstack.org/meetings/rdo_meeting___2018_02_21/2018/rdo_meeting___2018_02_21.2018-02-21-15.00.log.html
.
Meet
Hi all,
We've had to restart Gerrit on review.rdoproject.org a couple times, due to a
repository synchronization issue with GitHub.
GitHub has disabled some crypto standards from SSH [1], and that broke the jsch
[2] library version embedded with review.rdo's Gerrit. As a workaround, we have
up
==
#rdo: RDO meeting - 2018-04-11
==
Meeting started by jpena at 15:00:40 UTC. The full logs are available
at
http://eavesdrop.openstack.org/meetings/rdo_meeting___2018_04_11/2018/rdo_meeting___2018_04_11.2018-04-11-15.00.log.html
.
Meet
- Original Message -
> On Sat, Apr 14, 2018 at 3:07 AM, Alan Pevec wrote:
> >> - Tristan Cacqueray (tristanC)
> >> - Nicolas Hicher (nhicher)
> >> - Fabien Boucher (fbo)
> >> - Matthieu Huin (mhu)
>
> +1 to all :-)
>
I already voted in the review, but of course, +1 to all.
Cheers,
Ja
Hi all,
We are planning to do some routine maintenance activities of the DLRN version
in our RDO Trunk builders on April 24th.
These activities will not affect the RDO Trunk repos, they could only cause a
short delay in a package being built after a commit is merged upstream.
If you have any
==
#rdo: RDO meeting - 2018-05-16
==
Meeting started by jpena at 15:06:39 UTC. The full logs are available
at
http://eavesdrop.openstack.org/meetings/rdo_meeting___2018_05_16/2018/rdo_meeting___2018_05_16.2018-05-16-15.06.log.html
.
Meet
Dear all,
We will run a routine patch update procedure on the RDO Trunk infrastructure
(trunk.rdoproject.org and associated servers) tomorrow, June 19th, at 9:00 UTC.
During this maintenance, expected to last for 1h, the RDO Trunk repositories
will be available as usual, with a small interrupti
- Original Message -
> Dear all,
>
> We will run a routine patch update procedure on the RDO Trunk infrastructure
> (trunk.rdoproject.org and associated servers) tomorrow, June 19th, at 9:00
> UTC.
>
> During this maintenance, expected to last for 1h, the RDO Trunk repositories
> will b
Dear all,
We will run a routine patch update procedure on logs.rdoproject.org and
afs-mirror.rdoproject.org tomorrow, June 26th, at 9:00 UTC.
During this maintenance, expected to last for 1h, there might be short
interruptions to jobs using those resources (any job running on
review.rdoproject
- Original Message -
> On Mon, Jun 25, 2018 at 04:30:27AM -0400, Javier Pena wrote:
> > Dear all,
> >
> > We will run a routine patch update procedure on logs.rdoproject.org and
> > afs-mirror.rdoproject.org tomorrow, June 26th, at 9:00 UTC.
> >
>
- Original Message -
>
>
> - Original Message -
> > On Mon, Jun 25, 2018 at 04:30:27AM -0400, Javier Pena wrote:
> > > Dear all,
> > >
> > > We will run a routine patch update procedure on logs.rdoproject.org and
> > > afs
#rdo: RDO meeting 2018-06-27
Meeting started by jpena at 15:00:59 UTC. The full logs are available
at
http://eavesdrop.openstack.org/meetings/rdo_meeting_2018_06_27/2018/rdo_meeting_2018_06_27.2018-06-27-15.00.log.html
.
Meeting summar
Hi,
Sometimes we want to know how many packages are processed by our RDO Trunk
infrastructure, for statistical purposes or just because we want to brag about
it in some presentation :).
After an initial idea from dmsimard, we have extended the DLRN API and
connected that to Grafana, so now we
==
#rdo: RDO meeting - 2018-08-08
==
Meeting started by jpena at 15:03:47 UTC. The full logs are available
at
http://eavesdrop.openstack.org/meetings/rdo_meeting___2018_08_08/2018/rdo_meeting___2018_08_08.2018-08-08-15.03.log.html
.
Meet
>
> Hi,
>
> As part of the preparation tasks for Rocky GA we have created a new RDO Trunk
> repository centos7-rocky which follows stable/rocky branches.
>
> This repo is now consistent and is available in
> http://trunk.rdoproject.org/centos7-rocky-bootstrap but today, we will be
> moving it to ht
- Original Message -
> Hey all,
>
> I've been working alongside Mike Turek to try to get Triple O containers
> building on ppc64le. We're currently hung up on the
> python-octavia-tests-tempest-golang package from the delorean repo. If
> you go take a look at the repo itself [1], you'll
==
#rdo: RDO meeting - 2018-08-29
==
Meeting started by jpena at 15:01:17 UTC. The full logs are available
at
http://eavesdrop.openstack.org/meetings/rdo_meeting___2018_08_29/2018/rdo_meeting___2018_08_29.2018-08-29-15.01.log.html
.
Meet
Hi all,
As you're probably aware, there is an OpenStack rpm-packaging project [1],
where the RDO community has been collaborating with people from other rpm-based
distributions. We have been successful in reusing some tools created by that
project [2][3], but we've never been able to reuse the
==
#rdo: RDO meeting - 2018-09-12
==
Meeting started by jpena at 15:01:18 UTC. The full logs are available
at
http://eavesdrop.openstack.org/meetings/rdo_meeting___2018_09_12/2018/rdo_meeting___2018_09_12.2018-09-12-15.01.log.html
.
Meet
==
#rdo: RDO meeting - 2018-09-19
==
Meeting started by jpena at 15:02:05 UTC. The full logs are available
at
http://eavesdrop.openstack.org/meetings/rdo_meeting___2018_09_19/2018/rdo_meeting___2018_09_19.2018-09-19-15.02.log.html
.
Meet
Hi all,
We need to renew the RDO Registry SSL certificate. The process to do so is
automated, but slightly more complex than the usual for an Apache web server.
We will renew the certificate next Monday, October 1st. The estimated downtime
is very short (< 10 minutes), but just take it into acc
==
#rdo: RDO meeting - 2018-10-17
==
Meeting started by jpena at 15:00:26 UTC. The full logs are available
at
http://eavesdrop.openstack.org/meetings/rdo_meeting___2018_10_17/2018/rdo_meeting___2018_10_17.2018-10-17-15.00.log.html
.
Meet
==
#rdo: RDO meeting - 2018-11-21
==
Meeting started by jpena at 15:01:05 UTC. The full logs are available
at
http://eavesdrop.openstack.org/meetings/rdo_meeting___2018_11_21/2018/rdo_meeting___2018_11_21.2018-11-21-15.01.log.html
.
Meet
Hi,
We are going to update the DLRN code used by RDO Trunk builders on December 11,
to fix some recurring issues. The update process should be transparent, and you
could only notice a delay in new packages being built.
If you have any questions or concerns, please do not hesitate to contact me.
- Original Message -
> Hi,
>
> We are going to update the DLRN code used by RDO Trunk builders on December
> 11, to fix some recurring issues. The update process should be transparent,
> and you could only notice a delay in new packages being built.
>
> If you have any questions or con
==
#rdo: RDO meeting - 2019-01-23
==
Meeting started by jpena at 15:03:00 UTC. The full logs are available
at
http://eavesdrop.openstack.org/meetings/rdo_meeting___2019_01_23/2019/rdo_meeting___2019_01_23.2019-01-23-15.03.log.html
.
Meet
==
#rdo: RDO meeting - 2019-03-06
==
Meeting started by jpena at 15:00:56 UTC. The full logs are available
at
http://eavesdrop.openstack.org/meetings/rdo_meeting___2019_03_06/2019/rdo_meeting___2019_03_06.2019-03-06-15.00.log.html
.
Meet
Hi,
Once the initial bootstrap for the stable/stein workers has finished in RDO
Trunk, today we will switch the links and start serving them from their normal
URLs:
- centos7: https://trunk.rdoproject.org/centos7-stein
- fedora: https://trunk.rdoproject.org/fedora28-stein
If you are using any
Hi all,
We are going to run some patch maintenance on the RDO Trunk machines
(trunk.rdoproject.org and builders) on March 19, starting at 10:00 UTC.
There should not be a big disruption, just a few minutes during the
trunk.rdoproject.org reboot.
If you have any doubt, please do not hesitate to
Hi all,
Over the last few weeks, mjturek and baha have been busy working on a set of
periodic jobs to build TripleO images for the ppc64le arch [1].
The current missing step is publishing those images, and they are proposing to
push those to the RDO Registry instance at registry.rdoproject.org,
> Hi all,
>
> We are going to run some patch maintenance on the RDO Trunk machines
> (trunk.rdoproject.org and builders) on March 19, starting at 10:00 UTC.
>
> There should not be a big disruption, just a few minutes during the
> trunk.rdoproject.org reboot.
>
Hi,
The update is now complete
- Original Message -
> Hi all,
>
> Over the last few weeks, mjturek and baha have been busy working on a set of
> periodic jobs to build TripleO images for the ppc64le arch [1].
>
> The current missing step is publishing those images, and they are proposing
> to push those to the RDO R
e
> architecture for that image based on the host's architecture.
>
> -Trevor
>
> PS. If I've missed something important with the overall concerns here I
> apologize, but thought it necessary to spell out the goal as I understand
> it.
>
> > On Mar 21, 2019, at 1
Hi all,
We need to run a planned maintenance in registry.rdoproject.org on March 26th
at 9:00 UTC.
This maintenance will extend the disk currently being used to host the registry
images, to cope with current and future requirements. Unfortunately, it cannot
be performed online, so a short down
- Original Message -
> On Fri, Mar 22, 2019 at 8:35 PM Javier Pena < jp...@redhat.com > wrote:
> > - Original Message -
>
> > > I've been working with mjturek and baha on this a bit. I've responded
> > > inline
>
> > &g
- Original Message -
> Hi all,
>
> We need to run a planned maintenance in registry.rdoproject.org on March 26th
> at 9:00 UTC.
>
> This maintenance will extend the disk currently being used to host the
> registry images, to cope with current and future requirements.
> Unfortunately, i
==
#rdo: RDO meeting - 2019-03-27
==
Meeting started by jpena at 15:00:24 UTC. The full logs are available
at
http://eavesdrop.openstack.org/meetings/rdo_meeting___2019_03_27/2019/rdo_meeting___2019_03_27.2019-03-27-15.00.log.html
.
Meet
==
#rdo: RDO meeting - 2019-05-08
==
Meeting started by jpena at 15:00:31 UTC. The full logs are available
at
http://eavesdrop.openstack.org/meetings/rdo_meeting___2019_05_08/2019/rdo_meeting___2019_05_08.2019-05-08-15.00.log.html
.
Meet
- Original Message -
> Hi,
> We have started working on synchronizing OpenStack clients from Stein release
> into Fedora rawhide official repos. The goal is not only updating it in
> fedora but also removing non required openstack packages on Fedora and
> automating the process as much as
==
#rdo: RDO meeting - 2019-06-12
==
Meeting started by jpena at 15:00:29 UTC. The full logs are available
at
http://eavesdrop.openstack.org/meetings/rdo_meeting___2019_06_12/2019/rdo_meeting___2019_06_12.2019-06-12-15.00.log.html
.
Meet
Hi all,
For the last few days, I have been monitoring a spike in disk space utilization
for logs.rdoproject.org. The current situation is:
- 94% of space used, with less than 140GB out of 2TB available.
- The log pruning script has been reclaiming less space than we are using for
new logs durin
- Original Message -
> On Thu, Jun 13, 2019 at 8:22 AM Javier Pena < jp...@redhat.com > wrote:
> > Hi all,
>
> > For the last few days, I have been monitoring a spike in disk space
> > utilization for logs.rdoproject.org . The current situation is:
>
- Original Message -
> Hi all,
>
> For the last few days, I have been monitoring a spike in disk space
> utilization for logs.rdoproject.org. The current situation is:
>
> - 94% of space used, with less than 140GB out of 2TB available.
> - The log pruning script has been reclaiming les
==
#rdo: RDO meeting - 2019-08-21
==
Meeting started by jpena at 15:01:53 UTC. The full logs are available
at
http://eavesdrop.openstack.org/meetings/rdo_meeting___2019_08_21/2019/rdo_meeting___2019_08_21.2019-08-21-15.01.log.html
.
Meet
Hi all,
We have skipped this week's meeting due to lack of topics to discuss. See you
on September 5th for the next meeting!
Javier
___
dev mailing list
dev@lists.rdoproject.org
http://lists.rdoproject.org/mailman/listinfo/dev
To unsubscribe: dev-unsu
Hi all,
Due to an issue in the cloud provider, trunk.rdoproject.org has been down
during the weekend.
While we are still trying to recover it, we have switched to our secondary
server inside RDO Cloud. Depending on the DNS propagation time, it may still
take a few minutes to be visible, but no
> Hi all,
>
> Due to an issue in the cloud provider, trunk.rdoproject.org has been down
> during the weekend.
>
> While we are still trying to recover it, we have switched to our secondary
> server inside RDO Cloud. Depending on the DNS propagation time, it may still
> take a few minutes to be vi
> > Hi all,
> >
> > Due to an issue in the cloud provider, trunk.rdoproject.org has been down
> > during the weekend.
> >
> > While we are still trying to recover it, we have switched to our secondary
> > server inside RDO Cloud. Depending on the DNS propagation time, it may
> > still
> > take
>
> > > Hi all,
> > >
> > > Due to an issue in the cloud provider, trunk.rdoproject.org has been down
> > > during the weekend.
> > >
> > > While we are still trying to recover it, we have switched to our
> > > secondary
> > > server inside RDO Cloud. Depending on the DNS propagation time, it ma
Hi,
I would like to propose the following changes to the Administrators group in
review.rdoproject.org [1]:
- Add Yatin Karel (ykarel) to the group. Actually, I'm surprised he was not
already an administrator.
- Remove Frederic Lepied and Haïkel Guemar from the group. Both have moved on
to oth
==
#rdo: RDO meeting - 2019-09-11
==
Meeting started by jpena at 15:01:02 UTC. The full logs are available
at
http://eavesdrop.openstack.org/meetings/rdo_meeting___2019_09_11/2019/rdo_meeting___2019_09_11.2019-09-11-15.01.log.html
.
Meet
> RDO Kibaba, which was supposed to provide the similar log search experience
> as upstream http://logstash.openstack.org went down a long time ago, I
> reported it again on 18th on irc but got no replies.
>
> https://review.rdoproject.org/analytics/app/kibana
>
> As ruck/rover the ability to inv
==
#rdo: RDO meeting - 2019-10-09
==
Meeting started by jpena at 15:01:28 UTC. The full logs are available
at
http://eavesdrop.openstack.org/meetings/rdo_meeting___2019_10_09/2019/rdo_meeting___2019_10_09.2019-10-09-15.01.log.html
.
Meet
- Original Message -
> Hi,
>
> Last week I asked RDO related question in CentOS-devel mail list, you
> can see the question from bottom link [1]. Thanks for Alfredo kindly
> help.
>
> After we do some POC to build packages in link [2] , I still have some
> questions:
>
> 1. We want co
Hi,
Yesterday, during the weekly RDO meeting, we discussed the current schedule.
During the winter time, there are collisions with the schedule of some
community members, and it is also quite late for some of us.
So, I'd like to propose a change in the meeting time, to start 1 hour later
than
> Hi,
>
> Yesterday, during the weekly RDO meeting, we discussed the current schedule.
> During the winter time, there are collisions with the schedule of some
> community members, and it is also quite late for some of us.
>
> So, I'd like to propose a change in the meeting time, to start 1 hou
- Original Message -
>
> > Hi,
> >
> > Yesterday, during the weekly RDO meeting, we discussed the current
> > schedule.
> > During the winter time, there are collisions with the schedule of some
> > community members, and it is also quite late for some of us.
> >
> > So, I'd like to prop
==
#rdo: RDO meeting - 2019-11-27
==
Meeting started by jpena at 15:00:24 UTC. The full logs are available
at
http://eavesdrop.openstack.org/meetings/rdo_meeting___2019_11_27/2019/rdo_meeting___2019_11_27.2019-11-27-15.00.log.html
.
Meet
Hi,
During the last few months, we have been working on a component-based concept
for RDO Trunk. This means that the set of packages in RDO Trunks will be split
into separate logical components, that can be promoted independently by the
TripleO CI. Thus, an issue in one component will not neces
==
#rdo: RDO meeting - 2020-01-15
==
Meeting started by jpena at 14:04:24 UTC. The full logs are available
at
http://eavesdrop.openstack.org/meetings/rdo_meeting___2020_01_15/2020/rdo_meeting___2020_01_15.2020-01-15-14.04.log.html
.
Meet
GA.
Regards,
Javier
> Thanks
> Tim
>
> > On 15 Jan 2020, at 15:55, Javier Pena wrote:
> >
> > ==
> > #rdo: RDO meeting - 2020-01-15
> > ==
> >
> >
> > Meeting s
Hi all,
We are going to migrate trunk-primary.rdoproject.org to our new cloud provider,
starting on February 4th.
During this process, all RDO Trunk repositories will remain available, but you
may notice delays in getting new commits packaged while each worker data is
synchronized and enabled
==
#rdo: RDO meeting - 2020-02-05
==
Meeting started by jpena at 14:00:48 UTC. The full logs are available
at
http://eavesdrop.openstack.org/meetings/rdo_meeting___2020_02_05/2020/rdo_meeting___2020_02_05.2020-02-05-14.00.log.html
.
Meet
>
> On Tue, Feb 25, 2020 at 14:25 Alfredo Moralejo Alonso wrote:
> > On Tue, Feb 25, 2020 at 12:23 PM Sagi Shnaidman
> > wrote:
> >> We need to test what we ship to customers, so we need to figure that
> >>> out first for Ansible, together with the Ansible team.
> >>> Has shipping on Red Hat CD
==
#rdo: RDO meeting - 2020-03-25
==
Meeting started by jpena at 14:00:22 UTC. The full logs are available
at
http://eavesdrop.openstack.org/meetings/rdo_meeting___2020_03_25/2020/rdo_meeting___2020_03_25.2020-03-25-14.00.log.html
.
Meet
Dear all,
A couple weeks ago, we created a new component-enabled centos8-train builder
for RDO Trunk, using https://trunk.rdoproject.org/centos8-train-components as
its URL.
Today, we have renamed it to be the official centos8-train builder, and the
previous non-component-enabled one has been
> Hi folks,
>
> Would you please tag and push a new rdopkg release?
>
> https://github.com/softwarefactory-project/rdopkg/issues/186
>
> It would be really nice to have
> https://softwarefactory-project.io/r/18391 in a release.
>
Hi Ken,
We have tagged a new rdopkg release (1.3.0), and built
Hi all,
We are planning to run some planned maintenance activities on the RDO Trunk
machines on Tuesday, September 8th at 9:00 UTC.
These planned activities could result in short downtime periods as the httpd
service is restarted. The maintenance window is expected to last for 2 hours
maximum.
> Hi all,
>
> We are planning to run some planned maintenance activities on the RDO Trunk
> machines on Tuesday, September 8th at 9:00 UTC.
>
> These planned activities could result in short downtime periods as the httpd
> service is restarted. The maintenance window is expected to last for 2 hou
Hi,
We are planning to run some maintenance activities on the RDO AFS mirror
servers (mirror.regionone.rdo-cloud.rdoproject.org and
mirror.regionone.vexxhost.rdoproject.org) on next September 17th at 8:00 UTC.
During the maintenance, we may have some httpd service restarts, which mean
that som
Hi,
We are planning to run some maintenance activities to fix the DLRN DB
replication next Friday, September 18th, at 9:00 UTC.
These activities require the main DLRN DB to be set to read-only mode for a
while, so the DLRN API will not allow write operations (reporting results or
promotions) d
> Hi,
>
> We are planning to run some maintenance activities on the RDO AFS mirror
> servers (mirror.regionone.rdo-cloud.rdoproject.org and
> mirror.regionone.vexxhost.rdoproject.org) on next September 17th at 8:00
> UTC.
>
> During the maintenance, we may have some httpd service restarts, which
> Hi,
>
> We are planning to run some maintenance activities to fix the DLRN DB
> replication next Friday, September 18th, at 9:00 UTC.
>
> These activities require the main DLRN DB to be set to read-only mode for a
> while, so the DLRN API will not allow write operations (reporting results or
>
1 - 100 of 120 matches
Mail list logo
