Re: [openstack-dev] [nova][barbican][security] Ocata design summit session change

[Dave McCowan (dmccowan)]

Thanks Matt.
Cross-project CI testing is something the Barbican team is very interested
in.
I'll make sure we have representation.

On 10/13/16, 4:15 PM, "Matt Riedemann"  wrote:

>I've changed the nova design summit session on docs needed for newton to
>now be a session to cover the various security-related specs up for
>review:
>
>https://www.openstack.org/summit/barcelona-2016/summit-schedule/events/169
>77/nova-security-specs-and-testing
>
>And to also talk about getting a CI job going which will test some of
>these features, like with barbican as the key manager and using signed
>images.
>
>I've tagged this session with 'barbican' although I see that the
>barbican team is having another session at the same time. There was one
>other slot that I could have moved for nova but barbican had a conflict
>then too, so I've just left this where it is and if anyone from barbican
>can show up all the better, but I don't think it's necessarily a
>requirement.
>
>-- 
>
>Thanks,
>
>Matt Riedemann
>
>
>__
>OpenStack Development Mailing List (not for usage questions)
>Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
>http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev


__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [nova][barbican][security] Ocata design summit session change

[Rob C]

Thanks for the heads up, I'll do my best to attend and I'll encourage other
security folks to do likewise.

It looks like there's a good deal of security enforcing functionality in
these specs, I knew we've discussed getting Octa through threat analysis,
lets try to find a good time to schedule that too.

Cheers
-Rob

On Thu, Oct 13, 2016 at 9:15 PM, Matt Riedemann 
wrote:

> I've changed the nova design summit session on docs needed for newton to
> now be a session to cover the various security-related specs up for review:
>
> https://www.openstack.org/summit/barcelona-2016/summit-sched
> ule/events/16977/nova-security-specs-and-testing
>
> And to also talk about getting a CI job going which will test some of
> these features, like with barbican as the key manager and using signed
> images.
>
> I've tagged this session with 'barbican' although I see that the barbican
> team is having another session at the same time. There was one other slot
> that I could have moved for nova but barbican had a conflict then too, so
> I've just left this where it is and if anyone from barbican can show up all
> the better, but I don't think it's necessarily a requirement.
>
> --
>
> Thanks,
>
> Matt Riedemann
>
>
> __
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

[openstack-dev] [nova][barbican][security] Ocata design summit session change

[Matt Riedemann]

I've changed the nova design summit session on docs needed for newton to 
now be a session to cover the various security-related specs up for review:


https://www.openstack.org/summit/barcelona-2016/summit-schedule/events/16977/nova-security-specs-and-testing

And to also talk about getting a CI job going which will test some of 
these features, like with barbican as the key manager and using signed 
images.


I've tagged this session with 'barbican' although I see that the 
barbican team is having another session at the same time. There was one 
other slot that I could have moved for nova but barbican had a conflict 
then too, so I've just left this where it is and if anyone from barbican 
can show up all the better, but I don't think it's necessarily a 
requirement.


--

Thanks,

Matt Riedemann


__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev