Solum community,
I am pleased to announce an early preview of the Solum M2 Demo via Vagrant
for those who want to take a look. We created detailed instructions to
install the demo here:
https://wiki.openstack.org/wiki/Solum/solum_m2_demo
Disclaimers:
Please examine the look and feel right now
Maybe a crazy idea butŠ
What if we simply don't store the JSON blob data for M1 instead of putting
storing it in a way we don't like long term? This way, there is no need
to remember to change something later even though a bug could be created
anyways. I believe the fields that would be missing/
Solum community,
I notice that we are using String(36) UUID values in the database schema as
primary key for many new tables that we are creating. For example:
https://review.openstack.org/#/c/68328/10/solum/objects/sqlalchemy/application.py
Proposal: Add an int or bigint ID as the primary key,
Solum community,
I created several different approaches for community consideration
regarding Solum context, logging and data confidentiality. Two of these
approaches are documented here:
https://wiki.openstack.org/wiki/Solum/Logging
A) Plain Oslo Log/Config/Context is in the "Example of Oslo L
Thanks Clayton! I added your new content.
To all:
The OpenStack Security Guide is a very good resource to read -
http://docs.openstack.org/security-guide/content/openstack_user_guide.html
Apologies for not being up to speed on how things work in OpenStack yet
but here is a list of topics that I
With the comments that we've received, I would recommend that Clayton
remove the option to select the MySQL storage engine from Oslo config and
just "hardcode" InnoDB. I believe it entails just removing a few lines of
code. It doesn't sound like anyone has a reason to use any other storage
engine
TLDR: Should Solum log a warning if operators do not use the InnoDB
storage engine with MySQL in Solum's control plane?
Details:
I was looking at: https://review.openstack.org/#/c/57024/
Models.py to be specific.
The default storage engine is InnoDB for MySQL which is good. I took a
quick look
I agree. With many optional parameters possible, positional parameters
would seem to complicate things a bit (even for end users).
On 12/3/13 8:14 AM, "Arati Mahimane" wrote:
>
>
>On 12/3/13 7:51 AM, "Roshan Agrawal" wrote:
>
>>
>>
>>> -Original Message-
>>> From: Russell Bryant [mail
Yep, certainly interested in a broader OpenStack view of security; sign me
up. :)
On 11/27/13 9:06 PM, "Adrian Otto" wrote:
>
>On Nov 27, 2013, at 11:39 AM, Nathan Kinder
> wrote:
>
>> On 11/27/2013 08:58 AM, Paul Montgomery wrote:
>>> I created som
I created some relatively high level security best practices that I
thought would apply to Solum. I don't think it is ever too early to get
mindshare around security so that developers keep that in mind throughout
the project. When a design decision point could easily go two ways,
perhaps these g
10 matches
Mail list logo
