Re: [openstack-dev] [TripleO] Use MariaDB by default on Fedora
Coming back to this. I have updated the review https://review.openstack.org/#/c/90134/ so that it passing CI for ubuntu (obviously failing on fedora) and I am happy with it. In order to close this off my plan is to getting feedback on the mysql element in this review. Any changes that people request in the next few days I will make and test via the CI and internally. Next I will rename mysql - percona and restore the old mysql in this review. At which point the percona code will not be tested via CI so I don't want to make any more changes at that point so I hope it will get approved. So this review will move to adding a percona element. Then following the mariadb integration I would like to get this https://review.openstack.org/#/c/109415/ change to tripleo-incubator through that will include the new percona element in ubuntu images. So in the CI fedora will us mariadb and ubuntu will use percona. Looking forward to any feedback, Michael On 09 July 2014 14:44:15, Sullivan, Jon Paul wrote: -Original Message- From: Giulio Fidente [mailto:gfide...@redhat.com] Sent: 04 July 2014 14:37 To: OpenStack Development Mailing List (not for usage questions) Subject: Re: [openstack-dev] [TripleO] Use MariaDB by default on Fedora On 07/01/2014 05:47 PM, Michael Kerrin wrote: I propose making mysql an abstract element and user must choose either percona or mariadb-rpm element.CI must be setup correctly +1 seems a cleaner and more sustainable approach There was some concern from lifeless around recreating package-style dependencies in dib with element-provides/element-deps, in particular a suggestion that meta-elements are not desirable[1] (I hope I am paraphrasing you correctly Rob). That said, this is exactly the reason that element-provides was brought in, so that the definition of the image could have mysql as an element, but that the DIB_*_EXTRA_ARGS variable would provide the correct one, which would then list itself as providing mysql. This would not prevent the sharing of common code through a differently-named element, such as mysql-common. [1] see comments on April 10th in https://review.openstack.org/#/c/85776/ -- Giulio Fidente GPG KEY: 08D733BA ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev Thanks, Jon-Paul Sullivan ☺ Cloud Services - @hpcloud Postal Address: Hewlett-Packard Galway Limited, Ballybrit Business Park, Galway. Registered Office: Hewlett-Packard Galway Limited, 63-74 Sir John Rogerson's Quay, Dublin 2. Registered Number: 361933 The contents of this message and any attachments to it are confidential and may be legally privileged. If you have received this message in error you should delete it from your system immediately and advise the sender. To any recipient of this message within HP, unless otherwise stated, you should consider this message and attachments as HP CONFIDENTIAL. ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [TripleO] Use MariaDB by default on Fedora
On Fri, Jul 25, 2014 at 7:38 AM, Kerrin, Michael michael.ker...@hp.com wrote: Coming back to this. I have updated the review https://review.openstack.org/#/c/90134/ so that it passing CI for ubuntu (obviously failing on fedora) and I am happy with it. In order to close this off my plan is to getting feedback on the mysql element in this review. Any changes that people request in the next few days I will make and test via the CI and internally. Next I will rename mysql - percona and restore the old mysql in this review. At which point the percona code will not be tested via CI so I don't want to make any more changes at that point so I hope it will get approved. So this review will move to adding a percona element. Then following the mariadb integration I would like to get this https://review.openstack.org/#/c/109415/ change to tripleo-incubator through that will include the new percona element in ubuntu images. So in the CI fedora will us mariadb and ubuntu will use percona. Looking forward to any feedback, Michael On 09 July 2014 14:44:15, Sullivan, Jon Paul wrote: -Original Message- From: Giulio Fidente [mailto:gfide...@redhat.com] Sent: 04 July 2014 14:37 To: OpenStack Development Mailing List (not for usage questions) Subject: Re: [openstack-dev] [TripleO] Use MariaDB by default on Fedora On 07/01/2014 05:47 PM, Michael Kerrin wrote: I propose making mysql an abstract element and user must choose either percona or mariadb-rpm element.CI must be setup correctly +1 seems a cleaner and more sustainable approach There was some concern from lifeless around recreating package-style dependencies in dib with element-provides/element-deps, in particular a suggestion that meta-elements are not desirable[1] (I hope I am paraphrasing you correctly Rob). That said, this is exactly the reason that element-provides was brought in, so that the definition of the image could have mysql as an element, but that the DIB_*_EXTRA_ARGS variable would provide the correct one, which would then list itself as providing mysql. This would not prevent the sharing of common code through a differently-named element, such as mysql-common. [1] see comments on April 10th in https://review.openstack.org/#/c/85776/ -- Giulio Fidente GPG KEY: 08D733BA ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev Thanks, Jon-Paul Sullivan ☺ Cloud Services - @hpcloud Postal Address: Hewlett-Packard Galway Limited, Ballybrit Business Park, Galway. Registered Office: Hewlett-Packard Galway Limited, 63-74 Sir John Rogerson's Quay, Dublin 2. Registered Number: 361933 The contents of this message and any attachments to it are confidential and may be legally privileged. If you have received this message in error you should delete it from your system immediately and advise the sender. To any recipient of this message within HP, unless otherwise stated, you should consider this message and attachments as HP CONFIDENTIAL. ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev So this all sounds like an interesting mess. I'm not even really sure I follow all that's going on in the database area with the exception of the design which it seems is something that takes no account for testing or commonality across platforms (pretty bad IMO) but I don't have any insight there so I'll butt out. The LIO versus Tgt thing however is a bit troubling. Is there a reason that TripleO decided to do the exact opposite of what the defaults are in the rest of OpenStack here? Also any reason why if there was a valid justification for this it didn't seem like it might be worthwhile to work with the rest of the OpenStack community and share what they considered to be the better solution here? Sorry, I just haven't swallowed the TripleO pill. We seem to have taken the problem of how to make it easier to install OpenStack and turned it into as complex and difficult a thing as possible. Hey... it's hard to deploy and manage a cloud; have two! By the way, we did everything differently here than anywhere else so everything you thought you knew, still need it but won't help you here.. best of luck to you. ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [TripleO] Use MariaDB by default on Fedora
On Fri, Jul 25, 2014 at 7:59 AM, John Griffith john.griff...@solidfire.com wrote: On Fri, Jul 25, 2014 at 7:38 AM, Kerrin, Michael michael.ker...@hp.com wrote: Coming back to this. I have updated the review https://review.openstack.org/#/c/90134/ so that it passing CI for ubuntu (obviously failing on fedora) and I am happy with it. In order to close this off my plan is to getting feedback on the mysql element in this review. Any changes that people request in the next few days I will make and test via the CI and internally. Next I will rename mysql - percona and restore the old mysql in this review. At which point the percona code will not be tested via CI so I don't want to make any more changes at that point so I hope it will get approved. So this review will move to adding a percona element. Then following the mariadb integration I would like to get this https://review.openstack.org/#/c/109415/ change to tripleo-incubator through that will include the new percona element in ubuntu images. So in the CI fedora will us mariadb and ubuntu will use percona. Looking forward to any feedback, Michael On 09 July 2014 14:44:15, Sullivan, Jon Paul wrote: -Original Message- From: Giulio Fidente [mailto:gfide...@redhat.com] Sent: 04 July 2014 14:37 To: OpenStack Development Mailing List (not for usage questions) Subject: Re: [openstack-dev] [TripleO] Use MariaDB by default on Fedora On 07/01/2014 05:47 PM, Michael Kerrin wrote: I propose making mysql an abstract element and user must choose either percona or mariadb-rpm element.CI must be setup correctly +1 seems a cleaner and more sustainable approach There was some concern from lifeless around recreating package-style dependencies in dib with element-provides/element-deps, in particular a suggestion that meta-elements are not desirable[1] (I hope I am paraphrasing you correctly Rob). That said, this is exactly the reason that element-provides was brought in, so that the definition of the image could have mysql as an element, but that the DIB_*_EXTRA_ARGS variable would provide the correct one, which would then list itself as providing mysql. This would not prevent the sharing of common code through a differently-named element, such as mysql-common. [1] see comments on April 10th in https://review.openstack.org/# /c/85776/ -- Giulio Fidente GPG KEY: 08D733BA ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev Thanks, Jon-Paul Sullivan ☺ Cloud Services - @hpcloud Postal Address: Hewlett-Packard Galway Limited, Ballybrit Business Park, Galway. Registered Office: Hewlett-Packard Galway Limited, 63-74 Sir John Rogerson's Quay, Dublin 2. Registered Number: 361933 The contents of this message and any attachments to it are confidential and may be legally privileged. If you have received this message in error you should delete it from your system immediately and advise the sender. To any recipient of this message within HP, unless otherwise stated, you should consider this message and attachments as HP CONFIDENTIAL. ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev So this all sounds like an interesting mess. I'm not even really sure I follow all that's going on in the database area with the exception of the design which it seems is something that takes no account for testing or commonality across platforms (pretty bad IMO) but I don't have any insight there so I'll butt out. The LIO versus Tgt thing however is a bit troubling. Is there a reason that TripleO decided to do the exact opposite of what the defaults are in the rest of OpenStack here? Also any reason why if there was a valid justification for this it didn't seem like it might be worthwhile to work with the rest of the OpenStack community and share what they considered to be the better solution here? Sorry, I just haven't swallowed the TripleO pill. We seem to have taken the problem of how to make it easier to install OpenStack and turned it into as complex and difficult a thing as possible. Hey... it's hard to deploy and manage a cloud; have two! By the way, we did everything differently here than anywhere else so everything you thought you knew, still need it but won't help you here.. best of luck to you. Oh.. before the CD flames come my way, yes I know that's something somebody was interested in. ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo
Re: [openstack-dev] [TripleO] Use MariaDB by default on Fedora
Excerpts from John Griffith's message of 2014-07-25 06:59:38 -0700: On Fri, Jul 25, 2014 at 7:38 AM, Kerrin, Michael michael.ker...@hp.com wrote: Coming back to this. I have updated the review https://review.openstack.org/#/c/90134/ so that it passing CI for ubuntu (obviously failing on fedora) and I am happy with it. In order to close this off my plan is to getting feedback on the mysql element in this review. Any changes that people request in the next few days I will make and test via the CI and internally. Next I will rename mysql - percona and restore the old mysql in this review. At which point the percona code will not be tested via CI so I don't want to make any more changes at that point so I hope it will get approved. So this review will move to adding a percona element. Then following the mariadb integration I would like to get this https://review.openstack.org/#/c/109415/ change to tripleo-incubator through that will include the new percona element in ubuntu images. So in the CI fedora will us mariadb and ubuntu will use percona. Looking forward to any feedback, Michael On 09 July 2014 14:44:15, Sullivan, Jon Paul wrote: -Original Message- From: Giulio Fidente [mailto:gfide...@redhat.com] Sent: 04 July 2014 14:37 To: OpenStack Development Mailing List (not for usage questions) Subject: Re: [openstack-dev] [TripleO] Use MariaDB by default on Fedora On 07/01/2014 05:47 PM, Michael Kerrin wrote: I propose making mysql an abstract element and user must choose either percona or mariadb-rpm element.CI must be setup correctly +1 seems a cleaner and more sustainable approach There was some concern from lifeless around recreating package-style dependencies in dib with element-provides/element-deps, in particular a suggestion that meta-elements are not desirable[1] (I hope I am paraphrasing you correctly Rob). That said, this is exactly the reason that element-provides was brought in, so that the definition of the image could have mysql as an element, but that the DIB_*_EXTRA_ARGS variable would provide the correct one, which would then list itself as providing mysql. This would not prevent the sharing of common code through a differently-named element, such as mysql-common. [1] see comments on April 10th in https://review.openstack.org/#/c/85776/ -- Giulio Fidente GPG KEY: 08D733BA ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev Thanks, Jon-Paul Sullivan ☺ Cloud Services - @hpcloud Postal Address: Hewlett-Packard Galway Limited, Ballybrit Business Park, Galway. Registered Office: Hewlett-Packard Galway Limited, 63-74 Sir John Rogerson's Quay, Dublin 2. Registered Number: 361933 The contents of this message and any attachments to it are confidential and may be legally privileged. If you have received this message in error you should delete it from your system immediately and advise the sender. To any recipient of this message within HP, unless otherwise stated, you should consider this message and attachments as HP CONFIDENTIAL. ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev So this all sounds like an interesting mess. I'm not even really sure I follow all that's going on in the database area with the exception of the design which it seems is something that takes no account for testing or commonality across platforms (pretty bad IMO) but I don't have any insight there so I'll butt out. The LIO versus Tgt thing however is a bit troubling. Is there a reason that TripleO decided to do the exact opposite of what the defaults are in the rest of OpenStack here? Also any reason why if there was a valid justification for this it didn't seem like it might be worthwhile to work with the rest of the OpenStack community and share what they considered to be the better solution here? John, please be specific when you say the defaults are in the rest of OpenStack. We have a stated goal to deploy _with the defaults_. The default iscsi_helper is tgtadmin. We deploy with that unless another is selected. As you see below, nothing is asserted there unless a value is set: https://git.openstack.org/cgit/openstack/tripleo-image-elements/tree/elements/cinder/os-apply-config/etc/cinder/cinder.conf#n41 And the default in the Heat templates that will set that value matches cinder's current default: https://git.openstack.org/cgit/openstack/tripleo-heat-templates/tree/overcloud-source.yaml
Re: [openstack-dev] [TripleO] Use MariaDB by default on Fedora
On Fri, Jul 25, 2014 at 9:59 AM, John Griffith john.griff...@solidfire.com wrote: The LIO versus Tgt thing however is a bit troubling. Is there a reason that TripleO decided to do the exact opposite of what the defaults are in the rest of OpenStack here? Also any reason why if there was a valid justification for this it didn't seem like it might be worthwhile to work with the rest of the OpenStack community and share what they considered to be the better solution here? Not really following what you find troubling. Cinder allows you to configure it to use Tgt or LIO. Are you objecting to the fact that TripleO allows people to *choose* to use LIO? As was explained in the review[1], Tgt is the default for TripleO. If you want to use LIO, TripleO offers that choice, just like Cinder does. [1] https://review.openstack.org/#/c/78463/ -- -- James Slagle -- ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [TripleO] Use MariaDB by default on Fedora
On Fri, Jul 25, 2014 at 10:43 AM, James Slagle james.sla...@gmail.com wrote: On Fri, Jul 25, 2014 at 9:59 AM, John Griffith john.griff...@solidfire.com wrote: The LIO versus Tgt thing however is a bit troubling. Is there a reason that TripleO decided to do the exact opposite of what the defaults are in the rest of OpenStack here? Also any reason why if there was a valid justification for this it didn't seem like it might be worthwhile to work with the rest of the OpenStack community and share what they considered to be the better solution here? Not really following what you find troubling. Cinder allows you to configure it to use Tgt or LIO. Are you objecting to the fact that TripleO allows people to *choose* to use LIO? Nope, that's fine... what I'm uneasy about is there appears to be a suggestion to have different defaults for things based on distribution. If this turns out to be the only way to make things work, then sure... we do what we have to do. Maybe I'm missing some points in the thread, if it's strictly do we allow options then sure, I'm not saying that's a bad thing particularly if those options are the same as we already do in other projects. LIO is used on RHEL, because RHEL doesn't offer TGT. So what is the LIO versus Tgt thing? What version of RHEL don't offer tgtadm? It's in 6.5; also I responded to a post on this subject a while back about having consistent defaults whether you're dealing with an over-cloud or an under-cloud; IMO uniqueness between the two in terms of defaults is something that should be carefully weighed. My suggestion was and is, that if for example LIO was the only option, then we should work together to make that a consistent default across the board. Sounds like maybe I misunderstood what was being done here so perhaps it's not an issue. TripleO is a program aimed at installing, upgrading and operating OpenStack clouds using OpenStack's own cloud facilities as the foundations - building on nova, neutron and heat to automate fleet management at datacentre scale (and scaling down to as few as 2 machines). Sure, but for some crazy reason I had always assumed that there would be some 'value add' here, whether that be efficiency, ease of deployment or whatever. Not just I can use OpenStack to deploy OpenStack and throw away the large number of tools designed to do this sort of thing and reinvent them because it's neat. I'm not saying that's how I see it, but I am saying maybe the stated purpose could use a bit of detail. Nobody expects datacenter scale to be easy. We do, however, have a reasonable expectation that OpenStack can be used to deploy large, complex applications. If it cannot, OpenStack is in trouble. Sure... but I think by adding (more to the point exposing) as much complexity as possible and reinventing tools OpenStack will be in trouble as well (likely more trouble). Granted Heat is great for the deployment of applications in an OpenStack Cloud, so you're saying that since TripleO uses Heat it falls into the same category? OpenStack on OpenStack is just another application we're deploying? Then maybe all of this should be folded in to Heat in perhaps a different design, or maybe it already is for the most part. Can't really tell for sure as I've never really been able to do get anything really working with TripleO as of yet, which goes back to my earlier comment about complexity and what the actual goal is. As was explained in the review[1], Tgt is the default for TripleO. If you want to use LIO, TripleO offers that choice, just like Cinder does. Cool... you can disregard any comments I made on that subject then. [1] https://review.openstack.org/#/c/78463/ -- -- James Slagle -- ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [TripleO] Use MariaDB by default on Fedora
-Original Message- From: Giulio Fidente [mailto:gfide...@redhat.com] Sent: 04 July 2014 14:37 To: OpenStack Development Mailing List (not for usage questions) Subject: Re: [openstack-dev] [TripleO] Use MariaDB by default on Fedora On 07/01/2014 05:47 PM, Michael Kerrin wrote: I propose making mysql an abstract element and user must choose either percona or mariadb-rpm element.CI must be setup correctly +1 seems a cleaner and more sustainable approach There was some concern from lifeless around recreating package-style dependencies in dib with element-provides/element-deps, in particular a suggestion that meta-elements are not desirable[1] (I hope I am paraphrasing you correctly Rob). That said, this is exactly the reason that element-provides was brought in, so that the definition of the image could have mysql as an element, but that the DIB_*_EXTRA_ARGS variable would provide the correct one, which would then list itself as providing mysql. This would not prevent the sharing of common code through a differently-named element, such as mysql-common. [1] see comments on April 10th in https://review.openstack.org/#/c/85776/ -- Giulio Fidente GPG KEY: 08D733BA ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev Thanks, Jon-Paul Sullivan ☺ Cloud Services - @hpcloud Postal Address: Hewlett-Packard Galway Limited, Ballybrit Business Park, Galway. Registered Office: Hewlett-Packard Galway Limited, 63-74 Sir John Rogerson's Quay, Dublin 2. Registered Number: 361933 The contents of this message and any attachments to it are confidential and may be legally privileged. If you have received this message in error you should delete it from your system immediately and advise the sender. To any recipient of this message within HP, unless otherwise stated, you should consider this message and attachments as HP CONFIDENTIAL. ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [TripleO] Use MariaDB by default on Fedora
On 07/01/2014 05:47 PM, Michael Kerrin wrote: I propose making mysql an abstract element and user must choose either percona or mariadb-rpm element.CI must be setup correctly +1 seems a cleaner and more sustainable approach -- Giulio Fidente GPG KEY: 08D733BA ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [TripleO] Use MariaDB by default on Fedora
I propose making mysql an abstract element and user must choose either percona or mariadb-rpm element.CI must be setup correctly Michael On Monday 30 June 2014 12:02:09 Clint Byrum wrote: Excerpts from Michael Kerrin's message of 2014-06-30 02:16:07 -0700: I am trying to finish off https://review.openstack.org/#/c/90134 - percona xtradb cluster for debian based system. I have read into this thread that I can error out on Redhat systems when trying to install percona and tell them to use mariadb instead, percona isn't support here. Is this correct? Probably. But if CI for Fedora breaks as a result you'll need a solution first. ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [TripleO] Use MariaDB by default on Fedora
I am trying to finish off https://review.openstack.org/#/c/90134 - percona xtradb cluster for debian based system. I have read into this thread that I can error out on Redhat systems when trying to install percona and tell them to use mariadb instead, percona isn't support here. Is this correct? Michael On Friday 27 June 2014 16:49:58 James Slagle wrote: On Fri, Jun 27, 2014 at 4:13 PM, Clint Byrum cl...@fewbar.com wrote: Excerpts from James Slagle's message of 2014-06-27 12:59:36 -0700: Things are a bit confusing right now, especially with what's been proposed. Let me try and clarify (even if just for my own sake). Currently the choices offered are: 1. mysql percona with the percona tarball Percona Xtradb Cluster, not mysql percona 2. mariadb galera with mariadb.org packages 3. mariadb galera with rdo packages And, we're proposing to add 4. mysql percona with percona packages: https://review.openstack.org/#/c/90134 5. mariadb galera with fedora packages https://review.openstack.org/#/c/102815/ 4 replaces 1, but only for Ubuntu/Debian, it doesn't work on Fedora/RH 5 replaces 3 (neither of which work on Ubuntu/Debian, obviously) Do we still need 1? Fedora/RH + percona tarball. I personally don't think so. Do we still need 2? Fedora/RH or Ubuntu/Debian with galera packages from maraidb.org. For the Fedora/RH case, I doubt it, people will just use 5. 3 will be gone (replaced by 5). So, yes, I'd like to see 5 as the default for Fedora/RH and 4 as the default for Ubuntu/Debian, and both those tested in CI. And get rid of (or deprecate) 1-3. I'm actually more confused now than before I read this. The use of numbers is just making my head spin. There are 5 choices, some of which are not totally clear. Hence the need to clean things up. It can be stated this way I think: On RPM systems, use MariaDB Galera packages. If packages are in the distro, use distro packages. If packages are not in the distro, use RDO packages. There won't be a need to install from the RDO repositories. Mariadb galera packages are in the main Fedora package repositories, and for RHEL, they're in the epel repositories. On DEB systems, use Percona XtraDB Cluster packages. If packages are in the distro, use distro packages. If packages are not in the distro, use upstream packages. If anything doesn't match those principles, it is a bug. ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [TripleO] Use MariaDB by default on Fedora
On 06/30/2014 11:16 AM, Michael Kerrin wrote: I am trying to finish off https://review.openstack.org/#/c/90134 - percona xtradb cluster for debian based system. I have read into this thread that I can error out on Redhat systems when trying to install percona and tell them to use mariadb instead, percona isn't support here. Is this correct? I think on rhel mysql/xtradb is expected to work from the percona tarball, as it used to happen on fedora yet this change [1] is eventually going to switch the default solution to mariadb/galera for rhel too which is consistent with the previous idea from James there could still be unexpected issues on distro for which we don't have CI but I wouldn't expect troubles caused by your change 1. https://review.openstack.org/#/c/102818/ -- Giulio Fidente GPG KEY: 08D733BA ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [TripleO] Use MariaDB by default on Fedora
Excerpts from Michael Kerrin's message of 2014-06-30 02:16:07 -0700: I am trying to finish off https://review.openstack.org/#/c/90134 - percona xtradb cluster for debian based system. I have read into this thread that I can error out on Redhat systems when trying to install percona and tell them to use mariadb instead, percona isn't support here. Is this correct? Probably. But if CI for Fedora breaks as a result you'll need a solution first. ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [TripleO] Use MariaDB by default on Fedora
Things are a bit confusing right now, especially with what's been proposed. Let me try and clarify (even if just for my own sake). Currently the choices offered are: 1. mysql percona with the percona tarball 2. mariadb galera with mariadb.org packages 3. mariadb galera with rdo packages And, we're proposing to add 4. mysql percona with percona packages: https://review.openstack.org/#/c/90134 5. mariadb galera with fedora packages https://review.openstack.org/#/c/102815/ 4 replaces 1, but only for Ubuntu/Debian, it doesn't work on Fedora/RH 5 replaces 3 (neither of which work on Ubuntu/Debian, obviously) Do we still need 1? Fedora/RH + percona tarball. I personally don't think so. Do we still need 2? Fedora/RH or Ubuntu/Debian with galera packages from maraidb.org. For the Fedora/RH case, I doubt it, people will just use 5. 3 will be gone (replaced by 5). So, yes, I'd like to see 5 as the default for Fedora/RH and 4 as the default for Ubuntu/Debian, and both those tested in CI. And get rid of (or deprecate) 1-3. On Thu, Jun 26, 2014 at 5:30 PM, Giulio Fidente gfide...@redhat.com wrote: On 06/26/2014 11:11 AM, Jan Provaznik wrote: On 06/25/2014 06:58 PM, Giulio Fidente wrote: On 06/16/2014 11:14 PM, Clint Byrum wrote: Excerpts from Gregory Haynes's message of 2014-06-16 14:04:19 -0700: Excerpts from Jan Provazník's message of 2014-06-16 20:28:29 +: Hi, MariaDB is now included in Fedora repositories, this makes it easier to install and more stable option for Fedora installations. Currently MariaDB can be used by including mariadb (use mariadb.org pkgs) or mariadb-rdo (use redhat RDO pkgs) element when building an image. What do you think about using MariaDB as default option for Fedora when running devtest scripts? (first, I believe Jan means that MariaDB _Galera_ is now in Fedora) I think so too. Id like to give this a try. This does start to change us from being a deployment of openstck to being a deployment per distro but IMO thats a reasonable position. Id also like to propose that if we decide against doing this then these elements should not live in tripleo-image-elements. I'm not so sure I agree. We have lio and tgt because lio is on RHEL but everywhere else is still using tgt IIRC. However, I also am not so sure that it is actually a good idea for people to ship on MariaDB since it is not in the gate. As it diverges from MySQL (starting in earnest with 10.x), there will undoubtedly be subtle issues that arise. So I'd say having MariaDB get tested along with Fedora will actually improve those users' test coverage, which is a good thing. I am favourable to the idea of switching to mariadb for fedora based distros. Currently the default mysql element seems to be switching [1], yet for ubuntu/debian only, from the percona provided binary tarball of mysql to the percona provided packaged version of mysql. In theory we could further update it to use percona provided packages of mysql on fedora too but I'm not sure there is much interest in using that combination where people gets mariadb and galera from the official repos. IIRC fedora packages for percona xtradb cluster are not provided (unless something has changed recently). I see, so on fedora it will be definitely easier and safer to just use the mariadb/galera packages provided in the official repo ... and this further reinforces my idea that it is the best option to use that by default for fedora -- Giulio Fidente GPG KEY: 08D733BA ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev -- -- James Slagle -- ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [TripleO] Use MariaDB by default on Fedora
Excerpts from James Slagle's message of 2014-06-27 12:59:36 -0700: Things are a bit confusing right now, especially with what's been proposed. Let me try and clarify (even if just for my own sake). Currently the choices offered are: 1. mysql percona with the percona tarball Percona Xtradb Cluster, not mysql percona 2. mariadb galera with mariadb.org packages 3. mariadb galera with rdo packages And, we're proposing to add 4. mysql percona with percona packages: https://review.openstack.org/#/c/90134 5. mariadb galera with fedora packages https://review.openstack.org/#/c/102815/ 4 replaces 1, but only for Ubuntu/Debian, it doesn't work on Fedora/RH 5 replaces 3 (neither of which work on Ubuntu/Debian, obviously) Do we still need 1? Fedora/RH + percona tarball. I personally don't think so. Do we still need 2? Fedora/RH or Ubuntu/Debian with galera packages from maraidb.org. For the Fedora/RH case, I doubt it, people will just use 5. 3 will be gone (replaced by 5). So, yes, I'd like to see 5 as the default for Fedora/RH and 4 as the default for Ubuntu/Debian, and both those tested in CI. And get rid of (or deprecate) 1-3. I'm actually more confused now than before I read this. The use of numbers is just making my head spin. It can be stated this way I think: On RPM systems, use MariaDB Galera packages. If packages are in the distro, use distro packages. If packages are not in the distro, use RDO packages. On DEB systems, use Percona XtraDB Cluster packages. If packages are in the distro, use distro packages. If packages are not in the distro, use upstream packages. If anything doesn't match those principles, it is a bug. On Thu, Jun 26, 2014 at 5:30 PM, Giulio Fidente gfide...@redhat.com wrote: On 06/26/2014 11:11 AM, Jan Provaznik wrote: On 06/25/2014 06:58 PM, Giulio Fidente wrote: On 06/16/2014 11:14 PM, Clint Byrum wrote: Excerpts from Gregory Haynes's message of 2014-06-16 14:04:19 -0700: Excerpts from Jan Provazník's message of 2014-06-16 20:28:29 +: Hi, MariaDB is now included in Fedora repositories, this makes it easier to install and more stable option for Fedora installations. Currently MariaDB can be used by including mariadb (use mariadb.org pkgs) or mariadb-rdo (use redhat RDO pkgs) element when building an image. What do you think about using MariaDB as default option for Fedora when running devtest scripts? (first, I believe Jan means that MariaDB _Galera_ is now in Fedora) I think so too. Id like to give this a try. This does start to change us from being a deployment of openstck to being a deployment per distro but IMO thats a reasonable position. Id also like to propose that if we decide against doing this then these elements should not live in tripleo-image-elements. I'm not so sure I agree. We have lio and tgt because lio is on RHEL but everywhere else is still using tgt IIRC. However, I also am not so sure that it is actually a good idea for people to ship on MariaDB since it is not in the gate. As it diverges from MySQL (starting in earnest with 10.x), there will undoubtedly be subtle issues that arise. So I'd say having MariaDB get tested along with Fedora will actually improve those users' test coverage, which is a good thing. I am favourable to the idea of switching to mariadb for fedora based distros. Currently the default mysql element seems to be switching [1], yet for ubuntu/debian only, from the percona provided binary tarball of mysql to the percona provided packaged version of mysql. In theory we could further update it to use percona provided packages of mysql on fedora too but I'm not sure there is much interest in using that combination where people gets mariadb and galera from the official repos. IIRC fedora packages for percona xtradb cluster are not provided (unless something has changed recently). I see, so on fedora it will be definitely easier and safer to just use the mariadb/galera packages provided in the official repo ... and this further reinforces my idea that it is the best option to use that by default for fedora -- Giulio Fidente GPG KEY: 08D733BA ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [TripleO] Use MariaDB by default on Fedora
On Fri, Jun 27, 2014 at 4:13 PM, Clint Byrum cl...@fewbar.com wrote: Excerpts from James Slagle's message of 2014-06-27 12:59:36 -0700: Things are a bit confusing right now, especially with what's been proposed. Let me try and clarify (even if just for my own sake). Currently the choices offered are: 1. mysql percona with the percona tarball Percona Xtradb Cluster, not mysql percona 2. mariadb galera with mariadb.org packages 3. mariadb galera with rdo packages And, we're proposing to add 4. mysql percona with percona packages: https://review.openstack.org/#/c/90134 5. mariadb galera with fedora packages https://review.openstack.org/#/c/102815/ 4 replaces 1, but only for Ubuntu/Debian, it doesn't work on Fedora/RH 5 replaces 3 (neither of which work on Ubuntu/Debian, obviously) Do we still need 1? Fedora/RH + percona tarball. I personally don't think so. Do we still need 2? Fedora/RH or Ubuntu/Debian with galera packages from maraidb.org. For the Fedora/RH case, I doubt it, people will just use 5. 3 will be gone (replaced by 5). So, yes, I'd like to see 5 as the default for Fedora/RH and 4 as the default for Ubuntu/Debian, and both those tested in CI. And get rid of (or deprecate) 1-3. I'm actually more confused now than before I read this. The use of numbers is just making my head spin. There are 5 choices, some of which are not totally clear. Hence the need to clean things up. It can be stated this way I think: On RPM systems, use MariaDB Galera packages. If packages are in the distro, use distro packages. If packages are not in the distro, use RDO packages. There won't be a need to install from the RDO repositories. Mariadb galera packages are in the main Fedora package repositories, and for RHEL, they're in the epel repositories. On DEB systems, use Percona XtraDB Cluster packages. If packages are in the distro, use distro packages. If packages are not in the distro, use upstream packages. If anything doesn't match those principles, it is a bug. -- -- James Slagle -- ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [TripleO] Use MariaDB by default on Fedora
On 06/25/2014 06:58 PM, Giulio Fidente wrote: On 06/16/2014 11:14 PM, Clint Byrum wrote: Excerpts from Gregory Haynes's message of 2014-06-16 14:04:19 -0700: Excerpts from Jan Provazník's message of 2014-06-16 20:28:29 +: Hi, MariaDB is now included in Fedora repositories, this makes it easier to install and more stable option for Fedora installations. Currently MariaDB can be used by including mariadb (use mariadb.org pkgs) or mariadb-rdo (use redhat RDO pkgs) element when building an image. What do you think about using MariaDB as default option for Fedora when running devtest scripts? (first, I believe Jan means that MariaDB _Galera_ is now in Fedora) I think so too. Id like to give this a try. This does start to change us from being a deployment of openstck to being a deployment per distro but IMO thats a reasonable position. Id also like to propose that if we decide against doing this then these elements should not live in tripleo-image-elements. I'm not so sure I agree. We have lio and tgt because lio is on RHEL but everywhere else is still using tgt IIRC. However, I also am not so sure that it is actually a good idea for people to ship on MariaDB since it is not in the gate. As it diverges from MySQL (starting in earnest with 10.x), there will undoubtedly be subtle issues that arise. So I'd say having MariaDB get tested along with Fedora will actually improve those users' test coverage, which is a good thing. I am favourable to the idea of switching to mariadb for fedora based distros. Currently the default mysql element seems to be switching [1], yet for ubuntu/debian only, from the percona provided binary tarball of mysql to the percona provided packaged version of mysql. In theory we could further update it to use percona provided packages of mysql on fedora too but I'm not sure there is much interest in using that combination where people gets mariadb and galera from the official repos. IIRC fedora packages for percona xtradb cluster are not provided (unless something has changed recently). Using different defaults (and even drop support for one or another, depending on the distro), seems to me a better approach in the long term. Are there contrary opinions? 1. https://review.openstack.org/#/c/90134 ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [TripleO] Use MariaDB by default on Fedora
On 06/26/2014 11:11 AM, Jan Provaznik wrote: On 06/25/2014 06:58 PM, Giulio Fidente wrote: On 06/16/2014 11:14 PM, Clint Byrum wrote: Excerpts from Gregory Haynes's message of 2014-06-16 14:04:19 -0700: Excerpts from Jan Provazník's message of 2014-06-16 20:28:29 +: Hi, MariaDB is now included in Fedora repositories, this makes it easier to install and more stable option for Fedora installations. Currently MariaDB can be used by including mariadb (use mariadb.org pkgs) or mariadb-rdo (use redhat RDO pkgs) element when building an image. What do you think about using MariaDB as default option for Fedora when running devtest scripts? (first, I believe Jan means that MariaDB _Galera_ is now in Fedora) I think so too. Id like to give this a try. This does start to change us from being a deployment of openstck to being a deployment per distro but IMO thats a reasonable position. Id also like to propose that if we decide against doing this then these elements should not live in tripleo-image-elements. I'm not so sure I agree. We have lio and tgt because lio is on RHEL but everywhere else is still using tgt IIRC. However, I also am not so sure that it is actually a good idea for people to ship on MariaDB since it is not in the gate. As it diverges from MySQL (starting in earnest with 10.x), there will undoubtedly be subtle issues that arise. So I'd say having MariaDB get tested along with Fedora will actually improve those users' test coverage, which is a good thing. I am favourable to the idea of switching to mariadb for fedora based distros. Currently the default mysql element seems to be switching [1], yet for ubuntu/debian only, from the percona provided binary tarball of mysql to the percona provided packaged version of mysql. In theory we could further update it to use percona provided packages of mysql on fedora too but I'm not sure there is much interest in using that combination where people gets mariadb and galera from the official repos. IIRC fedora packages for percona xtradb cluster are not provided (unless something has changed recently). I see, so on fedora it will be definitely easier and safer to just use the mariadb/galera packages provided in the official repo ... and this further reinforces my idea that it is the best option to use that by default for fedora -- Giulio Fidente GPG KEY: 08D733BA ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [TripleO] Use MariaDB by default on Fedora
On 06/16/2014 11:14 PM, Clint Byrum wrote: Excerpts from Gregory Haynes's message of 2014-06-16 14:04:19 -0700: Excerpts from Jan Provazník's message of 2014-06-16 20:28:29 +: Hi, MariaDB is now included in Fedora repositories, this makes it easier to install and more stable option for Fedora installations. Currently MariaDB can be used by including mariadb (use mariadb.org pkgs) or mariadb-rdo (use redhat RDO pkgs) element when building an image. What do you think about using MariaDB as default option for Fedora when running devtest scripts? (first, I believe Jan means that MariaDB _Galera_ is now in Fedora) I think so too. Id like to give this a try. This does start to change us from being a deployment of openstck to being a deployment per distro but IMO thats a reasonable position. Id also like to propose that if we decide against doing this then these elements should not live in tripleo-image-elements. I'm not so sure I agree. We have lio and tgt because lio is on RHEL but everywhere else is still using tgt IIRC. However, I also am not so sure that it is actually a good idea for people to ship on MariaDB since it is not in the gate. As it diverges from MySQL (starting in earnest with 10.x), there will undoubtedly be subtle issues that arise. So I'd say having MariaDB get tested along with Fedora will actually improve those users' test coverage, which is a good thing. I am favourable to the idea of switching to mariadb for fedora based distros. Currently the default mysql element seems to be switching [1], yet for ubuntu/debian only, from the percona provided binary tarball of mysql to the percona provided packaged version of mysql. In theory we could further update it to use percona provided packages of mysql on fedora too but I'm not sure there is much interest in using that combination where people gets mariadb and galera from the official repos. Using different defaults (and even drop support for one or another, depending on the distro), seems to me a better approach in the long term. Are there contrary opinions? 1. https://review.openstack.org/#/c/90134 -- Giulio Fidente GPG KEY: 08D733BA ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
[openstack-dev] [TripleO] Use MariaDB by default on Fedora
Hi, MariaDB is now included in Fedora repositories, this makes it easier to install and more stable option for Fedora installations. Currently MariaDB can be used by including mariadb (use mariadb.org pkgs) or mariadb-rdo (use redhat RDO pkgs) element when building an image. What do you think about using MariaDB as default option for Fedora when running devtest scripts? Pros: better elements coverage, both mysql and mariadb elements would be tested, now only mysql element is used in tests Cons: different elements would be used for various distributions Jan ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [TripleO] Use MariaDB by default on Fedora
Excerpts from Jan Provazník's message of 2014-06-16 20:28:29 +: Hi, MariaDB is now included in Fedora repositories, this makes it easier to install and more stable option for Fedora installations. Currently MariaDB can be used by including mariadb (use mariadb.org pkgs) or mariadb-rdo (use redhat RDO pkgs) element when building an image. What do you think about using MariaDB as default option for Fedora when running devtest scripts? Id like to give this a try. This does start to change us from being a deployment of openstck to being a deployment per distro but IMO thats a reasonable position. Id also like to propose that if we decide against doing this then these elements should not live in tripleo-image-elements. Cheers, Greg -- Gregory Haynes g...@greghaynes.net ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [TripleO] Use MariaDB by default on Fedora
Excerpts from Gregory Haynes's message of 2014-06-16 14:04:19 -0700: Excerpts from Jan Provazník's message of 2014-06-16 20:28:29 +: Hi, MariaDB is now included in Fedora repositories, this makes it easier to install and more stable option for Fedora installations. Currently MariaDB can be used by including mariadb (use mariadb.org pkgs) or mariadb-rdo (use redhat RDO pkgs) element when building an image. What do you think about using MariaDB as default option for Fedora when running devtest scripts? (first, I believe Jan means that MariaDB _Galera_ is now in Fedora) Id like to give this a try. This does start to change us from being a deployment of openstck to being a deployment per distro but IMO thats a reasonable position. Id also like to propose that if we decide against doing this then these elements should not live in tripleo-image-elements. I'm not so sure I agree. We have lio and tgt because lio is on RHEL but everywhere else is still using tgt IIRC. However, I also am not so sure that it is actually a good idea for people to ship on MariaDB since it is not in the gate. As it diverges from MySQL (starting in earnest with 10.x), there will undoubtedly be subtle issues that arise. So I'd say having MariaDB get tested along with Fedora will actually improve those users' test coverage, which is a good thing. ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [TripleO] Use MariaDB by default on Fedora
Id also like to propose that if we decide against doing this then these elements should not live in tripleo-image-elements. I'm not so sure I agree. We have lio and tgt because lio is on RHEL but everywhere else is still using tgt IIRC. Looks like we do have a cinder-tgt and a cinder-lio which we dont actually use anywhere, so you are correct. The mariadb-galera / percona-cluster elements are much more complex and active though, and seem very likely to have issues with forgetting to or incorrectly porting changes between them. It might also be a moot point if we end up making it a default. :) However, I also am not so sure that it is actually a good idea for people to ship on MariaDB since it is not in the gate. As it diverges from MySQL (starting in earnest with 10.x), there will undoubtedly be subtle issues that arise. So I'd say having MariaDB get tested along with Fedora will actually improve those users' test coverage, which is a good thing. -- Gregory Haynes g...@greghaynes.net ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [TripleO] Use MariaDB by default on Fedora
- Original Message - From: Gregory Haynes g...@greghaynes.net To: openstack-dev openstack-dev@lists.openstack.org Sent: Monday, June 16, 2014 5:49:25 PM Subject: Re: [openstack-dev] [TripleO] Use MariaDB by default on Fedora Id also like to propose that if we decide against doing this then these elements should not live in tripleo-image-elements. I'm not so sure I agree. We have lio and tgt because lio is on RHEL but everywhere else is still using tgt IIRC. Looks like we do have a cinder-tgt and a cinder-lio which we dont actually use anywhere Isn't cinder-tgt used in devtest_overcloud? , so you are correct. The mariadb-galera / percona-cluster elements are much more complex and active though, and seem very likely to have issues with forgetting to or incorrectly porting changes between them. It might also be a moot point if we end up making it a default. :) However, I also am not so sure that it is actually a good idea for people to ship on MariaDB since it is not in the gate. As it diverges from MySQL (starting in earnest with 10.x), there will undoubtedly be subtle issues that arise. So I'd say having MariaDB get tested along with Fedora will actually improve those users' test coverage, which is a good thing. -- Gregory Haynes g...@greghaynes.net ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [TripleO] Use MariaDB by default on Fedora
On 06/16/2014 06:18 PM, Ryan Brady wrote: - Original Message - From: Gregory Haynes g...@greghaynes.net To: openstack-dev openstack-dev@lists.openstack.org Sent: Monday, June 16, 2014 5:49:25 PM Subject: Re: [openstack-dev] [TripleO] Use MariaDB by default on Fedora Id also like to propose that if we decide against doing this then these elements should not live in tripleo-image-elements. I'm not so sure I agree. We have lio and tgt because lio is on RHEL but everywhere else is still using tgt IIRC. Looks like we do have a cinder-tgt and a cinder-lio which we dont actually use anywhere Isn't cinder-tgt used in devtest_overcloud? Yes: http://git.openstack.org/cgit/openstack/tripleo-incubator/tree/scripts/devtest_overcloud.sh#n121 cinder-lio isn't currently used by anything in CI because, as I believe Clint noted, it's for RHEL support, although there's nothing stopping it from being used on other distros too. , so you are correct. The mariadb-galera / percona-cluster elements are much more complex and active though, and seem very likely to have issues with forgetting to or incorrectly porting changes between them. It might also be a moot point if we end up making it a default. :) However, I also am not so sure that it is actually a good idea for people to ship on MariaDB since it is not in the gate. As it diverges from MySQL (starting in earnest with 10.x), there will undoubtedly be subtle issues that arise. So I'd say having MariaDB get tested along with Fedora will actually improve those users' test coverage, which is a good thing. -- Gregory Haynes g...@greghaynes.net ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
