<div dir="ltr">Hi All, in regards to lifecycle management I've just submitted blueprint covering security assessment of OpenStack clouds [0].<div>Note that it doesn't aim to intersect with Congress project. Congress is focused on 'overlay' or cloud security policy.</div><div>Nessus integration is 100% oriented towards cloud control plane security, ie. assessment of controller and hypervisor hosts.</div><div><br></div><div><div>[0] <a href="https://blueprints.launchpad.net/fuel/+spec/fuel-provision-nessus">https://blueprints.launchpad.net/fuel/+spec/fuel-provision-nessus</a><br></div></div></div><div class="gmail_extra"><br><div class="gmail_quote">On Fri, Oct 16, 2015 at 2:50 AM, Mike Scherbakov <span dir="ltr"><<a href="mailto:mscherbakov@mirantis.com" target="_blank">mscherbakov@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 Shamail,<div>thank you for letting me know. <span style="line-height:1.5">I didn't come through the page when I was googling.</span></div><div><span style="line-height:1.5"><br></span></div><div><span style="line-height:1.5">We are collecting use cases though for underlay, so it's more relevant for such projects as Fuel, TripleO, Puppet OpenStack; than for VM, DB, etc. related management.</span></div><div><span style="line-height:1.5"><br></span></div><div><span style="line-height:1.5">If you have any work started on underlay, I'll be more than happy to collaborate.</span></div><div><span style="line-height:1.5"><br></span></div><div><span style="line-height:1.5">PS. Meanwhile we've got lots of feedback in the etherpad, thanks all!</span></div></div><br><div class="gmail_quote"><div><div class="h5"><div dir="ltr">On Wed, Oct 14, 2015 at 3:34 PM Shamail <<a href="mailto:itzshamail@gmail.com" target="_blank">itzshamail@gmail.com</a>> wrote:<br></div></div></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div><div class="h5">Great topic...<br>
<br>
Please note that the Product WG[1] also has a user story focused on Lifecycle Management. While FUEL is one aspect of the overall workflow, we would also like the team to consider project level enhancements (e.g. garbage collection inside the DB).<br>
<br>
The Product WG would welcome your insights on lifecycle management tremendously. Please help by posting comments to our existing user story[2].<br>
<br>
<br>
[1] <a href="https://wiki.openstack.org/wiki/ProductTeam" rel="noreferrer" target="_blank">https://wiki.openstack.org/wiki/ProductTeam</a><br>
[2] <a href="http://specs.openstack.org/openstack/openstack-user-stories/user-stories/draft/lifecycle_management.html" rel="noreferrer" target="_blank">http://specs.openstack.org/openstack/openstack-user-stories/user-stories/draft/lifecycle_management.html</a><br>
<br>
Thanks,<br>
Shamail<br>
<br>
> On Oct 14, 2015, at 5:04 PM, Mike Scherbakov <<a href="mailto:mscherbakov@mirantis.com" target="_blank">mscherbakov@mirantis.com</a>> wrote:<br>
><br>
> Hi fuelers,<br>
> as we all know, Fuel lacks many of life cycle management (LCM) use cases. It becomes a very hot issue for many of our users, as current LCM capabilities are not very rich.<br>
><br>
> In order to think how we can fix it, we need to collect use cases first, and prioritize them if needed. So that whatever a change in architecture we are about to make, we would need to ensure that we meet LCM use cases or have a proposal how to close it in a foreseeable future.<br>
><br>
> I started to collect use cases in the etherpad: <a href="https://etherpad.openstack.org/p/lcm-use-cases" rel="noreferrer" target="_blank">https://etherpad.openstack.org/p/lcm-use-cases</a>.<br>
><br>
> Please contribute in there.<br>
><br>
> Thank you,<br>
> --<br>
> Mike Scherbakov<br>
> #mihgen<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></div></div>
_______________________________________________<br>
Product-wg mailing list<br>
<a href="mailto:Product-wg@lists.openstack.org" target="_blank">Product-wg@lists.openstack.org</a><br>
<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/product-wg" rel="noreferrer" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/product-wg</a><span class="HOEnZb"><font color="#888888"><br>
</font></span></blockquote></div><span class="HOEnZb"><font color="#888888"><div dir="ltr">-- <br></div><div dir="ltr">Mike Scherbakov<br>#mihgen</div>
</font></span><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><br clear="all"><div><br></div>-- <br><div class="gmail_signature"><div dir="ltr"><div style="color:rgb(136,136,136);font-size:12.8000001907349px">Adam Heczko</div><div style="color:rgb(136,136,136);font-size:12.8000001907349px">Security Engineer @ Mirantis Inc.</div></div></div>
</div>