On 05/14/15 21:04, Boris Pavlovic wrote:
John,
I believe that backlog should be different much simpler then specs.
Imho Operators don't have time / don't want to write long long specs
and analyze how they are aligned with specs
or moreover how they should be implemented and how they impact
Hi,
I was talking with Matt (VW) about how best some large deployment
working sessions could send their requirements to Nova.
As an operator, if you have a problem that needs fixing or use case
that needs addressing, a great way of raising that issue with the
developer community is a Backlog
I heard lots of talk in Paris about having nova-network reach feature parity
with neutron.
With neutron, you can specify egress/ingress rules in Horizon, so if
nova-network ever got feature parity, it should work *someday*
On May 14, 2015, at 10:10 AM, Stephen Cousins steve.cous...@maine.edu
On May 12, 2015, at 3:00 PM, JJ Asghar jasg...@chef.io wrote:
I’d like to announce the OpenStack-Chef Ops Meetup in Vancouver. We have an
etherpad[1] going with topics people would like to discuss. I haven’t found a
room or space for us yet, but when I do I’ll comment back on this thread
Hi,
I will be moderating the Customer On-Boarding/Off-Boarding[1] session at
the summit, and wanted to make sure we get as much feedback into the
etherpad[2] as possible.
Both adding and removing users seems like a pretty simple idea, but it gets
complicated pretty quickly. So any suggestions,
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Hi Basil
On 14/05/15 16:04, Basil Baby wrote:
I can see the patch for CVE-2015-3456 updated to qemu-kvm package
on Precise - Icehouse branch.
https://launchpad.net/~ubuntu-cloud-archive/+archive/ubuntu/icehouse-s
taging/+build/7425816
Wouldn't this replace the database session... not the packaging session?
On Thu, May 14, 2015 at 11:10 AM, matt m...@nycresistor.com wrote:
A worthwhile discussion. But are we talking about this as it relates to
packaging or as a separate track related to the architectural and
procedural
If anyone from Canonical here who maintains ubuntu-cloud.archive.canonical,
I can see the patch for CVE-2015-3456 updated to qemu-kvm package on
Precise - Icehouse branch.
https://launchpad.net/~ubuntu-cloud-archive/+archive/ubuntu/icehouse-staging/+build/7425816
But, on precise-havana it is not
Hi all,
I'm using Juno and ocasionally see this kind of errors when I reboot one of
my rabbit nodes:
*MessagingTimeout: Timed out waiting for a reply to message ID
e95d4245da064c779be2648afca8cdc0*
I use ha queues in my openstack services:
*rabbit_hosts=192.168.113.206:5672
If you're using Rabbit 3.x you need to enable HA queues via policy on the
rabbit server side.
Something like this:
rabbitmqctl set_policy ha-all
'{ha-mode:all,ha-sync-mode:automatic}'
Obviously, tailor it to your own needs :-)
We've also seen issues with TCP_RETRIES2 needing to be turned way
Hi Kevin,
thank you for reply, I'm using rabbitmqctl set_policy HA '^(?!amq\.).*'
'{ha-mode: all}'
I will test with ha-sync-mode:automatic' and net.ipv4.tcp_retries2=5
Regards,
Pedro Sousa
On Thu, May 14, 2015 at 4:29 PM, Kevin Bringard (kevinbri)
kevin...@cisco.com wrote:
If you're
Hi everyone,
Rally team is happy to announce that we have just cut the new release 0.0.4!
*Release stats:*
- Commits: *87*
- Bug fixes: *21*
- New scenarios: *14*
- New contexts: *2*
- New SLA: *1*
- Dev cycle: *30 days*
- Release date: *14/May/2015*
*New features:*
-
On 5/14/15, 9:45 AM, Pedro Sousa pgso...@gmail.com wrote:
Hi Kevin,
thank you for reply, I'm using rabbitmqctl set_policy HA '^(?!amq\.).*'
'{ha-mode: all}'
I will test with ha-sync-mode:automatic' and net.ipv4.tcp_retries2=5
I don't know that you need to ha-sync-mode to automatic (I was
that makes more sense to me.
On Thu, May 14, 2015 at 12:13 PM, Matt Kassawara mkassaw...@gmail.com
wrote:
Wouldn't this replace the database session... not the packaging session?
On Thu, May 14, 2015 at 11:10 AM, matt m...@nycresistor.com wrote:
A worthwhile discussion. But are we talking
On 15 May 2015 at 07:15, Anne Gentle annegen...@justwriteclick.com wrote:
In response to the feedback during elections, the Technical Committee now
has a subteam dedicated to communications. Below is a link to the first post
in our revitalized series. As always, we're here for you and listening
On May 14, 2015, at 1:21 AM, aishwarya.adyanth...@accenture.com wrote:
Hi J,
I ran the command 'knife node list' and found the list to be empty while the
'knife client list' command displays chef-validator and chef-webui. It seems
like when I was creating the node through knife
On 5/14/2015 2:59 PM, Kris G. Lindgren wrote:
How would this impact someone running juno nova-compute on rhel 6 boxes?
Or installing the python2.7 from SCL and running kilo+ code on rhel6?
For [3] it couldn't we get the exact same information from /proc/cpuinfo?
In response to the feedback during elections, the Technical Committee now
has a subteam dedicated to communications. Below is a link to the first
post in our revitalized series. As always, we're here for you and listening
and adjusting.
Hi all,
I am very pleased to be facilitating the OpenStack Telco Working Group session
at the Vancouver summit. The session is scheduled as a working session on
Wednesday, May 20th @ 9:00 AM in East Building, Room 2/3 More details can be
found on the Liberty Design Summit schedule[0]. Please
Hello,
So if I understand You correct, it is not so dangeorus if I'm using
ibvirt with apparmor and this libvirt is adding apparmor rules for
every qemu process, yes?
--
Best regards / Pozdrawiam
Sławek Kapłoński
sla...@kaplonski.pl
On Wed, May 13, 2015 at 04:01:05PM +0100, Daniel P. Berrange
Thanks Kevin,
If I understood you well, scalability isn't impacted by number of tenants,
but rather by number of ports by network / security group / tenant router;
so, if I have a single giant tenant network with several thousands ports,
perhaps I'll have a problem.
Partitioning the load into
I'm +1 on this. If people want to run Liberty on an old platform, the onus
is on them to figure out how to install the relevant deps on that platform.
- jlk
On Thu, May 14, 2015 at 2:33 PM, Matt Riedemann mrie...@linux.vnet.ibm.com
wrote:
On 5/14/2015 3:35 PM, Matt Riedemann wrote:
On
On Thu, 14 May 2015, Anne Gentle wrote:
In response to the feedback during elections, the Technical Committee now
has a subteam dedicated to communications. Below is a link to the first
post in our revitalized series. As always, we're here for you and listening
and adjusting.
Awesome, thanks
Hi,
I am pleased to announce the general availability of OpenStack 2015.1.0
(aka Kilo) in Debian unstable (aka Sid) and through the official Debian
backports repository for Debian 8.0 (aka Sid).
Debian 8.0 Jessie just released
===
As you may know, Debian 8.0 was
On 5/14/2015 3:35 PM, Matt Riedemann wrote:
On 5/14/2015 2:59 PM, Kris G. Lindgren wrote:
How would this impact someone running juno nova-compute on rhel 6 boxes?
Or installing the python2.7 from SCL and running kilo+ code on rhel6?
For [3] it couldn't we get the exact same information
On Thu, May 14, 2015 at 2:32 PM, Robert Collins robe...@robertcollins.net
wrote:
On 15 May 2015 at 07:15, Anne Gentle annegen...@justwriteclick.com
wrote:
In response to the feedback during elections, the Technical Committee now
has a subteam dedicated to communications. Below is a link to
On 05/14/2015 05:23 PM, Sławek Kapłoński wrote:
Hello,
So if I understand You correct, it is not so dangeorus if I'm using
ibvirt with apparmor and this libvirt is adding apparmor rules for
every qemu process, yes?
You should certainly verify that apparmor rules are enabled for the qemu
Neutron scalability isn't impacted directly by the number of tenants
so that shouldn't matter too much. The following are a few things to
consider.
Number of ports per security group: Every time a member of a security
group (a port) is removed/added or has it's IP changed, a notification
goes out
Yes, correct. Tenants basically are just used as a tag to filter and
restrict API operations.
On May 14, 2015 4:35 PM, Gustavo Randich gustavo.rand...@gmail.com
wrote:
Thanks Kevin,
If I understood you well, scalability isn't impacted by number of tenants,
but rather by number of ports by
On 05/11/2015 11:23 AM, Kevin Benton wrote:
I apologize but I didn't quite follow what the issue was with tenants
allocating networks in your use case, can you elaborate a bit there?
From what it sounded like, it seems like you could define the vlan
range you want the tenants' internal
Again, a conversation that should include the ops list.
On Wed, May 13, 2015 at 6:28 AM, Adrian Otto adrian.o...@rackspace.com
wrote:
Solum uses it in our Vagrant setup. It makes the dev environment perform
very nicely, and is compatible with the Docker containers Solum generates.
Sent
31 matches
Mail list logo
