Hi,
I'm trying to install devstack and it keeps failing with:
2015-02-20 07:26:12.693 | ++ is_fedora
2015-02-20 07:26:12.693 | ++ [[ -z Ubuntu ]]
2015-02-20 07:26:12.693 | ++ '[' Ubuntu = Fedora ']'
2015-02-20 07:26:12.693 | ++ '[' Ubuntu = 'Red Hat' ']'
2015-02-20 07:26:12.693 | ++ '[' Ubuntu =
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 02/20/2015 12:02 PM, Eduard Matei wrote:
Hi,
I'm trying to install devstack and it keeps failing with:
2015-02-20 07:26:12.693 | ++ is_fedora 2015-02-20 07:26:12.693 | ++
[[ -z Ubuntu ]] 2015-02-20 07:26:12.693 | ++ '[' Ubuntu = Fedora
Potentially corrupted images are bad; depending on the affected data it
might only be diagnosed some time after installation, so IMO the fix is
needed.
Sure but there is a (potentially hefty) performance impact.
Well, do you want fast or working/consistent images?
Only a minor issue:
On Thursday, 19 de February de 2015 at 23:15, Kyle Mestery wrote:
[Adding neutron tag to subject, comments below.]
On Thu, Feb 19, 2015 at 3:55 PM, Ben Pfaff b...@nicira.com
(mailto:b...@nicira.com) wrote:
[moving this conversation to openstack-dev because it's more
interesting there
On 02/20/2015 12:26 AM, Adam Gandelman wrote:
Its more than just the naming. In the original proposal,
requirements.txt is the compiled list of all pinned deps (direct and
transitive), while requirements.in http://requirements.in reflects
what people will actually use. Whatever is in
Neutron experts,
I caught a bug report[1].
Currently, Neutron enable admin to delete default security group. But Neutron
doesn’t allow default security group to keep deleted. Neutron regenerates
default security group as security group api is called next. I have two
questions about the
Hmm, had the same issue like three hours ago but no longer now.
Either DevStack was updated in the last hour/mins or my fiddling with cwd
settings of my ansible scripts did the job, not sure which.
If you're running stack.sh not manually but scripted check your
environments cwd settings, is my
Yes, it looks like a bug that was merged which the gate didn't catch:
https://review.openstack.org/#/c/157720/ is the fix (I just pushed it up).
Could you share your localrc or local.conf? It would also be worth
tracking down which piece of devstack is changing your working directory
differently
Gary Kotton came across a doozy of a bug recently:
https://bugs.launchpad.net/nova/+bug/1419785
In short, when you start a Nova compute, it will query the driver for
instances and compare that against the expected host of the the instance
according to the DB. If the driver is reporting an
On 02/20/2015 06:14 AM, Ganapathy, Sandhya wrote:
Hi All,
I would like to discuss the Chassis Discovery Tool Blueprint -
https://review.openstack.org/#/c/134866/
The blueprint suggests Hardware enrollment and introspection for
properties at the Chassis layer. Suitable for micro-servers that
Aleksey,
Thank you for clarification. Personally, I'm more interested in IP-based
display/grouping/filtering of deployed nodes.
And yes, it would be super-useful to have filtering in back-end and API,
not only in UI.
--
Best regards,
Oleg
On Fri, Feb 20, 2015 at 12:30 PM, Aleksey Kasatkin
Oleg, The problem with IP addresses (for all networks but admin-pxe) is
that they are not available until deployment is started or
/clusters/(?Pcluster_id\d+)/orchestrator/deployment/defaults/ is called.
Nailgun just doesn't allocate them in advance. It was discussed some time
before (
Matt Riedemann wrote:
On 2/19/2015 6:06 PM, Henry Gessau wrote:
The fix: https://review.openstack.org/157606
That's busted by other things at the moment, it sounds like the solution
starts here:
https://review.openstack.org/#/c/157535/
Do you know where it ends ? We could set up Depends
It is not a topic specific to neutronclient.
We need more consistent versioning policy on client releases.
Assuming x.y.z as version number, just incrementing z should keep
backward compat.
For a client release for a new cycle (like this), it is better to bump
at least y version.
By doing so,
On 02/20/2015 06:14 AM, Sean Dague wrote:
Yes, it looks like a bug that was merged which the gate didn't catch:
https://review.openstack.org/#/c/157720/ is the fix (I just pushed it up).
Could you share your localrc or local.conf? It would also be worth
tracking down which piece of devstack
https://review.openstack.org/#/c/157535/
Do you know where it ends ? We could set up Depends lines on those
requirements stable/* reviews and line them up so that they are ready to
merge when openstackclient is fixed in devstack.
Alternative workaround is https://review.openstack.org/157654
On 19/02/15 18:57, Jay Pipes wrote:
On 02/19/2015 05:18 AM, Matthew Booth wrote:
Nova contains a config variable osapi_compute_unique_server_name_scope.
Its help text describes it pretty well:
When set, compute API will consider duplicate hostnames invalid within
the specified scope,
(I believe the version cap for icehouse 2.4 is expected to a policy like
this).
Yes, that assumed Semantic Versioning (semver.org) which 2.3.11 broke.
Cheers,
Alan
__
OpenStack Development Mailing List (not for usage
I too got this problem very frequently.
On Fri, Feb 20, 2015 at 4:32 PM, Eduard Matei
eduard.ma...@cloudfounders.com wrote:
Hi,
I'm trying to install devstack and it keeps failing with:
2015-02-20 07:26:12.693 | ++ is_fedora
2015-02-20 07:26:12.693 | ++ [[ -z Ubuntu ]]
2015-02-20
On Fri, Feb 20, 2015 at 12:10 PM, Doug Hellmann d...@doughellmann.com
wrote:
On Fri, Feb 20, 2015, at 02:07 PM, Joe Gordon wrote:
On Fri, Feb 20, 2015 at 7:27 AM, Doug Hellmann d...@doughellmann.com
wrote:
On Fri, Feb 20, 2015, at 06:06 AM, Sean Dague wrote:
On 02/20/2015
Ruby,
What you say makes sense to me. On keeping things consistent. So sounds
good to me to always use them and not have them be optional.
John
On Thu, Feb 19, 2015 at 9:32 AM, Ruby Loo rlooya...@gmail.com wrote:
I think that if there is a use case for an *ED state, then we should have
it.
On Fri, Feb 20, 2015, at 03:36 PM, Joe Gordon wrote:
On Fri, Feb 20, 2015 at 12:10 PM, Doug Hellmann d...@doughellmann.com
wrote:
On Fri, Feb 20, 2015, at 02:07 PM, Joe Gordon wrote:
On Fri, Feb 20, 2015 at 7:27 AM, Doug Hellmann d...@doughellmann.com
wrote:
On
Nova core reviewers,
May I request an FFE for Cisco VIF driver:
https://review.openstack.org/#/c/157616/
This is a small isolated change similar to the vhostuser / open contrail vif
drivers for which FFE has been granted.
Thanks,
Sourabh
From: Christopher Yeoh
All,
We spent some time at the OSSG mid-cycle meet-up this week discussing root
wrap, looking at the existing code, and considering some of the mailing list
discussions.
Summary of our discussions:
https://github.com/hyakuhei/OSSG-Security-Practices/blob/master/ossg_rootwrap.md
The one line
As discussed in Cinder Weekly meeting on 02/12 the deadline for K3 (kilo-3
k3 : Cinder https://launchpad.net/cinder/+milestone/kilo-3) is Feb28
(please correct me if I am wrong). So I have a working prototype for
micro-states feature https://review.openstack.org/#/c/124205 and is been
already out
Inline...
On Wed, Feb 18, 2015 at 7:48 PM, Vikram Choudhary
vikram.choudh...@huawei.com wrote:
Hi,
You can write your own driver. You can refer to below links for getting some
idea about the architecture.
https://wiki.openstack.org/wiki/Neutron/ServiceTypeFramework
This is a legacy
Hello,
Thx for tips. I have one more question. You point me fo neutron-fwaas project
which for me looks like different project then neutron. I saw fwaas service
plugin directly in neutron in Juno. So which version should I use: this
neutron-fwaas or service plugin from neutron? Or maybe it is
Howdy folks.
Does anyone know of any open source projects that facilitate managing
switches from within a browser (not CLI)? I know there are mechanism
drivers today that allow the ML2 plug-in to connect directly to a switch
via SSH and add/remove VLAN's, I'm wondering if this has been
Same project, shiny new repo.
doug
On Feb 20, 2015, at 4:05 PM, Sławek Kapłoński sla...@kaplonski.pl wrote:
Hello,
Thx for tips. I have one more question. You point me fo neutron-fwaas project
which for me looks like different project then neutron. I saw fwaas service
plugin directly
Hi Slawek,
During the Kilo development cycle the repositories of the three
services - FWaaS, LBaaS, VPNaaS, have split from the main neutron
repo. The pointers I posted were from this split repo. What you are
referring to is the Juno version of the code (during which all the
code was in one
On 2/20/2015 6:23 AM, Alan Pevec wrote:
https://review.openstack.org/#/c/157535/
Do you know where it ends ? We could set up Depends lines on those
requirements stable/* reviews and line them up so that they are ready to
merge when openstackclient is fixed in devstack.
Alternative
Hello,
Thx guys. Now it is clear for me :)
One more question. I saw that in this service plugin there is hardcoded quota
1 firewall per tenant. Do you know why it is so limited? Is there any
important reason for that?
And second thing. As there is only one firewall per tenant so all rules from
Inline...
On Fri, Feb 20, 2015 at 3:38 PM, Sławek Kapłoński sla...@kaplonski.pl wrote:
Hello,
Thx guys. Now it is clear for me :)
One more question. I saw that in this service plugin there is hardcoded quota
1 firewall per tenant. Do you know why it is so limited? Is there any
important
On Feb 21, 2015 12:20 AM, Jeremy Stanley fu...@yuggoth.org wrote:
On 2015-02-20 16:29:31 +0100 (+0100), Deepak Shetty wrote:
Couldn't find anything strong in the logs to back the reason for
OOM. At the time OOM happens, mysqld and java processes have the
most RAM hence OOM selects mysqld
On Feb 21, 2015 12:26 AM, Joe Gordon joe.gord...@gmail.com wrote:
On Fri, Feb 20, 2015 at 7:29 AM, Deepak Shetty dpkshe...@gmail.com
wrote:
Hi Jeremy,
Couldn't find anything strong in the logs to back the reason for OOM.
At the time OOM happens, mysqld and java processes have the most
Hi Ihar,
That was missed for the Juno release, I'll post a patch on master and then
backport it to stable/juno.
Thanks for catching that,
Ivar.
On Fri Feb 20 2015 at 11:06:11 AM Ihar Hrachyshka ihrac...@redhat.com
wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi,
does anyone know
Hi,
Davanum Srinivas wrote:
+1 to fix Oslo's service module any ways, irrespective of this bug.
By the way, the Service class is a blocker point for the implementation of
asyncio and threads specs:
https://review.openstack.org/#/c/153298/
https://review.openstack.org/#/c/156711/
We may
On Thu, Feb 19, 2015, Matthew Booth mbo...@redhat.com wrote:
Assuming this configurability is required, is there any way we can
instead use it to control a unique constraint in the db at service
startup? This would be something akin to a db migration. How do we
manage those?
Ignoring if this
Hi Jeremy,
Couldn't find anything strong in the logs to back the reason for OOM.
At the time OOM happens, mysqld and java processes have the most RAM hence
OOM selects mysqld (4.7G) to be killed.
From a glusterfs backend perspective, i haven't found anything suspicious,
and we don't have the
On Fri, Feb 20, 2015, at 07:01 AM, Alan Pevec wrote:
(I believe the version cap for icehouse 2.4 is expected to a policy like
this).
Yes, that assumed Semantic Versioning (semver.org) which 2.3.11 broke.
To elaborate, the issue here is that the dependencies between 2.3.10 and
2.3.11
Morgan Fainberg morgan.fainb...@gmail.com writes:
The Keystone development team is planning to deprecate deployment of Keystone
under Eventlet during the Kilo cycle. Support for deploying under eventlet
will
be dropped as of the “M”-release of OpenStack.
great! glad there is one project
Hi,
Seems to be fixed now, your comments gave me an idea and i included a cd
/opt/devstack in the command for stack.sh, now it looks like this:
HOME=/opt/stack cd /opt/devstack sudo -u stack
/opt/devstack/stack.sh
Just as a side note, it was working yesterday, without cd /opt/devstack,
and it
On Fri, Feb 20, 2015 at 12:45:46PM +0100, Miguel Ángel Ajo wrote:
On Thursday, 19 de February de 2015 at 23:15, Kyle Mestery wrote:
On Thu, Feb 19, 2015 at 3:55 PM, Ben Pfaff b...@nicira.com
(mailto:b...@nicira.com) wrote:
My initial reaction is that we can implement security groups as
On Thu, Feb 19, 2015, at 09:45 PM, Mike Bayer wrote:
Doug Hellmann d...@doughellmann.com wrote:
5) Allow this sort of connection sharing to continue for a deprecation
period with apppropriate logging, then make it a hard failure.
This would provide services time to find and fix
On Fri, Feb 20, 2015, at 06:06 AM, Sean Dague wrote:
On 02/20/2015 12:26 AM, Adam Gandelman wrote:
Its more than just the naming. In the original proposal,
requirements.txt is the compiled list of all pinned deps (direct and
transitive), while requirements.in http://requirements.in
+1 to fix Oslo's service module any ways, irrespective of this bug.
+1 to The db library shouldn't be concerned with whether or not it's
in a forked process -- that's not its job
-- dims
On Fri, Feb 20, 2015 at 10:17 AM, Doug Hellmann d...@doughellmann.com wrote:
On Thu, Feb 19, 2015, at
I'm working on the external devstack plugin for neutron-lbaas and found that it
was leaving behind stale ip network namespaces after running clean.sh.
Comparing to unstack.sh, which calls run_phase unstack I saw that clean.sh
was not calling run_phase clean, and thus my cleanup code wasn't
Doug Hellmann d...@doughellmann.com wrote:
And I don't think we want the database library doing anything with this
case at all. Recovery code is tricky, and often prevents valid use cases
(perhaps the parent *meant* for the child to reuse the open connection
and isn't going to continue
On Fri, Feb 20, 2015 at 3:06 AM, Sean Dague s...@dague.net wrote:
It sounds like you are suggesting we take the tool we use to ensure that
all of OpenStack is installable together in a unified way, and change
it's installation so that it doesn't do that any more.
Which I'm fine with.
But
On Friday, 20 de February de 2015 at 17:06, Ben Pfaff wrote:
On Fri, Feb 20, 2015 at 12:45:46PM +0100, Miguel Ángel Ajo wrote:
On Thursday, 19 de February de 2015 at 23:15, Kyle Mestery wrote:
On Thu, Feb 19, 2015 at 3:55 PM, Ben Pfaff b...@nicira.com
(mailto:b...@nicira.com) wrote:
I can report that we do use this option (‘global' setting.) We have to
enforce name uniqueness for instances’ integration with some external
systems (namely AD and Spacewalk) which require unique naming.
However, we also do some external name validation which I think
effectively enforces
It seems to me that the blueprint serial-ports[1] didn't implement
everything which was described in its spec. If one of you could have a
look at the following examples and help me to understand if these
observations are right/wrong that would be great.
Example 1:
The flavor provides the
On Fri, Feb 20, 2015 at 06:03:46PM +0100, Markus Zoeller wrote:
It seems to me that the blueprint serial-ports[1] didn't implement
everything which was described in its spec. If one of you could have a
look at the following examples and help me to understand if these
observations are
On Fri, Feb 20, 2015 at 12:40:34PM +0100, Philipp Marek wrote:
Well, do you want fast or working/consistent images?
Sure I often said I'll take slow and correct over fast and buggy anyday.
Oh, okay... with the safe default being derived from the qemu version ;)
Umm excuse my ignorance but
On Fri, Feb 13, 2015 at 11:57 AM, Joe Gordon joe.gord...@gmail.com wrote:
1.
A few months back we started the process to remove the tempest CLI
tests from tempest [0]. Now that we have successfully pulled novaclient
CLI
tests out of tempest, we have the process sorted
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Those are good news!
I commented on the pull request. Briefly, we can fetch from git, but
would prefer an official release.
Thanks,
/Ihar
On 02/19/2015 11:26 PM, Robert Li (baoli) wrote:
Hi Kyle, Ihar,
It looks promising to have our patch
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi,
I would like to introduce a hacking check that would be disabled by
default:
https://review.openstack.org/157894
I see the following commit in flake8:
https://gitlab.com/methane/flake8/commit/b301532636b60683b339a2d081728d22957a142f
which
Doug Hellmann wrote:
On Thu, Feb 19, 2015, at 09:45 PM, Mike Bayer wrote:
Doug Hellmannd...@doughellmann.com wrote:
5) Allow this sort of connection sharing to continue for a deprecation
period with apppropriate logging, then make it a hard failure.
This would provide services time to
Sean Dague wrote:
On 02/20/2015 12:26 AM, Adam Gandelman wrote:
Its more than just the naming. In the original proposal,
requirements.txt is the compiled list of all pinned deps (direct and
transitive), while requirements.inhttp://requirements.in reflects
what people will actually use.
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 02/18/2015 08:45 PM, Armando M. wrote:
On 17 February 2015 at 22:00, YAMAMOTO Takashi
yamam...@valinux.co.jp mailto:yamam...@valinux.co.jp wrote:
hi,
i want to add an extra requirement specific to OVS-agent. (namely,
I want to add ryu
On Fri, Feb 20, 2015 at 7:29 AM, Deepak Shetty dpkshe...@gmail.com wrote:
Hi Jeremy,
Couldn't find anything strong in the logs to back the reason for OOM.
At the time OOM happens, mysqld and java processes have the most RAM hence
OOM selects mysqld (4.7G) to be killed.
From a glusterfs
Doug Hellmann d...@doughellmann.com wrote:
On Fri, Feb 20, 2015, at 11:28 AM, Mike Bayer wrote:
Doug Hellmann d...@doughellmann.com wrote:
And I don't think we want the database library doing anything with this
case at all. Recovery code is tricky, and often prevents valid use cases
Hi,
I have submitted presentations for Openstack L summit :
The Heat Orchestration Template Builder: A
demonstrationhttps://www.openstack.org/vote-vancouver/Presentation/the-heat-orchestration-template-builder-a-demonstration
Please cast your vote if you feel it is worth for presentation.
On 2015-02-20 16:29:31 +0100 (+0100), Deepak Shetty wrote:
Couldn't find anything strong in the logs to back the reason for
OOM. At the time OOM happens, mysqld and java processes have the
most RAM hence OOM selects mysqld (4.7G) to be killed.
[...]
Today I reran it after you rolled back some
On 2015-02-20 09:38:22 -0800 (-0800), Mike Perez wrote:
[...]
I was also not aware of the assistance being given to Open Source
solutions, but makes sense to me.
To quote Harry Tuttle, We're all in it together.
--
Jeremy Stanley
On Fri, Feb 20, 2015 at 10:16 AM, Joshua Harlow harlo...@outlook.com
wrote:
It'd be interesting to see what a distribution (canonical, redhat...)
would think about this movement. I know yahoo! has been looking into it for
similar reasons (but we are more flexibly then I think a packager such
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 02/20/2015 12:07 PM, Ihar Hrachyshka wrote:
Hi,
I would like to introduce a hacking check that would be disabled
by default:
https://review.openstack.org/157894
I see the following commit in flake8:
I started https://etherpad.openstack.org/p/service-py-replacements with
some ideas/thoughts/notes; feel free to add any on u want (or adjust it
accordingly with better ideas).
-Josh
Victor Stinner wrote:
Hi,
Davanum Srinivas wrote:
+1 to fix Oslo's service module any ways, irrespective of
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi,
does anyone know why we don't maintain an entry point for APIC agent
in setup.cfg? The code in [1] looks like there is a main() function
for the agent, but for some reason it's not exposed to any
console_script during installation of neutron.
Is
On Fri, Feb 20, 2015 at 7:27 AM, Doug Hellmann d...@doughellmann.com
wrote:
On Fri, Feb 20, 2015, at 06:06 AM, Sean Dague wrote:
On 02/20/2015 12:26 AM, Adam Gandelman wrote:
Its more than just the naming. In the original proposal,
requirements.txt is the compiled list of all pinned
Hi all,
this is a reflection of the discussion I just had on #openstack-infra; it's
about (re-)using the central CI infrastructure for our Open-Source DRBD
driver too.
The current status is:
* The DRBD driver is already in Cinder, so DRBD-replicated Cinder storage
using iSCSI to the
Steve, thanks for sharing this - the decomposed blueprints are going
to make getting involved easy. Containerizing OpenStack services
looks like a great solution to the challenge of upgrades, and pace of
the work you and others on the Kolla team have kept up is impressive.
Regarding Fuel, we are
On 2/20/15, 12:07, Ihar Hrachyshka ihrac...@redhat.com wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi,
I would like to introduce a hacking check that would be disabled by
default:
https://review.openstack.org/157894
I see the following commit in flake8:
On Fri, Feb 20, 2015, at 02:07 PM, Joe Gordon wrote:
On Fri, Feb 20, 2015 at 7:27 AM, Doug Hellmann d...@doughellmann.com
wrote:
On Fri, Feb 20, 2015, at 06:06 AM, Sean Dague wrote:
On 02/20/2015 12:26 AM, Adam Gandelman wrote:
Its more than just the naming. In the original
On 2/20/15 9:06 AM, Mike Dorman wrote:
I can report that we do use this option (‘global' setting.) We have to
enforce name uniqueness for instances’ integration with some external
systems (namely AD and Spacewalk) which require unique naming.
However, we also do some external name validation
75 matches
Mail list logo
