Though we can add multiple subnets to the Network. We don't have an option to
attach/select subnet to Network. It is observed that when all the IP Address
are consumed from first subnet, then it starts using the next subnet available
for the network.
More flexibility in selecting subnet to
Hi,
On 14/08/13 21:12, Lorin Hochstein wrote:
Here's a neutron implementation question: why does neutron model
network and subnet as separate entities?
Or, to ask another way, are there are any practical use cases where you
would *not* have a one-to-one relationship between neutron networks
On 15/08/2013, at 3:02 AM, Jay Pipes jaypi...@gmail.com wrote:
On 08/14/2013 12:25 PM, Mac Innes, Kiall wrote:
So, Are we saying that UIs built on OpenStack APIs shouldn't be able to
show traditional pagination controls? Or am I missing how this should
work with marker/limit?
No, not
Hi, all.
Currently, there is only one pid running for neutron-server. It's not
enough to handle the requests when undering lots of API access. So multiple
workers for neutron-server are urgrent necessary.
Please refer to
https://blueprints.launchpad.net/neutron/+spec/multi-workers-for-api-server
Hi Konglingxian
1. evacuate
- Nova user request for evacuate operation manually.
- Evacuate call rebuild method in compute
2. auto-ha
- All operation is doing automatically.
- Only role of administrator is register auto-ha-hosts, fixing broken
host, restoring migrated vm.
- auto-ha call
That's an interesting article and also meaningful for coders. If I have a
patch more than 200 or 300 lines, to split this may be a good idea.
Some time, an easy patch with a little more lines would prevent more
reviewers to think about it.
On Thu, Aug 15, 2013 at 10:12 AM, Robert Collins
On Thu, Aug 15, 2013 at 7:12 AM, Christopher Yeoh cbky...@gmail.com wrote:
On Thu, Aug 15, 2013 at 11:42 AM, Robert Collins
robe...@robertcollins.net wrote:
This may interest data-driven types here.
https://www.ibm.com/developerworks/rational/library/11-proven-practices-for-peer-review/
On Thu, Aug 15, 2013 at 9:54 PM, Daniel P. Berrange
berra...@redhat.comwrote:Commit message quality has improved
somewhat since I first wrote
published
that page, but there's definitely still scope to improve things further.
What
it really needs is for more reviewers to push back against
On Thu, Aug 15, 2013 at 7:57 AM, Christopher Yeoh cbky...@gmail.com wrote:
On Thu, Aug 15, 2013 at 9:54 PM, Daniel P. Berrange
berra...@redhat.comwrote:Commit message quality has improved somewhat since
I first wrote
published
that page, but there's definitely still scope to improve
On Thu, Aug 15, 2013 at 09:46:07AM -0500, Dolph Mathews wrote:
On Thu, Aug 15, 2013 at 7:57 AM, Christopher Yeoh cbky...@gmail.com wrote:
On Thu, Aug 15, 2013 at 9:54 PM, Daniel P. Berrange
berra...@redhat.comwrote:Commit message quality has improved somewhat
since I first wrote
On Thu, Aug 15, 2013 at 9:56 AM, Daniel P. Berrange berra...@redhat.comwrote:
On Thu, Aug 15, 2013 at 09:46:07AM -0500, Dolph Mathews wrote:
On Thu, Aug 15, 2013 at 7:57 AM, Christopher Yeoh cbky...@gmail.com
wrote:
On Thu, Aug 15, 2013 at 9:54 PM, Daniel P. Berrange
Hi folks,
We'll be have the Savanna team meeting today as usual in #openstack-meeting-alt
channel.
Agenda:
https://wiki.openstack.org/wiki/Meetings/SavannaAgenda#Agenda_for_August.2C_15
http://www.timeanddate.com/worldclock/fixedtime.html?msg=Savanna+Meetingiso=20130815T18
Sincerely yours,
I don't know any actual numbers but I would have the concern that images tend
to stick around longer than instances. For example, if someone takes daily
snapshots of their server and keeps them around for a long time, the number of
exists events would go up and up.
Just a thought, could be a
Recently I've been focused on ensuring we don't drop notifications in
CM. But problems still exist downstream, after we've captured the raw
event.
From the efforts going on with the Ceilometer sample pipeline, the new
dispatcher model and the upcoming trigger pipeline, the discussion
around retry
I updated the implementation section of
https://wiki.openstack.org/wiki/Heat/Blueprints/as-update-policy on instance
naming to support UpdatePolicy where in the case of the LaunchConfiguration
change, all the instances need to be replaced and to support
MinInstancesInService, the handle_update
On Thu, Aug 15, 2013 at 12:00 PM, Mark Washenberger
mark.washenber...@markwash.net wrote:
On Thu, Aug 15, 2013 at 5:12 AM, Christopher Yeoh cbky...@gmail.comwrote:
On Thu, Aug 15, 2013 at 11:42 AM, Robert Collins
robe...@robertcollins.net wrote:
This may interest data-driven types
On 08/15/2013 02:00 PM, Eric Windisch wrote:
On Wed, Aug 14, 2013 at 4:08 PM, Sandy Walsh sandy.wa...@rackspace.com
wrote:
At Eric's request in https://review.openstack.org/#/c/41979/ I'm
bringing this to the ML for feedback.
Thank you Sandy.
Currently, oslo-common rpc behaviour is to
On Aug 13, 2013, at 3:35 PM, Melanie Witt wrote:
On Aug 13, 2013, at 2:11 AM, Day, Phil wrote:
If we really want to get clean separation between Nova and Neutron in the V3
API should we consider making the Nov aV3 API only accept lists o port ids
in the server create command ?
That way
I like to take a different approach. If my commit message is going to take more
than a couple lines for people to understand the decisions I made, I go and
make an issue in the issue tracker before committing locally and then reference
that issue in the commit message. This helps in a few ways:
Hi All,
Hacking 0.7 has just been released, and merged into openstack/requirements (
https://review.openstack.org/#/c/41523/), due to a bug in hacking 0.6 that
made H202, 'assertRaises Exception too broad', not work (
https://bugs.launchpad.net/hacking/+bug/1206302).
Additionally Hacking 0.7
Mark,
As you suggested, I've created a single blueprint :
https://blueprints.launchpad.net/glance/+spec/export-import-image-metadata-ovf
I don't have any idea about its dependencies, maybe could you fix the
blueprint if needed.
I think you can also delete :
Wrong copy paste, sorry.
We can delete :
https://blueprints.launchpad.net/glance/+spec/api-v2-export-properties
https://blueprints.launchpad.net/glance/+spec/api-v2-import-properties
Thank's,
Emilien Macchi
# OpenStack Engineer
// eNovance
*Introduction and Requirements*
So there's kind of a perfect storm happening around autoscaling in Heat
right now. It's making it really hard to figure out how I should compose
this email. There are a lot of different requirements, a lot of different
cool ideas, and a lot of projects that want to
Updated every project to the latest. but each time i ran devstack, the
exercise test failed at the same place bundle.sh
Any hints?
In console.log
Uploaded image as testbucket/bundle.img.manifest.xml
++ euca-register testbucket/bundle.img.manifest.xml
++ cut -f2
+ AMI='S3ResponseError: Unknown
On Aug 15, 2013, at 1:13 PM, Joe Gordon wrote:
+1 from me as long as this wouldn't change anything for the EC2 API's
security groups support, which I assume it won't.
Correct, it's unrelated to the ec2 api.
We discussed briefly in the nova meeting today and there was consensus that
removing
25 matches
Mail list logo
