Hi,
We have submitted the following LBaaS related BPs:
https://blueprints.launchpad.net/neutron/+spec/lbaas-support-routed-service-insertion
https://blueprints.launchpad.net/neutron/+spec/lbaas-lvs-driver
https://blueprints.launchpad.net/neutron/+spec/lbaas-lvs-extra-features
I can't attend the
Hi,
Please find a summary of talks and discussion related to LBaaS for the summit
at:
https://docs.google.com/document/d/1Vjm57lh7PnXDelOy-VxsJkzc8QRiNN368sS11ePs_vA/edit?pli=1#heading=h.6doqijxd389j
I have also added the list bellow to it.
We can review in the meeting today.
Regards,
Hi all,
Climate is growing and time is coming for having a weekly meeting in
between all of us.
There is a huge number of reviews in progress, and at least the first
agenda will be triaging those, making sure they are either coming to
trunk as soon as possible, or splitted into smaller chunks
Hello all,
I noticed, that when I run tests using tox I get some redundant modules
installed to tox virtual environments. At the moment, pep8 specific
requirements (such as pep8, flake8 and so on) are stated in
test-requirements.txt file, which is meant to contain testing specific
modules (nose,
Hi, Swami,
I am also very interested in this topic. we have been looking into this domain
for months, will be happy to share what we have.
Please include me in the discussion loop.
Thanks,
--
Jaesuk Ahn, Ph.D.
Team Leader
Next Generation Cloud Platform Development Project
KT (Korea
Hi Swami
I am interested in this, please keep me in the loop.
/Alan
From: Vasudevan, Swaminathan (PNB Roseville)
[mailto:swaminathan.vasude...@hp.com]
Sent: October-22-13 8:50 PM
To: cloudbengo; Artem Dmytrenko; yong sheng gong (gong...@unitedstack.com);
OpenStack Development Mailing List
Hi Clint,
Thank you! I have few replies/questions in-line.
Cheers,
Patrick
On 10/23/13 8:36 PM, Clint Byrum wrote:
Excerpts from Patrick Petit's message of 2013-10-23 10:58:22 -0700:
Dear Steve and All,
If I may add up on this already busy thread to share our experience with
using Heat in
Sorry, I clicked the 'send' button too quickly.
On 10/24/13 11:54 AM, Patrick Petit wrote:
Hi Clint,
Thank you! I have few replies/questions in-line.
Cheers,
Patrick
On 10/23/13 8:36 PM, Clint Byrum wrote:
Excerpts from Patrick Petit's message of 2013-10-23 10:58:22 -0700:
Dear Steve and All,
On 10/24/2013 03:52 AM, Victor Sergeyev wrote:
Hello all,
I noticed, that when I run tests using tox I get some redundant modules
installed to tox virtual environments. At the moment, pep8 specific
requirements (such as pep8, flake8 and so on) are stated in
test-requirements.txt file, which is
On Wed, Oct 23, 2013 at 4:33 PM, Russell Bryant rbry...@redhat.com wrote:
Greetings,
At the last Nova meeting we started talking about some updates to the
Nova blueprint process for the Icehouse cycle. I had hoped we could
talk about and finalize this in a Nova design summit session on Nova
+1
Le 24/10/2013 09:45, Sylvain Bauza a écrit :
Hi all,
Climate is growing and time is coming for having a weekly meeting in
between all of us.
There is a huge number of reviews in progress, and at least the first
agenda will be triaging those, making sure they are either coming to
trunk as
Hi all,
I want create volume in horizon, but it report error msg.
And I have following action，
1. stop_service tgt
2. mv /etc/init/tgt.conf /etc/init/tgt.conf.disabled
3. restart_service iscsitarget
And /var/log/cinder/* log is:
-
So, we have 2 places for configuration management - database and config file
Config file for tunning all datasource type behavior during installation
and database for all changeable configurations during usage and
administration of Trove installation.
Database usecases:
- update/custom image
-
I put the client code out for review as WIP:
https://review.openstack.org/#/c/53602/
Regards,
PCM (Paul Michali)
MAIL p...@cisco.com
IRC pcm_ (irc.freenode.net)
TW @pmichali
On Oct 23, 2013, at 4:53 PM, Nachi Ueno na...@ntti3.com wrote:
Hi Paul
I rebased the patch, and working on
On 10/24/2013 08:38 AM, Joe Gordon wrote:
Since the beginning of OpenStack we have had vim modelines all over the
codebase, but after seeing this
patch https://review.opeenstack.org/#/c/50891/
https://review.openstack.org/#/c/50891/ I took a further look into vim
modelines and think we
+1 to remove them.
-- dims
On Thu, Oct 24, 2013 at 8:44 AM, Monty Taylor mord...@inaugust.com wrote:
On 10/24/2013 08:38 AM, Joe Gordon wrote:
Since the beginning of OpenStack we have had vim modelines all over the
codebase, but after seeing this
patch
Hi all,
maybe a bit off track with respect to latest concrete discussions, but I
noticed the announcement of project Solum on openstack-dev.
Maybe this is playing on a different level, but I still see some relation
to all the software orchestration we are having. What are your opinions on
this?
Hi Adrian,
really intersting! I wonder what the relation to all the software
orchestration in Heat discussions is that have been going on for a while
now.
Regards,
Thomas
Adrian Otto adrian.o...@rackspace.com wrote on 23.10.2013 21:03:10:
From: Adrian Otto adrian.o...@rackspace.com
To:
On 24/10/13 13:38 +0100, Joe Gordon wrote:
Since the beginning of OpenStack we have had vim modelines all over the
codebase, but after seeing this patch https://review.opeenstack.org/#/c/50891/
I took a further look into vim modelines and think we should remove them.
Before going any further, I
+1 on the topic
How about we catch them in hacking so that they won't ever come back?
On Thu, Oct 24, 2013 at 4:53 PM, Davanum Srinivas dava...@gmail.com wrote:
+1 to remove them.
-- dims
On Thu, Oct 24, 2013 at 8:44 AM, Monty Taylor mord...@inaugust.com
wrote:
On 10/24/2013 08:38
Can you pastebin the full cinder-volume.log please, from the moment
the create RPC comes in until the error (or just the full file if taht
is easier)
On 24 October 2013 13:36, ifzing ifz...@126.com wrote:
Hi all,
I want create volume in horizon, but it report error msg.
And I have following
On 10/24/2013 08:38 AM, Joe Gordon wrote:
Why remove them?
* Modelines aren't supported by default in debian or ubuntu due to
security reasons: https://wiki.python.org/moin/Vim
* Having modelines for vim means if someone wants we should support
modelines for emacs
It seems like adopting 0.1.8 is the right approach. If it doesn't work with
other projects, we should work to help those projects get updated to work
with it.
--Morgan
On Thursday, October 24, 2013, Zhi Yan Liu wrote:
Hi all,
Adopt 0.1.8 as iso8601 minimum version:
+1 and likely this should be added to hacking so they don't sneak back in
by accident / reviewers missing the line since we've had them for do long.
On Thursday, October 24, 2013, Flavio Percoco wrote:
On 24/10/13 13:38 +0100, Joe Gordon wrote:
Since the beginning of OpenStack we have had vim
In the last meeting we discussed an idea that I think is worth trying at
least for icehouse-1 to see if we like it or not. The idea is that
*every* blueprint starts out at a Low priority, which means best
effort, but no promises. For a blueprint to get prioritized higher, it
should have 2
Hi,
Currently in LBaaS when health monitor object is deleted all associations
with pools are deleted automatically. A bug was reported recently in
Neutron where the reporter considers this behavior as wrong:
https://bugs.launchpad.net/neutron/+bug/1243129
I have no strong opinion so I'd like to
Hi,
The gate for stable Hanava is broken in Nova with the following error:
==
2013-10-24
12:48:35.629http://logs.openstack.org/95/53595/1/check/check-tempest-devstack-vm-full/14c606f/console.html#_2013-10-24_12_48_35_629
|
Example 1:
==
n-conductor log in tempest/devstack -
http://logs.openstack.org/70/52870/3/check/check-tempest-devstack-vm-full/f46b756/logs/screen-n-cond.txt.gz
Total log lines: 84076
Total non DEBUG lines: 61
Question: do we need more than 1 level of
This is your semestrial public service announcement.
This Sunday a large chunk of the world will drop DST, while most
countries in North America will not (until November 3). This generally
results in widespread confusion and chaos until things settle a few
weeks later.
Remember *our meetings are
On Thu, Oct 24, 2013 at 07:05:19AM -0700, Dan Smith wrote:
Some of them are not useful to me (but might be to others), like the
amqp channel lines. However, everything else has been pretty crucial at
one point or another when debugging issues that span between the two
tightly-coupled services.
Yep, that was the feature I was referring to.
As I said I don't have anything defiant that shows this to be not working (and
the code looks fine) - just wanted to try and simplify the world a bit for a
while.
-Original Message-
From: Melanie Witt [mailto:melw...@yahoo-inc.com]
Sent:
This is a quite interest findings. so If we use httplib, this won't happen?
That's my understanding. It also looks like you might be able to configure
the retrys in later versions of httplib2
-Original Message-
From: Nachi Ueno [mailto:na...@ntti3.com]
Sent: 24 October 2013 00:38
To:
Hey folks!
I'm totally excited to present to you a proposal of OpenStack Diagnostics
project (codenamed Rubick).
This project aims to provide a simple and convenient tool (or few tools)
for OpenStack cloud operator to inspect and validate a consistency and
correctness of configuration of their
On Thu, Oct 24, 2013 at 3:24 PM, Lars Kellogg-Stedman l...@redhat.comwrote:
On Thu, Oct 24, 2013 at 07:05:19AM -0700, Dan Smith wrote:
Some of them are not useful to me (but might be to others), like the
amqp channel lines. However, everything else has been pretty crucial at
one point or
On 10/24/13 4:46 PM, Dan Smith d...@danplanet.com wrote:
In the last meeting we discussed an idea that I think is worth trying at
least for icehouse-1 to see if we like it or not. The idea is that
*every* blueprint starts out at a Low priority, which means best
effort, but no promises.
On 10/24/2013 08:51 AM, Thomas Spatzier wrote:
Hi Adrian,
really intersting! I wonder what the relation to all the software
orchestration in Heat discussions is that have been going on for a while
now.
It's a good question. Personally, I would expect Heat to be a key
element of how Solum
On 10/24/2013 07:43 AM, Joe Gordon wrote:
On Wed, Oct 23, 2013 at 4:33 PM, Russell Bryant rbry...@redhat.com
mailto:rbry...@redhat.com wrote:
Here is a first cut at the process. Let me know what you think is
missing or should change. I'll get the result of this thread posted on
On 10/24/2013 10:05 AM, Dan Smith wrote:
Example 1:
==
n-conductor log in tempest/devstack -
http://logs.openstack.org/70/52870/3/check/check-tempest-devstack-vm-full/f46b756/logs/screen-n-cond.txt.gz
Total log lines: 84076
Total non DEBUG lines: 61
Question:
On 10/24/2013 10:52 AM, Gary Kotton wrote:
On 10/24/13 4:46 PM, Dan Smith d...@danplanet.com wrote:
In the last meeting we discussed an idea that I think is worth trying at
least for icehouse-1 to see if we like it or not. The idea is that
*every* blueprint starts out at a Low priority,
If we had DEBUG and DEBUG2 levels, where one of them would only be seen
at the higher debug level, would that be useful?
I'm fine with not seeing those for devstack runs, yeah.
--Dan
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
+1
On Thu, Oct 24, 2013 at 5:43 PM, Nikolay Starodubtsev
nstarodubt...@mirantis.com wrote:
+1, but we need to wait for Dina. She has more problems with schedule than
me
Nikolay Starodubtsev
Software Engineer
Mirantis Inc.
Skype: dark_harlequine1
On Thu, Oct 24, 2013 at 4:11 PM,
On 10/24/13 at 11:07am, Russell Bryant wrote:
On 10/24/2013 10:52 AM, Gary Kotton wrote:
On 10/24/13 4:46 PM, Dan Smith d...@danplanet.com wrote:
In the last meeting we discussed an idea that I think is worth trying at
least for icehouse-1 to see if we like it or not. The idea is that
+1
On Thu, Oct 24, 2013 at 5:43 PM, Nikolay Starodubtsev
nstarodubt...@mirantis.com wrote:
+1, but we need to wait for Dina. She has more problems with schedule than
me
Nikolay Starodubtsev
Software Engineer
Mirantis Inc.
Skype: dark_harlequine1
On Thu, Oct 24, 2013 at 4:11 PM,
On 10/24/2013 11:00 AM, Sean Dague wrote:
On 10/24/2013 10:05 AM, Dan Smith wrote:
Example 1:
==
n-conductor log in tempest/devstack -
http://logs.openstack.org/70/52870/3/check/check-tempest-devstack-vm-full/f46b756/logs/screen-n-cond.txt.gz
Total log lines: 84076
Russell Bryant wrote:
At the last Nova meeting we started talking about some updates to the
Nova blueprint process for the Icehouse cycle. I had hoped we could
talk about and finalize this in a Nova design summit session on Nova
Project Structure and Process [1], but I think we need to push
Cool. All the core devs gave a go, let's begin with Mondays 1000 UTC on
#openstack-meeting
I modified the Meetings wikipage [1] and created a wikipage for our own
agenda [2]
[1] : https://wiki.openstack.org/wiki/Meetings
[2] : https://wiki.openstack.org/wiki/Meetings/Climate
Thanks,
On a previous project, I wrote a library that provided a command-line
option to set the logging levels for different loggers. This was handy for
developers and for support. An example translated to Keystone would be like
keystone-all --logging=keystone.identity=DEBUG
Now the keystone.identity
So if we decide to support any number of config options for each various
datastore version, eventually we'll have large config files that will be hard
to manage.
What about storing the extra config info for each datastore version in its own
independent config file? So rather than having one
I am 1% behind that idea. It makes things easier to manage.
On Thu, Oct 24, 2013 at 10:44 AM, Tim Simpson tim.simp...@rackspace.comwrote:
So if we decide to support any number of config options for each various
datastore version, eventually we'll have large config files that will be
Hi all,
The [state-management] project team holds a weekly meeting in
#openstack-meeting on thursdays, 2000 UTC. The next meeting is today,
2013-10-24!!!
As usual, everyone is welcome :-)
Link: https://wiki.openstack.org/wiki/Meetings/StateManagement
Taskflow:
On Wed, Oct 23, at 7:35 am, Sylvain Afchain sylvain.afch...@enovance.com
wrote:
I'm interested as well. On our side we are working on this BP
https://blueprints.launchpad.net/neutron/+spec/l3-high-availability
And might be good to revisit the Multi-host DHCP and L3 blueprint
On 10/24/2013 11:46 AM, Brant Knudson wrote:
On a previous project, I wrote a library that provided a command-line
option to set the logging levels for different loggers. This was handy
for developers and for support. An example translated to Keystone would
be like
keystone-all
On 10/24/2013 11:32 AM, Thierry Carrez wrote:
Russell Bryant wrote:
At the last Nova meeting we started talking about some updates to the
Nova blueprint process for the Icehouse cycle. I had hoped we could
talk about and finalize this in a Nova design summit session on Nova
Project Structure
I guess I get to buck the trend :).
On 25 October 2013 01:38, Joe Gordon joe.gord...@gmail.com wrote:
Since the beginning of OpenStack we have had vim modelines all over the
codebase, but after seeing this patch
https://review.opeenstack.org/#/c/50891/ I took a further look into vim
modelines
Hi,
I've registered a BP for L3 router service integration with service
framework.
https://blueprints.launchpad.net/neutron/+spec/l3-router-service-type
In general, the implementation will align with how LBaaS is integrated with
the framework. One consideration we heard from several team
This is being tracked in bug
https://bugs.launchpad.net/tempest/+bug/1244055and a fix is working
its way through the gate now (
https://review.openstack.org/#/c/53699/)
On Thu, Oct 24, 2013 at 2:51 PM, Gary Kotton gkot...@vmware.com wrote:
Hi,
The gate for stable Hanava is broken in Nova with
Thanks for doing this.
Gary
From: Joe Gordon joe.gord...@gmail.commailto:joe.gord...@gmail.com
Reply-To: OpenStack Development Mailing List
openstack-dev@lists.openstack.orgmailto:openstack-dev@lists.openstack.org
Date: Thursday, October 24, 2013 9:48 PM
To: OpenStack Development Mailing List
On 24 October 2013 04:33, Russell Bryant rbry...@redhat.com wrote:
Greetings,
At the last Nova meeting we started talking about some updates to the
Nova blueprint process for the Icehouse cycle. I had hoped we could
talk about and finalize this in a Nova design summit session on Nova
Thanks all for the information!
Floren
2013/10/21 Thierry Carrez thie...@openstack.org:
Dolph Mathews wrote:
On Sun, Oct 20, 2013 at 1:31 PM, Edgar Magana emag...@plumgrid.com
mailto:emag...@plumgrid.com wrote:
Just just need to send a patch to gerrit.
From you local repo, do the
Hi Raja,
I'm sorry, I haven't careated documents yet. When I create, I'll share you.
Thanks,
Toshi
On Wed, Oct 23, 2013 at 6:39 AM, Raja Srinivasan
raja.sriniva...@riverbed.com wrote:
Hi Toshi
If you have some documentation on the demo, please share it.
Thanks Regards
Raja Srinivasan
-2 to 10 minute downtimes.
+1 to doing the evolution gracefully. There is a spec for doing that
from the H summit; someone just needs to implement it.
-Rob
On 25 October 2013 09:30, Michael Still mi...@stillhq.com wrote:
Hi.
Because I am a grumpy old man I have just -2'ed
Hi,
1) If you have 30 million instance it means that you have 300 million
instance_system_metadata records
All these records will be downloaded every 6 seconds (in periodic tasks) to
compute_nodes = which means that OpenStack on scale out of box doesn't
work.
If you have 3 million instance the
On Oct 24, 2013, at 7:47 AM, Day, Phil philip@hp.com wrote:
Yep, that was the feature I was referring to.
As I said I don't have anything defiant that shows this to be not working
(and the code looks fine) - just wanted to try and simplify the world a bit
for a while.
Of course.
Folks,
We’ve been discussing Marconi’s storage sharding architecture over the past
couple of weeks and I took some time today to draw up our current thinking on
the design. I’ve also added this link to the blueprint.
http://grab.by/rsoI
I’d like to get the team’s thoughts on this and get the
On Fri, Oct 25, 2013, Michael Still mi...@stillhq.com wrote:
Because I am a grumpy old man I have just -2'ed
https://review.openstack.org/#/c/39685/ and I wanted to explain my
rationale. Mostly I am hoping for a consensus to form -- if I am wrong
then I'll happy remove my vote from this patch.
On 10/24/2013 04:40 PM, Boris Pavlovic wrote:
Hi,
1) If you have 30 million instance it means that you have 300 million
instance_system_metadata records
All these records will be downloaded every 6 seconds (in periodic tasks)
to compute_nodes = which means that OpenStack on scale out of box
On Fri, Oct 25, 2013 at 8:19 AM, Johannes Erdfelt johan...@erdfelt.com wrote:
On Fri, Oct 25, 2013, Michael Still mi...@stillhq.com wrote:
However, when I run it with medium sized (30 million instances)
databases, the change does cause a 10 minute downtime. I don't
personally think the change
This is good discussion.
+1 for using Neutron ports for defining zones. I see Kaiwei's point but for
DELL, neutron ports makes more sense.
I am not sure if I completely understood the bump-in-the-wire/zone
discussion. DELL security appliance allows using different zones with
bump-in-the-wire. If
On Fri, Oct 25, 2013, Michael Still mi...@stillhq.com wrote:
On Fri, Oct 25, 2013 at 8:19 AM, Johannes Erdfelt johan...@erdfelt.com
wrote:
On Fri, Oct 25, 2013, Michael Still mi...@stillhq.com wrote:
However, when I run it with medium sized (30 million instances)
databases, the change
On 25 October 2013 10:04, Chris Behrens cbehr...@codestud.com wrote:
On Oct 24, 2013, at 1:33 PM, Robert Collins robe...@robertcollins.net wrote:
-2 to 10 minute downtimes.
+1 to doing the evolution gracefully. There is a spec for doing that
from the H summit; someone just needs to
Johannes,
+1, purging should help here a lot.
Best regards,
Boris Pavlovic
On Fri, Oct 25, 2013 at 2:01 AM, Johannes Erdfelt johan...@erdfelt.comwrote:
On Fri, Oct 25, 2013, Michael Still mi...@stillhq.com wrote:
On Fri, Oct 25, 2013 at 8:19 AM, Johannes Erdfelt johan...@erdfelt.com
Hi,
We are going to implement 2-arm type lbaas using LVS, and have submitted
the following BPs.
https://blueprints.launchpad.net/neutron/+spec/lbaas-support-routed-service-insertion
https://blueprints.launchpad.net/neutron/+spec/lbaas-lvs-driver
Is this really a viable solution?
I believe its more democratic to ensure everyone gets a chance to present the
blueprint someone has spent time to write. This was no favoritism or biased
view will ever take place and we let the community gauge the interest.
/Alan
-Original Message-
On Fri, Oct 25, 2013 at 9:07 AM, Boris Pavlovic bo...@pavlovic.me wrote:
Johannes,
+1, purging should help here a lot.
Sure, but my point is more:
- pruning isn't done by the system automatically, so we have to
assume it never happens
- we need to have a clearer consensus about what we
Hi,
We encounter the following error in our lab when we auto allocate the VIP IP
Address for create_vip API.
==
ERROR: quantumclient.shell Unable to complete operation for network
On Thu, Oct 24, 2013 at 3:06 PM, Robert Collins
robe...@robertcollins.netwrote:
On 25 October 2013 10:04, Chris Behrens cbehr...@codestud.com wrote:
On Oct 24, 2013, at 1:33 PM, Robert Collins robe...@robertcollins.net
wrote:
-2 to 10 minute downtimes.
+1 to doing the evolution
Michael,
- pruning isn't done by the system automatically, so we have to assume
it never happens
We are working around it
https://blueprints.launchpad.net/nova/+spec/db-purge-engine
- we need to have a clearer consensus about what we think the maximum
size of a nova deployment is. Are
Hi, Oda-san,
Thanks for your response.
L3 agent function should remain the same, as one driver implementation of
L3 router plugin.
My understanding is your lbaas driver can be running on top of L3 agent and
LVS' own routing services. Is my understanding correct?
Thanks,
Gary
On Thu, Oct 24,
Gary,
In the context of the nvp plugin we use a mechanism for enabling 'advanced'
capabilities of a router leveraging a 'router_service_type' extension.
this allow us to configure two types of routers, one which does just L3
forwarding, NAT and a few other things, and another one which also has
Hi Gray,
Thanks for your response.
Our plan is as follows:
* LVS driver is one of lbaas provider driver.
It communicates with l3_agent instead of lbaas_agent.
* For l3_agent side, I think the implementation is same as
fwaas. L3NATAgent inherits like LVSL3AgentRpcCallback
class added which
I’m getting a “Not allowed here” error when I click through to the BP. (Yes,
I’m subscribed.)
On Oct 24, 2013, at 11:56 AM, Gary Duan gd...@varmour.com wrote:
Hi,
I've registered a BP for L3 router service integration with service framework.
Hi all,
I'd like to nominate Lucas Gomes for ironic-core. He's been consistently
doing reviews for several months and has led a lot of the effort on the API
and client libraries.
Thanks for the great work!
-Deva
http://russellbryant.net/openstack-stats/ironic-reviewers-90.txt
Hi Thomas, here's my opinion: Heat and Solum contributors will work
closely together to figure out where specific feature implementations
belong... But, in general, Solum is working at a level above Heat. To
write a Heat template, you have to know about infrastructure setup and
configuration
Hi, Geoff,
This is because I haven't added spec to the BP yet.
Gary
On Thu, Oct 24, 2013 at 4:51 PM, Geoff Arnold ge...@geoffarnold.com wrote:
I’m getting a *“**Not allowed here”* error when I click through to the
BP. (Yes, I’m subscribed.)
On Oct 24, 2013, at 11:56 AM, Gary Duan
So, I observe a consensus here of long migrations suckm +1 to that.
I also observe a consensus that we need to get no-downtime schema changes
working. It seems super important. Also +1 to that.
Getting back to the original review, it got -2'd because Michael would like
to make sure that the
On 24/10/13 11:54 +0200, Patrick Petit wrote:
Hi Clint,
Thank you! I have few replies/questions in-line.
Cheers,
Patrick
On 10/23/13 8:36 PM, Clint Byrum wrote:
Excerpts from Patrick Petit's message of 2013-10-23 10:58:22 -0700:
Dear Steve and All,
If I may add up on this already busy thread
Done!
In https://github.com/mseknibilel/OpenStack-Grizzly-Install-Guide/issues/89
this page, I meet the problem is same to this guys.
its because --tid=1 for ietadm allready exists. delete the new created volume
with status error and type via console the following command:
ietadm --op delete
Thanks everyone who have joined Savanna meeting.
Here are the logs from the meeting:
Minutes:
http://eavesdrop.openstack.org/meetings/savanna/2013/savanna.2013-10-24-18.05.html
Minutes (text):
http://eavesdrop.openstack.org/meetings/savanna/2013/savanna.2013-10-24-18.05.txt
Log:
On 10/24/2013 05:19 PM, Johannes Erdfelt wrote:
On Fri, Oct 25, 2013, Michael Still mi...@stillhq.com wrote:
Because I am a grumpy old man I have just -2'ed
https://review.openstack.org/#/c/39685/ and I wanted to explain my
rationale. Mostly I am hoping for a consensus to form -- if I am
Hello Savanna team,
I've just skimmed through the online documentation and I'm very interested in
this project. We have a grizzly environment with all the latest patches as well
as several Havana backports applied. We are are doing bare metal provisioning
through Nova. It is limited to flat
Thomas and Russell,
On Oct 24, 2013, at 8:03 AM, Russell Bryant rbry...@redhat.com wrote:
On 10/24/2013 08:51 AM, Thomas Spatzier wrote:
Hi Adrian,
really intersting! I wonder what the relation to all the software
orchestration in Heat discussions is that have been going on for a while
On Oct 23, 2013, at 7:03 AM, Illia Khudoshyn wrote:
Hi Denis, Michael, Vipul and all,
I noticed a discussion in irc about adding a single entry point (sort of
'SuperManager') to the guestagent. Let me add my 5cent.
I agree with that we would ultimately avoid code duplication. But from
The bump-in-the-wire mode we were referring to here is the one where the
firewall has both legs on the same subnet/network. The point that was
trying to be made was that applying zones in that case would not make as
much sense. At this point there is no proposal though to validate and
restrict
93 matches
Mail list logo
