On Tue, Jul 15, 2014 at 9:15 PM, Arnaud Legendre wrote:
> Greetings,
>
> I am facing an issue and looking for guidance/best practice. So, here is the
> problem:
>
> - glance [stable/icehouse] contains a requirement to oslo.vmware >= 0.2 [1]
> and consequently requirements/global-requirements [stab
Since Keystone moved to running under httpd,
it uses port 5000 by default. Seems like something is already running on
port 5000 on your machine.
You can try finding the process running
on port 5000 by doing: netstat -plten
|grep java and then killing it, the
PID should be one of th columns.
Regard
On 15/07/14 20:43, Tomas Sedovic wrote:
> On 15/07/14 20:01, Zane Bitter wrote:
>> On 14/07/14 12:21, Tomas Sedovic wrote:
>>> On 12/07/14 06:41, Zane Bitter wrote:
On 11/07/14 09:37, Tomas Sedovic wrote:
>>
> [snip]
>>>
There is one aspect of this that probably doesn't work yet: ori
What are the benefits of doing this over
looking at the existing rechecks, and if not there opening a bug and rechecking
the new bug?
Regards,
Steve Martinelli
Software Developer - Openstack
Keystone Core Member
Phone:
1-905-413-2851
E-mail: steve...@ca.ibm.com
8200 Warden Ave
Markham, ON
Hello,
What do you think about allowing some text after the words "recheck no
bug"? EG to include a snippet from the log showing the failure has been
at least briefly investigated before attempting a recheck. EG:
recheck no bug
Compute node failed to spawn:
2014-07-15 12:18:09.936 | 3f1
I don't think this is a usecase that could be supported right now.
There will be multiple issues with running two ovs instances on the node, e.g.
how to manage two sets of userspace utilities, two ovsdb servers etc.
Also there would be some limitations from how ml2 plugin does port binding
(di
Daniel P. Berrange wrote:
> On Wed, Jul 16, 2014 at 11:57:33AM +, Tim Bell wrote:
>> It seems a pity to archive the comments and reviewer lists along
>> with losing a place to continue the discussions even if we are not
>> expecting to see code in Juno.
>
> Agreed, that is sub-optimal to say t
Hi
Please review: https://review.openstack.org/#/c/105669/
Thanks
Avishay
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
On Tue, Jul 15, 2014 at 9:54 AM, Henry Nash
wrote:
> Do people think this is a good idea? Useful in other projects? Concerned
> about the risks?
FWIW, we have this in Swift for a while and we actually uses it for
different testing in cloud capabilities.
I personally find it useful for clien
Hi Everyone,
Just wanted to send a reminder to the list that we're not having a meeting this
week. Since most people are here in Darmstadt this week at the mid-cycle meet-up
there isn't a reason to have the regular weekly meeting. So I'm cancelling this
week's meeting. We will have our next meetin
Hi,
We were looking at this solution in the beginning, but it’s won’t work with
opendaylight.
With opendaylight there is no agent running on the node so this info would have
to be provided by opendaylight.
Thanks
Przemek
From: Irena Berezovsky [mailto:ire...@mellanox.com]
Sent: Sunday, July 13,
Le 16/07/2014 14:09, Daniel P. Berrange a écrit :
> On Wed, Jul 16, 2014 at 11:57:33AM +, Tim Bell wrote:
>> As we approach Juno-3, a number of specs have been correctly marked
>> as abandoned since they are not expected to be ready in time for the
>> release.
>>
>> Is there a mechanism to keep
On 16 July 2014 03:57, Jay S. Bryant wrote:
> John,
>
> So you have said a few times that the specs are a learning process.
> What do you feel with have learned thus far using specs?
I'm not John, but I'm going to answer as if you'd addressed the question wider:
- Specs can definitely help flesh
Some comments inline:
> Agreed-- I think we need to more fully flesh out how extension list / tags
> should work here before we implement it. But this doesn't prevent us from
> rolling forward with a "version 1" of flavors so that we can start to use
> some of the benefits of having flavors (like
So I see a couple of issues here:
1) reliability - need to decide what the scheduler does if the nova
api isn't responding - hanging and ignoring future scheduling requests
is not a good option... a timeout and putting the volume into error
might be fine.
2) Nova doesn't expose hostname as identi
On Wed, Jul 16, 2014 at 11:57:33AM +, Tim Bell wrote:
> As we approach Juno-3, a number of specs have been correctly marked
> as abandoned since they are not expected to be ready in time for the
> release.
>
> Is there a mechanism to keep these specs open for discussion even
> though there is
As we approach Juno-3, a number of specs have been correctly marked as
abandoned since they are not expected to be ready in time for the release.
Is there a mechanism to keep these specs open for discussion even though there
is no expectation that they will be ready for Juno and 'defer' them to
On Wed, Jul 16, 2014 at 11:24 AM, Joe Gordon wrote:
>
>
>
> On Tue, Jul 15, 2014 at 7:20 AM, Morgan Fainberg <
> morgan.fainb...@gmail.com> wrote:
>
>>
>>
>> On Tuesday, July 15, 2014, Steven Hardy wrote:
>>
>>> On Mon, Jul 14, 2014 at 02:43:19PM -0400, Adam Young wrote:
>>> > On 07/14/2014 11:4
Dugger, Donald D said on Tue, Jul 15, 2014 at 09:15:06PM +:
> I `really` dislike paging through 10 screens of an email to discover
> the single comment buried somewhere near the end.
https://wiki.openstack.org/wiki/MailingListEtiquette#Trimming
That's not inline style's fault, that's pure laz
On Mon, 14 Jul 2014, Sean Dague wrote:
Javelin2 lives in tempest, currently the following additional fixes are
needed for it to pass the server & image creation in grenade -
https://review.openstack.org/#/q/status:open+project:openstack/tempest+branch:master+topic:javelin_img_fix,n,z
Thanks fo
Hi all,
When I just set up my develope environment use devstack at CentOS 6.5,
that fetch devstack source via github.com and checkout stable/icehouse branch.
and bellow[1] is the error log fragment.
I'm not sure if I am ok to ask my question in this mail list or not,
because I search all of the
Very cool Gary.
On Wed, Jul 16, 2014 at 5:31 AM, Gary Kotton wrote:
> Hi,
> I just thought it would be nice to give the community a little update about
> the current situation:
>
> Version is 0.4
> (https://github.com/openstack/requirements/blob/master/global-requirements.txt#L58)
>
> This is use
Ben,
LGTM as well. i was finally able to look :)
-- dims
On Wed, Jul 16, 2014 at 4:35 AM, Flavio Percoco wrote:
> On 07/15/2014 07:42 PM, Ben Nemec wrote:
>> And the link, since I forgot it before:
>> https://github.com/cybertron/oslo.serialization
>>
>
> LGTM!
>
> Thanks for working on this!
>
Thanks for your feedbacks and comments, guys
This is a proposal for modified SNI management part for next RST patch:
“
For SNI functionality, tenant will supply list of TLS containers in specific
Order.
In case when specific back-end is not able to support SNI capabilities,
its driver should throw
It seems that you are sharing one port between two instances, which
won't be a legal configuration.
On Wed, Jul 16, 2014 at 01:17:00AM -0500, yulin...@dell.com wrote:
> Dell Customer Communication
>
> Hi,
> I'm using heat to create a stack with two instances. I always got one of them
> successfu
On 14/07/14 19:11, Ben Nemec wrote:
> +1. In my experience they've both demonstrated that they know what
> they're doing.
>
> I think the bikeshedding/grammar nits on specs is kind of a separate
> issue that will need to be worked out in general. It's still very early
> on in this new *-specs re
Hi there,
Just to apologize and inform that most of the links to the logs of Midokura
CI bot on gerrit are dead now. That is because I accidentally deleted all
the logs (instead of over a month old logs) today. Logs for the jobs after
the deletion are saved just fine.
We'll be more careful about h
Hi Rob,
Being added as a core review would be great, thank you all for the votes of
confidence, and I'll do my best to keep tripleo making great progress.
Thanks,
Jon-Paul Sullivan ☺ Cloud Services - @hpcloud
Postal Address: Hewlett-Packard Galway Limited, Ballybrit Business Park, Galway.
Regi
Robert Collins said on Wed, Jul 16, 2014 at 09:13:52AM +1200:
> Alexis, Jon - core status means a commitment to three reviews a work
> day (on average), keeping track of changing policies and our various
> specs and initiatives, and obviously being excellent to us all :).
Hello,
Thank you all for
Hi,
I just thought it would be nice to give the community a little update about the
current situation:
1. Version is 0.4
(https://github.com/openstack/requirements/blob/master/global-requirements.txt#L58)
* This is used by glance and ceilometer
* There is a patch in review for N
On Tue, Jul 15, 2014 at 7:20 AM, Morgan Fainberg
wrote:
>
>
> On Tuesday, July 15, 2014, Steven Hardy wrote:
>
>> On Mon, Jul 14, 2014 at 02:43:19PM -0400, Adam Young wrote:
>> > On 07/14/2014 11:47 AM, Steven Hardy wrote:
>> > >Hi all,
>> > >
>> > >I'm probably missing something, but can anyone
On 07/15/2014 07:16 PM, Doug Hellmann wrote:
> On Tue, Jul 15, 2014 at 1:03 PM, Ken Giusti wrote:
>>
>> These packages may be obtained via EPEL for Centos/RHEL systems
>> (qpid-proton-c-devel), and via the Qpid project's PPA [3]
>> (libqpid-proton2-dev) for Debian/Ubuntu. They are also available
On 07/15/2014 06:20 PM, Kurt Griffiths wrote:
> Hi folks, we’ve been talking about this in IRC, but I wanted to bring it
> to the ML to get broader feedback and make sure everyone is aware. We’d
> like to change our meeting time to better accommodate folks that live
> around the globe. Proposals:
>
Hello guys,
I'm in the process of writing a cinder filter and weigher, I need to
know whether I can use something like 'nova-api' inside filter/weigher
to query the tags of a virtual machine running on a compute-node.
I need to create the cinder volume on the same host as the VM (which was
cre
On 07/15/2014 07:42 PM, Ben Nemec wrote:
> And the link, since I forgot it before:
> https://github.com/cybertron/oslo.serialization
>
LGTM!
Thanks for working on this!
> On 07/14/2014 04:59 PM, Ben Nemec wrote:
>> Hi oslophiles,
>>
>> I've (finally) started the graduation of oslo.serialization
On Tue, Jul 15, 2014 at 11:40 AM, Nels Nelson
wrote:
> Thanks for your response, Joe.
>
> Am I understanding you correctly that the Hypervisor Support Status does
> not in fact hinge on any particular Tempest tests, but rather, simply on
> individual tests for the libvirt-lxc driver used for gati
On 07/15/2014 04:18 PM, Matt Riedemann wrote:
> I've been looking at bug 1341777 since yesterday originally because of
> g-api logs and this warning:
>
> "HttpConnectionPool is full, discarding connection: 127.0.0.1"
>
> But that's been around awhile and it sounds like an issue with
> python-swif
Hello everyone!
I would like to bring the next two points to everybody's attention:
1) As Henry mentioned if you add new migration you should make it
unconditional. Conditional migrations should not be merged since now.
2) If you add some new models you should ensure that module containing it
is
On 2014/15/07 20:29, Gregory Haynes wrote:
Excerpts from Jaromir Coufal's message of 2014-07-15 07:15:12 +:
On 2014/10/07 22:19, Gregory Haynes wrote:
Excerpts from Jaromir Coufal's message of 2014-07-09 07:51:56 +:
Hey folks,
after few rounds of reviews and feedbacks, I am sending wi
Hi Wan,
thanks for great notes. My response is inline:
On 2014/15/07 23:19, Wan-yen Hsu wrote:
The "Register Nodes" panel uses "IPMI user" and "IPMI Password".
However, not all Ironic drivers use IPMI, for instance, some Ironic
drivers will use iLO or other BMC interfaces instead of IPMI. I wo
I think the problem could be that you need one network port for each
server, but you just have one OS::Neutron::Port resource defined.
wrote on 16/07/2014 08:17:00:
> From:
> To:
> Date: 16/07/2014 08:20
> Subject: [openstack-dev] heat stack-create with two vm instances
> always got one failed
101 - 141 of 141 matches
Mail list logo
