11:04 a.m.
==============================
#rdo: RDO meeting - 2017-09-13
==============================
Meeting started by chandankumar at 15:02:00 UTC. The full logs are
available at
http://eavesdrop.openstack.org/meetings/rdo_meeting___2017_09_13/2017/rdo...
.
Meeting summary
---------------
* Roll Call (chandankumar, 15:02:12)
* dropping patches repositories (chandankumar, 15:05:17)
* AGREED: create patches branches on-demand (number80, 15:17:05)
* AGREED: abandon patches open reviews for EOL branches (number80,
15:17:15)
* ACTION: number80 document that where it fits ^ (number80, 15:17:27)
* Fedora worker cleanup in RDO Trunk (chandankumar, 15:18:31)
* ACTION: jpena to check inclusion of openstack-macros in RDO Trunk
(jpena, 15:27:18)
* Using the CentOS extras Ansible (chandankumar, 15:35:10)
* rdopkg is now in Fedora 25+ and EPEL 7 (chandankumar, 15:44:26)
* ACTION: jruzicka to update website (jruzicka, 15:47:17)
* chair for next meeting (chandankumar, 15:51:40)
* ACTION: jruzicka to chair for next meeting (chandankumar, 15:53:25)
* Open discussion (chandankumar, 15:53:50)
Meeting ended at 16:01:34 UTC.
Action items, by person
-----------------------
* jpena
* jpena to check inclusion of openstack-macros in RDO Trunk
* jruzicka
* jruzicka to update website
* jruzicka to chair for next meeting
* number80
* number80 document that where it fits ^
* openstack
* jpena to check inclusion of openstack-macros in RDO Trunk
People present (lines said)
---------------------------
* chandankumar (48)
* number80 (47)
* apevec (43)
* jruzicka (31)
* snecklifter (25)
* jpena (18)
* dmsimard (8)
* openstack (8)
* rbowen (7)
* Duck (6)
* PagliaccisCloud (2)
* rdogerrit (2)
* jatanmalde (2)
Generated by `MeetBot`_ 0.1.4
11:34 a.m.
New subject: [rdo-list] [CentOS-devel] [Minutes] RDO meeting - 2017-09-13
On Wed, Sep 13, 2017 at 10:04 AM, Chandan kumar <chkumar246(a)gmail.com> wrote:
* Using the CentOS extras Ansible (chandankumar, 15:35:10)
There was some discussion here about ceph-ansible requiring Ansible
2.3.2, and how CentOS Extras only includes Ansible 2.3.1.
I wasn't aware of the specific Ansible 2.3.2 requirement. Can you
share more details? Should we update the "(Build)Requires: ansible >=
2.2.0.0" lines in ceph-ansible.spec?
Ye olde Upstream Vendor just shipped Ansible 2.3.2 to RHEL Extras 8
days ago in https://access.redhat.com/errata/RHBA-2017:2606 , so I
expect CentOS Extras to catch up in a bit.
- Ken
2:56 p.m.
New subject: [rdo-list] [CentOS-devel] [Minutes] RDO meeting - 2017-09-13
On 13/09/17 18:34, Ken Dreyer wrote:
On Wed, Sep 13, 2017 at 10:04 AM, Chandan kumar
<chkumar246(a)gmail.com> wrote:
> * Using the CentOS extras Ansible (chandankumar, 15:35:10)
There was some discussion here about ceph-ansible requiring Ansible
2.3.2, and how CentOS Extras only includes Ansible 2.3.1.
RDO can be more aggressive with updates but we try to stay as close as
possible from RHEL/CentOS base repositories.
2.3.2 allows us to test against next Ansible release and it will only be
in -testing for now. We might decide to stick with 2.3.1 in -release repo.
I wasn't aware of the specific Ansible 2.3.2 requirement. Can
you
share more details? Should we update the "(Build)Requires: ansible >=
2.2.0.0" lines in ceph-ansible.spec?
For now, keep it to 2.3.1, when CentOS extras will get updated 2.3.2
will be fine.
Ye olde Upstream Vendor just shipped Ansible 2.3.2 to RHEL Extras 8
days ago in https://access.redhat.com/errata/RHBA-2017:2606 , so I
expect CentOS Extras to catch up in a bit.
- Ken
_______________________________________________
rdo-list mailing list
rdo-list(a)redhat.com
https://www.redhat.com/mailman/listinfo/rdo-list
To unsubscribe: rdo-list-unsubscribe(a)redhat.com
11:50 a.m.
New subject: [rdo-list] [CentOS-devel] [Minutes] RDO meeting - 2017-09-13
On Wed, Sep 13, 2017 at 1:56 PM, Haïkel Guémar <hguemar(a)redhat.com> wrote:
On 13/09/17 18:34, Ken Dreyer wrote:
> There was some discussion here about ceph-ansible requiring Ansible
> 2.3.2, and how CentOS Extras only includes Ansible 2.3.1.
>
RDO can be more aggressive with updates but we try to stay as close as
possible from RHEL/CentOS base repositories.
2.3.2 allows us to test against next Ansible release and it will only be in
-testing for now. We might decide to stick with 2.3.1 in -release repo.
Thanks. I'm curious, when you push things to -testing, is it *always*
the case that you expect it to go into -release one day? Or are there
some things that you know for certain will never go from -testing to
-release?
> I wasn't aware of the specific Ansible 2.3.2 requirement. Can
you
> share more details? Should we update the "(Build)Requires: ansible >=
> 2.2.0.0" lines in ceph-ansible.spec?
>
For now, keep it to 2.3.1, when CentOS extras will get updated 2.3.2 will be
fine.
Thanks Haïkel! I've made that change in
https://github.com/ceph/ceph-ansible/pull/1901 . It will be in the
next release of ceph-ansible after 3.0.0rc7, probably 3.0.0rc8.
- Ken
2754
days inactive
2759
days old
3 comments
3 participants
participants (3)
-
Chandan kumar -
Haïkel Guémar -
Ken Dreyer