On 28 May 2014, at 17:14, Sergey Lukjanov wrote:
> 1. How should we handle addition of new functionality to the API,
> should we bump minor version and just add new endpoints?
Agree with most of folks. No new versions on adding new endpoints.
Semantic changes require new major version of rest a
On 05/29/2014 07:23 AM, Alexander Ignatov wrote:
On 28 May 2014, at 20:02, Sergey Lukjanov wrote:
sahara-image-elements
We're agreed that some common parts should be merged into the
diskimage-builder repo (like java support, ssh, etc.). The main issue
of keeping -image-elements separated is
On 05/28/2014 12:37 PM, Dat Tran wrote:
Hi everyone,
I have a idea for new project: Mahout-as-a-service.
Main idea of this project:
- Install OpenStack
- Deploying OpenStack Sahara source
- Deploying Mahout on Sahara OpenStack system.
- Construction of the API.
Through web or mobile interface,
On 5/29/2014 4:41 AM, Xurong Yang wrote:
> Hi, stackers
> if i define provider when creating network, but no segmentation_id,
> net-create fail. why not allocate segmentation_id automatically?
> ~$ neutron net-create test --provider:network_type=vlan
> --provider:physical_network=default
> Invali
On 28 May 2014, at 20:02, Sergey Lukjanov wrote:
> Hey folks,
>
> it's a small wrap-up for the topic "Sahara subprojects releasing and
> versioning" that was discussed partially on summit and requires some
> more discussions. You can find details in [0].
>
>> common
>
> We'll include only one
Comment inline at bottom of message...
-Original Message-
From: Jay Pipes [mailto:jaypi...@gmail.com]
Sent: 06 May 2014 18:44
To: openstack-dev@lists.openstack.org
Subject: Re: [openstack-dev] [nova] Question about addit log in nova-compute.log
On 05/06/2014 01:37 PM, Jiang, Yunhong wrot
Hello,
Wiadomość napisana przez Vladimir Kuklin w dniu 29 maj
2014, o godz. 12:09:
> may be the problem is that you are using liftetime crm attributes instead of
> 'reboot' ones. shadow/commit is used by us because we need transactional
> behaviour in some cases. if you turn crm_shadow off,
On Wed, May 28, 2014 at 10:18 PM, Jaromir Coufal wrote:
> Hi All,
>
> There is a lot of tags in the subject of this e-mail but believe me that all
> listed projects (and even more) are relevant for the designs which I am
> sending out.
>
> Nodes management section in Horizon is being expected for
Hi,
Just a reminder that the weekly Nova API meeting is being held tomorrow
Friday UTC .
We encourage cloud operators and those who use the REST API such as
SDK developers and others who and are interested in the future of the
API to participate.
In other timezones the meeting is at:
EST
Hi,
vxlan network are inserted/verified in DB one by one, which could explain
the time required
https://github.com/openstack/neutron/blob/master/neutron/plugins/ml2/drivers/type_vxlan.py#L138-L172
Cédric
On Thu, May 29, 2014 at 12:01 PM, Xurong Yang wrote:
> Hi, Folks,
>
> When we configur
may be the problem is that you are using liftetime crm attributes instead
of 'reboot' ones. shadow/commit is used by us because we need transactional
behaviour in some cases. if you turn crm_shadow off, then you will
experience problems with multi-state resources and
location/colocation/order const
On 05/28/2014 10:03 PM, Gabriel Hurley wrote:
> It's sort of a silly point, but as someone who would likely consume the
> split-off package outside of the OpenStack context, please give it a
proper
> name instead of "django_horizon". The module only works in Django, the
name
> adds both clutter and
On 05/29/2014 05:26 AM, Thierry Carrez wrote:
> Sean Dague wrote:
>> I honestly just think we might want to also use it as a time to rethink
>> our program concept. Because all our programs that include projects that
>> are part of the integrated release are 1 big source tree, and maybe a
>> couple
Hi, Folks,
When we configure VXLAN range [1,16M], neutron-server service costs long
time and cpu rate is very high(100%) when initiation. One test base on
postgresql has been verified: more than 1h when VXLAN range is [1, 1M].
So, any good solution about this performance issue?
Thanks,
Xurong Ya
On Thu, May 29, 2014 at 04:29:34AM +, Tracy Jones wrote:
> Hi Folks - I spoke with Michael at the summit about bug management for
> Juno. Other than tagging the untagged bugs each week,
I'm try to do that (and some triage/root-cause analysis for
libvirt/QEMU/KVM-based bugs and would like to
Hi James,
that's a good point. I just restructured the etherpad so that there are
3 sections: one is for July 28 - Aug 1, second is for July 21-25 and
third one is for those who want to attend but can't make it within
suggested dates. So I would like to encourage everybody who is willing
to a
Sean Dague wrote:
> I honestly just think we might want to also use it as a time to rethink
> our program concept. Because all our programs that include projects that
> are part of the integrated release are 1 big source tree, and maybe a
> couple of little trees that orbit it (client and now specs
Hi everyone,
Recently, wrapt was added as a dependency. The Python module suffers
from obvious design issues, like for example:
- Lack of Python 3.4 support
- Broken with Python 3.2
- Upstream sources in "src" instead of "wrapt" so then running py.test
doesn't work unless you do "ln -s src wrapt",
Hey Mainn,
mostly it is driven by following requirements:
https://etherpad.openstack.org/p/ironic-ui
plus what you already know from Tuskar point of view - which is simply
monitoring, monitoring, monitoring :)
Hope it helps
-- Jarda
On 2014/29/05 05:51, Tzu-Mainn Chen wrote:
Hi Jarda,
Thes
Hi, stackers
if i define provider when creating network, but no segmentation_id,
net-create fail. why not allocate segmentation_id automatically?
~$ neutron net-create test --provider:network_type=vlan --provider:physical_
network=default
Invalid input for operation: segmentation_id required for VL
On 05/27/14 16:44, Bartosz Kupidura wrote:
> Hello,
> Responses inline.
>
>
> Wiadomość napisana przez Vladimir Kuklin w dniu 27 maj
> 2014, o godz. 15:12:
>
>> Hi, Bartosz
>>
>> First of all, we are using openstack-dev for such discussions.
>>
>> Second, there is also Percona's RA for Percona
Could we replace the refresh from the period task with a timestamp in the
network cache of when it was last updated so that we refresh it only when it’s
accessed if older that X ?
From: Aaron Rosen [mailto:aaronoro...@gmail.com]
Sent: 29 May 2014 01:47
To: Assaf Muller
Cc: OpenStack Development
On 28/05/14 17:01 +, Kurt Griffiths wrote:
Crew, as discussed in the last team meeting, I have updated the API v1.1 spec
to remove the ability to get one or more messages by ID. This was done to
remove unnecessary complexity from the API, and to make it easier to support
different types of me
Hi All,
The reason I ask this question in openstack-dev is there is a lot of
confusion going around other projects moving to keystone v3. Would it be a
problem if I use keystone v3 api for authenticating and point other
services to use keystone v2 with keystone v3 token? The main issue here is
key
Just chiming in with a side-note.
I always liked the idea of Postern for things like this though the crypto
geek in me always worries about making key retrieval too easy for
developers, bad things happen down that road.
The OSSG can help with overall secure design and would be happy to consult
if
101 - 125 of 125 matches
Mail list logo
