<div dir="ltr">I agree with Evgeniy on this we should be able to build the your test, env easily enough to accommodate this. If we cant then we should spend time there since AFAICT it overlaps with user ask<br><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">
1. Disable authentication<br></blockquote><div>we should be able to set them to a known option with a config drive or metadata service. This isn't the first time that we've needed to get more complicated with the fuel master deployment automation </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">2. Development packages should be added (nc, iperf, tcpdump, systemtap)<br>
</blockquote><div>They should be available on the iso to install if you need them. If not create a bug for it </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">
3. Extra verbosity should be turned on. CoreDumps should be enabled and analyzed.<br></blockquote><div>Debug should come on by default, this could be a config drive option to update the openstack.json data </div><div><br>
</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">4. Special OpenStack flavors (m1.tiny should be 128MB instead of 512MB)<br>
</blockquote><div>I thought we where going to do this for test env's? already</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">
5. Additional messages in REST/JSON or any other API</blockquote><div>I'm not sure what is lacking here, can you explain more? </div></div><div class="gmail_extra"><br><br><div class="gmail_quote">On Wed, Jul 9, 2014 at 2:40 AM, Evgeniy L <span dir="ltr"><<a href="mailto:eli@mirantis.com" target="_blank">eli@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">Hi Sergii,<div><br></div><div>Sorry, but I don't like the idea of creating yet another type of iso, it will complicate debugging process (because of different environments).</div>
<div><br></div><div><span style="font-family:arial,sans-serif;font-size:13px">Disable authentication - if we have a feature, we should not disable it, during the development we need to make sure that this feature works fine with any other features which we are working on.</span><br>
</div><div><span style="font-family:arial,sans-serif;font-size:13px"><br></span></div><div><font face="arial, sans-serif">If we want to solve this problem, I think it will be better to create some scripts to make your env more developer friendly i.e. install nc, iperf, tcpdump, systemtap.</font></div>
</div><div class="gmail_extra"><br><br><div class="gmail_quote"><div><div class="h5">On Tue, Jul 8, 2014 at 11:39 PM, Sergii Golovatiuk <span dir="ltr"><<a href="mailto:sgolovatiuk@mirantis.com" target="_blank">sgolovatiuk@mirantis.com</a>></span> wrote:<br>
</div></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div><div class="h5"><div dir="ltr"><div>Hi crew,<br><br>There is no functioning "dev" mode as of right now in the Fuel ISO build. Authentication feature makes developer's life even more painful. A lot of tests must be rewritten to pass authentication. Manual testing will be slowed down as it will require additional steps. This complicates many things we do. "Dev" mode should slightly modify ISO for development use. Here are the features we should turn on in 'dev" mode<br>
<br></div><div>1. Disable authentication<br></div><div>2. Development packages should be added (nc, iperf, tcpdump, systemtap)<br></div><div>3. Extra verbosity should be turned on. CoreDumps should be enabled and analyzed.<br>
</div><div>4. Special OpenStack flavors (m1.tiny should be 128MB instead of 512MB)<br></div><div>5. Additional messages in REST/JSON or any other API<br><br></div><div>If you have anything to add please bring that to our attention so we'll try to cover your wishlist in blueprint.<br>
<br></div><div>Thank you.<br></div><div><div><div><div dir="ltr">--<br>
Best regards,<br>
Sergii Golovatiuk,<br>
Skype #golserge<br>
IRC #holser<br></div></div>
</div></div></div>
<br></div></div>_______________________________________________<br>
OpenStack-dev mailing list<br>
<a href="mailto:OpenStack-dev@lists.openstack.org" target="_blank">OpenStack-dev@lists.openstack.org</a><br>
<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><br>
<br></blockquote></div><br></div>
<br>_______________________________________________<br>
OpenStack-dev mailing list<br>
<a href="mailto:OpenStack-dev@lists.openstack.org">OpenStack-dev@lists.openstack.org</a><br>
<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><br>
<br></blockquote></div><br><br clear="all"><div><br></div>-- <br><div dir="ltr">Andrew<div>Mirantis</div><div>Ceph community</div></div>
</div>