<html><head><meta http-equiv="content-type" content="text/html; charset=utf-8"></head><body dir="auto"><div><div style="direction: inherit;">Production ready will not be deployed from source. </div><div style="direction: inherit;"><br></div><div style="direction: inherit;">Just my 2 cents. </div><br>Inviato da iPhone</div><div><br>Il giorno 02 ott 2016, alle ore 18:36, Amrith Kumar <<a href="mailto:amrith@tesora.com">amrith@tesora.com</a>> ha scritto:<br><br></div><blockquote type="cite"><div><span></span><br><span></span><br><blockquote type="cite"><span>-----Original Message-----</span><br></blockquote><blockquote type="cite"><span>From: Turbo Fredriksson [<a href="mailto:turbo@bayour.com">mailto:turbo@bayour.com</a>]</span><br></blockquote><blockquote type="cite"><span>Sent: Sunday, October 02, 2016 10:13 AM</span><br></blockquote><blockquote type="cite"><span>To: openstack List <<a href="mailto:openstack@lists.openstack.org">openstack@lists.openstack.org</a>></span><br></blockquote><blockquote type="cite"><span>Subject: Re: [Openstack] Trove MySQL v5.[67] images?</span><br></blockquote><blockquote type="cite"><span></span><br></blockquote><blockquote type="cite"><span>On Oct 2, 2016, at 2:00 AM, Amrith Kumar wrote:</span><br></blockquote><blockquote type="cite"><span></span><br></blockquote><blockquote type="cite"><blockquote type="cite"><span>I recall from our conversation that you didn't "trust all these *stack</span><br></blockquote></blockquote><blockquote type="cite"><span>builders".</span><br></blockquote><blockquote type="cite"><blockquote type="cite"><span>If you are now using a system that is devstack based these images could</span><br></blockquote></blockquote><blockquote type="cite"><span>help.</span><br></blockquote><blockquote type="cite"><span></span><br></blockquote><blockquote type="cite"><span>I still don't do that, it's all hand crafted from scratch. Well, almost -</span><br></blockquote><blockquote type="cite"><span>I still use packages (which do _A LOT_ of the .. 'boring, simple' setup</span><br></blockquote><blockquote type="cite"><span>for me) but that'll change next time. Next time I'm doing it from source</span><br></blockquote><blockquote type="cite"><span>(because I'm embarrassed by the quality of the packages - I did a small</span><br></blockquote><blockquote type="cite"><span>upgrade a few months ago and absolutly everything broke, I had to</span><br></blockquote><blockquote type="cite"><span>completely</span><br></blockquote><blockquote type="cite"><span>reinstall the controller)!</span><br></blockquote><blockquote type="cite"><span></span><br></blockquote><blockquote type="cite"><span>That's the only way _I_ can learn! Others might be different and I respect</span><br></blockquote><blockquote type="cite"><span>that, but _I_ need to do this from scratch ("the hard way" if you like) to</span><br></blockquote><blockquote type="cite"><span>be able to gain anything from this - the point wasn't just to "get a test</span><br></blockquote><blockquote type="cite"><span>setup of Openstack up and running" or "setup a test so I can look at it"</span><br></blockquote><blockquote type="cite"><span>but actually setting up a production-like system and to be able to</span><br></blockquote><blockquote type="cite"><span>administrate it and especially fix problems if (when!) they arise! AND to</span><br></blockquote><blockquote type="cite"><span>gain knowledge on how all this works together.</span><br></blockquote><blockquote type="cite"><span></span><br></blockquote><blockquote type="cite"><span></span><br></blockquote><span></span><br><span>[amrith] As I said in IRC, one doesn't begin a career in aviation by attempting to land a Tomcat on an aircraft carrier in rough seas, but you felt that it would be "fun". I hope you are having "fun".</span><br><span></span><br><blockquote type="cite"><span>It's been the worst few months in my life (and it's been a long life :)</span><br></blockquote><blockquote type="cite"><span>with almost 24/7 work on getting this in the state it is now, but now that</span><br></blockquote><blockquote type="cite"><span>almost everything works the way I want it, I feel a great satisfaction and</span><br></blockquote><blockquote type="cite"><span>my knowledge of "The Cloud ((tm))" have been greatly improved and I almost</span><br></blockquote><blockquote type="cite"><span>feel</span><br></blockquote><blockquote type="cite"><span>I can put "Cloud Expert Extraordinair" on the CV :D :D.</span><br></blockquote><blockquote type="cite"><span></span><br></blockquote><blockquote type="cite"><span>I wouldn't recommend this to anyone 'green', but anyone that's already</span><br></blockquote><blockquote type="cite"><span>bald</span><br></blockquote><blockquote type="cite"><span>(there's going to be a lot of 'hair tearing' and 'head scratching' :) and</span><br></blockquote><blockquote type="cite"><span>those that have a 'bigger purpose' than the immediate setup, oh yeah!</span><br></blockquote><blockquote type="cite"><span></span><br></blockquote><blockquote type="cite"><blockquote type="cite"><span>[1]</span><br></blockquote></blockquote><blockquote type="cite"><span><a href="http://docs.openstack.org/developer/trove/dev/building_guest_images.html">http://docs.openstack.org/developer/trove/dev/building_guest_images.html</a></span><br></blockquote><blockquote type="cite"><span></span><br></blockquote><blockquote type="cite"><span>Tried that for over a week. Failed so miserably, it's embarrassing!</span><br></blockquote><blockquote type="cite"><span>Don't know if it's me, the docs or the image builder..</span><br></blockquote><blockquote type="cite"><span></span><br></blockquote><blockquote type="cite"><span>But I do remember that even if (when!) I followed the documentations _to</span><br></blockquote><blockquote type="cite"><span>the</span><br></blockquote><blockquote type="cite"><span>letter_, it still failed.</span><br></blockquote><blockquote type="cite"><span></span><br></blockquote><blockquote type="cite"><span>Also, some versions of the image builder worked better than others (but I</span><br></blockquote><blockquote type="cite"><span>could</span><br></blockquote><blockquote type="cite"><span>not figure out the exact version used by the documenter), so it would be</span><br></blockquote><blockquote type="cite"><span>beneficial to specify the exact versions used when writing the</span><br></blockquote><blockquote type="cite"><span>documentation.</span><br></blockquote><blockquote type="cite"><span></span><br></blockquote><blockquote type="cite"><span></span><br></blockquote><blockquote type="cite"><span>And have someone that never done it before do a run-through first - I know</span><br></blockquote><blockquote type="cite"><span>from personal experience that you get .. 'code blind' (for lack of a</span><br></blockquote><blockquote type="cite"><span>better</span><br></blockquote><blockquote type="cite"><span>word) when you've worked with a project and try to write the docs - some</span><br></blockquote><blockquote type="cite"><span>things</span><br></blockquote><blockquote type="cite"><span>you know 'subconsciously' don't work (or work only in a specific use-case</span><br></blockquote><blockquote type="cite"><span>etc)</span><br></blockquote><blockquote type="cite"><span>and then 'automatically' leave that information out..</span><br></blockquote><blockquote type="cite"><span></span><br></blockquote><blockquote type="cite"><span>That is why [good] companies _NEVER_ (ever!!) allow the coders/admins to</span><br></blockquote><blockquote type="cite"><span>go</span><br></blockquote><blockquote type="cite"><span>any where _near_ the documentation! In a open source community, that is</span><br></blockquote><blockquote type="cite"><span>unfortunately almost never an option, but it can be mitigated somewhat by</span><br></blockquote><blockquote type="cite"><span>having other people in the community do a run-through.</span><br></blockquote><blockquote type="cite"><span></span><br></blockquote><blockquote type="cite"><blockquote type="cite"><span>[2] <a href="http://docs.openstack.org/developer/trove/dev/guest_cloud_init.html">http://docs.openstack.org/developer/trove/dev/guest_cloud_init.html</a></span><br></blockquote></blockquote><blockquote type="cite"><span></span><br></blockquote><blockquote type="cite"><span>I can vaguely remember that. I know it failed, but can't remember the</span><br></blockquote><blockquote type="cite"><span>details.</span><br></blockquote><blockquote type="cite"><span></span><br></blockquote><blockquote type="cite"><blockquote type="cite"><span>[3] <a href="https://review.openstack.org/#/c/374952/">https://review.openstack.org/#/c/374952/</a></span><br></blockquote></blockquote><blockquote type="cite"><span></span><br></blockquote><blockquote type="cite"><span>That look quite interesting, thanx. I'll try again..</span><br></blockquote><blockquote type="cite"><span></span><br></blockquote><blockquote type="cite"><span>"If you don't succeed, try and try [and try and try ..] again!" :)</span><br></blockquote><blockquote type="cite"><span></span><br></blockquote><blockquote type="cite"><blockquote type="cite"><span>OpenStack has guest images suitable for use with devstack[4]</span><br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><span>[4] <a href="http://tarballs.openstack.org/trove/images/">http://tarballs.openstack.org/trove/images/</a></span><br></blockquote></blockquote><blockquote type="cite"><span></span><br></blockquote><blockquote type="cite"><span>What does that actually mean? Is it not possible to use these images other</span><br></blockquote><blockquote type="cite"><span>than with devstack? An instance image should be a unique, separate</span><br></blockquote><span></span><br><span>[amrith] The paragraph</span><br><span></span><br><span>"OpenStack has guest images suitable for use with devstack[4] (available for download at <a href="http://tarballs.openstack.org">tarballs.openstack.org</a>) but that would require a devstack based system and I recall from our conversation that you didn't "trust all these *stack builders". If you are now using a system that is devstack based these images could help."</span><br><span></span><br><span>always amounts to the following; if you are using a devstack based system these may help. But since you insist on not doing that, I can only hope that you have "fun". I'd like to help you but you have sought not to take any of it, so there is little else I can do.</span><br><span></span><br><blockquote type="cite"><span>instance</span><br></blockquote><blockquote type="cite"><span>right?</span><br></blockquote><blockquote type="cite"><span>_______________________________________________</span><br></blockquote><blockquote type="cite"><span>Mailing list: <a href="http://lists.openstack.org/cgi-">http://lists.openstack.org/cgi-</a></span><br></blockquote><blockquote type="cite"><span>bin/mailman/listinfo/openstack</span><br></blockquote><blockquote type="cite"><span>Post to : <a href="mailto:openstack@lists.openstack.org">openstack@lists.openstack.org</a></span><br></blockquote><blockquote type="cite"><span>Unsubscribe : <a href="http://lists.openstack.org/cgi-">http://lists.openstack.org/cgi-</a></span><br></blockquote><blockquote type="cite"><span>bin/mailman/listinfo/openstack</span><br></blockquote><span></span><br><span>_______________________________________________</span><br><span>Mailing list: <a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack</a></span><br><span>Post to : <a href="mailto:openstack@lists.openstack.org">openstack@lists.openstack.org</a></span><br><span>Unsubscribe : <a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack</a></span><br><span></span><br><span>!DSPAM:1,57f13a96176139535417096!</span><br><span></span><br></div></blockquote></body></html>