[openstack-dev] [Product] [fuel] Life cycle management use cases

Adam Heczko aheczko at mirantis.com
Fri Oct 16 02:08:52 UTC 2015


Hi All, in regards to lifecycle management I've just submitted blueprint
covering security assessment of OpenStack clouds [0].
Note that it doesn't aim to intersect with Congress project. Congress is
focused on 'overlay' or cloud security policy.
Nessus integration is 100% oriented towards cloud control plane security,
ie. assessment of controller and hypervisor hosts.

[0] https://blueprints.launchpad.net/fuel/+spec/fuel-provision-nessus

On Fri, Oct 16, 2015 at 2:50 AM, Mike Scherbakov <mscherbakov at mirantis.com>
wrote:

> Hi Shamail,
> thank you for letting me know. I didn't come through the page when I was
> googling.
>
> 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.
>
> If you have any work started on underlay, I'll be more than happy to
> collaborate.
>
> PS. Meanwhile we've got lots of feedback in the etherpad, thanks all!
>
> On Wed, Oct 14, 2015 at 3:34 PM Shamail <itzshamail at gmail.com> wrote:
>
>> Great topic...
>>
>> 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).
>>
>> The Product WG would welcome your insights on lifecycle management
>> tremendously.  Please help by posting comments to our existing user
>> story[2].
>>
>>
>> [1] https://wiki.openstack.org/wiki/ProductTeam
>> [2]
>> http://specs.openstack.org/openstack/openstack-user-stories/user-stories/draft/lifecycle_management.html
>>
>> Thanks,
>> Shamail
>>
>> > On Oct 14, 2015, at 5:04 PM, Mike Scherbakov <mscherbakov at mirantis.com>
>> wrote:
>> >
>> > Hi fuelers,
>> > 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.
>> >
>> > 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.
>> >
>> > I started to collect use cases in the etherpad:
>> https://etherpad.openstack.org/p/lcm-use-cases.
>> >
>> > Please contribute in there.
>> >
>> > Thank you,
>> > --
>> > Mike Scherbakov
>> > #mihgen
>> >
>> __________________________________________________________________________
>> > OpenStack Development Mailing List (not for usage questions)
>> > Unsubscribe:
>> OpenStack-dev-request at lists.openstack.org?subject:unsubscribe
>> > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>> _______________________________________________
>> Product-wg mailing list
>> Product-wg at lists.openstack.org
>> http://lists.openstack.org/cgi-bin/mailman/listinfo/product-wg
>>
> --
> Mike Scherbakov
> #mihgen
>
> __________________________________________________________________________
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: OpenStack-dev-request at lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
>


-- 
Adam Heczko
Security Engineer @ Mirantis Inc.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20151016/0eaba096/attachment.html>


More information about the OpenStack-dev mailing list