<div dir="ltr"><div class="gmail_default" style="font-family:courier new,monospace"><br></div><div class="gmail_extra"><br><br><div class="gmail_quote">On Fri, Jul 25, 2014 at 7:59 AM, John Griffith <span dir="ltr"><<a href="mailto:john.griffith@solidfire.com" target="_blank">john.griffith@solidfire.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><div style="font-family:courier new,monospace"><br></div><div class="gmail_extra"><div><div class="h5">
<br>
<br><div class="gmail_quote">On Fri, Jul 25, 2014 at 7:38 AM, Kerrin, Michael <span dir="ltr"><<a href="mailto:michael.kerrin@hp.com" target="_blank">michael.kerrin@hp.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Coming back to this.<br>
<br>
I have updated the review <a href="https://review.openstack.org/#/c/90134/" target="_blank">https://review.openstack.org/#<u></u>/c/90134/</a> 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.<br>
<br>
Then following the mariadb integration I would like to get this <a href="https://review.openstack.org/#/c/109415/" target="_blank">https://review.openstack.org/#<u></u>/c/109415/</a> 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.<br>
<br>
Looking forward to any feedback,<br>
<br>
Michael<div><div><br>
<br>
On 09 July 2014 14:44:15, Sullivan, Jon Paul wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
-----Original Message-----<br>
From: Giulio Fidente [mailto:<a href="mailto:gfidente@redhat.com" target="_blank">gfidente@redhat.com</a>]<br>
Sent: 04 July 2014 14:37<br>
To: OpenStack Development Mailing List (not for usage questions)<br>
Subject: Re: [openstack-dev] [TripleO] Use MariaDB by default on Fedora<br>
<br>
On 07/01/2014 05:47 PM, Michael Kerrin wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
I propose making mysql an abstract element and user must choose either<br>
percona or mariadb-rpm element.CI must be setup correctly<br>
</blockquote>
<br>
+1<br>
<br>
seems a cleaner and more sustainable approach<br>
</blockquote>
<br>
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).<br>
<br>
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.<br>
<br>
This would not prevent the sharing of common code through a differently-named element, such as mysql-common.<br>
<br>
<br>
[1] see comments on April 10th in <a href="https://review.openstack.org/#/c/85776/" target="_blank">https://review.openstack.org/#<u></u>/c/85776/</a><br>
<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
--<br>
Giulio Fidente<br>
GPG KEY: 08D733BA<br>
<br>
______________________________<u></u>_________________<br>
OpenStack-dev mailing list<br>
<a href="mailto:OpenStack-dev@lists.openstack.org" target="_blank">OpenStack-dev@lists.openstack.<u></u>org</a><br>
<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" target="_blank">http://lists.openstack.org/<u></u>cgi-bin/mailman/listinfo/<u></u>openstack-dev</a><br>
</blockquote>
<br>
Thanks,<br>
Jon-Paul Sullivan ☺ Cloud Services - @hpcloud<br>
<br>
Postal Address: Hewlett-Packard Galway Limited, Ballybrit Business Park, Galway.<br>
Registered Office: Hewlett-Packard Galway Limited, 63-74 Sir John Rogerson's Quay, Dublin 2.<br>
Registered Number: 361933<br>
<br>
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.<br>
<br>
To any recipient of this message within HP, unless otherwise stated, you should consider this message and attachments as "HP CONFIDENTIAL".<br>
______________________________<u></u>_________________<br>
OpenStack-dev mailing list<br>
<a href="mailto:OpenStack-dev@lists.openstack.org" target="_blank">OpenStack-dev@lists.openstack.<u></u>org</a><br>
<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" target="_blank">http://lists.openstack.org/<u></u>cgi-bin/mailman/listinfo/<u></u>openstack-dev</a><br>
</blockquote>
<br>
______________________________<u></u>_________________<br>
OpenStack-dev mailing list<br>
<a href="mailto:OpenStack-dev@lists.openstack.org" target="_blank">OpenStack-dev@lists.openstack.<u></u>org</a><br>
<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" target="_blank">http://lists.openstack.org/<u></u>cgi-bin/mailman/listinfo/<u></u>openstack-dev</a></div></div></blockquote><div> </div></div></div>
</div><div style="font-family:'courier new',monospace">
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.</div>
<div style="font-family:'courier new',monospace"><br></div><div style="font-family:'courier new',monospace">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?</div>
<div style="font-family:'courier new',monospace"><br></div><div style="font-family:'courier new',monospace">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.<br>
</div><br></div></div></blockquote><div class="gmail_default" style="font-family:'courier new',monospace">Oh.. before the CD flames come my way, yes I know that's something somebody was interested in.</div>
</div><br></div></div>