<div dir="ltr"><div class="gmail_default" style="font-family:monospace,monospace">Alex, </div><div class="gmail_default" style="font-family:monospace,monospace"><br></div><div class="gmail_default" style="font-family:monospace,monospace">>This should have been created before removing the thing providing this information previously.</div><div class="gmail_default" style="font-family:monospace,monospace"><br></div><div class="gmail_default" style="font-family:monospace,monospace">Once again, using version.yaml you could NOT reproduce the env, because what was really installed on the Fuel node had nothing in common with what it was written in version.yaml. The information you think was actual was, in fact, not actual.</div><div class="gmail_default" style="font-family:monospace,monospace"><br></div><div class="gmail_default" style="font-family:monospace,monospace">Having 'shotgun report' output you can see real SHA sums, not ephemeral (like in version.yaml).</div><div class="gmail_default" style="font-family:monospace,monospace"><br></div><div class="gmail_default" style="font-family:monospace,monospace">And without removal version.yaml we could not implement some features in make system, so, this new build/test package based approach could not have been implemented before version.yaml removal. We are moving towards better developer experience NOT making things worse. In fact version.yaml removal and substitution it with 'shotgun report' was a fix for broken version.yaml content. </div><div class="gmail_default" style="font-family:monospace,monospace"><br></div><div class="gmail_default" style="font-family:monospace,monospace">As for attaching short report to bugs instead of long report, I don't know what motivation was for this change except their convenience. Probably short report is to be used for internal QA team purposes only.</div><div class="gmail_default" style="font-family:monospace,monospace"><br></div><div class="gmail_default" style="font-family:monospace,monospace"><br></div><div class="gmail_default" style="font-family:monospace,monospace"><br></div><div class="gmail_default" style="font-family:monospace,monospace"><br></div></div><div class="gmail_extra"><br clear="all"><div><div class="gmail_signature"><div>Vladimir Kozhukalov</div></div></div>
<br><div class="gmail_quote">On Mon, Mar 21, 2016 at 11:20 PM, Alex Schultz <span dir="ltr"><<a href="mailto:aschultz@mirantis.com" target="_blank">aschultz@mirantis.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 class="gmail_extra"><br><div class="gmail_quote"><span class="">On Mon, Mar 21, 2016 at 1:59 PM, Vladimir Kozhukalov <span dir="ltr"><<a href="mailto:vkozhukalov@mirantis.com" target="_blank">vkozhukalov@mirantis.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex"><div dir="ltr"><div style="font-family:monospace,monospace">Alex,</div><div style="font-family:monospace,monospace"><br></div><div style="font-family:monospace,monospace">That is just a short report that QA team needs for their convenience. Please consider this letter as just FYI, nothing more. </div><div style="font-family:monospace,monospace"><br></div></div></blockquote><div><br></div></span><div>If a bug only contains the short report, how do we work on fixing the bug? My question is valid and should be answered. What good is this information if I cannot reproduce an environment with this information? How does one translate or locate specific package versions for reproducing issues? Is this documented? If not, will it be? I'd like to know what the point of this short report is since I'm not sure how it could be consumed by QA/Devs? </div><span class=""><div><br></div><div> </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex"><div dir="ltr"><div style="font-family:monospace,monospace"></div><div style="font-family:monospace,monospace">'shotgun report' allows you to see commit SHA from which a package was built. It is even more information than it was available in version.yaml and this information is actual unlike the content of version.yaml.</div><div style="font-family:monospace,monospace"><br></div><div style="font-family:monospace,monospace">I know you were opposing getting rid of version.yaml but the thing is Fuel now can be installed on any CentOS 7.2 node directly from RPM repository. You don't even need the Fuel ISO, and thus version.yaml could not be an artifact that we could rely on (no ISO build id any more, no sha sums). Instead, now we rely on packages that are currently installed on the master node. The only issue with this approach is the ability to easily reproduce the env having just this list of packages attached to a bug. But it is not worse that it was with version.yaml. </div><div style="font-family:monospace,monospace"><br></div></div></blockquote><div><br></div></span><div>I was only opposed to getting rid of it without a proper replacement which is why I keep asking the same questions as an equivalent replacement does not seem to exist. Also it is much worse now that we don't have version.yaml because I may have no way to locate these mystical package versions that keep getting reported. At least with git hashes I could at least look at the same code base across everything. Now without this information I have no way of building a complete picture of the code being utilized in the environment.</div><span class=""><div> </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex"><div dir="ltr"><div style="font-family:monospace,monospace"></div><div style="font-family:monospace,monospace">I'm currently working on design draft about modular data driven functional testing. This could also help for troubleshooting. In a nutshell the developer experience will be like: </div><div style="font-family:monospace,monospace"> 1) you look at log files (`shotgun dump`) and roughly locate the issue (that allows you to choose respective test case) </div><div style="font-family:monospace,monospace"> 2) you run script passing some data to it (data are to come from 'shotgun report --machinereadable' or smth like this) </div><div style="font-family:monospace,monospace"> 3) this script builds testing/experimental env for you (env is to include only those components that are respective to chosen test case)</div><div style="font-family:monospace,monospace"> 5) you run some tests against this lab and manually do some experiments to kill the bug</div><span><font color="#888888"><div style="font-family:monospace,monospace"><br></div><div style="font-family:monospace,monospace"> <br></div></font></span></div></blockquote><div><br></div></span><div>This should have been created before removing the thing providing this information previously. Yes I know I sound like a broken record on this, but it's very hard to address issues if you cannot reproduce the environment they occur on. I'm trying to make sure we are providing all the information to aid in reproducing issues to get them fixed and not just providing more information that is ultimately ignored because it's useless.</div><div><br></div><div>Thanks,</div><div>-Alex</div><span class=""><div> </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex"><div dir="ltr"><span><font color="#888888"><div style="font-family:monospace,monospace"></div><div style="font-family:monospace,monospace"><br></div></font></span></div><div class="gmail_extra"><span><font color="#888888"><br clear="all"><div><div><div>Vladimir Kozhukalov</div></div></div></font></span><div><div>
<br><div class="gmail_quote">On Mon, Mar 21, 2016 at 5:28 PM, Alex Schultz <span dir="ltr"><<a href="mailto:aschultz@mirantis.com" target="_blank">aschultz@mirantis.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex"><div dir="ltr"><br><div class="gmail_extra"><br><div class="gmail_quote"><span>On Mon, Mar 21, 2016 at 7:21 AM, Volodymyr Shypyguzov <span dir="ltr"><<a href="mailto:vshypyguzov@mirantis.com" target="_blank">vshypyguzov@mirantis.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex"><div dir="ltr"><div class="gmail_quote"><div dir="ltr"><div><div><div><div>Hi, all<br><br></div>Just wanted to inform you, that shotgun2 now has new command short-report, which allows you to receive shorter and cleaner output for attaching to bug description, sharing, etc.<br><br></div>Usage: shotgun2 short-report<br></div>Example output: <a href="http://paste.openstack.org/show/491256/" target="_blank">http://paste.openstack.org/show/491256/</a><br><br></div></div></div></div></blockquote><div><br></div></span><div>How will we be able to find those specific packages and how will we be able to correlate them with the equivalent commit in the git repository?<br></div><div><br></div><div>Thanks,</div><div>-Alex</div><div> </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex"><div dir="ltr"><div class="gmail_quote"><div dir="ltr"><div></div><div>Regards,<br></div><div>Volodymyr<br></div></div></div></div>
<br>__________________________________________________________________________<br>
OpenStack Development Mailing List (not for usage questions)<br>
Unsubscribe: <a href="http://OpenStack-dev-request@lists.openstack.org?subject:unsubscribe" rel="noreferrer" target="_blank">OpenStack-dev-request@lists.openstack.org?subject:unsubscribe</a><br>
<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" rel="noreferrer" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><br>
<br></blockquote></div><br></div></div>
<br>__________________________________________________________________________<br>
OpenStack Development Mailing List (not for usage questions)<br>
Unsubscribe: <a href="http://OpenStack-dev-request@lists.openstack.org?subject:unsubscribe" rel="noreferrer" target="_blank">OpenStack-dev-request@lists.openstack.org?subject:unsubscribe</a><br>
<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" rel="noreferrer" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><br>
<br></blockquote></div><br></div></div></div>
<br>__________________________________________________________________________<br>
OpenStack Development Mailing List (not for usage questions)<br>
Unsubscribe: <a href="http://OpenStack-dev-request@lists.openstack.org?subject:unsubscribe" rel="noreferrer" target="_blank">OpenStack-dev-request@lists.openstack.org?subject:unsubscribe</a><br>
<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" rel="noreferrer" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><br>
<br></blockquote></span></div><br></div></div>
<br>__________________________________________________________________________<br>
OpenStack Development Mailing List (not for usage questions)<br>
Unsubscribe: <a href="http://OpenStack-dev-request@lists.openstack.org?subject:unsubscribe" rel="noreferrer" target="_blank">OpenStack-dev-request@lists.openstack.org?subject:unsubscribe</a><br>
<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" rel="noreferrer" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><br>
<br></blockquote></div><br></div>