- Original Message -
From: henry hly henry4...@gmail.com
To: OpenStack Development Mailing List (not for usage questions)
openstack-dev@lists.openstack.org
On Fri, Dec 12, 2014 at 11:41 AM, Dan Smith d...@danplanet.com
wrote:
[joehuang] Could you pls. make it more clear for the
On Thu, Dec 11, 2014 at 10:33 PM, Anita Kuno ante...@anteaya.info wrote:
On 12/11/2014 09:36 AM, Jon Bernard wrote:
Heya, quick Ceph CI status update. Once the test_volume_boot_pattern
was marked as skipped, only the revert_resize test was failing. I have
submitted a patch to nova for
In the week since the last email we've had no major CI failures. This makes
it very easy for me to write my first CI report.
There was a brief period where all the Ubuntu tests failed while an update
was rolling out to various mirrors. DerekH worked around this quickly by
dropping in a DNS hack,
Hi Eoghan and folks,
I'm thinking of adding an API to create multiple alarms in a batch.
I think adding an API to create multiple alarms is a good option to solve the
problem that once an *alarm target* (a vm or a new group of vms) is created,
multiple requests will be fired because multiple
- Original Message -
From: Pasquale Porreca pasquale.porr...@dektech.com.au
To: openstack-dev@lists.openstack.org
Well, one of the main reason to choose an open source product is to
avoid vendor lock-in. I think it is not
advisable to embed in the software running in an instance a
On Fri, Dec 12, 2014 at 4:10 PM, Steve Gordon sgor...@redhat.com wrote:
- Original Message -
From: henry hly henry4...@gmail.com
To: OpenStack Development Mailing List (not for usage questions)
openstack-dev@lists.openstack.org
On Fri, Dec 12, 2014 at 11:41 AM, Dan Smith
On Thu, Dec 11, 2014 at 23:05:01, Mathieu Gagné wrote:
When no security group is provided, Nova will default to the default
security group. However due to the fact 2 security groups had the same
name, nova-compute got confused, put the instance in ERROR state and
logged this traceback [1]:
Hi folks,
when i launch instance use cirros image in the new openstack environment(juno
version centos7 OS base), the following piece is error logs from compute node.
anybody meet the same error?
2014-12-12 17:16:52.481 12966 ERROR nova.compute.manager [-]
On Fri, Dec 12, 2014 at 01:21:36PM +0900, Ryu Ishimoto wrote:
On Thu, Dec 11, 2014 at 7:41 PM, Daniel P. Berrange berra...@redhat.com
wrote:
Yes, I really think this is a key point. When we introduced the VIF type
mechanism we never intended for there to be soo many different VIF types
From my point of view it is not advisable to base some functionalities
of the instances on direct calls to Openstack API. This for 2 main
reasons, the first one: if the Openstack code changes (and we know
Openstack code does change) it will be required to change the code of
the software running in
It is possible to decide in advance how many PL will be necessary for a
service, so their creation can be decided externally from the SC. Anyway
the role that any PL should assume and so the image to install on each
PL should be decided by the SC.
On 12/12/14 09:54, Steve Gordon wrote:
-
-Original Message-
From: Zane Bitter [mailto:zbit...@redhat.com]
Sent: Friday, December 12, 2014 6:37 AM
To: openstack-dev@lists.openstack.org
Subject: Re: [openstack-dev] [Heat] Convergence proof-of-concept
showdown
On 11/12/14 08:26, Murugan, Visnusaran wrote:
[Murugan,
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
On 12/12/14 00:05, Mathieu Gagné wrote:
We recently had an issue in production where a user had 2
default security groups (for reasons we have yet to identify).
This is probably the result of the race condition that is discussed in
the thread:
Hi zaneb,
Etherpad updated.
https://etherpad.openstack.org/p/execution-stream-and-aggregator-based-convergence
-Original Message-
From: Murugan, Visnusaran
Sent: Friday, December 12, 2014 4:00 PM
To: OpenStack Development Mailing List (not for usage questions)
Subject: Re:
Hi,
As with 5.1.x, please inform the list if you are rising priority to critical in
any bugs targeted to 6.0.
Regards,
On 09 Dec 2014, at 23:43, Mike Scherbakov mscherba...@mirantis.com wrote:
Hi all,
I'm glad to announce that we've reached Hard Code Freeze (HCF) [1] criteria
for 6.0
Here's an example: Admin user Joe has an Domain open and stares at it for
15 minutes while he updates the description. Admin user Bob is asked to go
ahead and enable it. He opens the record, edits it, and then saves it. Joe
finished perfecting the description and saves it. Doing this action
On 10/12/14 17:23 -0500, Sean Dague wrote:
On 12/10/2014 04:00 PM, Doug Hellmann wrote:
On Dec 10, 2014, at 3:26 PM, Joshua Harlow harlo...@outlook.com wrote:
Hi oslo folks (and others),
I've recently put up a review for some common deprecation patterns:
On Fri, Dec 12, 2014 at 10:46 AM, Daniel P. Berrange
berra...@redhat.com wrote:
On Fri, Dec 12, 2014 at 01:21:36PM +0900, Ryu Ishimoto wrote:
On Thu, Dec 11, 2014 at 7:41 PM, Daniel P. Berrange berra...@redhat.com
wrote:
[..]
Port binding mechanism could vary among different networking
On Fri, Dec 12, 2014 at 03:05:28PM +0100, Maxime Leroy wrote:
On Fri, Dec 12, 2014 at 10:46 AM, Daniel P. Berrange
berra...@redhat.com wrote:
On Fri, Dec 12, 2014 at 01:21:36PM +0900, Ryu Ishimoto wrote:
On Thu, Dec 11, 2014 at 7:41 PM, Daniel P. Berrange berra...@redhat.com
wrote:
[..]
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Reading the latest comments at
https://github.com/PyMySQL/PyMySQL/issues/275, it seems to me that the
issue is not to be solved in drivers themselves but instead in
libraries that arrange connections (sqlalchemy/oslo.db), correct?
Will the proposed
On 12/11/2014 12:55 PM, Andrew Laski wrote:
Cells can handle a single API on top of globally distributed DCs. I
have spoken with a group that is doing exactly that. But it requires
that the API is a trusted part of the OpenStack deployments in those
distributed DCs.
And the way the rest of
Guys,
we've done a good job in 6.0. Most of the features were merged before
feature freeze. Our QA were involved in testing even earlier. It was much
better than before.
We had a discussion with Anastasia. There were several bug reports for
features yesterday, far beyond HCF. So we still have a
Hi,
I don't agree with many of your statements but, I would like to
continue discussion about really important topic i.e. UI flow, my
suggestion was to add groups, for plugin in metadata.yaml plugin
developer can have description of the groups which it belongs to:
groups:
- id: storage
Hi,
We are running tempest on icehouse, in our tempest runs, we found that the
below test cases are failing in random iterations but not always.
tempest.api.object_storage.test_account_services.AccountTest.test_update_account_metadata_with_delete_matadata_key[gate,smoke]
On 12/12/2014 03:37 AM, Rao Dingyuan wrote:
Hi Eoghan and folks,
I'm thinking of adding an API to create multiple alarms in a batch.
I think adding an API to create multiple alarms is a good option to solve the
problem that once an *alarm target* (a vm or a new group of vms) is created,
On 12/12/2014 09:50 AM, Russell Bryant wrote:
On 12/11/2014 12:55 PM, Andrew Laski wrote:
Cells can handle a single API on top of globally distributed DCs. I
have spoken with a group that is doing exactly that. But it requires
that the API is a trusted part of the OpenStack deployments in
Thanks everyone for sharing yours opinion! I will create a separate change
with another option that was suggested.
Yes, I'm currently working on this bug
https://bugs.launchpad.net/neutron/+bug/1194579.
On Fri, Dec 12, 2014 at 2:41 PM, Ihar Hrachyshka ihrac...@redhat.com
wrote:
-BEGIN
Not entirely sure why they both exist either.
So by move, you meant override (nuance). That's different and I have no
issue with that.
I'm also fine with attempting to consolidate _conf and _scripts.
David
On Thu, Dec 11, 2014 at 1:22 PM, Thai Q Tran tqt...@us.ibm.com wrote:
It would not
Hi all,
Neutron grenade jobs have been failing since late afternoon Thursday, due to
split fallout. Armando has a fix, and it’s working it’s way through the gate:
https://review.openstack.org/#/c/141256/
Get your rechecks ready!
Thanks,
Doug
From: Douglas Wiegley
This has merged now, FYI.
On Fri, Dec 12, 2014 at 10:28 AM, Doug Wiegley do...@a10networks.com
wrote:
Hi all,
Neutron grenade jobs have been failing since late afternoon Thursday,
due to split fallout. Armando has a fix, and it’s working it’s way through
the gate:
Hi everyone,
I have been reading the etherpad from the Paris summit wrt to moving the
functional tests into their respective projects
(https://etherpad.openstack.org/p/kilo-crossproject-move-func-tests-to-projects).
I am mostly interested this from the nova project
perspective. However, I
On Dec 11, 2014, at 2:27 PM, Sean Dague s...@dague.net wrote:
On 12/11/2014 04:16 PM, Jay Pipes wrote:
On 12/11/2014 04:07 PM, Vishvananda Ishaya wrote:
On Dec 11, 2014, at 1:04 PM, Jay Pipes jaypi...@gmail.com wrote:
On 12/11/2014 04:01 PM, Vishvananda Ishaya wrote:
On Dec 11, 2014, at
In your previous example, you are posting to a certain URL (i.e./keystone/{ver:=x.0}/{method:=update}).client: POST /keystone/{ver:=x.0}/{method:=update} = middleware: just forward to clients[ver].getattr("method")(**kwargs) = keystone: updateCorrect me if I'm wrong, but it looks like you have a
It seems to me that the consensus on keeping the simpler approach -- to
make Bootstrap data-backdrop=static as the default behavior -- has been
reached. Am I right?
On Thu, Dec 4, 2014 at 10:59 PM, Kruithof, Piet pieter.c.kruithof...@hp.com
wrote:
My preference would be “change the default
On Dec 12, 2014, at 9:27 AM, Ihar Hrachyshka ihrac...@redhat.com wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Reading the latest comments at
https://github.com/PyMySQL/PyMySQL/issues/275, it seems to me that the
issue is not to be solved in drivers themselves but instead in
In general, I agree with Jay about the opaqueness of the names. I see
however good reasons for having user-defined unique attributes (see
Clint's point about idempotency).
A middle ground here could be granting to the users the ability to specify
the resource ID.
A similar proposal was made some
Consolidating them would break it for users that have customization and
extension on the two templates.
-Lin
On Fri, Dec 12, 2014 at 9:20 AM, David Lyle dkly...@gmail.com wrote:
Not entirely sure why they both exist either.
So by move, you meant override (nuance). That's different and I have
On 12/12/2014 11:06 AM, Andrew Laski wrote:
On 12/12/2014 09:50 AM, Russell Bryant wrote:
On 12/11/2014 12:55 PM, Andrew Laski wrote:
Cells can handle a single API on top of globally distributed DCs. I
have spoken with a group that is doing exactly that. But it requires
that the API is a
On Fri, Dec 12, 2014 at 6:50 AM, Russell Bryant rbry...@redhat.com wrote:
On 12/11/2014 12:55 PM, Andrew Laski wrote:
Cells can handle a single API on top of globally distributed DCs. I
have spoken with a group that is doing exactly that. But it requires
that the API is a trusted part of
We have a high priority bug in 6.0:
https://bugs.launchpad.net/fuel/+bug/1401852. Here is the story.
Our openstack services use to send logs in strange format with extra copy
of timestamp and loglevel:
== ./neutron-metadata-agent.log ==
2014-12-12T11:00:30.098105+00:00 info: 2014-12-12
On Fri, Dec 12, 2014 at 1:48 AM, Pasquale Porreca
pasquale.porr...@dektech.com.au wrote:
From my point of view it is not advisable to base some functionalities
of the instances on direct calls to Openstack API. This for 2 main
reasons, the first one: if the Openstack code changes (and we know
As is the case with anything we change, but that should not stop us from making improvements/progress. I would argue that it would make life easier for them since all scripts are now in one place.-Lin Hua Cheng os.lch...@gmail.com wrote: -To: "OpenStack Development Mailing List (not for
On Dec 12, 2014, at 1:16 PM, Mike Bayer mba...@redhat.com wrote:
On Dec 12, 2014, at 9:27 AM, Ihar Hrachyshka ihrac...@redhat.com wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Reading the latest comments at
https://github.com/PyMySQL/PyMySQL/issues/275, it seems to me that
If we allow resource IDs to be set they will no longer be globally unique.
I'm not sure if this will impact anything directly right now, but it might
be something that impacts tools orchestrating multiple neutron deployments
(e.g. cascading, cells, etc).
On Fri, Dec 12, 2014 at 10:25 AM, Ivar
On 12/12/2014 03:28 AM, Deepak Shetty wrote:
On Thu, Dec 11, 2014 at 10:33 PM, Anita Kuno ante...@anteaya.info wrote:
On 12/11/2014 09:36 AM, Jon Bernard wrote:
Heya, quick Ceph CI status update. Once the test_volume_boot_pattern
was marked as skipped, only the revert_resize test was
Hi Anton,
it depends on the storage service which you use on this lab.
Tempest tests can fail, for example, if the configuration or your object
storage has some customizations. Also you can change the tempest
configuration to adapt tempest tests for your environment.
On my test OpenStack
Hi,
I would like to use devstack to deploy OpenStack on a multi-node setup,
i.e. separate Controller, Network and Compute nodes
What is the localrc for each node?
I would assume, for example, we don’t need to enable neutron service at the
Controller node, etc…
Does anyone has the localrc file
Hi
We are currently using PATCH in the Poppy API to update existing resources.
However, we have recently had some discussions on how this should have been
implemented.
I would like to get the advise of the Openstack Community and the API working
group on how PATCH semantics should work.
The
I have adapted to Neutron the specs review dashboard prepared by Joe
Gordon for Nova. Check it out below.
Reminder: the deadline to approve kilo specs is this coming Monday, Dec 15.
Renat, Dmitri,
On supplying the global context into the workflow execution...
In addition to Renat's proposal, I have a few here.
1) Pass them implicitly in start_workflow as another kwargs in the
**params. But on thinking, we should probably make global context
explicitly defined in the WF
On Fri, Dec 12, 2014 at 1:03 PM, Danny Choi (dannchoi)
dannc...@cisco.com wrote:
Hi,
I would like to use devstack to deploy OpenStack on a multi-node setup,
i.e. separate Controller, Network and Compute nodes
What is the localrc for each node?
I would assume, for example, we don’t need to
(apologies for my pushiness, but getting all the projects using olso.log for
logging will really help the ops experience)
All projects (except maybe Swift) should be moving to use oslo.logging.
Therefore, your longterm fix is the right way to go. When you find log issues
like the one in
On 12/12/2014 01:35 PM, Dmitry Pyzhov wrote:
We have a high priority bug in 6.0:
https://bugs.launchpad.net/fuel/+bug/1401852. Here is the story.
Our openstack services use to send logs in strange format with extra
copy of timestamp and loglevel:
== ./neutron-metadata-agent.log ==
On 12/12/2014 01:05 PM, Maru Newby wrote:
On Dec 11, 2014, at 2:27 PM, Sean Dague s...@dague.net wrote:
On 12/11/2014 04:16 PM, Jay Pipes wrote:
On 12/11/2014 04:07 PM, Vishvananda Ishaya wrote:
On Dec 11, 2014, at 1:04 PM, Jay Pipes jaypi...@gmail.com wrote:
On 12/11/2014 04:01 PM,
On 2014-12-12 4:40 PM, Sean Dague wrote:
While there is a good case for the UX of unique names - it also makes
orchestration via tools like puppet a heck of a lot simpler - the fact is that
most OpenStack resources do not require unique names. That being the case, why
would we want security
On Friday, December 12, 2014, Sean Dague s...@dague.net wrote:
On 12/12/2014 01:05 PM, Maru Newby wrote:
On Dec 11, 2014, at 2:27 PM, Sean Dague s...@dague.net javascript:;
wrote:
On 12/11/2014 04:16 PM, Jay Pipes wrote:
On 12/11/2014 04:07 PM, Vishvananda Ishaya wrote:
On Dec 11,
On 12/12/2014 05:00 PM, Morgan Fainberg wrote:
On Friday, December 12, 2014, Sean Dague s...@dague.net
mailto:s...@dague.net wrote:
On 12/12/2014 01:05 PM, Maru Newby wrote:
On Dec 11, 2014, at 2:27 PM, Sean Dague s...@dague.net
javascript:; wrote:
On 12/11/2014
On 12/09/2014 03:54 PM, Ken'ichi Ohmichi wrote:
Hi,
This case is always tested by Tempest on the gate.
https://github.com/openstack/tempest/blob/master/tempest/api/compute/servers/test_delete_server.py#L152
So I guess this problem wouldn't happen on the latest version at least.
Thanks
Morgan Fainberg [mailto:morgan.fainb...@gmail.com] on Friday, December 12, 2014
2:01 PM wrote:
On Friday, December 12, 2014, Sean Dague
s...@dague.netmailto:s...@dague.net wrote:
On 12/12/2014 01:05 PM, Maru Newby wrote:
On Dec 11, 2014, at 2:27 PM, Sean Dague s...@dague.netjavascript:;
+1 to stop parsing logs on UI and show them as is. I think it's more
than enough for all users.
On Fri, Dec 12, 2014 at 8:35 PM, Dmitry Pyzhov dpyz...@mirantis.com wrote:
We have a high priority bug in 6.0:
https://bugs.launchpad.net/fuel/+bug/1401852. Here is the story.
Our openstack
Tihomir,
Today I added one glance call based on Richard’s decorator pattern[1] and
started to play with incorporating some of your ideas. Please note, I only had
limited time today. That is passing the kwargs through to the glance client.
This was an interesting first choice, because it
Breaking something for existing user is progress, but not forward. :)
I don't mind moving the code around to _scripts file, but simply dropping
the _conf file is my concern since it might already be extended from.
Perhaps document it first that it will be deprecated, and remove it on
later
Haha, sure I'm willing to make concessions. I'll update the patch to retain the _conf file but it will be blank. This way, we can move forward and not break it for existing users.I'll also document it somewhere in the patch.-Lin Hua Cheng os.lch...@gmail.com wrote: -To: "OpenStack
On 12/12/14 05:29, Murugan, Visnusaran wrote:
-Original Message-
From: Zane Bitter [mailto:zbit...@redhat.com]
Sent: Friday, December 12, 2014 6:37 AM
To: openstack-dev@lists.openstack.org
Subject: Re: [openstack-dev] [Heat] Convergence proof-of-concept
showdown
On 11/12/14 08:26,
Hi everybody,
At some point, our db archiving functionality got broken because there was a
change to stop ever deleting instance system metadata [1]. For those
unfamiliar, the 'nova-manage db archive_deleted_rows' is the thing that moves
all soft-deleted (deleted=nonzero) rows to the shadow
Winson, Lakshmi, Renat:
It looked good and I began to write down the summary:
https://etherpad.openstack.org/p/mistral-global-context
But than realized that it’s not safe to assume from the action, that the global
context will be supplied as part of API call.
Check it out in the etherpad.
Hello, Andrew,
I do consider this to be out of scope for cells, for at least the medium
term as you've said. There is additional complexity in making that a
supported configuration that is not being addressed in the cells
effort. I am just making the statement that this is something cells
Hello, Russell,
Personally, I see the globally distributed
OpenStack under a single API case much more complex, and worth
considering out of scope for the short to medium term, at least.
Thanks for your thougths. Do you mean it could be set in the roadmap, but not a
scope in short or medium
Hi All,
It's great to see the vendor plugin decomposition spec[1] finally getting
merged! Now that the spec is completed, I have a question on how this may
impact neutronclient, and in particular, its handling of vendor extensions.
One of the great things about splitting out the plugins is that
On 12 December 2014 at 22:18, Ryu Ishimoto r...@midokura.com wrote:
Hi All,
It's great to see the vendor plugin decomposition spec[1] finally getting
merged! Now that the spec is completed, I have a question on how this may
impact neutronclient, and in particular, its handling of vendor
Dear neutron community,
Can you please clarify couple points on the vendor code decomposition?
- Assuming I would like to create the new driver now (Kilo development
cycle) - is it already allowed (or mandatory) to follow the new process?
https://review.openstack.org/#/c/134680/
- Assuming the
On Dec 12, 2014, at 10:30, Joe Gordon joe.gord...@gmail.com wrote:
On Fri, Dec 12, 2014 at 6:50 AM, Russell Bryant rbry...@redhat.com wrote:
On 12/11/2014 12:55 PM, Andrew Laski wrote:
Cells can handle a single API on top of globally distributed DCs. I
have spoken with a group that
On 12 December 2014 at 23:01, Yuriy Shovkoplias yshovkopl...@mirantis.com
wrote:
Dear neutron community,
Can you please clarify couple points on the vendor code decomposition?
- Assuming I would like to create the new driver now (Kilo development
cycle) - is it already allowed (or
Ya...got that :)
Thanks Elizabeth.
Regards,
Pradhan
On Thu, Dec 11, 2014 at 12:10 AM, Elizabeth K. Joseph l...@princessleia.com
wrote:
On Tue, Dec 9, 2014 at 11:34 PM, P Pradhan psp0...@gmail.com wrote:
Hi,
We work for Openstack/ironic project.
As we are trying/exploring to try
Hi folks,
when i launch instance use cirros image in the new openstack environment(juno
version centos7 OS base), the following piece is error logs from compute node.
anybody meet the same error?
2014-12-12 17:16:52.481 12966 ERROR nova.compute.manager [-]
Your neutron-server could not bind to socket. This has nothing to do with
sriov. I am wondering how you got aget-list when your neutron-server isn't
listening on 9696. Besides the agent-list does not list
'neutron-sriov-nic-agent'.
I believe your neutron-server is already running and the error
Our compute nodes are using vhost_net, we haven't made any changes to
buffer our NIC.
The system is not over loaded, cpu usage aren't higher than 30%
On 12 December 2014 at 02:35, mad Engineer themadengin...@gmail.com wrote:
so looks like its not the issue with openvswitch,missed is quite
What kernel version are you running on the host?
On Fri, Dec 12, 2014 at 12:09 PM, André Aranha andre.f.ara...@gmail.com wrote:
Our compute nodes are using vhost_net, we haven't made any changes to buffer
our NIC.
The system is not over loaded, cpu usage aren't higher than 30%
On 12 December
78 matches
Mail list logo
