Re: [openstack-dev] [rdo-list] [TripleO] What's the plan for shipping Pike TripleO containers ?

2017-08-30 Thread Van Leeuwen, Robert
> snip > It's probably also worth asking if we want to be shipping stable > containers at all ? Who will be the users of those stable containers ? > snip My 2cts as a consumer of “just” RDO packages and working to move to containers: (We are currently running our own puppet infra and have

[openstack-dev] [neutron][osc] Openstack client, unit tests & creating default empty values

2017-05-01 Thread Van Leeuwen, Robert
Hello, The unit test for the network/v2/fakes.py for the port creates empty dictionaries e.g. for allowed_address_pairs: port_attrs = { 'admin_state_up': True, 'allowed_address_pairs': [{}], 'binding:host_id': 'binding-host-id-' + uuid.uuid4().hex,

Re: [openstack-dev] [Openstack-operators] [Neutron] Deprecating the use_namespaces option - Now's the time to speak up!

2015-03-23 Thread Van Leeuwen, Robert
I think there are valid reasons to not use namespaces: * Fewer moving parts == less can potentialy fail * Troubleshooting is easier due to less places to look / need no familiarity with namespaces tools * If I remember correctly setting up a namespace can get really slow when you

Re: [openstack-dev] [Openstack-operators] [Neutron] Deprecating the use_namespaces option - Now's the time to speak up!

2015-03-23 Thread Van Leeuwen, Robert
Are the setups out there *not* using the use_namespaces option? I'm curious as to why, and if it would be difficult to migrate such a setup to use namespaces. At my previous employer we did not use namespaces. This was due to a installation a few years ago on SL6 which did not have name